Order lines and products

Each order line belongs to a customer order and carries a line number, SKU, ordered units, allocated units, shipped units, unit price, tax and revision. The product catalog identifies the sellable SKU, name, base unit, active state and standard price. Line quantities are the working record for partial fulfillment; the order status gives a concise summary of that work. A shipped quantity should be traceable to the actual shipping event rather than inferred from a status change alone.

• Identify the product. Match each line SKU to the active product and its base unit before allocation.
• Compare quantity stages. Keep ordered, allocated and shipped units distinct so a short pick does not look like a completed shipment.
• Review each revision. A changed line has a revision that the next operation must check before acting.

The same order may contain products with different availability and shipping timing. Fulfillment staff need line-level detail when a parcel contains only part of the order. The customer order can then be part shipped while another line still awaits work. Product standard price helps identify a catalog value, but the line’s own net unit price and tax represent the order economics that should be reviewed for that order.

Define the SKU mapping between the selling channel and product catalog. Match each line SKU to an active product before allocation. Agree whether each channel sends ordered quantities in the product base unit and how a coordinator resolves an unrecognized SKU. Decide who may revise quantity or price after confirmation. A change must retain a clear reason and be checked against the current order and line revisions so an operator does not allocate against an older version.

Choose a representative mixed order for rehearsal: one line allocates in full; another has fewer units available. Inspect the order’s promised date and communicate the partial shipment before marking work complete. The reported unshipped units should follow the difference between ordered and shipped line quantities.

An order has a common item and a slower item. The operator allocates the available units and records the allocation event for the product. Picking confirms what was physically found. The first shipment records only the units actually sent and the order becomes part shipped. The remaining units stay visible on the line. When another shipment occurs, its event and line quantity explain why the order can become Shipped.

Replay the same allocation request using its operation key. The line must not gain another allocation merely because the request was repeated. Change the line revision and try an old request as well: it should surface a conflict for review. This protects the quantity history that operations and customer service will later use to explain the shipment.

• Order lines to reconcile — Ordered, allocated and shipped quantities together for each line.
• Part-shipped orders — Orders with remaining units to investigate.
• Order status board — A status view of drafts, active work and shipped orders.

Allocation to delivery connects line changes with physical events. Order confirmation covers the handoff into fulfillment. Check the data model for the line and product references.