The handoff is the product

Most supply chain software is good at its own job. The ERP knows the purchase order. The WMS knows the stock. The TMS knows the movement. Ask any of them what happened between those jobs and the answer is a project. That space between systems is where the first mile lives.

Tasks versus handoffs

A task is work inside a system: create a PO, receive a pallet, book a container. A handoff is the transfer of a record from one party or system to the next: the PO reaching the supplier, the pack reaching the forwarder, the booking reaching the container, the container reaching the leg. Tasks are well served. Handoffs are usually not served at all.

The distinction matters because handoffs fail differently. A task failure is visible inside the system that owns it, with an error and an owner. A handoff failure is silent: the pack was correct, the booking was correct, and the two never met. Each system can prove it did its part. None can prove what happened between them.

The four handoffs that decide the first mile

Across retail import, the same four handoffs recur. The PO has to reach the supplier as a record the supplier can pack against, not a PDF to interpret. The packed cartons have to reach the booking with their SSCC identity intact. The booking has to reach the container with its cartons and mode attached. The container has to reach the leg chain with its vessel, voyage and seal, and the leg has to write events that the whole chain can see.

Every one of those is a place where a copy is made, a field is dropped, or a document is retyped. The mistakes are not exotic. They are the boring ones: a quantity that changed in the copy, a destination that was right in the PO and wrong in the booking, a carton that exists physically and not in the record.

What a handoff needs

A handoff needs three things: identity, state and evidence. Identity means the same object is recognised on both sides, which is why the SSCC matters. State means the receiver knows what condition the object is in, not just that it exists. Evidence means the transfer itself is recorded, with who accepted what and when.

A file transfer satisfies none of the three. It moves bytes. It does not establish that the supplier's carton is the forwarder's carton, or that the booking the CFS received is the booking the supplier made. The evidence of the handoff is an email thread, which is to say no evidence at all.

Integration is not a handoff

Integrations connect systems. Handoffs connect records, and the two are not the same. A perfect API between the ERP and the TMS can still drop the carton identity if neither system models the carton. The pipe is fine. The object is missing.

This is why integration projects so often end with a reconciliation dashboard. The dashboard is honest: it shows the places where the copies disagree. But it is also an admission that the handoff has no owner, so the business has hired people to watch it.

The alternative is to make the handoff a first-class part of the record: the same chain of objects, linked, with the state transitions written as they happen. The product is not any one node. It is the fact that the nodes are connected.