See what disconnected Order Operations costs you. | Try the ROI Calculator
A backorder is a customer order accepted for a product that is temporarily out of stock, to be fulfilled when inventory arrives. In ecommerce and retail, backorders let you keep selling through a stockout instead of losing the sale, in exchange for a promise your operation now has to keep.
When an item is on backorder, it can still be ordered even though it is temporarily out of stock; the order waits, tied to incoming supply, and ships when the replenishment lands. Backordered means the sale exists, with payment terms and an expected date attached, which is what separates it from a cancellation or a "notify me" signup.
You can buy it now and it ships later, on a stated date.
An open order consumes a unit you do not have yet, and your systems have to hold it against the inbound purchase order, transfer, or production run that will cover it.
The difference between a backorder and out of stock is whether the customer can still buy. Out of stock stops the sale; a backorder accepts it against expected supply.
| Out of stock | On backorder | |
|---|---|---|
| Can the customer order? | No | Yes |
| Is there expected supply? | Unknown or none | Yes, with an expected date |
| What the listing shows | Unavailable, or notify me | Buyable, with a ship-by expectation |
| Operational commitment | None | An open order that must be tracked and fulfilled |
The two failure modes are opposites. A stockout with supply already en route but no way to accept orders is lost revenue; a backorder with no reliable arrival date is a broken promise waiting to happen. Both come from one gap between the orders you accept and the inventory heading toward you.
Backorders happen when demand outruns on-hand supply while replenishment is still in motion.
Spikes, lead times, and inventory drift are conditions to manage; pre-selling is a decision. Both land in the same place: an accepted order is only as honest as the inbound supply your systems can tie it to.
Allowing backorders is a revenue decision with an operational price. It protects sales you would otherwise lose, but every one of them is a commitment your operation has to track, communicate, and keep.
Backorder management is the workflow that ties accepted orders to inbound supply, keeps every channel's count honest while stock is out, and releases them the moment it lands.
Instead of failing an out-of-stock order, order management routes it against inbound supply and holds it in a known state, tied to the purchase order or transfer that will cover it. The promise is grounded in a confirmed receipt, not optimism.
The moment inventory is received, waiting orders release automatically and flow to fulfillment. Nothing waits on a person to notice, so the stockout becomes a delay the customer was already told about.
Overselling during a stockout compounds the stockout. Real-time inventory visibility updates every channel as supply changes and keeps committed backorders counted, so the 4,000 units on an inbound container get promised once instead of sold three times across marketplace, DTC, and wholesale.
A stated ship week beats a vague "in stock soon" on the product page, at checkout, and in the confirmation email. Set the expected date from real inbound data, revise it when supply moves, and notify the customer before they have to ask.
Backorder communication works when it is specific, early, and kept current.
Product page. Show the product as buyable with an expected ship date.
Checkout. Restate the expected ship date before payment.
After purchase. Confirm the date, then update on every change; silence is what turns a waiting customer into a cancellation.
Partial stock. If part of the order is on hand, offer a split shipment and let the customer choose.
When something is on backorder, the seller has accepted your order for a product that is temporarily out of stock and will ship it when new inventory arrives, usually against a stated ship week. The order is real and stays open while it waits on supply.
A backorder takes as long as the replenishment behind it, most often a few days to several weeks. The date for any one order comes from the inbound supply it is tied to, so an operation that tracks commitments against its purchase orders and transfers can name a specific week rather than quote that whole span.
A backorder sells an existing product that is temporarily out of stock, while a pre-order sells one that has not been released yet. Operationally the two behave alike. Each is an accepted order held against expected supply and released when inventory arrives, so the same handling workflow serves both.
Payment timing on backorders is the seller's policy choice, with most sellers either charging in full at purchase or authorizing now and capturing at shipment. Up-front payment firms the commitment and simplifies accounting; capture at shipment means a slipped date creates fewer refunds. Either way, state the policy clearly at checkout on backordered items.
Most sellers let customers cancel a backordered order any time before it ships, and a captured payment becomes a refund. Those requests cluster where communication fails; an order carrying a credible, current ship date holds, while one that has gone quiet does not.
Reducing backorders means closing the gap between demand signals and replenishment. Keep channel inventory synced in real time so overselling never manufactures backorders, watch sell-through against inbound supply, and set reorder points that reflect the full multi-channel picture. The involuntary ones are worth engineering away; the deliberate ones are strategy.
