How to cancel a Kakobuy order: the stage you are in decides the answer

Find your stage before you look for a cancel button

Cancellation is not one action with one answer. It is a label people put on four different situations, and the situation decides who can act: the buying side can stop a purchase before it is placed, the warehouse can stop a parcel before it is packed, and after packing nobody can stop anything, only claim. Find the row that matches your order state, then read that branch only.

One minute of stage detection saves a week of messaging. Open the order record and look for four markers: whether payment to the seller was actually placed, whether an intake scan exists, whether QC photos are published, and whether a parcel record with a label exists.

• No seller payment placed yet: this is the easiest branch, and the shortest.
• Payment placed, no intake scan: the buying side can still attempt a stop.
• Intake scan exists, not packed: a stop is still requestable, with evidence.
• Packed out with a label: cancellation is over; disputes are what remain.

If the intake marker is missing but a week has passed, you are probably in the second branch rather than the first. The [payment for the item stage](/steps/pay-domestic/) covers what a placed payment means for the seller side.

Branch A: the seller payment has not been placed yet

This is the only branch where a request is normally enough on its own. Nothing has been bought on the source marketplace, so there is no seller to convince and no return to negotiate. Ask once, in writing, and ask for a confirmation line rather than a reassurance.

• State the item reference and the word cancel in the first line of the message.
• Ask for a written confirmation that the payment will not be placed.
• Ask what happens to any balance already sitting in your account.
• Keep the reply with its timestamp; it is the whole record for this branch.

Expect a short delay between the request and the last moment a payment can be placed. If a payment slips through anyway, you have moved to branch B, and the reply you kept becomes useful evidence that you asked in time.

Branch B: the payment is placed and the item has not arrived

Here the question changes from cancelling to stopping. A placed payment means the seller has an order, and a seller may already have shipped or may refuse. The realistic outcomes are a seller-side cancellation before dispatch, a refused delivery back to the seller, or, most often, a wait followed by a return once the item reaches the warehouse.

A refusal is not free. If the parcel comes back to the seller and the seller disputes it, the evidence is whatever the carrier recorded, not your message. Write the intent before the delivery, not after it.

Branch C: the item is in the warehouse and unpacked

Cancellation has ended by this point, and a return has taken its place. Returns are judged on evidence rather than on preference, and the strongest evidence you can hold at this stage is a defect visible in the intake material or a mismatch between the listing and the item. The [returns and disputes topic](/table/returns/) sets out which evidence each reason actually rests on.

Send one message with the reference, one reason, and the specific evidence attached. Long explanations about changed plans do not move a return, because the counterparty cannot act on a change of mind. A sizing mismatch, an obvious defect, or a wrong item are all actionable reasons, and the [warehouse intake stage](/steps/warehouse-in/) shows which of them the intake record can support.

1. Check the intake photos and the measured weight and dimensions first.
2. Choose one reason and state it in a single sentence.
3. Attach the picture that shows it; if no picture shows it, say so plainly.
4. Ask what the next step is and when the window closes.

If you intend to keep the item after all, say that too, and withdraw the request in writing. A half-open return request can hold an item in place while a storage clock runs, which costs you time for no benefit.

What it costs when you argue the wrong branch

Three costs show up repeatedly. The first is time: a branch-B stop request answered after the parcel reached the warehouse has wasted the whole transit window and produced nothing. The second is the storage clock, which keeps running while a return is discussed, so an item can accrue days of storage during an argument about a refund.

The third is the packing mistake. Asking to hold an item for a return, then paying freight on the same parcel in a hurry, is how people ship an item they meant to send back. Packing is a separate decision from a return request, and the [payment for freight stage](/steps/pay-freight/) should be read before you commit to either.

Four conditions that quietly block a stop request

A stop request can be perfectly worded and still fail, because of conditions that have nothing to do with the message. Knowing them in advance tells you whether to send the request at all or to go straight to the return branch.

The third row is the one people miss. A merged parcel is a single shipment with a single label, so a stop request aimed at one item inside it has no matching action on the other side. Ask for a split first, and accept that a split reopens the packing and weighing steps for both parts, which can also change the freight figure you were quoted.

The fifth row changes the nature of the request rather than blocking it. Once the intake photos are published, you are no longer asking anyone to prevent something; you are asking them to assess something, and the photo set is the only shared basis you both have. Read it before you write, because a request that contradicts the pictures wastes a full round of messages.

If you already picked the wrong branch, this is the recovery order

1. Write down the current stage from the order record, with the date.
2. Stop the action that is still open, usually packing or freight payment.
3. Restate the request as a return or a claim, using the correct branch language.
4. Attach the evidence that fits the new branch, not the old one.
5. Ask for the deadline in writing and diary it.

The recovery is mostly about language. A return request that reads like a cancellation gets parked, because the person reading it has no cancellation to process. Rewrite the first line to match the branch you are actually in, and keep the rest of the history below it.

For the timing rules on each branch, keep a small list of the dates that matter: intake, packing, freight payment, and the stated end of any claim window. A diary with four dates per order is enough, and it beats recalling a deadline from memory under pressure.

One habit prevents most of this: check the stage before sending the message, every time. The stage is a fact you can read in ten seconds, and it decides everything that follows.