NEXALYPLANNER JOURNAL

How to Track Partial Shipments and Backorders

Track customer-order shipments by order ID, line ID and shipment reference. Use a worked backorder ledger to keep outstanding units and next actions visible.

NexalyPlanner Journal · Published October 11, 2026

Packing desk with blue mugs in an outgoing parcel and additional mugs on a shelf for a later shipment.
Illustration: record each dispatch separately while keeping outstanding items on the original order.

To track a partial shipment, keep the original customer order and add a separate record for each dispatch. Count shipped units against the ordered quantity for each SKU. The units still owed stay open until they ship or the customer agrees to cancel them.

A backorder is an unfulfilled customer commitment waiting for stock. A partial shipment describes what has already left your business. An order can have both: some units dispatched and the remaining units backordered. This guide provides copyable tables, not a downloadable workbook or a live carrier tracker.

Start with the small-business order tracking guide if you have not yet created stable order and line IDs.

Keep three linked records

Use an order-line table for the customer commitment, a shipment table for dispatch events and an open-unit review for outstanding work. Keep the same order ID and line ID across all three. One order with two parcels is still one customer order.

RecordFields to keepWhat it answers
Order lineOrder ID, line ID, SKU, original ordered units, agreed cancelled units, promised dateWhat does the customer still expect?
Shipment eventShipment ID, order ID, line ID, date, shipped units, dispatch referenceWhat actually left, and when?
Open-unit reviewOutstanding units, stock status, owner, next action, review dateWhat needs work now?

Use one shipment-event row per line in each dispatch. If SH-501 contains two SKUs, it needs two rows sharing the shipment ID, with distinct line IDs and quantities. Do not repeat the full order quantity on each dispatch.

Calculate outstanding units by line

Outstanding units = original ordered units − cumulative shipped units − agreed cancelled units

Check that all quantities use the same unit. Three packs and three individual items are different commitments. Cancelled units in this calculation are units cancelled before shipment. A returned shipped item needs a separate return record; do not also count it as an unshipped cancellation.

If the result is negative, investigate duplicate events, overshipping or an incorrect cancellation. Do not silently hide the discrepancy by flooring outstanding units to zero. Returned goods and replacement shipments require separate links to the original shipment so they do not obscure the initial commitment.

Work a two-parcel example

Fictional order ORD-205 has five blue mugs under line L1. The customer agrees that three can ship now and two later. No units are cancelled.

EventShipmentUnits in this dispatchCumulative shippedOutstanding
Order confirmedNone005
First dispatchSH-501332
Second dispatchSH-508250

The first dispatch makes the line partially shipped. It does not make the order complete. Store each parcel reference beside its event, and keep the two outstanding mugs on the working queue. Zero outstanding units means this merchandise commitment is fulfilled; it does not prove delivery or payment settlement.

Alternative outcome: after SH-501, the customer agrees to cancel one remaining mug. Record one cancelled unit and the agreement reference. Outstanding becomes 5 − 3 − 1 = 1. Shipping the last mug then closes the merchandise commitment. Keep the refund review separate from the shipment count.

Correct dispatch events without losing the history

Choose a unique shipment ID before recording the dispatch. When one parcel contains several lines, identify an event by shipment ID plus line ID. Review that pair before entering another row: importing or copying the same event twice would overstate shipped units.

Keep draft packing rows out of cumulative shipped quantities until dispatch is confirmed. A printed label or a packed box is not, by itself, proof that the parcel left your business. Record the confirmation reference you use for your operation.

If SH-501 was entered as four mugs but only three left, preserve the original entry and its correction note. In a manual event ledger, mark the incorrect row as superseded and add the corrected three-unit row. Sum only confirmed active shipment rows. The corrected outstanding quantity is two, not one; do not add the correction as another shipment on top of the original.

Before closing the line: verify the SKU and units, unique dispatch events, agreed unshipped cancellations and the remaining customer commitment. Check delivery and payment separately.

Review the backorder queue before promising dates

For every outstanding line, record the missing SKU, units owed, supplier or stock follow-up, owner and next review date. Keep the original customer promise, the latest estimate and the customer-approved revision in separate fields. An estimated restock date is not a confirmed dispatch date.

When new stock arrives, confirm usable quantities before allocating it. Do not assume one supplier receipt covers every waiting order. Compare commitments SKU by SKU with the free Reserved vs Available Stock Planner. It is a manual stock snapshot, not a backorder ledger, and it does not import this table or synchronize store inventory.

For supplier deliveries into your business, use the purchase order tracking guide. Customer shipments out and supplier receipts in need different records even when both are called partial deliveries.

Send a specific customer update

A useful update identifies the order, the dispatched items, the remaining items and the next date you will confirm progress. Use a parcel reference only for the parcel actually dispatched. Do not promise that the remaining units are on their way when they are still waiting for stock.

Example: “For ORD-205, three blue mugs were dispatched under SH-501. Two remain outstanding. We will confirm the restock position on October 16.” Replace the fictional date and quantities with verified records. Agree any split-delivery costs or revised arrangements with the customer before proceeding.

Test your working method before using the full queue

Enter the five-unit example, then record dispatches of three and two units. Check that cumulative shipped becomes five without creating a second order or duplicating its payment. Next, test the one-unit cancellation alternative and confirm that one unit remains outstanding.

The paid Sales Management System provides a broader offline orders, sales and stock workspace. Review its setup guide and temporary preview before choosing it. This article's shipment-event table is a manual example, not a claim that the app has a dedicated backorder or split-shipment module.

Common questions

Should I create a new order for the second parcel?

Keep the original order ID and add another shipment event. If your platform creates linked fulfillment records, preserve those references. A second parcel should not duplicate the customer commitment or payment.

Can paid orders still be backordered?

Yes. Payment and fulfillment are separate facts. Keep outstanding units visible even when the order is paid in full.

What if the customer cancels the remaining quantity?

Record only the agreed unshipped cancellation. Review money and reserved stock separately using the cancelled-order stock release workflow.

Platform reference

Shopify's individual fulfillment documentation describes fulfilling part of an order with selected quantities and separate shipment tracking. That is platform-specific guidance; the manual ledger above is our own worked example. Reviewed October 11, 2026.

Start with an editable order-line record

The free small business order tracker CSV provides ordered, shipped and cancelled quantity fields. For several parcels on one line, keep a separate shipment-event ledger and reconcile its shipped total to the order line; do not repeat the full paid amount for each parcel.