“The stock should arrive next week” can sound reassuring inside an operations meeting. It is much less useful to someone who has already paid for an order.
The relationship problem starts when the brand and warehouse use the same word—arrival—to mean different things. A truck appointment, a counted receipt and stock cleared for picking are three different milestones. Your customer needs to know what happens to their order, not which milestone made the internal forecast slip.
Separate the warehouse update from the customer promise
Ask the fulfillment partner for four fields: the affected SKU and quantity, the current inbound milestone, the earliest supportable dispatch date and the uncertainty behind that date. A supplier estimate without a confirmed delivery appointment should not become a confident shipping email.
For covered U.S. orders, the FTC's merchandise-order rule guide explains the seller's obligation to have a reasonable basis for its shipment promise. If the seller cannot ship within the applicable period, it must offer the buyer a delay option or cancellation with a prompt refund. Notice and consent requirements differ for definite, indefinite and repeated delays; a generic status-page update is not a substitute for the required notice. Use the guide to have your compliance owner approve the actual messages and timing.
The practical consequence for the service relationship is simple: warehouse uncertainty must reach the brand early enough to act. Do not wait for the missed date to ask who owns the conversation.
Three situations need three different internal decisions
For this desk exercise, we mapped three hypothetical order situations to an operating response. These are proposed workflows, not tested provider capabilities or ready-to-send legal notices.
| Situation | What support needs from operations | Proposed owner and next action |
|---|---|---|
| Restock has a supportable revised dispatch date | Arrival, receiving and release assumptions behind that date | Brand support prepares the approved customer choice; warehouse preserves the order state |
| Supplier cannot give a credible arrival date | Explicit unknown status, affected orders and next evidence checkpoint | Brand decides how to communicate uncertainty without inventing a date |
| A previously revised dispatch date will also be missed | New cause, current consent record and shipment status | Compliance/support reviews the further-delay notice; warehouse prevents uncontrolled release |
This is deliberately more specific than “keep customers informed.” Each row connects evidence, a customer decision and a physical shipping action.
Put the waiting orders in a queue people can trust
A useful joint queue contains order ID, original promised ship date, affected line, last customer communication, response, operational hold and next review owner. Limit access to the people who need customer information. Keep the customer-facing message and its delivery record with the case.
Suppose, in an illustrative example, a replenishment pallet reaches the dock on Tuesday but inspection cannot finish until Thursday. Telling customers “your order ships Tuesday” skips the warehouse work that makes stock usable. If there is no supported completion time, leave the dispatch date unresolved while the team obtains the evidence. A precise but unsupported date is not better service.
Have support and the 3PL agree what happens when cancellation arrives during receiving or allocation. Which system blocks release? Who confirms the block? Which person resolves a mismatch? This should be answered before inbound stock triggers a rush of waiting orders.
Do not make every customer ask twice
Set a regular checkpoint for new evidence and an earlier escalation for threatened promises. The interval is an operating agreement you choose; it is not a universal legal deadline. Make the next update someone’s responsibility even when the update is that the arrival date is still unknown.
An account manager can help translate warehouse reality into plain language: what changed, what is known, what remains uncertain and what the brand is doing next. They should not improvise your refund policy or promise a dispatch date the floor has not accepted.
Before closing the incident, reconcile the waiting queue. Every order should have an explained disposition: shipped under the applicable customer decision, still waiting with an owner, or canceled and handled through the refund process. A newly received pallet does not by itself resolve the customers who were waiting for it.
Related reading
Sources
- FTC business guide: shipment promises, delay options and consent — accessed 2026-10-03.