When an order arrives late
An order usually appears in Yessort within moments of being placed, because the channel tells us. Sometimes that message does not arrive, and the order appears up to an hour later instead.
That gap is a safety net doing its job.
Why a missed order is serious
More serious than it first sounds, and worth understanding before dismissing it.
An order that never reaches Yessort is not merely absent from a list. There is no order, no stock reservation and no invoice — while the customer has paid and is expecting their goods. The stock they bought is not held for them, so it can be sold again to someone else.
And nothing else in the system heals it. Stock reconciles do not create missing orders; accounting cannot invoice an order that does not exist. Without a re-check, the first sign would be a customer asking where their parcel is.
What the re-check does
Every hour, Yessort re-reads recently changed orders from each active channel and takes in any it does not have.
It looks back three hours each time. Running hourly over a three-hour window means every order is covered three times, so a skipped run or a slow retry does not open a gap.
Bringing in an order this way produces exactly the same result as receiving it live: the same reservation, the same invoicing, the same picking work. It is late, not different.
Fulfilments too
The same applies to fulfilments the channel reports. Their re-check looks back 26 hours — a wider window, because fulfilment volume is lower and the cost of re-checking is smaller.
If goods went out through the channel without Yessort having allocated them, the dispatched quantity is recorded even though Yessort never picked it, so the order does not wrongly read as unfulfilled. See fulfilment groups.
What you would notice
An order appearing later than the customer says they placed it. Up to an hour is normal.
An order arriving already dispatched, where the channel fulfilled it before Yessort knew about it.
Neither needs action. Both are the backstop working.
When to be concerned
Orders consistently arriving an hour late rather than occasionally. That suggests events are not being delivered at all and the backstop is carrying the whole load — worth investigating the connection rather than accepting it.
An order that never appears. Beyond an hour, the re-check should have caught it. Check the connection is active and not in error — see check a channel's sync activity.
No screen shows this
There is no report of what a re-check found. The order simply exists, indistinguishable from one that arrived live, which is what you want — but it does mean you cannot look up whether an order came in late. See safety nets.