Alert when an order contains a line that cannot be fulfilled from current stock, and route it to whoever writes to the customer rather than to the warehouse. The failure mode here is silence: the order sits looking normal in the queue while the customer assumes it is on its way, and every day of that is harder to recover from than the delay itself.
Why this one is worth an interruption
A backorder is not a fulfilment problem, it is a communication problem with a fulfilment cause. The stock will arrive when it arrives. What you control is whether the customer learns about it from you or works it out from a tracking number that never appears.
Left undetected, these are also the orders most likely to produce a chargeback, because a customer who has been charged, has heard nothing, and cannot see movement has very few options they consider reasonable.
The threshold
The trigger is order creation, not fulfilment attempt. Waiting until a picker discovers the problem loses you the days that matter.
| Condition | Set it to | Why that number |
|---|---|---|
| Trigger point | at order creation | Not when picking fails, which can be days later |
| Scope | any line short, not just the whole order | Partial shortfalls are the ones that get missed |
| Escalate at | no expected date within 7 days | Beyond a week, the decision changes from wait to refund |
| Value flag | above your average order value | High-value backorders deserve a call, not an email |
Who should receive it
The owner is whoever will write to the customer. Everything else is secondary.
- Whoever handles customer communication, because the first action is a message.
- The person who raises purchase orders, so the shortfall can pull a reorder forward.
- Whoever set the delivery promise on the product page, if that is a different person.
What to do when it fires
- Find the real expected date from the supplier before writing to anyone. A message with no date is worse than no message.
- Write to the customer the same day, giving the date and the option to cancel.
- Decide whether to split the order and ship what you have, using a written rule rather than per-order judgement.
- Flag the product so the same promise is not made to the next customer today.
When not to set this alert
Do not set this on made-to-order or pre-order products, where the wait is the product and the customer already knows.
Do not set it if your storefront already prevents overselling and you have verified that it works. In that case the alert has nothing to catch and you are adding noise to prove a negative.
Common questions
What is the difference between a backorder and a stuck shipment?
A backorder is stock that does not exist yet, so the constraint is supply and the conversation is about a date. A stuck shipment is stock that exists and has left but is not arriving, so the constraint is the carrier and the conversation is about what you are doing right now.
When should the customer be told?
The same day, with a real date from the supplier. A message that says there is a delay without saying how long transfers the anxiety without resolving anything.
Should we split the order?
Decide by rule rather than per order: split when the delayed item is more than a few days out and the order is above a value floor, hold when it is not. The consistency matters more than which way you set it.