On-time performance by cut-off — did the order ship on time?
Set a cut-off and dispatch time for working days, choose the measurement start and end, and the report will show how many orders shipped before the deadline and which were late.
Find the report under Reports → Logistics → On-time performance by cut-off. It answers one question: did the order leave the warehouse by the deadline for its shipping day? The unit is the order, not the parcel — an order with three parcels counts once.
Set the cut-off schedule
The schedule is saved for the company and visible to everyone who can read the report. A user with write permission in the Reports module can change it.
- Open the schedule panel on the report screen. In Basic view, set one cut-off time for Monday to Friday (for example, 12:00), a dispatch time (for example, 16:00 — carrier pickup; blank means the end of the day), the holiday switch, and the on-time target as a percentage.
- In Advanced view, set a separate cut-off and dispatch time for each day (including Saturday and Sunday), choose service days counted as business or calendar days (1 business day = the next business day; 1 calendar day = the next day; if that falls on a non-working day, the deadline moves to the next business day and its dispatch time), and set per-integration overrides — Allegro at 14:00, bol.com at 16:00, and Kaufland with no Saturdays can all operate in one warehouse.
- Save. The report recalculates immediately using the new policy.
The on-time target draws a line on the trend and controls its colours: green at or above the target, orange up to 10 percentage points below it, and red below that.
How the report sets a deadline
- Cut-off determines when an order must arrive; dispatch time determines when it must leave. These are two different times: an order received at 11:59 with a 12:00 cut-off has until dispatch time (for example, 16:00), not one minute.
- An order received on a working day by the cut-off time must ship that same day. The report compares down to the second: with a 12:00 cut-off, an order at 12:00:00 is still before the cut-off, while one at 12:00:30 is after it.
- An order received after cut-off, on a weekend, or on a holiday must ship on the next working day. The report shows these three groups separately (before cut-off / after cut-off / non-working day).
- Deadline = that day’s dispatch time; a day without a dispatch time counts to 23:59 (as Allegro, eBay, and Empik do). Service days move the dispatch day forward by the chosen number of business or calendar days. Calendar days ending on a weekend or holiday move the deadline to the next working day: Thursday after cut-off + 1 calendar day = Saturday → Monday, by Monday’s dispatch time.
- On time = the end point (packing, dispatch/carrier scan, or tracking sent) is no later than the deadline.
- Missed shipping deadlines tells you how many dispatch opportunities have passed: deadline Friday, packed Sunday → 1; packed Monday after the deadline → 2.
Example: cut-off 12:00, dispatch by 16:00. An order received Monday at 11:59 is due Monday at 16:00. One received Saturday at 9:00 is due Monday at 16:00. Packed Monday at 15:00 is on time; at 17:00 it is late, with one missed dispatch deadline.
Choose the measurement start and end
| Setting | Options | When to choose it |
|---|---|---|
| Start | Entry into Noxti · purchase in the store · release to warehouse · first entry into selected statuses (for example “Paid”) | Store purchase mirrors marketplace rules; warehouse release measures only what the warehouse controls; status is useful when the warehouse cannot start before payment or approval |
| End | Packed in WMS · handed to carrier (earlier of dispatch scan and pickup scan) · tracking sent to marketplace | Packing measures the warehouse; handover to carrier measures what the customer sees; tracking measures what the marketplace sees (Amazon, Empik) |
The report period uses the order’s start date. Filters: marketplace, carrier, country. The range limit is 186 days.
Read the result
- On-time performance — share of measured orders (those with an end point) that met the deadline. Beside it is the strict rate, where open orders past deadline count as late.
- Open after deadline — released to the warehouse, no end point, and past the deadline. These need action today. Orders that never entered the warehouse (for example, fulfilled by the marketplace or consolidation sources) are shown separately and do not count as failures. Those already past their deadline have a separate not released, overdue counter; review them (payment, stock shortage), but they do not change any on-time rate.
- Before cut-off / after cut-off / non-working day — three groups with different deadlines. If after-cut-off orders are also late (they have until the next working day’s dispatch time), the problem is capacity, not the cut-off hour.
- By order time — the time of day when on-time performance drops. If the bars are already falling at 12:00 with a 14:00 cut-off, the warehouse’s effective cut-off is 12:00.
- How late — up to an hour means you just missed the dispatch time (carrier pickup); more than a day means orders are stuck (no stock, exceptions).
- Breakdowns — by integration (with its own target if overridden), carrier, country, and shipping day. The daily trend groups by expected shipping day. All days up to the last shipping day for orders from before the range (which may be several days with service days and overrides), and days after the end of the range, are marked partial; they can also contain orders outside the selected range. If an integration with an override ships on a non-working day in the company schedule (for example, Saturday), the chart shows its orders instead of a gap.
- Late orders — up to 50 of the most overdue orders, with links to the orders. The “of N” count shows how many there really are; narrow the filters to see the rest.
Pitfalls
- No status history. An order created manually has no entry showing when it entered the initial status. If it is currently in the selected status, the report counts from its creation time and shows the number of such cases in data quality.
- Carrier scans depend on the carrier. When measuring the end as handover to the carrier or tracking sent, do not set dispatch time equal to the pickup time: a scan at 16:05 with dispatch time 16:00 makes every order late. Leave dispatch time blank (end of day) or enter the end of the pickup window with some buffer. If the carrier picks up the next morning, you can add 1 service day — but service days apply to every measurement end (switching the report to packing will include that extra day too), so for a single integration, set it in that integration’s override. The report uses the earlier of the dispatch scan and carrier scan because some carriers timestamp their scan at the sorting depot a day later.
- Hours are calendar hours. The average start-to-end time counts weekends like any other time; on-time performance depends only on comparison with the deadline.
- Lead Time is a different report: it counts parcels and time to carrier handover without a concept of a deadline. Here the unit is orders and the report checks the promise.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo