Backorder management: keeping the order when the shelf is empty

It is 4:40 on a Friday afternoon. The sales rep has already promised the customer 40 units, shipping Monday. When the warehouse lead opens the screen, on-hand shows 46 units, but 34 of those are reserved against orders that were confirmed earlier in the week. Actually sellable: 12. For the remaining 28 units there is no purchase order with the supplier and no date anyone can defend. Those 28 units appear on nobody's screen that evening, and two weeks later, when the customer cancels, no one can reconstruct where the promise came from.

Backorder management is the discipline that fills exactly that gap. This article starts with what changes when unmet demand is recorded rather than refused, then defines the moment an order actually becomes a backorder. From there: a decision table for which requests deserve an open commitment, the rules for quoting a date, the fields a backorder record must carry, how allocation works when goods arrive, why marketplaces are a special case, the cash-flow side, the metrics worth tracking, and how to reduce backorders at the root. A short FAQ closes it out.

What actually changes when you record unmet demand?

"We are out of stock" ends a conversation. A backorder turns the same situation into an open commitment: the demand is not refused, it is recorded, and it is fulfilled automatically once goods arrive. The difference shows up in your data long before it shows up in customer sentiment. Refused demand is written nowhere. Two months later, when someone asks why a line sells so poorly, all you have is sales figures — the lost demand left no trace.

Recorded demand, by contrast, produces a signal. Repeated backorder lines against the same SKU tell you the reorder point is set too low or the supplier lead time is longer than the assumption behind it. That makes backorders a purchasing input, not just a customer-service courtesy.

Where the demand came from matters too. An order that drops out of a web cart and an order taken over the phone can be for the same SKU, yet they carry very different cancellation risk. Bringing those channels together is the precondition for telling them apart, and tying order data to the customer record changes who you extend a commitment to and on what history.

At what point does an order become a backorder?

Most of the damage comes from one conflated concept: on-hand stock and available stock are not the same number. You may hold 46 units while part of that is already reserved against confirmed orders. In Rocketly this separation lives in Stock Movements, where receipts, issues, transfers and reservations are distinct movement types and nothing is deleted after the fact — a correction is added as a new movement. The Stock Health Dashboard puts available and reserved quantity side by side, which ends the "but the system said we had them" argument.

The backorder threshold sits against that available figure. Once demand exceeds it you have two options: hold the whole order open, or fulfil partially. Partial fulfilment means shipping the 12 units you have now and leaving an open line for the remaining 28. It splits your shipping cost, but unless the customer needs a complete set it is usually the better trade.

The expensive scenario is demand that quietly disappears. On the web side that shows up as carts abandoned because a size or variant reads as unavailable, and recovering orders that were never completed is the mirror image of backorder logic: one brings demand back, the other keeps it from leaving.

Which orders deserve a backorder, and which do not?

Not every unmet request should become an open commitment. If the lead time is unpredictable, the item is seasonal, or the buyer can switch brands in an afternoon, an open promise damages the relationship rather than protecting it. Rather than leaving that to instinct, tie the call to a few observable criteria.

Criterion	Backorder makes sense	Backorder is risky
Lead time	Supplier has confirmed a date you can defend	Import, customs or production queue is open-ended
Substitutability	Made to spec, brand-committed or project-specific item	Commodity item with five near-identical alternatives
Customer history	Established account with a purchase record	First-time buyer, contact details unverified
Payment terms	Deposit taken or contract in place	Paid in full up front, so cancellation hits cash directly
Required-by date	Customer states a date and it clears your estimate	The need-by date falls before the date you can quote

Read the table as a set of thresholds, not a rulebook. When two conditions from the right-hand column apply at once, a clear no plus a substitute recommendation is usually the more honest answer — and most buyers would rather solve the problem today than wait a fortnight and be disappointed.

What are you really promising when you quote a date?

Dates are the fragile part of any backorder. The date you give a customer is not the date your supplier gave you: goods receipt, quality check, put-away and pick-and-pack all sit between the two. Those steps take a day or two, and a quoted date that excludes them makes you late on every single order.

Second rule: quote a window, not a day. "Ships 17-20 March" absorbs small slippage in the supply chain without turning it into an incident. Third rule: when a date moves, you call the customer — a delay discovered by asking always feels larger than the same delay you disclosed first.

That outreach rarely works through one channel: some buyers never open email, others will not pick up the phone. Meeting customers on the channel they actually use matters more for backorder updates than almost anywhere else, because a missed notification is the most common trigger for cancellation.

The same principle applies to messaging: an update is only useful if it is visible next to the order itself. If a sales conversation running over messaging is not attached to the order record, what you told the customer lives on one person's handset — and nobody can answer for it while that person is on leave.

What fields does a backorder record need to carry?

Keep a backorder as a structured record, not a note in a comment box. The minimum set:

• Item and variant, unfulfilled quantity, original order date
• The shipping window quoted to the customer, and the assumption behind it
• The linked purchase order or expected goods receipt
• Priority: account importance, need-by date, deposit status
• Expiry condition: the date after which the line closes on its own
• The last update sent to the customer, and who sent it

Rocketly's Backorder Management feature holds exactly this record: unmet demand is not discarded, it stays as an open line, and it closes automatically when the goods are received. The question "did that shipment arrive, and who was it for?" goes to the record rather than to somebody's memory. When a supplier moves a date, Order Revision handles the trail: a purchase order that has already been sent can be revised, and each revision is stored with its change summary, so the second date you quoted is traceable to a cause.

Visibility across the team matters as much as the fields. If nobody owns the reply when a customer writes "where is my order", the record does no work. Collecting incoming messages on one team screen is what stops backorder chasers from going unanswered.

Who decides the allocation order when stock arrives?

Three orders are waiting and the delivery covers two. If you have not agreed the rule in advance, allocation goes to whoever opens the screen first. The most defensible default is order date: first in, first served. It is fair, it explains itself, and it ends the argument.

Departing from the default should require a written reason. Legitimate exceptions exist: a customer whose need-by date is this week ahead of one who needs stock next month; an order with a deposit against one without; a partial shipment that keeps a production line running. If the exception is not recorded, the same behaviour becomes arbitrary prioritisation within a few weeks.

For dated goods, allocation is also a question of which batch. Lot / Serial Tracking provides traceability by batch and serial number and issues stock on a FEFO basis, so the units that go to a waiting customer are the ones that have been on the shelf longest.

As delays stretch, complaints stop arriving privately and start appearing in public channels. Running a large backorder queue without a process for questions that arrive in the open means explaining the same delay twice, in two places, with two different answers.

How do backorders work when you sell on marketplaces?

On your own storefront you can make an open commitment. On a marketplace you usually cannot. Handling-time rules, seller-score penalties for late dispatch and automatic cancellation make backorders impractical by design. So the right multichannel strategy is not to push backorders onto the marketplace — it is to pin the quantity you publish there to true available stock.

That requires the number sent to each channel to come from one source. In Rocketly the 16 Marketplace and Store Connectors establish the link and orders land as draft invoices, while stock or product writes only run once mappings are complete and permission has been granted explicitly. The constraint feels restrictive until you notice what it prevents: you never publish stock you do not have because a SKU was mapped to the wrong record.

The more channels you add, the more that single-source question dominates, and it is the most concrete argument for consolidating multichannel orders in one place — you stop maintaining three different numbers for the same SKU in three different seller panels.

Where do backorders sit in your cash flow?

A prepaid backorder looks like money in the bank and is not. That amount is an undelivered obligation, refundable the moment the customer walks away. Plan your open backorder balance as earned revenue and a wave of cancellations makes you spend the same money twice.

Backorders also trigger an outflow on the purchasing side: you pay the supplier to bring goods in, and collection completes only after despatch. The number of days between those two events belongs squarely inside your cash flow planning, and the gap widens exactly as the backorder queue grows.

The opposite failure is just as real: eliminating backorders by holding more stock. That solves the problem with cash and it is usually expensive. Goods sitting on a shelf are capital you cannot use, and every decision about managing working capital looks for a balance between those two extremes. Rocketly's ABC Analysis makes that easier by classifying inventory by value, so you raise safety stock only where the capital is actually justified rather than across every SKU.

Which metrics tell you whether backorders are under control?

Counting open backorders alone is misleading — the number should rise during a promotion. Four measures carry real information:

• First-pass fill rate: the share of orders shipped with no wait at all
• Backorder age: the average and the worst open line, in days
• Promise-kept rate: orders shipped within the first window you quoted
• Backorder-driven cancellation rate: orders abandoned while waiting

The breakdown matters as much as the totals. If the same SKU keeps topping the list, the problem is planning, not supply; if different SKUs rotate through it, the supplier side is the likelier culprit. Rocketly's Supplier Performance view puts order and delivery counts, total spend and average delivery time next to each other, so you measure which supplier holds a date instead of guessing.

Getting those numbers in front of you on a fixed day beats remembering to open a dashboard. A summary that arrives on schedule is the simple habit that stops a backorder queue from growing quietly for a quarter.

How do you bring the backorder count down for good?

Even a well-run backorder process is symptom management. The real work is stopping the same item from running out again. Three parts: a correct reorder point, a realistic lead-time assumption, and early warning.

A reorder point is expected consumption over the lead time plus a safety buffer. As an illustration: an item selling four units a day on a ten-day lead time consumes 40 units before replenishment lands, and the buffer for demand variability pushes the threshold above that. The figures differ by business; what does not is that the threshold should be built from consumption history rather than a hunch.

On the early-warning side, Rocketly's Stock at Risk queue makes this concrete: it prioritises items using demand velocity, available quantity, lead time and safety-stock assumptions, showing which item runs out in how many days and which is already below its reorder point. You can raise a draft purchase order straight from the row, so acting on the warning does not require a second screen. Stock Alerts covers the rest, scanning critical, out-of-stock and overstock conditions every fifteen minutes with in-app and email notifications.

If you sell bundles, the threshold has to be calculated at component level. The Kit / Bundle Product feature computes how many sets are currently buildable from component stock, so "the bundle looked available but one part was out" gets caught before the sale, not after. If you want to try these flows against your own catalogue, you can open a free Rocketly account and walk through the stock and backorder screens with your own data.

FAQ

Is a backorder the same thing as a pre-order?

No. A pre-order is a deliberately opened sales channel for an item that has not launched or whose first batch is still inbound; the buyer knows from the outset that nothing is on the shelf. A backorder happens when an item already on sale runs out, so it is unexpected. The record structure looks similar, but customer expectations and the tone of your communication do not.

Should I take payment up front on a backorder?

It depends on the item. For made-to-spec or hard-to-resell goods, a deposit is a reasonable way to share cancellation risk. For commodity items, full prepayment creates a refund burden the moment you slip. Weigh collection rate and cancellation cost in the same view.

When should an open backorder line be closed?

Write the expiry condition when you open it: if the customer does not reconfirm after a stated date, the line closes itself. Lines left open indefinitely distort reporting months later and, worse, allocate arriving stock to a customer who moved on.

Partial shipment or wait for the full quantity?

If the customer is not using the items as a set, partial shipment is usually better: the open quantity falls and the relationship holds. For assembly or project delivery, split shipments create extra handling at the customer's end, so waiting for the full quantity and quoting one firm date is the better call.