Table of Contents
The Silo Problem: Why Visibility Breaks
A typical cross-border order touches 7+ systems and 12+ stakeholders:
CRM / Opportunity
CLM / Terms
ERP / PO
Portal / Email
TMS / Forwarder
Broker / ABI
WMS / Receiving
ERP / AP / AR
Each system has its own status codes, data model, and update cadence. The "truth" exists nowhere — only fragments. Customer asks "where's my order?" and you check 4 systems, make 3 calls, send 2 emails. By the time you answer, the status has changed.
The Complete Order Lifecycle: 10 Stages
True visibility means tracking every stage with granular milestones:
| Stage | Key Milestones | Data Sources | Typical Blind Spots |
|---|---|---|---|
| 1. Order Entry | PO created, acknowledged, scheduled | ERP, Supplier Portal | Supplier acknowledgment delay |
| 2. Production | Material ready, WIP, finished, inspected | Supplier MES, Quality | No visibility into supplier floor |
| 3. Pre-Shipment | Packed, docs ready, booking confirmed | Supplier, Forwarder | Doc completeness, booking gaps |
| 4. Export | Loaded, sailed/departed, VGM filed | Carrier, Terminal | Rolled containers, blank sailings |
| 5. In-Transit | Port events, transshipment, ETA updates | Carrier API, AIS, Terminal | Transshipment delays, port congestion |
| 6. Arrival | Discharged, available, exam status | Terminal, Customs | Customs hold, exam queue |
| 7. Clearance | Entry filed, released, duty paid | Broker, ABI, CBP | PGA holds, valuation queries |
| 8. Inland | Drayage, rail, truck, DC arrival | TMS, Carrier, GPS | Chassis shortage, rail dwell |
| 9. Receiving | Unloaded, counted, inspected, putaway | WMS, Quality | Qty/quality mismatch, no ASN |
| 10. Settlement | Three-way matched, invoiced, paid | ERP, AP, Bank | Invoice mismatch, payment hold |
The Orchestration Layer: Connecting the Dots
You don't replace all 7 systems. You add an order orchestration layer that:
- Ingests events from every system via API, webhook, EDI, email parsing, portal scrape
- Normalizes to a canonical order event model (stage, milestone, timestamp, location, party, status)
- Correlates events to the master order record (PO + line + shipment + container)
- Computes derived state: current stage, next milestone, predicted ETA, risk flags
- Publishes real-time views via API, dashboard, webhook, mobile push
Canonical Event Schema (Simplified)
{
"orderId": "PO-2026-04521",
"lineId": "PO-2026-04521-001",
"shipmentId": "SHP-77841",
"containerId": "MSCU1234567",
"event": {
"type": "MILESTONE",
"code": "VESSEL_DEPARTED",
"stage": "EXPORT",
"timestamp": "2026-08-10T14:32:00Z",
"location": { "unlocode": "CNSHA", "name": "Shanghai" },
"party": { "type": "CARRIER", "id": "MSC", "name": "MSC" },
"details": { "vessel": "MSC GINA", "voyage": "G423E", "nextPort": "USLAX" }
},
"derived": {
"currentStage": "IN_TRANSIT",
"predictedEta": "2026-08-24T18:00:00Z",
"riskFlags": ["TRANSSHIPMENT_TIGHT"]
}
}Predictive ETAs: From Reactive to Proactive
Carrier ETAs are optimistic. Terminal ETAs are conservative. AIS data is noisy. The orchestration layer combines multiple signals:
Carrier Schedule
Published proforma, updated weekly. Baseline.
AIS / Vessel Tracking
Real-time position, speed, heading. Detects diversions, slow steaming.
Terminal Operations
Berthing window, crane assignment, yard density. Ground truth.
Port Congestion Index
Anchorage queue, berth occupancy, dwell trends. Predictive.
Historical Patterns
Lane-season-carrier actuals vs. published. ML calibration.
Predictive Model Output
- P10 / P50 / P90 ETA — probabilistic range, not single date
- Delay probability — % chance of >3 day / >7 day delay
- Root cause attribution — carrier, port, customs, weather, transshipment
- Confidence score — data quality / model certainty
Real-World Impact
Importer of automotive parts reduced safety stock 22% after switching from carrier ETA to probabilistic P50 ETA — because they could trust the prediction and plan receiving labor / line feed accordingly.
Stakeholder Views: One Source, Many Lenses
The orchestration layer serves tailored views without data duplication:
| Role | Key Questions | View |
|---|---|---|
| Sales / CSR | "When will my customer get it?" "Can I promise Friday?" | Customer-facing tracker, promised date vs. predicted, delay alerts |
| Procurement | "Is supplier on track?" "Do I need to expedite?" | Supplier performance, production milestones, PO risk heatmap |
| Logistics | "Which containers need action?" "Bookings vs. actuals" | Container dashboard, exception queue, carrier scorecard |
| Customs / Compliance | "Any holds?" "Docs complete?" "Entry status?" | Clearance timeline, PGA flags, duty estimate vs. actual |
| Warehouse | "What's arriving today?" "Dock doors?" "Labor needed?" | Inbound schedule, ASN matching, receiving queue |
| Finance | "When does liability transfer?" "Accrual timing?" | Incoterm transition points, invoice matching readiness |
| Executive | "OTIF trend?" "Exceptions aging?" "Working capital?" | KPI dashboard, exception aging, cash-to-cash cycle |
Exception Management: Automate the Routine, Escalate the Rest
95% of orders flow normally. Visibility pays off on the 5% that don't.
Automated Exception Detection
| Exception | Detection Logic | Auto-Action | Escalation |
|---|---|---|---|
| No supplier ack (48h) | PO sent, no acknowledgment event | Reminder to supplier, alert buyer | Buyer + manager (24h) |
| Production delay | Milestone missed > 2 days | Request recovery plan from supplier | Procurement lead (48h) |
| Rolled container | Container not on loaded vessel manifest | Re-book next sailing, notify logistics | Logistics manager (immediate) |
| Customs hold | Entry status = HOLD/EXAM | Alert broker, request docs | Compliance officer (4h) |
| ETA shift > 3 days | Predicted ETA moves > 72h | Recalculate inventory impact | Planner + Sales (24h) |
| Qty/quality mismatch | GRN qty ≠ PO qty or fail inspection | Create discrepancy case, notify supplier | Quality + Procurement (24h) |
Exception Resolution Workflow
- System creates case with full context (order, shipment, events, predicted impact)
- Assigned to owner via RACI matrix (role-based, not person-based)
- Owner sees recommended actions (re-book, expedite, split, cancel, substitute)
- Action taken → system tracks, updates prediction, notifies stakeholders
- Resolution closes case → root cause tagged → feeds prevention analytics
Unify Your Order Visibility
GlobalTradePro's Order Orchestration module connects ERP, TMS, WMS, Customs, and Supplier Portal into a single real-time view.
Request Order Visibility Demo