How the order value changes the answer

The chain breaks at the earliest point on the route. The order was placed, money may have moved, and nothing was handed to a warehouse, because there was nothing to hand over. That is the same break as a paid order that never shipped, with a different cause behind it.

Value is what changes the response, and it is worth being blunt about why. No platform has published an order-value rule this site could read, so the two lines used here, 60 and 225, are ours and are labelled as ours. They decide how much chasing an order deserves, not what you are owed.

One thing does not scale with price: the paper trail. A small order and a large one produce the same four facts — what you paid, what you were told, when you were told, and what the seller page says now. Collecting them takes minutes either way.

Below the first threshold

Under 60 paid, the honest advice is to stop treating the item as a project. The chase involves the same steps whatever the amount, and at this size those steps cost more attention than the goods did. Write the row down and move on.

If the item is still wanted, rebuild its source address and check that the listing answers, then order it from a platform whose ledger row is still accepting. That route gets you the goods; a dispute about a closed platform gets you correspondence.

What not to do: do not assume a compensation window exists, and do not treat an unanswered message as a deadline. This site records no refund or return period for any platform, so any figure you have seen for one was written by somebody who did not check it either.

Between the two thresholds

Between 60 and 225, one documented attempt is worth the time. Find the order record, note whether the platform ever confirmed a purchase from the seller, and keep both dates together. One attempt, written down, beats five messages sent from memory.

Which record you hold decides what you can ask. An order that reached a purchase stage shows a failed purchase and a reason; an order that never got that far shows money held against something nobody bought. Those are different rows, and the platform ledger entry for ACBuy, closed on observed behaviour and checked on 29 September 2026, tells you which channels still exist for either one.

Then make the call once: order the item again somewhere that takes rebuilt addresses, or drop it and delete the row. Write the choice and its date beside the order. Deciding once is what stops the same search from restarting every few weeks.

Above the second threshold

Above 225, build a file rather than a memory. It needs five things: the order confirmation, the payment record, the seller listing address, the date the item was reported out of stock, and every message in the order it arrived. One folder, dated, beats a screenshots album you have to search.

Then use every channel that still exists, and let the ledger tell you which those are. It prints a status and a checked date for each platform, and the ACBuy row reads closed on observed behaviour rather than on a company statement. A closed row means no order flow, which turns the chase into paperwork.

Two habits protect a file. Keep copies rather than originals, and re-date it every time you touch it, because a record nobody has opened for three months reads as abandoned. If the item is still wanted, buy the rebuilt source address from a platform whose row is accepting orders today, and check that row’s date before paying.