These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Kanban Replenishment
- Features
- Order lines
Order lines
Compare ordered, allocated and shipped units at the line that created demand.
OverviewMy Customer Orders×
SCM with Kanban Replenishment · Order lines
New
My Customer Orders
Customer orders
| Record number | Subject | Status | Promised date | Owner | |
|---|---|---|---|---|---|
| CO-44326 | Draft co-616 | Draft | 14 Oct | ||
| CO-31421 | Confirmed co-408 | Confirmed | 26 Oct | ||
| CO-63331 | Allocated co-381 | Allocated | 27 Oct | ||
| CO-89233 | Part shipped co-338 | Part shipped | 15 Oct | ||
| CO-58157 | Shipped co-797 | Shipped | 16 Oct |
6 of 6 records
Draft co-616Customer orders · CO-44326
DraftPromised date14 Oct
What you can do
Read the quantity behind the order
An order can be on the right customer account and still have the wrong replenishment quantity. Order lines hold the item code, line number, ordered units, allocated units and shipped units. The Order Coordinator uses them to judge how much demand remains before entering the requested units on a pull card. A promised date on the parent order gives the line its service context.
Suppose one customer order has a line with units already shipped and another line still waiting for stock. A new empty-bin signal should be tied to the order whose remaining demand is being served. Staff can compare the line quantities against the signal’s requested units and any dated fulfillment events. The signal links to the parent order, so the exact line behind a request should be agreed in the operating handoff.
How the work is organized
- Line identity. The line number and item code separate demand within one order.
- Progress quantities. Ordered, allocated and shipped units show what remains to examine.
- Commercial context. Unit price and tax belong to the line while the parent carries the order total.
Keep quantity language consistent across products. The product catalog has a base unit. Decide whether incoming order lines use that unit or need a documented conversion before importing them. Otherwise a requested unit count on a signal can look plausible while meaning a different physical quantity.
What to agree during setup
Choose the line numbering convention, item code source and policy for partial shipment. Reconcile every imported line to one parent order. Check whether a catalog product with the same item code is active before using its standard price as context. The line’s commercial price may differ from the product’s standard price, so do not overwrite one with the other.
Agree how the team records allocation and shipment progress. Dated fulfillment events show an event type, quantity, product and external event identifier. Use the event trail when a line-level figure changes. A physical pick or shipment should be evidenced by the appropriate event; the line totals alone are a summary for follow-up.
Check the handoff on an actual case
Choose a pilot order with partial fulfillment. Read its line quantities, then compare the dated events for the same parent order. Ask the Order Coordinator to explain the remaining quantity before preparing a signal. If another event arrives with a repeated external event identifier, review that source event before changing progress again.
Next, examine the order through the Operations Overview. The unshipped-unit figure should send staff back to the correct order and line. The Auditor should be able to trace any difference through the linked events without changing the order. This rehearsal catches mismatched item codes and quantity units early.
What your team sees
- Order Lines — Line quantities show remaining demand under each customer order.
- Operations Overview — Unshipped units lead staff to the parent order.
Follow the work through
What it keeps track of
Data model- Order lines
- Order lines under a customer order, carrying planned effort, owner and progress rollups.
- Customer orders
- Customer orders: the commercial container that drives replenishment, with owner, promised date, net amount and lifecycle status.
- Products
- Stocked products and their standard USD prices.
- Fulfillment events
- Dated fulfillment events promised against a customer order, with outcome status and owner.
- Replenishment signals
- Kanban replenishment signals: the pull card that triggers replenishment work for an order line, with priority, dates and state.
Who uses it
Permissions- Order Coordinator
- Maintains operational line progress.
- Auditor
- Checks the linked event trail.
- Order Reviewer
- Uses the line and order revision when examining a request.
Set up SCM with Kanban Replenishment your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.