Working-Day Delivery Dates: Cutoffs, Holidays, and Day Zero
Follow an order through a Friday cutoff, a manually entered closure, dispatch, and three working transit days without confusing a planning date with a carrier commitment.
Separate order acceptance from time in transit
A three-day service does not necessarily arrive three calendar days after an order is entered. First identify when the shipment can be dispatched. The order date may be closed, or its origin-local acceptance cutoff may have passed. Then count transit under the chosen working calendar. Collection bookings, warehouse release, customs, delivery appointments, and the carrier's actual service rules can introduce further conditions. A planning calculator is useful when those boundaries are explicit, not when it hides them behind a single date.
Worked example: Friday afternoon to the following Friday
Enter Friday, October 16, 2026 at 16:30, with a 15:00 cutoff, Monday-Friday working days, three transit working days, and October 19 as an entered closure. Friday misses cutoff. Saturday and Sunday are closed, and Monday is the manually entered closure, so effective dispatch is Tuesday, October 20. With dispatch counted as day zero, Wednesday is transit day one, Thursday is day two, and Friday, October 23 is day three. The elapsed interval from the order date is seven calendar days.
Make day zero or day one an explicit choice
If the same example counts dispatch as transit day one, Tuesday is one, Wednesday is two, and Thursday, October 22 is three. That one-day difference comes entirely from the counting convention, not a faster truck. Confirm which convention the actual service uses. In this calculator, zero transit days always returns the effective dispatch date. It does not bypass a missed cutoff or turn a closed order date into a working dispatch date.
Treat the cutoff boundary consistently
An order at exactly 15:00 is at the cutoff, not before it, under this model. It rolls to the next eligible working date just like a later order. An order already on a closed date rolls once to the next working date; its clock time does not trigger a second roll. All entered times use the origin-local clock, with no destination time-zone conversion. The output is an arrival date, not an arrival hour or a guaranteed delivery appointment.
Own the calendar assumptions
The example closure is not asserted to be a national holiday. Enter holidays, shutdowns, or other closed dates that actually apply to the service. Selecting Saturday as a working day changes both dispatch and transit in this single-calendar model. A shipment with different origin, destination, linehaul, and customs calendars needs more detailed planning. The calculator does not fetch live holiday observance, strikes, weather, lane schedules, or carrier capacity. Confirm those conditions before making a customer promise.
Check a date against operational evidence
Retain the order timestamp, service cutoff, calendar, and transit convention with the estimate. Review the exported date trace when a weekend or closure makes the result surprising. If an actual dispatch differs from the assumption, replan from the confirmed date rather than preserving an obsolete commitment. Carrier service descriptions explain that availability and acceptance conditions matter; they do not validate a user-entered lane. Track planned and actual dates separately to identify whether delays originate in release, dispatch, transit, or final delivery.