Warehouse capacity
See usable pallet positions and operating headroom.
OperationsAdd order processing, production, dispatch, transit, customs, and receiving time into a serial replenishment lead-time estimate.
Add order processing, production, dispatch, transit, customs, and receiving time into a serial replenishment lead-time estimate.
All stages are serial and on one day basis. Overlap, holidays and live shipment events are not modeled.
This model treats all stages as sequential. Use the same time convention for every input: all calendar days or all working-day equivalents. Enter zero for stages already included elsewhere. The result describes order release to stock being usable, not just port-to-port transit. Stage shares help identify which entered components dominate the estimate.
Separate process time, waiting, transport, and other entered stages to see where the elapsed lead time accumulates. A large queue can matter more than a short improvement to the physical task.
Do not add durations measured on incompatible calendars or count overlapping activities twice. This additive breakdown does not solve a dependency network. Use confirmed stage boundaries when comparing a future scenario with actual performance.
Do not sum overlapping stages or duplicate handling time already included in transit. This is not a live ETA, business-calendar calculation, or uncertainty model. Supplier and route delays must be reflected in your own assumptions.
Worked example: Working-Day Delivery Dates: Cutoffs, Holidays, and Day Zero
No. Convert stage assumptions to one consistent time basis before entering them. The tool does not map durations onto a calendar.
Yes, as an entered average lead-time assumption on the same day basis as daily demand. Variability and supplier disruption require separate assessment.