The Open Logistics Specs are built from two layers:
  • Platform Constructs (this tab) are concepts that any multi-tenant API platform needs, whatever its domain: how requests, IDs, errors and versions work; who the tenants and users are; how providers are integrated; how events, jobs, documents and money flow. Nothing here is specific to shipping.
  • Specification (the first tab) defines the logistics domain on top of them: shipments, rates, tracking, customs, networks, fleets, inventory and the parties involved.
Keeping the layers apart keeps the logistics chapters focused, and makes the constructs reusable by any domain that adopts the same conventions. Some constructs have logistics extensions, which stay in the logistics chapters. Examples: carrier label specs and certification (chapter 25 §6), carrier invoice audit (chapter 28 §2), and the lsp integration interface (chapter 26 §3).