Map order and material flow

A supply chain can look like a single line: a customer orders a product, someone buys it, and a carrier delivers it. In practice, three things move separately. The physical product changes location and custody. Information moves through order, inventory and shipment records. Decisions determine when a team may promise, buy or release goods. If customer service sees “shipped” while the carrier has no recorded handover, the box is not necessarily missing. The system may have changed status before the physical transfer. A specialist starts by making these flows visible rather than guessing the cause of delay.

An “event” is a step that can be identified: order received, stock confirmed, purchase order created, goods physically received, units picked, carrier handover or proof of delivery. Useful event fields include a shared order or item identifier, a time with time zone, location, recording party, quantity and unit, and status. Not every event needs every field, but missing common identifiers prevent confident joins. GS1 traceability distinguishes a critical tracking event from the data that describe it. We use that distinction to organize a record; the fictional example is neither an official GS1 implementation nor a statement of law.

Start with one customer order and a stable identifier. Work backward to the source of available units: distribution-center stock, an expected supplier receipt or production. Give each node three parallel lines: “Product: where is the quantity?”, “Information: what does the record show?”, and “Decision: who may commit or release it?” Put an expected date on each arrow, then compare it with observed events. SCOR separates the connected Plan, Order, Source, Transform, Fulfill and Return processes. It is a useful process map, but the location of a step in a particular organization may differ. A process name does not prove that an event occurred.

The map exposes waiting time between teams. Suppose a supplier confirmed dispatch on Monday and a distribution center recorded receipt on Wednesday. Those events alone do not prove that transit took two days. Physical receipt may have occurred Tuesday, with late entry into the system. Record “two calendar days observed between dispatch confirmation and receipt entry,” then request a carrier handover record or gate scan before assigning the delay to transport. Normalize time zones before subtracting timestamps. If the purchase order says 120 cases and the receipt says 1,200 eaches, apply the approved unit conversion before comparing quantities. Direct comparison creates a false shortage.

Consider a fictional lamp retailer. Customer order O-417 asks for ten lamps on Monday morning. The system reports “10 available” at the distribution center, but a shelf count shows eight. A receiving sheet records four more lamps arriving Monday evening and not yet posted. There may be 12 physical units if all four pass receipt checks and are not reserved, but that is not automatically 12 available-to-promise units. Check acceptance, location and competing reservations first. The specialist identifies the contradiction and asks the inventory owner to reconcile it; the specialist does not adjust the balance without authority.

Map O-417 as order → commitment check → allocation → shelf pick → carrier handover → delivery evidence. The four incoming lamps follow a separate supplier-to-inventory path that meets the order path only after accepted receipt. The output is more than a tidy diagram: an event table that shows evidence, source and gap. “10 available” is a system statement, “eight on shelf” is a physical observation, and “four pending acceptance” is an intermediate state. A promise of ten requires reconciliation or an assured alternative. If the customer's date is near, escalate the risk to the authorized service owner with two explicit options: ship eight if split delivery is acceptable, or defer the commitment until receipt is accepted.

A second worked check uses purchase order P-88 for 40 cases and a warehouse record for 400 eaches. The approved pack definition is ten eaches per case. Conversion gives 40 case-equivalents received, so the two internal figures show no apparent quantity difference. Yet the carrier's handover document lists only 38 cases. That conflicts with the internal count. Do not choose whichever number seems more plausible. Inspect package labels, the receiving record and whether two cases came from another source or a counting error. Pending that check, keep the disputed amount out of promiseable stock and log the exception, subject to the organization's own policy. The example shows why the map needs item identity, unit and evidence as well as arrows.