Preorder vs backorder — same sale, completely different plan
Preorder vs backorder explained — both sell against zero stock, but one is a planned strategy and one is a failure. How to tell which you're running.
InventoryX is in development and not available today. ClearStock is the live Shopify app.
The difference between a preorder and a backorder isn't the order record — Shopify logs both identically as unfulfilled sales against zero inventory. The difference is when you decided. A preorder is a sale you accepted deliberately before the goods existed, with a stated window and a purchase plan behind it. A backorder is a sale that slipped through because your count was wrong, your sync lagged, or nobody turned off "continue selling when out of stock" (Shopify Help Center, "Selling when out of stock," accessed October 2026). One is a strategy; the other is an incident wearing the same paperwork. Here's the state machine behind both, and the test for which one you're actually running.
The state machine: two paths through zero stock
Every sale against zero inventory passes through the same states. What differs is the planning that happens at each gate:
The preorder path (planned):
- Planned absence — you know the SKU will be dark before it happens (new launch, reprint, restock in transit). You set the window, the price, and the buy quantity first.
- Open preorder — the product sells with "ships in November" stated on the page. Every order is a unit you now owe.
- Buy trigger — preorders (capped) tell you exactly how many units to purchase. No forecast needed; the demand is already counted.
- Receive & fulfill — stock lands, preorder queue ships first, the toggle turns off.
The backorder path (unplanned):
- Unexpected absence — demand outran your count or your reorder. You didn't choose the dark period; it arrived.
- Leak sale — an order lands anyway: a stale toggle, a sync gap, a POS sale of units that weren't there. Nobody told the customer the ship date, because nobody knows it.
- Improvise — you discover the backorder when you try to fulfill it, apologize, and either wait for the next PO or refund.
- Aftermath — trust spent, no demand data gained, and the count error that caused it still unfixed.
Same Shopify order record. In path one, states 1 and 2 happened on purpose with a number attached. In path two, they happened by accident with no number attached — which is why backorders feed directly into the overselling mechanics and their prevention.
Side-by-side
| Preorder | Backorder | |
|---|---|---|
| Chosen? | Yes — planned before stock exists | No — discovered after the sale |
| Customer knows the date | Yes, stated at purchase | No, or a guess under pressure |
| Informs the buy quantity | Yes — preorders ARE the forecast | No — it's noise your forecast has to survive |
| Trust effect | Builds, if windows hold | Burns, every time |
| Underlying setting | "Continue selling when out of stock," on purpose | The same setting, forgotten |
| Exit | Fulfill the queue, close the window | Refund, or fulfill late |
The operational tell: a preorder has a published ship window and a cap; a backorder has neither. If you can't answer "what's the window and what's the max units" for a dark SKU currently taking orders, you're running backorders and calling them preorders.
When each is a strategy — and when it's a failure
Preorder is a strategy when:
- The SKU is new or a known reprint and you want demand validated before cash is committed to the PO.
- The buy is big relative to your cash and customer prepayment de-risks it.
- The window is honest — built from your supplier's actual delivery history, not their quote.
- You cap the preorders at a quantity you can actually purchase and fulfill.
Preorder becomes a failure when the window was aspirational, the cap didn't exist, or the window repeats — a SKU that is perpetually "on preorder" isn't running a strategy, it's running a subscription to apologies.
A backorder is a failure by definition — but a recoverable one if you treat it as a diagnostic. Each backorder points at a specific defect: a toggle left on, a count error at receiving, a sync gap, a reorder that fired late. The dark days that produced it have a dollar cost you can estimate with the out-of-stock cost math, and the count accuracy problems behind repeat backorders live in your receiving and counting discipline, not in the storefront setting.
The deliberate-looking middle case: some stores run "backorder-allowed as policy" — keeping popular SKUs sellable through dark periods with long stated windows. If the window is published, honest, and backed by an in-transit PO, that's a preorder wearing a backorder's name. The label matters less than the three tests: planned, dated, capped.
Which one are you running? A 3-question test
For any SKU currently selling against zero inventory:
- Did you decide the dark period in advance? No → backorder path; stop the leak first (toggle, count check), then plan.
- Is there a stated ship window the customer saw at checkout? No → you owe an email today with a real date.
- Do you know the exact number of units owed, and does it fit your next PO? No → count the unfulfilled queue now and reconcile it against the incoming order before it lands.
Fail any question and the order in front of you is a backorder regardless of what you've been calling it.
Where the preorder mechanics live
The setup detail — native toggle, deposits, mixed carts, caps — is covered in Shopify preorders; this article is the decision layer, that one is the mechanics layer.
Common questions
What is a backorder in Shopify? A backorder is an order accepted when inventory was already at zero — typically through the "Continue selling when out of stock" setting left on, or a sync gap between channels. The order records normally, but it can't fulfill until stock arrives, and in the accidental case the customer was never told a ship date.
What's the actual difference between preorder and backorder? Intent and timing. A preorder is planned before stock exists, with a published window and a purchase plan; a backorder happens by accident after the fact. Shopify records both identically — the difference shows up in whether a window was stated and whether the buy quantity was chosen on purpose.
Can I convert accidental backorders into preorders? Partially. You can't change history, but you can recover: email affected customers with a real date based on your supplier's delivery history, offer the choice to wait or refund, and fix the underlying cause (toggle, count, reorder timing) so the next dark period is planned instead of leaked.
Should I allow backorders on my bestsellers as a policy? Only if the three conditions hold: the window is published and honest, an inbound PO is actually in transit, and the number of open orders stays within what you can buy. Without those, backorder-allowed is overselling with better branding, and it burns the trust preorders are supposed to build.
Do preorders count toward my sales numbers? Yes — Shopify records preorder sales as orders at purchase time, which inflates current-period sales and deflates future-period sales when they fulfill. Keep preorders in a separate fulfillment view so your velocity and reorder math isn't distorted by orders that couldn't ship.
Next step
Open your unfulfilled orders list today and filter for zero-inventory SKUs. Every order there is either a preorder or a backorder — apply the three-question test to each SKU. The backorders need a date-and-apology email this week; the preorders need their cap and toggle reviewed before the next restock lands.