Order lines

An order line carries a line number, revision, SKU and quantity fields for ordered, allocated and shipped units. Net unit price and tax can be kept on the same line. The line belongs to a customer order, so its quantities can be read with the order’s customer, status and promised date. Product records hold the product’s SKU, base unit and standard price; shipment events refer to the product involved.

• Enter demand. Order Coordinator records each line and its ordered units.
• Compare progress. Fulfillment Coordinator checks allocated and shipped units against what was ordered.
• Trace events. Use dated fulfillment events to see when a product was allocated, picked, shipped, delivered or returned.

Line quantities and fulfillment events answer related questions. The line shows the current ordered, allocated and shipped amounts; the event gives a dated record of what occurred. A routing record’s routed units is a separate supplier-side measure. The team should compare these measures during an exception rather than treating them as interchangeable.

Check a line revision before correcting quantities after routing review. The line SKU is text, while a fulfillment event references a product record; staff should confirm that those identities match when they reconcile a shipment.

Choose one SKU format and base unit for each product. Agree how source channels send line numbers and revisions. Confirm who may correct a line after order confirmation, and how that correction affects a route already under review. Decide the rule for a split shipment, where one line is shipped and another remains open. The promised date belongs to the order and should remain visible alongside line progress.

Enter an order with two lines. One SKU has ten ordered units; the other has five. Allocate the first line, then record a shipped event for only part of its quantity. Check the order line progress view against the event history. The open units should still be clear, and the order should be read as partly shipped when appropriate. A supplier acknowledgement should remain a route fact until a separate fulfillment event arrives.

Repeat the case with a return event. Review the dated event and original line values before making a correction. The team needs the product and external event ID to distinguish that return from an unrelated supplier response.

• Order line progress — Ordered, allocated and shipped units for the selected order.
• Shipment events — Product events that explain movement after the line was entered.

Trace shipment evidence and review the model.