Beyond the PDF: How IATA’s "ONE Record" is Revolutionizing the Air Waybill

IATA ONE Record is an industry data-sharing standard and API model that upgrades the traditional air waybill from a static PDF into a connected, machine-readable shipment record accessible to all authorized partners.

What ONE Record is

ONE Record is an IATA-led initiative that defines a common data model and API framework for air cargo. Instead of exchanging isolated PDF documents and siloed records, ONE Record enables a single, interoperable digital shipment record — a living document that authorized stakeholders can read and update in real time. The concept moves the air waybill (AWB) from a paper or PDF artifact into a distributed, semantically consistent digital object accessible through secure APIs.

Why this matters for the air waybill

The traditional AWB serves three main roles: a receipt for cargo, evidence of contract of carriage, and a document containing shipment instructions and metadata. Historically, these roles were fulfilled with paper forms or scanned PDFs exchanged between shippers, forwarders, carriers, ground handlers, customs, and consignees. That approach creates friction: duplicate data entry, versioning errors, late visibility, and slow customs clearance. ONE Record reduces these frictions by providing:

• Real-time visibility: updates to status, location, and handling events are immediately available to authorized parties.
• Richer data: structured fields for product attributes, handling instructions, compliance data, and attached documents (e.g., certificates, permits).
• Better automation: systems can consume the same structured payloads for routing, customs clearance, billing, and warehouse operations.

How ONE Record differs from e‑AWB

Electronic AWB (e-AWB) replaces the paper AWB with electronic transmission of the carrier’s contract and summary data. e-AWB modernized the title and legal aspects of the AWB but often remained a PDF or simple electronic record exchanged on a per-transaction basis. ONE Record goes further by defining a holistic data model and APIs that represent the entire shipment lifecycle, not just the contract. In other words, e-AWB digitizes the document; ONE Record digitizes the shipment as a connected set of data and events.

Key technical features

ONE Record is built on modern web principles and open standards to maximize interoperability across platforms and providers. Important elements include:

• Semantic data model: standardized field names and structures so different systems interpret the same data consistently.
• RESTful APIs and JSON: machine-readable endpoints for querying and updating shipment records.
• Linking and attachments: the ability to reference related documents, certificates, photos, and location events from the central record.
• Access control and security: role-based permissions, encrypted transport, and authentication mechanisms to ensure only authorized actors can view or change a record.

Practical benefits — examples

Consider a temperature-sensitive pharmaceutical shipment. With traditional PDFs, a consignee might not see temperature excursions until the shipment arrives, or the forwarder might not have an automated alert about a hold at customs. With ONE Record:

• Temperature sensor data can be attached or linked to the shipment record, enabling automated alarms and corrective workflows.
• Customs officials can access validated document attachments (e.g., certificates of origin) directly via the API, speeding clearance.
• Carriers and ground handlers can update status events (accepted, on‑board, off‑loaded) in real time, improving ETAs for downstream processes such as warehousing and last‑mile delivery.

Operational implications for stakeholders

Shippers and forwarders gain consistent, machine-readable data for booking, tracking, and claims. Carriers reduce manual checks and data re-entry. Customs and regulators can perform risk assessments with richer data. Ground handlers and warehouses can pre-plan capacity and resources based on live manifests. In short, ONE Record supports end-to-end coordination rather than point-to-point document exchange.

Implementation best practices

Companies adopting ONE Record should consider a staged approach to reduce disruption:

1. Start with pilot lanes and high-value or time-sensitive cargo where visibility pays off quickly.
2. Map existing AWB fields and internal data models to the ONE Record semantic model to ensure consistency.
3. Integrate through middleware or API gateways to decouple legacy systems while enabling data translation.
4. Establish governance: define roles, ownership, data quality rules, and who can update which fields.
5. Coordinate with trading partners on security, consent, and data-sharing rules to avoid access issues later.

Common pitfalls and how to avoid them

Adopters often stumble by treating ONE Record as simply another file format. Typical mistakes include:

• Neglecting governance: without clear policies, multiple parties may overwrite fields or create conflicting records.
• Poor data mapping: inconsistent harmonization between legacy fields and the ONE Record model leads to loss of meaning.
• Ignoring user experience: APIs must be paired with dashboards or integrations so humans can act on automated insights.
• Underestimating security needs: broad data access without proper roles risks exposure of commercially sensitive information.

The future impact

As adoption grows across airlines, forwarders, customs authorities, and integrators, ONE Record promises to transform air cargo into a more connected, predictable, and automated mode of transport. It will lower operating costs by reducing manual work, speed customs clearances with richer machine-readable evidence, and enable new services such as dynamic routing, automated claims, and predictive ETAs. For shippers and logistics providers who invest early in integration and governance, ONE Record will become an engine for operational efficiency and new customer-facing capabilities.

Conclusion



ONE Record is not just a technical specification — it is an operational shift from static documents to shared, live shipment data. For the air waybill, that means moving beyond the PDF and toward a digital record that supports collaboration, automation, and better outcomes across the supply chain. The transition requires technical integration, stakeholder coordination, and clear governance, but the payoff is a faster, more transparent, and more reliable air cargo ecosystem.