# How should an order keep reserved, shipped and billed quantities consistent?

By Sean Everett · October 7, 2026

Represent each stage of the order explicitly, preserve line-level quantities and test partial fulfillment and corrections before relying on a single completion status.

Topics: Order operations · Inventory systems · Workflow design

## Separate a stock commitment from a completed delivery

An order can be accepted before stock is available, reserved before picking and partly shipped before it is fully billed. Define these states and the evidence required to move between them. Make the customer-facing promise reflect what the operation can actually support.

Microsoft’s inventory documentation illustrates an important distinction: a reservation can apply to physical stock or, with the relevant configuration, to items ordered but not yet received. Reserved therefore does not always mean ready to dispatch.

Record which stock, location and order line a commitment applies to. Define how a cancellation or change releases or reallocates it. Check that the same quantity cannot quietly support incompatible promises elsewhere in the workflow.

## Preserve the quantities behind each status

A partial delivery creates several quantities that can differ at the same time: ordered, reserved, shipped, invoiced and remaining. Keep these attached to the relevant lines and events rather than inferring them from one overall order label.

Microsoft’s sales-order overview describes invoices based on delivered packing-slip quantities and separate delivery and invoice remainders. Its workflow can remain open while quantities are outstanding. Use the distinction when deciding what complete means in the product being evaluated.

Test a representative order split across deliveries. Confirm which quantities each invoice covers and what remains to be fulfilled. Include a change to the unfulfilled portion, with explicit treatment of anything already shipped or billed. Have the responsible operations and finance teams agree the expected records.

## Check transitions and corrections end to end

A Microsoft shipment walkthrough shows how one line can be partially shipped while the order remains open. Build similarly concrete acceptance cases for the actual system. A status change should be traceable to the underlying event and quantity.

Include a delayed update, a repeated submission and a correction after downstream work has started. Verify that connected systems converge on the intended result without duplicating stock commitments, shipments or charges. Keep unresolved differences visible to the team that can correct them.

Reconcile the order, inventory and billing views at meaningful checkpoints. Give exceptions an owner and retain a clear account of what changed. The operating goal is a dependable chain of commitments and completed events that customers and staff can understand, including when fulfillment takes more than one step.

## Related reading

- [Microsoft: Inventory reservation behavior](https://learn.microsoft.com/en-us/dynamics365/supply-chain/inventory/reserve-inventory-quantities)
- [Microsoft: Sales orders, deliveries and invoices](https://learn.microsoft.com/en-us/dynamics365/supply-chain/sales-marketing/overview-sales-marketing)
- [Microsoft: Partial sales-order shipment](https://learn.microsoft.com/en-us/dynamics365/supply-chain/sales-marketing/tasks/ship-sales-orders-without-warehousing)
- [Evaluating the complete platform workflow](https://evergences.com/insights/workflow-based-platform-evaluation/)

Source: https://evergences.com/insights/order-inventory-state-integrity/