Freight density
Find your shipment density and estimated freight class.
Freight & shippingSet the origin-local order time, cutoff, working weekdays, and holidays to estimate a delivery date.
Set the origin-local order time, cutoff, working weekdays, and holidays to estimate a delivery date.
The same entered working calendar is used for dispatch and transit. At or after the cutoff, an otherwise working order date rolls to the next working date; closed order dates roll once. Holidays are entered manually, not fetched or inferred. All times use the origin-local clock with no time-zone conversion, and arrival is a date only. Zero transit days returns the effective dispatch date. Complete date trace is included in CSV; the on-screen table shows at most 120 dates.
| Date | Weekday | Calendar status | Transit day count | Event |
|---|---|---|---|---|
| 2026-10-16 | Fri | Working | N/A | Order 16:30 / cutoff reached |
| 2026-10-17 | Sat | Closed weekday | N/A | |
| 2026-10-18 | Sun | Closed weekday | N/A | |
| 2026-10-19 | Mon | Holiday / closed | N/A | |
| 2026-10-20 | Tue | Working | 0 | Effective dispatch |
| 2026-10-21 | Wed | Working | 1 | |
| 2026-10-22 | Thu | Working | 2 | |
| 2026-10-23 | Fri | Working | 3 | Estimated arrival |
The same working-week and holiday calendar controls dispatch and transit. An order on a closed date rolls to the next working date. On an open date, an order at or after cutoff rolls to the next working date; before cutoff, dispatch stays on that date. By default dispatch is day zero. With day one selected, dispatch counts as the first transit day. Zero transit days always returns effective dispatch. Dates use UTC-backed, date-only calendar arithmetic, independent of browser time zone or daylight-saving shifts. The example holiday is a manually entered closure, not a national holiday assertion.
Establish effective dispatch before counting transit working days. A missed cutoff, weekend, or entered closure can shift the starting date even when the transit duration itself stays unchanged.
Day-zero and day-one conventions produce different dates. Confirm the actual service rule and enter the relevant closures; no national holidays are inferred. The result uses one origin-local calendar and is a planning date, not a live carrier ETA or appointment guarantee.
A planning date, not a live carrier ETA or guarantee. All entered times share the origin-local clock; no origin/destination time-zone conversion is applied. Holidays and service weekdays are manual assumptions. Confirm actual carrier acceptance, collection cutoffs, service availability, holiday observance, and delivery appointments. Up to 366 transit working days and 500 entered closures; CSV includes the full calculation calendar.
FedEx explanation of service cutoffs and holiday availabilityWorked example: Working-Day Delivery Dates: Cutoffs, Holidays, and Day Zero
No. At the exact cutoff or later, a working order date rolls to the next eligible dispatch date. Confirm the convention in your actual service agreement.
No. Enter the closures that apply to the service. The same entered calendar is used throughout; this does not model different origin and destination calendars or customs delays.