RestocksAIO
Home/Blog/When a marketplace cancels a confirmed sale before you ship
Multi-platform selling

When a marketplace cancels a confirmed sale before you ship

A marketplace can cancel a confirmed sale before you ship. That sale still belongs to one owned unit until you confirm the cancellation and check what happened to its linked listings.

Start from the cancelled sale and the one owned unit

Open the marketplace notice and your inventory record at the same time. Write down the order ID, the style code, the size and the sale date. Find the one owned unit that sale was matched to before you confirmed it.

That unit may still show as sold or reserved in your records. Do not treat live sibling listings as proof the unit is free. Listing count on other sites is not committed quantity. One owned unit can have several linked marketplace listings at once.

If you already made a label, started a payout claim or saved an invoice, those steps do not clear the unit. You restore availability only after a confirmed cancellation or a return you have physically checked. A cancel-before-ship case follows the first path, not the second.

Put the pair back on the shelf while you work. Mark the box with the unit ID so you do not mix it with open orders. This is different from a buyer return. For that path, use the returned-pair checklist instead.

Use this checklist before the unit is available again

Run these steps in order. Each one names the input, what to check and what to do with the result.

  1. Input: the marketplace cancellation notice and the sale line in your records. Check: the order shows cancelled or void on the seller screen, not only in email. Result: if the site still shows an open order, contact marketplace support before you change stock.
  2. Input: the one owned unit tied to that sale. Check: no other confirmed unfulfilled sale still sits on that unit. Result: if another sale is active, stop and resolve the double-sale path first. See the first ten minutes after a double sale.
  3. Input: sibling listings linked to the same unit. Check: each marketplace still shows the listing you expect, or shows it ended when the sale confirmed. Result: if a listing is missing and the unit should be live, republish on that channel. Do not delist valid cross-listings just because one channel cancelled.
  4. Input: any label, pickup booking or proof-of-delivery file you created for the cancelled sale. Check: the carrier or marketplace shows the shipment as void or unused. Result: cancel the pickup or destroy the unused label in your own log. Do not use that paperwork as proof the unit is free.
  5. Input: payout and invoice rows for that sale ID. Check: the payout is reversed, still pending or never started. Result: mark the sale cancelled in your payout log. Create a corrected invoice only if your usual close process needs one.

When every line passes, set the owned unit to available in your master record. Then sync listings if your workflow needs it.

What automation handles and what you check by hand

Supported sale cleanup can remove sibling listings after a confirmed sale. A cancellation may not run the same path in reverse. Open each linked listing by hand and read what the marketplace shows today.

Confirm Sales loads pending orders from supported marketplaces. It does not replace reading a cancellation on the seller portal. Load the sale, read the status there, then update your record.

Auto Delist deletes other marketplace listings when a sale is detected. After a cancel, check whether those listings need to go live again. The app may show still-listed rows in review when a delete failed. Fix those by hand before you call the unit available.

Sales and payout tracking can mark paid or pending on eligible sales. You still confirm the cancellation against the marketplace payout screen. Unmatched rows stay open until you can tie them to a statement line.

Label and invoice tools build documents from sale data. Voiding or deleting a local file does not cancel the marketplace order. Run the checklist first, then clean documents second.

Close the cancel on the same unit record

Write one note on the unit: cancel date, marketplace name and order ID. Keep it with the pair until the next sale ships. That note beats memory when a payout question arrives weeks later.

Log the cancel in the same daily pass you use for sales and payouts. Pair it with your daily operations close so open cancels do not sit beside confirmed orders.

Scan confirmed unfulfilled sales once more before end of day. The cancelled unit should not appear there. Every other open sale should still map to a real box on the shelf.

When the unit is available and sibling listings match your plan, stop. Do not reprice until you have checked the payout floor for that pair. A restored listing is not a reason to chase the lowest ask on every site.

Add restock.gg as a preferred source on Google

Related reading

All articles

Ready to run it like an operation?

7-day Standard trial, or a 3-day Premium setup sprint. Pricing, inventory, listings, documents and analytics in one pane.