Air cargo has spent decades exchanging shipment information through documents, EDI messages and system-to-system handoffs. In 2026, IATA is pushing the industry toward a different model. Since January 1, 2026, ONE Record has been the preferred method for cargo data sharing.
The important word is preferred. ONE Record is not a global law forcing every airline and forwarder onto one platform. It is an IATA standard designed to give cargo stakeholders a common data model, secured web APIs and a shared view of shipment information.
For ecommerce, that matters because air cargo is often the least visible part of a parcel's tracking history. The parcel can be highly instrumented before export and after domestic injection, while the international linehaul in between is represented by only a few coarse milestones.
What is ONE Record?
IATA describes ONE Record as a data-sharing standard that creates a single-record view of a shipment. Instead of every participant sending its own copy of the same document to the next participant, the model lets authorised parties exchange structured logistics objects through standardised APIs.
The standard has three main technical layers:
- A common data model. ONE Record uses linked-data structures and JSON-LD so different systems describe cargo objects in a consistent way.
- A web API specification. Participants can request and update logistics data through standard interfaces rather than relying only on point-to-point EDI messages.
- A security model. Identity, authentication and access rights are built into the data-sharing framework so a participant sees the information it is authorised to use.
The goal is not one giant central database. It is interoperability between systems that can understand and exchange the same logistics objects.
What changed in 2026?
January 1, 2026 was IATA's target for ONE Record to become the preferred cargo data-sharing method. By March, IATA said airlines representing more than 70% of global air waybill volume were on track for implementation.
That is progress, not universal adoption. A 2025 IATA industry survey found awareness above 70% among respondents but readiness below 50%. IATA also reported more than 30 active pilots, covering use cases such as electronic air waybill submission, shipment tracking, customs status updates and end-to-end data exchange between forwarder and airline systems.
| Old pattern | ONE Record direction |
|---|---|
| Copies of data passed between systems | Shared logistics objects accessed through standard APIs |
| Multiple message formats and mappings | Common cargo data model |
| Point-to-point integration | Authorised ecosystem access |
| Changes can create another document or message | Updates attach to the same logistics object and audit trail |
| Tracking often reconstructed from separate feeds | Tracking can be generated from a more connected operational record |
Why ecommerce makes the problem harder
IATA itself points to ecommerce as one of the pressure points. High-volume ecommerce flows can involve large numbers of house waybills that have to stay aligned with airline master air waybill records across multiple systems and jurisdictions.
A consumer sees one parcel. Air cargo may see that parcel as one piece inside a consolidation. The airline moves the master shipment, while a forwarder, postal operator or ecommerce logistics provider holds the parcel-level relationship.
That hierarchy is why air-linehaul tracking often looks sparse. A flight departure can be known at master-air-waybill level while the consumer tracking system still needs to work out which individual parcels were inside the consolidation and when they became available to the next network.
Does ONE Record fix parcel tracking?
Not by itself.
ONE Record standardises air-cargo data exchange. It does not replace the tracking systems used by postal operators, express carriers or last-mile delivery companies. A parcel still needs to be linked correctly to the cargo objects representing the air movement, and the destination carrier still has its own event vocabulary after handover.
The improvement is upstream. Better-structured air-cargo data can reduce the blind spot between export acceptance and destination injection, provided the parties in the route support the standard and expose the relevant events.
For a tracking platform, that creates three opportunities:
- Better identity resolution. Parcel, house-waybill and master-air-waybill relationships can be represented more explicitly.
- More precise linehaul milestones. Operational events can be consumed from a common model instead of being reconstructed from different carrier messages.
- Cleaner handovers. A destination network can receive richer upstream information before physical arrival, reducing the gap between two tracking systems.
What should logistics teams do now?
Most ecommerce merchants will not implement ONE Record directly. The relevant question is if the forwarders, air-cargo technology providers and logistics partners in their routes are implementing it.
- Ask air-freight partners about ONE Record support. A yes/no answer is not enough. Ask which use cases are live: booking, shipment status, customs, piece-level data or all of them.
- Map identifiers across the route. Know how parcel IDs, house waybills and master air waybills connect. Better upstream data has little value if the identifiers cannot be joined.
- Separate planned from observed events. A richer data model can carry both. Customer-facing tracking should make clear what physically happened versus what is scheduled.
- Preserve raw events. Normalisation is useful, but the underlying cargo event and source should remain available for investigations and exception handling.
- Measure the handoff gap. Track the time between the final air-cargo event and the first destination-carrier event. That is where improved interoperability should become visible.
Why this matters beyond aviation
The wider significance of ONE Record is architectural. Logistics is moving away from sending copies of documents toward exposing structured state through APIs. Parcel tracking has already moved in that direction through carrier APIs and webhooks. Air cargo is now formalising the same idea around a common industry data model.
The difficult part remains the boundaries. Postal standards, private carrier status codes, airline cargo data and marketplace order data still describe different layers of the same physical movement. ONE Record removes one source of fragmentation. It does not remove all of them.
For ecommerce tracking, that is still meaningful. A better-described middle mile gives the systems above it less guessing to do.
Sources & methodology
- International Air Transport Association (IATA) ONE Record programme and technical overview Primary source.
- IATA IATA highlights three priorities for air cargo Primary source.
- IATA ONE Record industry readiness survey and pilot examples Primary source.
- IATA ONE Record Developer Portal ONE Record cargo ontology Primary technical documentation.
