The air cargo industry has been chasing the "paperless" dream for decades. With IATA’s ONE Record now the established standard as of 2026, we finally have what looks like a finish line. We have a single source of truth, a digital thread that connects every stakeholder, and a standardized data model that finally kills off the legacy ghosts of Cargo-IMP.
But here is the hard truth for airline GSAs, freight forwarders, and prime contractors: Visibility is not the same as execution.
Knowing exactly where a shipment is stuck doesn't get it moving. Seeing a data error in a digital master file doesn't coordinate the three different stakeholders required to fix it.
ONE Record is a necessary foundation: it’s the "Layer 2" of transportation execution data. But to actually manage a complex, multi-party logistics environment, you need an Infrastructure-Grade Execution Layer sitting above that data.
The "Visibility Trap": Why Data Standards Aren't Enough
The industry often mistakes transparency for control.
When you implement ONE Record, you gain a clear view of the shipment lifecycle. You see the quote, the booking, and the tracking events in real-time. This is a massive leap forward from the fragmented silos of the past.
However, visibility without a coordination engine is just watching a train wreck in slow motion.
Imagine a high-value pharmaceutical shipment arriving at a gateway. The data says it’s there. But the ground handler is backlogged, the specialized trucker is waiting three miles away, and the GSA doesn't have a structured workflow to trigger the handoff.
The data standard tells you what is happening. It doesn't tell your partners how to execute the next step or hold them accountable for the delay. This is where execution breaks down.
Defining the Layers: Where ONE Record Fits
To understand why your operations still feel fragmented despite better data, we have to look at the 4-Layer Digital Freight Model.
- Layer 1: Physical Assets (The planes, trucks, and warehouses).
- Layer 2: Transportation Execution Data (This is where IATA ONE Record lives. It’s the record of what is moving).
- Layer 3: Commercial Systems (The ERPs, WMS, and TMS platforms used by individual companies).
- Layer 4: Digital Freight Infrastructure (The coordination layer that sits above the systems to manage multi-party workflows).
Most organizations are over-invested in Layers 2 and 3. They have great data standards and robust internal systems. But they lack Layer 4: the infrastructure that plugs all those stakeholders into a single, coordinated execution flow.
At ImEx Cargo, we built Plug-In Freight Ops™ specifically to be that Layer 4. It doesn't replace your ONE Record data; it activates it.

The GSA & Forwarder Gap: Coordination Over Connectivity
For Airline GSAs and large-scale forwarders, the challenge isn't just "connecting" to partners; it’s managing the execution risk between them.
When execution is left to emails, phone calls, and "checking the portal," the benefit of the data standard is lost.
Plug-In Freight Ops™ provides:
- Workflow Standardization: Moving from quote → booking → tracking with automated, enforced handoffs.
- Partner Accountability: Real-time performance tracking that goes beyond just "status updates."
- Audit-Ready Oversight: A centralized coordination layer that captures every decision and handoff for complex logistics-driven projects.
Moving Beyond "Data Points" to "Execution Milestones"
In a traditional setup, a "milestone" is a piece of data: Cargo Received.
In an infrastructure-grade execution environment, a milestone is a coordinated event.
When cargo is received, the system doesn't just update a status. It triggers the next step in the workflow, alerts the next stakeholder in the chain, and validates that all compliance documents are present. If a delay occurs, the coordination layer identifies the bottleneck and provides the tools to resolve it: not just the data to report it.
This is the difference between having a map (ONE Record) and having a Command and Control center (Plug-In Freight Ops™).

Why Plug-In Freight Ops™ is the Missing Piece
We designed Plug-In Freight Ops™ to be a digital execution infrastructure layer. It is designed to coordinate logistics across fragmented, multi-stakeholder environments: the exact environments where ONE Record is most needed but often fails to drive actual movement.
Rather than replacing your existing TMS or your IATA-compliant data feeds, our platform sits above them. It standardizes and manages execution across the full shipment lifecycle.
For organizations managing airline operations or complex infrastructure programs, this provides:
- Reduced Fragmentation: No more chasing updates across five different systems.
- Improved Execution Speed: Automated handoffs mean cargo doesn't sit idle waiting for a manual email.
- Economic Impact Visibility: Easily integrate and track diverse supplier networks within the same execution flow.
The Path Forward: From Standards to Infrastructure
IATA ONE Record is a massive win for the industry. It gives us a common language. But a language is only useful if you have a plan for the conversation.
If your organization is still struggling with delays, lack of partner accountability, or manual "workarounds" despite having better data visibility, you don't have a data problem. You have an execution coordination problem.
We typically address this through a focused pilot. We can map Plug-In Freight Ops™ to your current operation and show you how to turn your ONE Record data into a high-performance execution engine.
Ready to move past just "seeing" your cargo and start coordinating its execution?

