The Physical Economy: A Field Guide › Chapter 6
The industry runs on a stack assembled over fifty years, layer by layer, with each layer solving its buyer's problem and ignoring everyone else's.
| Layer | What it is | Who buys it | Names you'll hear |
|---|---|---|---|
| EDI | 1970s-era standardized messaging (tenders, statuses, invoices) still carrying a huge share of B2B freight data | Everyone, reluctantly | X12 204/214/210 message types; VANs |
| ERP | The system of record for orders and money | Shippers | SAP, Oracle, NetSuite, Dynamics |
| WMS | Runs the inside of the warehouse: inventory, picking, putaway | Warehouses, 3PLs | Manhattan, Blue Yonder, Körber, SphereWMS, dozens more |
| TMS | Plans and buys transportation: rating, tendering, settlement | Shippers, brokers, 3PLs | Oracle OTM, Blue Yonder, MercuryGate, McLeod, Tailwind |
| Visibility | Tracks trucks between facilities | Shippers | project44, FourKites, Descartes MacroPoint |
| Load boards | Spot-market matching | Brokers, carriers | DAT, Truckstop |
| Container lifecycle | Tracking + execution for international containers, ocean through drayage and empty return | Importers, exporters, drayage, forwarders | Gnosis Freight, Flexport |
| Fraud/identity | Carrier vetting and identity assurance | Brokers | Highway, CargoNet, Overhaul |
| YMS / dock scheduling | The gate, yard, and dock doors — the physical interface | Facilities | Opendock (Loadsmart), Conduit, GoRamp, DataDocks, Descartes C3 — and Dock Optimizer |
Notice two things. First, every layer stops at the dock door. The ERP knows the order, the TMS knows the tender, visibility knows the highway — and none of them knows what happened in the fifty feet where freight actually changed custody. The WMS, which does operate inside the building, faces inward toward inventory, not outward toward carriers; it was never designed to talk to a driver.
Second, each layer is sold to a different party, which is why integration is the industry's permanent condition. A mid-sized 3PL might operate its own WMS, three customers' TMS portals, two visibility platforms it's forced to feed, EDI with its largest client, and email for everyone else — per building. This is not an exaggeration; it is Tuesday. Any product that adds an eleventh tab loses. Products win here by absorbing integration pain, which is why our Integration Hub (AI-assisted mapping between all these systems) is not a feature — it's a precondition for being adopted at all.
The dock is the physical API endpoint of a building, and today it's undocumented: no schema, no auth, no rate limiting, no logs. Callers (carriers) integrate by phone. Dock Optimizer is, quite literally, publishing the API — booking is the endpoint, verification is auth, check-in events are the logs, and the multi-party record is the audit trail. Once you see the dock as an interface, the rest of this guide reads as platform economics rather than logistics exotica.
A new generation of software is finally attacking the physical layers, each from its own angle. Opendock (Loadsmart) built the largest carrier-facing scheduling network; Conduit pairs dock scheduling with yard visibility for warehouses; GoRamp leads time-slot management in Europe; Highway rebuilt carrier identity for brokers; and Gnosis Freight — whose Container Lifecycle Management platform runs the international container's journey from ocean sailing through drayage to empty return — proved the defining insight of the wave: execution beats passive visibility. Tracking a thing is a feature; operating the moment it changes hands is a platform. Dock Optimizer applies that same insight at the building itself.
The full field guide by email — plus future deep dives on the physical economy as we publish them.
One email with the guide, and future deep dives from the Conmitto / Dock Optimizer team. Reply to unsubscribe. No drip sequence.