1. Build a promise from five different dates
Write down the supplier’s estimated completion, estimated arrival at your warehouse, first allocatable stock, promised ship date or window, and expected delivery. The last two serve different purposes. The ship window tells the buyer when the parcel is expected to enter the carrier’s possession. The delivery estimate also depends on service, destination and when handoff actually happens.
| Date | Meaning | Owner and source | Buyer sees | Change affects |
|---|---|---|---|---|
| Supplier finish | Units produced | Buyer · supplier schedule | Internal | Inbound forecast |
| Warehouse ETA | Expected arrival | Inbound lead · freight update | Usually internal | Receiving slot |
| Allocatable | Accepted usable stock | Warehouse · receipt and inspection | Internal | Order allocation |
| Ship window | Expected handoff | Brand · supported release plan | Yes | Promise and delay action |
| Delivery estimate | Expected arrival to buyer | Merchant · service and destination | When offered | Buyer arrival expectation |
Work forward from production evidence. Ask the supplier for the latest finish forecast and quantity by SKU. Add inbound transport, receiving appointments, inspection, any kitting or labeling, pick and pack time and the next pickup the warehouse can actually meet. Use available capacity after other commitments. When the lead time varies by color or size, quote against the slowest required line for a combined order or disclose separate windows. Record the assumptions with the forecast owner.
Before opening a batch, cap the number of orders against reasonably supported sellable units and dispatch slots. Ask what portion of the supplier forecast is firm and which units are assigned elsewhere. Save the evidence and the buffer used. Recheck the cap when a production or receiving milestone slips.
Use batches to protect the promise. For an illustrative November 2026 schedule, batch A has a Nov 9 supplier estimate, recorded receipt Nov 12 and verified allocatable stock Nov 13. Its purchase promise is Nov 16–18. Batch B has a Nov 16 supplier estimate, a Nov 19 arrival estimate and a Nov 20 allocation target, with a separately supported Nov 23–25 ship window. The example transit estimate is two to four business days from actual handoff for both batches. These dates illustrate the different fields. They do not establish a carrier delivery commitment.
Show the applicable window before purchase, in checkout where possible and in the confirmation. Save the version by line, with batch, displayed window, time zone and whether the order waits for all items. A page update can guide the next buyer. For existing orders, work from the saved promise and any later accepted revision. If the supplier changes the forecast, assess each affected batch against its deadline instead of updating every order to the latest forecast.
Check how the window appears to the buyer on mobile and in confirmation emails. A delivery estimate calculated from checkout needs the preorder wait included. If you show a transit range separately, say when it starts. Resolve contradictory dates across product, checkout and confirmation before opening the batch.
Account for weekends, holidays and warehouse cutoffs in the schedule. A carton checked in late Friday may miss an inspection slot or pickup. Use the warehouse’s local time and the dates when it and the carrier can work. If the upper end of the window lacks a reasonable basis, pause selling that batch and collect waitlist interest while supply is verified. An estimate still needs support. Keep the general shipping policy consistent with the product-specific terms. FTC Rule
Two ways to make a vague promise usable
| Vague example | Clearer example |
|---|---|
| Ships next month | Batch A ships Nov 16–18, 2026, warehouse local time. |
| Expedited preorder | Batch B ships Nov 23–25, 2026. Expedited transit starts after handoff. |



