Usually feels like
An evening
You put the machine down and come back to it the same day.
Checkout finishing is a minutes wait. Somebody agreeing to the order is a different event with a person inside it, so it does not share that band.
The wait, in plain words
Placing an order is something you do. Accepting it is something a vendor does. The software will hold an order between those two events for as long as it takes, and the screen showing it will not look concerned about the gap.
This catches people out because the checkout felt final. Funds moved into escrow, a reference appeared, the stock count moved. All of that is your half. The other half is a person opening a queue and deciding whether they can fill what you asked for.
There is nothing to watch. The status changes when somebody changes it, and they are not doing that while you look at it. Checking once tomorrow gives you the same answer as refreshing all evening, at a much better price.
Underneath, while nothing moves
An order in this state is a row with a status on it. The vendor side shows a queue of those rows, and working the queue is a sitting, the same as messages are a sitting. Between sittings, rows pile up. Yours is somewhere in the pile, and the pile gets picked up when the person picks it up.
Accepting is not a formality. A vendor is checking that they can actually fill the order: that stock matches the listing, that the destination is one they work with, that nothing about it is unusual enough to want a message first. An order accepted without those checks is worse for you than one that waits, because it becomes a problem later instead of a decision now.
The gap you are experiencing is therefore made of two invisible numbers: how often that person sits down, and how many rows were ahead of yours. Neither is on your screen. What is on your screen is elapsed time, which is why elapsed time gets read for meaning it does not carry.
One thing does run in the background. The escrow clock generally starts somewhere in this process rather than at the moment of acceptance, so an order sitting unaccepted is not necessarily an order with all of its time still in front of it. Escrow running down to auto release takes that clock on its own terms.
Behaving, and not behaving
An ordinary gap and a gap worth acting on are separated less by length than by what has passed through the middle of them.
A gap that means nothing
The order went in during the evening and is still unaccepted at bedtime. Vendors sleep. This is the most ordinary state an order can be in and it should not cost you a single thought.
Or it went in on a Friday and is unaccepted on a Saturday. Weekends are days off in most of the places people live, and a shop is still a job.
A gap that has started to mean something
A whole weekend has passed, the queue was clearly worked at some point inside it, and other things about the shop moved while your row did not. Same silence, different reading.
Or the listing you bought came down while your order sat. That is worth one short message, not a ticket. If the message also goes unanswered, you are in a vendor gone quiet.
The reason overnight is unremarkable and a weekend is not is that a night contains no working time at all, while a weekend contains at least one plausible sitting. Once you can reasonably assume the queue was opened and your row was passed over, the silence stops being about schedule and starts being about the order itself.
Even then the move is a message, not a ticket. Support cannot accept an order on a vendor's behalf, so opening a support ticket at this stage stacks one wait on top of another and answers neither.
It also helps to remember what acceptance is worth. It is a person putting their name against filling your order, which is a small commitment but a real one. A shop that accepts everything the moment it arrives has told you nothing by accepting yours, and a shop that reads before agreeing has told you something. The wait you are sitting through is the price of the second kind, and it is not a high price.
- Placed
- You finished checkout. The record exists and the funds sit in escrow.
- Unaccepted
- Normal. The row is in a queue that somebody works in sittings.
- Accepted
- A person read it and agreed to fill it. This is the state you are actually waiting for.
- Cancelled or refunded
- Also a resolution. A vendor who cannot fill an order and says so early has done you a favour.
Safe to do meanwhile
None of this makes anybody sit down sooner. It makes the next step shorter when they do.
- Read the listing terms againHandling times, cut offs and stated days off are usually written down and almost always skipped.
- Look at the clock rather than the statusThe status is the thing you are staring at. The clock is the thing that has consequences.
- Leave the message box aloneA message about an unaccepted order joins the same queue as the order it is about.
- Come back tomorrow, onceOvernight states belong to the next band down, and the next band down is a morning job.
What makes it longer
The reasons an order sits are ordinary, and none of them are about you personally.
- An order placed after the last sitting of somebody's day, which means it waits for the first sitting of the next one.
- A weekend, a holiday, or a stated break that was written in the listing nobody read.
- A rush, where a queue that is normally short is not, and every row in it waits behind every other row.
- Something unusual in the order, which a careful vendor will want to ask about before agreeing to it.
- Cancelling and reordering, which puts you at the back of the same queue and throws away whatever position you had.
- A vendor who accepts in batches at a fixed point in their day, so the gap is set by their routine and not by your order.
What this card is not. This card cannot tell you what any vendor is doing, and an unaccepted order is not evidence of anything by itself.