Communicate stockouts without conflicting promises
Coordinate stock evidence, affected orders, customer options, and replenishment updates so stockout messages reflect facts your team can verify.

Stockout communication should give customers a reliable account of what your business knows, what remains uncertain, and which options are actually available. The difficulty is rarely writing a sympathetic sentence. It is coordinating inventory, suppliers, fulfilment, and support so the sentence remains true after another order arrives or a supplier changes its estimate.
This guide explains an administrative process for small retailers. It separates preventing new promises from resolving orders already accepted, and it distinguishes an expected replenishment from stock that can be supplied. Local consumer rules and the commitments made at purchase still need appropriate review; one store policy cannot override every market’s requirements.
Establish the real shortage before announcing a date
Confirm the exact SKU, variant, location, and affected quantity. Check whether the problem is a physical shortage, an availability calculation, a damaged batch, a transfer, or a product-data mismatch. These situations can require different customer updates.
Shopify’s inventory-state guide distinguishes incoming units from units available to sell. The broader principle is straightforward: a planned delivery is not the same as verified stock ready for fulfilment. Keep those states separate in your own records.
Use the inventory discrepancy process when physical evidence conflicts with the system. Until the relevant facts are established, give the stock issue an owner and prevent unsupported promises rather than filling the gap with an optimistic date.
Separate new visitors from customers with accepted orders
New visitors need an accurate product offer before they buy. Existing customers need information about the order and commitment already made to them. Updating a product page for future orders does not inform people whose purchase has already been accepted.
Create two linked workstreams. The catalogue owner checks product availability, relevant sales channels, and checkout behaviour. The order owner identifies affected customers, reviews the actual purchase terms and applicable requirements, and coordinates approved options.
Do not assume a general website banner reaches everyone. A customer may have ordered through a marketplace, a saved checkout link, or another supported channel. Use the order record to determine the appropriate communication route, with a recovery process for failed messages or missing contact information.
Create one replenishment record with evidence and confidence
Record the supplier or internal source, expected quantity, estimate date, evidence reference, last confirmation time, and person responsible for checking it. Distinguish an unconfirmed estimate, supplier-confirmed plan, shipment in transit, goods received, and goods verified for sale.
Avoid expressing confidence as an invented percentage. Use plain operational labels with definitions your team understands. “Supplier estimate, not yet dispatched” communicates more useful uncertainty than an unsupported “90% likely” date.
Record what would change the estimate. A production completion, shipment confirmation, receiving inspection, or customs event may be relevant depending on the business. The next review date should connect to that evidence rather than to a habit of asking the supplier for the same unsupported reassurance every morning.
Stop conflicting promises across channels
List where the product is offered: your site, marketplaces, sales messages, advertisements, printed materials, or direct quotations. Identify which channels use live inventory and which use manually maintained information. A correction in one place may not reach another.
Check both availability wording and purchase behaviour. A page marked unavailable should not continue accepting an ordinary immediate-dispatch order because a basket rule still allows it. If backorders or preorders are offered, their terms and operating process need to be intentionally designed rather than created accidentally by a stock error.
Keep a correction log with channel, change made, time, owner, and verification result. The product data quality checklist explains how the visible page, selected variant, basket, checkout, and published data should describe a consistent offer.
Build a list of affected order lines
Identify orders by the affected item and quantity, not only by order date. A customer may have several items, some available and some not. Record any already fulfilled quantity and the current source state before deciding what communication is required.
Check whether a customer has an existing exception, cancellation request, replacement, or refund in progress. Merge relevant information so a stockout message does not contradict a decision another team has already made. Keep separate issues linked rather than treating each automated alert as a new case.
Prioritize required action using the original commitment and applicable obligations. Do not silently move the oldest orders behind new ones because new customers are easier to contact. If allocation rules are needed, have the authorized business owner approve and document them.
Define customer options before sending the message
Support should receive a current list of options the business can actually deliver. These might include waiting under an agreed revised arrangement, an available alternative chosen by the customer, a partial shipment where appropriate, or cancellation and refund under the applicable circumstances.
| Option being considered | Fact to verify first | Decision to record |
|---|---|---|
| Wait for replenishment | Evidence for the revised expectation | Customer choice where required and next update |
| Choose another item | Actual availability and relevant differences | Customer’s selected item and approved price treatment |
| Split the order | Feasible fulfilment and cost arrangements | Affected lines and agreed shipping plan |
| Cancel affected items | Current order and payment status | Authorized cancellation and refund route |
The table is a planning aid, not a universal statement of legal entitlement. Do not offer store credit as the only option merely because it is operationally convenient when the customer’s rights or agreed terms require something else.
Write the first update around a useful decision
A good update identifies the affected item, explains the verified issue in plain language, gives the approved options, and states what the customer needs to do. If the customer need not act immediately, explain when the next update will arrive and what the business is checking.
Keep an uncertain replenishment estimate visibly uncertain. Avoid presenting the supplier’s hoped-for production date as a delivery date at the customer’s address. Those are different events with different dependencies.
Do not hide the problem beneath promotional language. A stockout notice should resolve an existing purchase question. Requests to buy a more expensive alternative or join a marketing list can distract from that purpose and create unnecessary pressure when the customer is waiting for goods already ordered.
Check the applicable shipping-delay requirements
Legal requirements differ by market and transaction. Your business should review the rules relevant to where and how it sells, rather than copying a delay notice from another country. Build those requirements into the approved process with qualified help where needed.
For the United States, the FTC’s merchandise-order rule guide addresses shipment promises, delay notices, customer choices, and refunds. Its detailed conditions should be checked for transactions within its scope; they are not a worldwide timetable.
Record the original promise and relevant order evidence. A later website edit does not rewrite the information shown when a customer purchased. Keeping that history helps the authorized reviewer determine the appropriate response and prevents support from relying on a current product page that no longer matches the order.
Work through a hypothetical delayed kettle shipment
Imagine a retailer discovering that a particular kettle colour cannot be supplied from the expected delivery. Twelve accepted orders include that variant. The catalogue owner prevents new immediate-dispatch purchases for the affected item while checking all supported channels.
The replenishment record shows a supplier estimate but no dispatch confirmation. The owner approves a customer message that identifies the affected variant and presents only verified options. Another colour is available, but support does not substitute it automatically. Customers who choose an alternative have that decision recorded against the specific order line.
One customer chooses cancellation; finance receives the authorized request with the order and payment reference. Another customer agrees to wait under the applicable arrangement, and the case retains a next update date. When the supplier later changes its estimate, the waiting customer receives a new factual update. This hypothetical case illustrates coordinated records and choices, not a reported merchant outcome or a universal legal procedure.
Keep an update schedule that survives a lack of news
Set the next update point before the first message is sent. Assign an owner to check replenishment evidence and another owner, if different, to communicate with customers. A promise to provide an update remains a commitment even if the supplier has nothing new to report.
When information has not changed, say what was checked, what remains unconfirmed, and which previously approved options remain available. Do not repeatedly move the expected date forward by a few days without explaining the basis or considering the appropriate customer decision.
Record message failures and unanswered requests separately. A sent email is not proof that a required customer choice was received. Follow the approved process for reminders, alternate contact routes, and unresolved responses, reflecting the actual terms and applicable rules.
Coordinate partial shipments and allocation
A partial shipment changes the order’s practical state. Identify which items will move, which remain open, how shipping charges are handled, and what the customer has agreed where relevant. Give the warehouse a line-level instruction with the decision reference.
When replenishment arrives, confirm that it is usable and available before allocating it. Do not send a general “back in stock” message that creates new demand before checking existing commitments. Decide how orders are allocated and who can approve exceptions to that rule.
Keep evidence of the final dispatch for each remaining line. A customer whose first parcel arrived should not disappear from the stockout queue while another item remains outstanding. The ecommerce support handoff guide connects those fulfilment facts to the customer conversation.
Avoid making substitutions a hidden default
Alternatives can help, but differences matter. Confirm size, colour, compatibility, included accessories, price, and relevant conditions. Do not call two products equivalent merely because they sit in the same catalogue category.
Ask for the customer’s actual choice through the approved route when a substitution is appropriate. Record the selected item and the applicable commercial decision. A vague reply such as “that is fine” should be read in its conversation context, not treated as approval of a different proposal added later.
If a customer does not choose an alternative, preserve the original case and its next action. Silence should not automatically authorize the easiest option for the retailer. Required consent and remedy decisions need to follow the applicable rules and the commitments governing the transaction.
Close the shortage with evidence rather than an announcement
Replenishment received is not the same as every affected order resolved. Check the incoming quantity, product identity, condition, and available stock. Then reconcile affected order lines against dispatches, agreed alternatives, cancellations, and confirmed refund actions.
Update product availability only after the appropriate stock verification. Review the related channel changes so an old unavailable banner does not remain while another channel sells the item incorrectly. Keep the final replenishment and order-resolution references in the stockout record.
Record any continuing work with a separate owner. A supplier dispute, inventory correction, or payment investigation may remain after customer orders have been addressed. Closing the communication incident should not erase those tasks or imply that their outcome has been settled.
Keep the explanation accessible to the covering person
Store the current approved explanation beside the stock issue, with a date and the conditions under which it can be used. A covering colleague should be able to distinguish a supplier estimate from verified replenishment without searching an absent person’s inbox. Include links to the affected-order list and the latest customer options, while keeping personal order details appropriately restricted.
When an estimate changes, mark the earlier explanation as superseded and identify the new facts. Do not leave several equally plausible message drafts in circulation. This simple version discipline helps the business maintain consistent answers across shifts, time zones, and communication channels while the underlying situation remains uncertain.
Measure the process and improve the next shortage
For a pilot, track affected orders, time from verified shortage to first appropriate update, unanswered choices, missed update commitments, contradictory promises, and orders reopened after apparent resolution. Separate delay length from communication quality; the team may improve one without changing the other.
Review the original cause. The issue may arise from forecast assumptions, a receiving delay, an inventory definition, or product availability that was never updated. Select one practical prevention measure and give it an owner rather than adding more generic apology templates.
Keep the essential records simple: one verified stock issue, one replenishment evidence record, a complete affected-order list, and a current communication plan. Those connections let a small team provide honest updates and usable choices while managing uncertainty responsibly.
Sources and editorial method
Checked October 15, 2026. Primary references: Shopify: inventory states and FTC: merchandise-order rule business guide. FTC rules discussed here are specific to transactions within their United States scope. The record design, option table, and kettle scenario are original operational examples, not legal determinations or guaranteed results.



