Backorder management: reconcile orders to incoming stock

Accepted orders need a recoverable promise, a visible allocation rule, and a record of what changed when supply moves.

Kartik Deshpande··5 min read

A backorder is an accepted order for goods that cannot yet be supplied from available stock and remain due for later fulfillment. Managing it means keeping the unfilled order quantity tied to credible incoming supply, a stated allocation rule, and the customer’s current promise. Record partial shipments and cancellations so the queue shows what is still owed rather than the original order amount.

A stockout describes unavailable inventory; a backorder records demand the business has accepted despite that shortage. The stockout investigation addresses why usable goods were unavailable. The work here is recovering accepted orders without assigning the same incoming units to several customers or leaving an obsolete delivery date in the sales record.

Build the queue from open order lines

For each line, retain the order identifier, item revision, fulfillment location, ordered quantity, fulfilled quantity, canceled quantity, and remaining quantity. Keep the customer’s requested date separate from the accepted promise (including any approved revision). Include the extraction time so the operator can tell a current balance from a stale export.

NetSuite’s backorder explanation distinguishes accepting an order for later fulfillment from showing an item as out of stock. It also describes customer notification and fulfillment after supply arrives. Your own payment, cancellation, and shipment terms still control the customer commitment; a status label does not supply those terms.

State how the queue handles partially filled lines, approved substitutions, and canceled orders. If an order was for 30 pieces, 10 shipped, and five were canceled, the remaining obligation is 15 pieces. Do not use invoiced quantity as shipped quantity without checking the business process, since billing and physical fulfillment can happen at different times.

Match usable receipts to the allocation policy

An open purchase order is evidence of expected supply, not evidence that the stock is available. Keep supplier confirmation, expected arrival, receiving time, inspection requirements, and the location that can fulfill the order. A receipt scheduled for Friday may not be usable for a customer shipment on Friday if quality inspection or transport is still required.

Have the responsible owner define which orders receive constrained supply. First accepted order, contractual priority, customer class, and approved expedites are different policies. Preserve any exception approval and the orders displaced by it. Customer service should not promise a receipt allocation that purchasing or fulfillment has already committed elsewhere.

The available-to-promise article covers the dated availability calculation. A recovery queue should consume its accepted allocations once, with the appropriate item and location keys. If another system already reports availability net of commitments, subtracting the same commitments again would understate the supply left for the queue.

Keep supply evidence connected to the customer promise
Confirm supply
Apply allocation
Record promise
Changing a receipt date should expose the affected order lines before a replacement promise is accepted.

Allocate a partial receipt without hiding the shortage

Assume a hypothetical item with no currently available stock and three accepted backorders at one location. Order A needs 40 pieces, B needs 30, and C needs 20. All quantities are in pieces, no substitute is approved, and the agreed policy gives A priority, then B, then C. The supplier confirms that only 60 pieces of the expected 90 will arrive in the next usable receipt.

OrderOpen piecesAllocation from 60Still unfilled
A40400
B302010
C20020
Total906030

The allocation covers A and part of B. It leaves 30 pieces unsupported by that receipt. Keep B open for ten pieces and C open for twenty rather than reporting both as scheduled because the purchase order has a date. If the remaining supplier quantity lacks a confirmed date, record that uncertainty and give customer service an owner for the follow-up.

Now assume B permits partial shipments but A requires a complete shipment. The allocation still meets A’s condition; the twenty pieces for B can ship under the stated terms once received and released. If B instead requires a complete shipment, its allocation does not by itself authorize a partial dispatch. Record the shipment rule before translating an allocation into a customer message.

Trace one order through its supply records

Use a permitted open-order sample and the receipts and reservations that support its current promise.

Record promise changes and completion evidence

Customer service owns the accepted communication, while purchasing owns supplier confirmation and fulfillment owns release and shipment. Retain the prior promise, revised promise, reason, communication date, and source confirmation. A planned email and a sent message are different states, and neither establishes that a customer accepted a changed delivery term.

Update the queue from completed shipment and cancellation records using stable line identifiers. Keep returns separate from unshipped quantities unless the order policy creates a replacement obligation. Reconcile opening backlog plus newly accepted demand minus fulfillment and cancellation to closing backlog, with adjustments explained. This catches lines that remain open after they were shipped or disappear during an export.

Measure backlog age from a declared date, such as acceptance or the first missed promise. Report those measures with different labels rather than blending them. The fill rate article explains why quantities and order-line measures answer different service questions. Keep a worsening aged queue visible even when new orders make the total service percentage look better.

Where Permute connects the recovery queue

Permute sells connected business data and custom applications. We can bring permitted order, inventory, supplier, and receipt records into a scoped application or recurring review, matching item, location, and order-line references before calculating open quantities.

We can reuse your declared allocation and backlog definitions while preserving source timestamps and unresolved receipts. An order operations manager could inspect which promises depend on a changed supplier confirmation and open the supporting order and receipt records. The scope depends on the available history, connections, permissions, and refresh timing agreed for that review.

Keep shipment and customer commitments under approval

We are not a forecasting engine. A report cannot guarantee an incoming date, approve a substitute, change payment terms, or ship goods. This analytical workflow reads the supplied evidence; any external change needs a supported action, explicit approval, and current permissions. Follow the applicable sales terms and company policy when accepting or revising a backorder.

Manage a backorder as a remaining obligation with a dated supply path. Reconcile its quantity after every shipment or cancellation, then allocate incoming units under a visible policy. Keep unsupported quantities and uncertain dates open for review. Preserve the promise history so the customer and fulfillment records can be checked against the same commitment.

Review an order with a changing supply date

Bring a backordered line and its allocation and receipt records to assess where the promise loses its evidence.

Questions about backordered orders

Is a backorder the same as a preorder?

They can create similar fulfillment work, but the reason for taking the order differs. A preorder is accepted before a planned release or availability event, while a backorder arises when accepted demand cannot be supplied from available stock. Keep the specific terms on the order rather than relying on either label.

Should payment be collected before fulfillment?

That depends on the sales agreement, payment method, and applicable requirements. Keep the permitted payment state separate from the physical fulfillment state. Have the responsible owner confirm the terms before changing collection or refund behavior.

What if there is no confirmed replenishment date?

Keep the order’s remaining quantity visible with an unconfirmed supply date and a follow-up owner. Do not replace the missing confirmation with an internal planning date presented as a promise. Customer service should follow the applicable terms when offering available choices.