The FTC’s merchandise-order business guide explains that sellers need a reasonable basis for shipment representations and must follow delay-notice, consent and refund requirements when they cannot ship on time. The rules differ for first and subsequent delays; silence is not a general permission to keep extending an order. This article focuses on operating records, rather than prescribing a notice for every legal situation.
AMS analysis: preserve the promise before replacing it
Keep the shipment representation that applied when the customer ordered. A later product-page edit should not erase that evidence. Record the order’s affected items, the original shipment commitment and when the business learned it could not meet it. Distinguish shipment from delivery: a supplier’s expected arrival at the store does not establish when the merchant can hand the customer’s package to a carrier.
For a hypothetical retailer waiting for a delayed kitchen appliance, purchasing should give support the basis for any revised date. Is the item allocated, in transit or merely expected in a future production run? Support should not turn the most optimistic internal estimate into a firm external promise. If a date cannot be supported, the notice and decision process must reflect that uncertainty.
Make the response change the operational state
Save the notice version, destination, sending time and any delivery failure. Connect the customer’s response to the order so a cancellation reaches the fulfillment team before the package is released. A response sitting in a general inbox while a warehouse screen still says ready is an avoidable conflict. Assign an owner to resolve replies that do not clearly identify the order or requested choice.
Treat a second delay as a new review, with its own deadline and required customer decision. Do not copy the first notice automatically or assume that a previous willingness to wait covers every later change. Have the business’s adviser approve the applicable notice logic and cancellation timing. The staff workflow should implement that decision rather than improvising legal conditions in a support reply.
Close the loop on cancellation and refunds
When an order is cancelled, record the affected items and refund action, then check the payment provider’s result. An internal note saying refund requested is different from a completed processor record. Route failed or unmatched refunds to a named person and keep the customer communication consistent with the actual status.
Review delayed orders by their next decision deadline, not only by how long they have been open. The owner should be able to ask which orders need a notice, which await an answer and which must be cancelled or refunded. That view turns a growing backorder list into a set of accountable actions, while preventing a revised estimate from concealing an unresolved customer choice.