Supply chain visibility becomes useful when a missing or unexpected event changes a decision. A parcel map that refreshes every minute still leaves a buyer exposed if nobody can explain which carton contains the missing SKU or who must resolve an export hold.
For a China-origin operation, design visibility around the handoffs that matter to the shipment. Supplier readiness, warehouse receipt, inspection release, packing, carrier acceptance and destination delivery each need a defined meaning and an evidence source.
Choose the object being tracked
An order number cannot identify everything in a supply chain. One purchase order may arrive in several cartons, and one customer order may leave in more than one parcel. A consolidated movement may contain goods from several suppliers without merging their ownership or product identities.
Create a relationship map between purchase-order line, SKU, lot where relevant, carton, pallet, shipment and customer order. Assign stable identifiers before goods start moving. When the warehouse repacks a carton, record the old-to-new relationship rather than pretending the original carton still exists.
The GS1 Global Traceability Standard distinguishes identifiers for products, logistics units and shipment groupings. The practical lesson is to decide which identity each system is actually reporting.
Write an event contract
For each milestone, specify the event’s trigger, required fields and owner. “Received” might mean a vehicle reached the gate, cartons were unloaded, quantities were counted or stock passed inspection. Those are separate states with different implications for an ecommerce seller.
A warehouse-receipt record could contain the supplier reference, received carton identifiers, SKU quantities, condition exceptions, location and receipt time. An inspection-release record should identify the approved lot and decision. A carrier-handoff event needs the parcel reference and the evidence accepted by the transport process.
Keep correction events. If an operator first records twelve cartons and later confirms eleven, overwriting the original number erases the explanation for an inventory discrepancy. A correction should point to the original event and carry its reason and approver.
Distinguish movement delay from information delay
Consider this illustrative sequence. A carrier accepts a parcel at 16:10, but its message reaches the warehouse system at 20:40. A dashboard using only message receipt time will show a late physical handoff even though the delay was in the data exchange.
Store event time and system receipt time separately. Preserve the time-zone offset, the source system and an external reference that allows the event to be checked. If a source has no dependable physical timestamp, label the information accordingly rather than estimating a scan time.
GS1 EPCIS offers a common model for exchanging visibility events. A small operation can begin with a simpler documented schema, provided that its fields retain consistent meanings across integrations.
Alert on a decision, not every status change
An alert needs a business consequence. Useful triggers include a supplier missing its agreed readiness milestone, a received carton without an inspection decision, or a handed-over parcel without the expected transport evidence.
For each trigger, define the eligible population, review interval, severity, owner and next action. Avoid assigning a single universal time limit to unrelated routes. A missing scan on one parcel channel may require a different investigation from a missing milestone on a sea-air transfer.
Suppress duplicate alerts while keeping their history. An unresolved exception should become older and, where appropriate, more serious. It should not appear as a new problem every time the source sends the same message.
Show confidence and gaps to the customer team
Customer-facing tracking should distinguish confirmed events from planned milestones. If the warehouse has packed a parcel but the carrier has not accepted it, say so. A planned flight or vessel connection is not evidence that cargo traveled on it.
Display the last confirmed event, the next expected decision and the owner of any unresolved exception. When information is unavailable, a clear gap is more useful than a fabricated progress percentage.
Test the visibility design with one deliberately incomplete shipment: a missing supplier reference, a split carton and a late carrier message. The system is ready when the team can trace all three, explain their customer impact and show who resolved them.
Sources and verification links
Operational rules can change. Check the linked primary sources and confirm shipment-specific requirements before booking.