Multi-leg Shipments
A real import move is factory → export drayage → origin port → main vessel → (transshipment) → destination port → import drayage → DC. Qubere models it as one canonical leg structure both apps read from — with a per-leg document checklist, rule-based route inference from the paperwork, and a journey ribbon that never collapses the whole thing into one status.
Phase 1 shipped (PR #107). Not in scope: real-time carrier-tracking integrations, last-mile parcel legs, converging the TMS freight-ops movement model onto ShipmentLeg.
The problem
"It can't tell me 'the ocean leg is missing its master bill' vs 'the import leg is missing its delivery order' — it's one pile linked to the shipment."
No per-leg docs
"The customs team and the freight team show different leg counts for the same container — different pipelines, never reconciled."
Two leg models
"The ribbon says 'Arrived.' The import drayage hasn't started. And 'arrived at port' is not 'released by customs.'"
Flattened status
How Qubere addresses it
The journey ribbon
The full end-to-end route: per-leg status, per-leg document completeness, per-leg ETA. No collapsing a multi-leg shipment into one status. And the customs rail is independent — an arrival never implies a release.
Per-leg document checklists
Each leg has stable document slots — booking confirmation, shipping instructions on the export leg; master bill on the ocean leg; arrival notice, delivery order on the import leg; POD on the final leg. One document can fill a slot on more than one leg.
Rule-based route inference
From the documents on a shipment, Qubere proposes leg count, mode, endpoints, sequence, and the per-leg document set. Deterministic (rules-v1), idempotent (keyed on a SHA-256 of the inputs), and it never invents a carrier or vessel it can't derive — those stay null for the broker to confirm.
Why this is the "tech advanced" story
The independent customs rail means the ribbon will never let "arrived at port" masquerade as "cleared." For a customer running Qubere for customs and freight, the leg count is the same on both sides — because it's the same data. Most competitors keep two disagreeing models and a status that lies.
Objection handling
| "Do you integrate with carrier tracking / ocean visibility?" | Not in this phase. Inference and the ribbon consume whatever tracking events already arrive on the shipment. Adding visibility providers is a defined next step, not a current capability. |
| "How accurate is the inference?" | Deterministic rule logic, not a model. It proposes structure and checklists from document types, port pairs, and reference numbers, and is conservative — anything it can't derive is left blank for you. A head-start, not an autopilot. |
| "Can one container split into multiple downstream shipments?" | Sub-shipment splitting / one-to-many is explicitly a non-goal for now. |
The close
Next step: bring a recent multi-leg move with its document set. We run the inference live and you check the proposed route and checklist against reality.
Full detail: docs/apps/tms/sales/multi-leg-shipments.md