Dispatch note · 19 Nov 2026
Order cutoffs and the fulfilment SLA that survives a Monday
A cutoff time is a promise about a queue, not a clock. The desks that keep the promise design for the worst day of the week, not the average one.

A cutoff is a queue, not a clock
An order placed at 13:59 and an order placed at 14:01 arrive in the same warehouse on the same afternoon, and only one of them is promised same-day dispatch. The difference is a queue position, not a moment in time.
The cutoff tells the customer when their order enters the pick queue. Everything after that - pick, pack, label, manifest, carrier scan - is a chain of queues, and the promise is only kept if every link keeps its own schedule.
A desk that publishes a cutoff without publishing the downstream chain is publishing a number it cannot defend. The customer reads a promise; the warehouse reads a workload.
The honest design publishes the cutoff, the dispatch window and the carrier's collection time, and it makes all three consistent with the staffing on the floor.
Build the promise from lane data
A delivery promise is made of lane data: origin warehouse, carrier, service level, transit time and the historical spread around that transit time.
The spread matters more than the mean. A lane with a four-day average and a two-day standard deviation cannot support a five-day promise at any useful confidence level.
The desk should compute the promise from the ninety-fifth percentile of observed transit, not the average, and it should refresh the calculation monthly as the carrier's network changes.
A promise built from the mean is a promise that is missed on half the orders and spectacularly missed on the rest, and the refunds land in the same week as the marketing push.
The three clocks: order, pick, label
The order clock starts when payment is authorised, not when the confirmation email is sent. A payment that is reviewed manually for two hours consumes the whole dispatch window.
The pick clock starts when the order is released to the floor. A wave that is released at 15:00 for a 14:00 cutoff is already late, whatever the timestamp on the order says.
The label clock is the one that customers can see, because the carrier's first scan is visible in the tracking page. A label printed at 16:00 and collected at 18:00 reads as dispatched at 18:00.
Measuring all three clocks separately is the only way to find which one is failing. A single on-time percentage hides whether the loss is in payments, picking or the carrier's collection.
Buffer the Monday, not the average
Weekend orders accumulate and land on Monday morning. A desk staffed for the average Tuesday will fail every Monday by a predictable margin.
The fix is a capacity plan with a weekly shape rather than a monthly total: Monday and Tuesday carry a backlog, Wednesday and Thursday carry the marketing sends, Friday carries the cut-off for weekend delivery.
The plan should be expressed in orders per hour per function, and it should be compared with the actual curve every week. A plan that is not compared with actuals is a wish.
The buffer is cheaper than the apology. Two extra pickers on Monday morning cost less than the refunds and the reviews that a missed Monday generates.
Holidays and the calendar that is not yours
The carrier's calendar is not the brand's calendar. A national holiday closes the carrier's hub, and a regional holiday closes a sorting centre on one lane only.
The desk should maintain a lane-by-lane holiday table for the next two quarters, and it should apply the table to the promise calculation rather than to the cutoff alone.
A promise that ignores a carrier holiday is a promise that is missed by a whole day, and the customer experiences it as a lost parcel rather than a closed hub.
The table should also cover the destination country's holidays, because a parcel that arrives during a week-long closure sits in a depot and ages.
What to measure, and what the number hides
On-time dispatch is the share of orders released to the carrier by the promised window. It is a leading indicator and it is the one the desk can act on today.
On-time delivery is the share of parcels that arrive by the promised date. It lags by the transit time and it is the one the customer experiences.
A desk should report both, and it should report the miss reasons in a fixed taxonomy: payment review, stock discrepancy, pick error, label failure, carrier no-show.
A single percentage without a reason split is a number that starts arguments between departments instead of ending them.
Communicating a miss before the customer asks
The customer discovers a delay in one of two ways: the brand tells them, or the tracking page tells them. The first preserves trust; the second spends it.
A proactive notice should carry the new date, the reason in one sentence, and an option - cancel, wait, or split the shipment. An option turns a failure into a service.
The notice should be triggered by a threshold on the dispatch clock, not by a daily report. A notice that arrives after the original date has already passed is an apology, not a service.
The template should be written before the peak season, tested in the customer's language, and approved by the support team that will handle the replies.
The promise as a contract term
A delivery promise is also a contract term when the marketplace or the payment provider measures it. Late dispatch affects seller metrics, and enough misses affect the account.
The desk should know which channels measure which metric, and it should set the promise differently per channel rather than exporting one number to all of them.
The internal target should be tighter than the external promise, so that the published number is met on a normal week without heroics.
The gap between the internal target and the published promise is the desk's safety margin, and it should be written down rather than discovered during a peak.
The cutoff and the inventory reservation
An order that enters the queue reserves stock only if the system reserves it at the same moment. A queue that reserves later is a queue that oversells.
The reservation should happen at payment authorisation, and the order should be released to the floor only when the stock is committed, not when it is located.
A stock discrepancy discovered at pick time is a dispatch miss, and the desk should count it under the stock reason rather than under the pick reason.
The cutoff's real promise is that an order placed before it will be picked from stock that exists, and that promise is an inventory question before it is a logistics one.
The carrier's scan is the only scan the customer sees
A label printed is not a parcel dispatched, and the tracking page shows the carrier's first scan rather than the warehouse's internal event.
The desk should measure the gap between label print and first scan, and treat a gap over the collection window as a miss even if the internal report says on time.
A warehouse that prints labels early to hit an internal timestamp is gaming its own metric, and the customer experiences the difference.
The honest measure is the first scan, and it is the one the carrier will also report in its own service dashboard.
The short version
A cutoff is a queue position, and the promise behind it is three clocks and a carrier's collection time.
Build the promise from lane percentiles, staff for the weekly shape, and measure the first carrier scan rather than the internal label time.
Publish the cutoff, the dispatch window and the collection together, and write the miss notice before you need it.
Two final numbers
Track the share of orders that enter the queue before the cutoff and leave it before the carrier's collection, and publish that ratio internally every week.
It is the one metric that describes the whole chain, and it is small enough to act on before the customer notices.
The desk that publishes its cutoff, its dispatch window and its carrier collection on the same page is the order fulfilment service with published cutoffs, and that triple is the first thing to check.
What to check
- Cutoff, dispatch window and carrier collection published together
- Promise computed from lane p95 transit, refreshed monthly
- Order, pick and label clocks measured separately
- Weekly capacity shape, with a Monday buffer
- Lane-by-lane holiday table for two quarters
- Miss reasons reported in a fixed taxonomy
- Proactive delay notice with an option attached