Preorders and Backorders: How DTC Brands Fulfill What Isn't in Stock Yet
Selling stock you don't have yet is a fulfillment problem long before it becomes a customer service problem. Here is how preorders and backorders actually move through a DTC operation.
Most direct-to-consumer brands sell something they don't physically have at least a few times a year. A hero SKU sells out three weeks before the replenishment container lands. A new colorway goes live for preorder to gauge demand before the purchase order is placed. A supplier slips, and 400 open orders sit waiting on one carton.
The decision to take the order is a merchandising call. Everything after that is a fulfillment problem, and it is the part that usually gets designed last.
Preorder and backorder are not the same thing
They get used interchangeably, and they behave very differently on the warehouse floor.
A preorder is a planned sale of inventory that does not exist yet. You know roughly when stock arrives, you have set a ship-by expectation at checkout, and demand accumulates in a queue you control.
A backorder is an unplanned overshoot. The item was sellable, inventory hit zero, and orders kept coming — usually because the channel's stock count lagged behind reality.
The operational difference matters: a preorder queue is something you build on purpose and release deliberately. A backorder queue is something that happens to you, and it always arrives mixed in with normal same-day orders.
Decide what happens to the rest of the cart
The single most consequential setting is what your system does with a mixed order — one in-stock item, one that isn't.
| Approach | What the customer gets | What it costs you |
|---|---|---|
| Hold the whole order | One shipment, when everything is ready | Waiting customers, more "where is my order" contacts |
| Split shipment | The available item now, the rest later | Two picks, two cartons, two parcel charges |
| Cancel the unavailable line | The rest ships, the missing item is refunded | Lost revenue on a sale you already won |
There is no universally right answer, but there is a wrong one: leaving it undefined, so the warehouse decides case by case. That is how a brand ends up paying for split shipments on $18 orders without ever choosing to.
A reasonable default is a value threshold — split when the ready portion is worth shipping on its own, hold when it isn't — set as a rule rather than a judgment call.
Give the queue a release plan, not just a date
When the container lands, a preorder backlog does not go out on its own. Someone has to decide the release order, and the warehouse has to be able to execute it without hand-sorting.
Things worth settling before receiving day:
- Sequence. Oldest order first is the fair default and the one customers expect. It only works if order date, not import date, drives the pick sequence.
- Allocation split. If 600 units arrive against 500 preorders and live demand, decide up front how much is reserved for the backlog versus released back to the storefront. Otherwise the sales channel quietly eats the queue.
- Receiving priority. Preorder stock should be flagged inbound so it gets put away and made available first, not stacked behind routine replenishment.
- Throughput. Releasing 500 held orders at 4pm creates a pick wave that competes with the day's normal volume. Splitting the release across two days is usually less disruptive than a single-day flood.
This is where accurate reorder discipline pays for itself — the deeper mechanics of buffer sizing are covered in our piece on safety stock and reorder points.
Keep the promise honest at checkout
Backorders generate support tickets mostly when the store said one thing and the shipment did another. A few practices keep the gap small:
- State a ship window, not a delivery date. What a fulfillment operation controls is when the parcel leaves; transit is the carrier's.
- Put the window on the product page, in the cart, and in the confirmation email.
- Send a message when the date moves, before the original date passes. A proactive update costs one email; a missed date costs a ticket and often a refund.
- Flag preorder lines on the packing slip so the warehouse doesn't treat a deliberate hold as a picking error.
Watch the channel sync interval
Most unplanned backorders trace back to one thing: the storefront's available quantity was stale. If inventory syncs every 15 minutes and a flash promotion moves 40 units in 10, the channel will sell stock that is already gone.
Two guardrails handle most of it. Hold a small buffer quantity back from the sellable count on fast movers, so the sync lag has room to be wrong. And treat sync failures as an alert, not a log entry — a feed that silently stopped updating overnight is the most expensive quiet failure in ecommerce operations. Brands running several storefronts at once should also read how multichannel inventory allocation splits stock without overselling.
Questions worth asking your 3PL
Before the first preorder goes live, confirm the operation can actually do what your storefront is promising:
- Can orders be held at the warehouse without being cancelled or aging out of the queue?
- Can a held batch be released in order-date sequence?
- Are split shipments a configurable rule or a manual decision?
- Can inbound stock be flagged for priority putaway against a waiting queue?
- What does the reporting show for open backorder age — and can you see it without asking?
A fulfillment partner that can answer those five questions concretely will handle a sold-out launch far better than one that treats every held order as an exception. If you are building this into a growing DTC operation, our DTC fulfillment services page covers how these order flows are set up day to day, and the team is glad to walk through your specific channel mix.
