Thirty years after the initiative that gave rise to the WCO Data Model, exchanging data is only part of the challenge. Border authorities also need to interpret and use what they receive.
Imagine a trader submitting shipment information to one authority, only to find that another asks for the same details in a different format. Both procedures may be digital, yet the trader still has to enter the information again. A technical connection between systems does little to solve that problem if they use different definitions for the data they exchange.
The WCO Data Model gives Customs and other border authorities a shared way to define and exchange information. Its harmonised data definitions and reusable electronic messages help administrations meet their own requirements while working from the same standard. The work began as a G7 initiative in 1996, and the WCO formally adopted the first version of the Customs Data Model in 2002.
The difference between sending data and understanding it was central to the WCO’s in July 2026.
That distinction between exchanging data and giving it a shared meaning ran through the WCO’s 30th-anniversary webinar on 8 July 2026. The discussion presented Version 4.3.0, examined administrations’ implementation experience and explored how the Model’s definitions could become easier for software to use directly.
A shared meaning for trade data
Interoperability depends on more than a connection between systems. A message may reach its destination successfully, yet still leave the receiving authority uncertain about what a field means or how it relates to the rest of the information. When definitions differ, exchanging data does not necessarily make it usable.
The WCO Data Model provides a common framework for addressing that uncertainty. It combines harmonised data definitions with reusable message structures, allowing administrations to select the elements their procedures require while drawing on meanings that other users of the standard can recognise. As explained during the webinar, those structures can be implemented in different formats, including UN/EDIFACT, XML and JSON. The technology used to transmit the message can vary; the definitions underpinning it remain shared.
This makes data modelling relevant well beyond the IT department. Before information can be represented in a message, authorities must establish what their procedures require and why. The WCO’s Data Model Projects Team brings Customs practitioners, policy and legal officers together with data modellers and technical specialists to translate those requirements into a consistent structure. For Customs, the implication is practical: defining a data field means clarifying the operational requirement behind it. Agreeing on that meaning provides a foundation for using information across systems and authorities.
What Version 4.3.0 adds
Version 4.3.0 extends the Model to new operational contexts through information packages: subsets of its definitions and structures assembled for a specific business need. It also adds tools for developing JSON messages and broadens support for digital supporting documents, while retaining compatibility with the Version 4 series.
Advance information on maritime passengers and crew
The new Maritime Advance Passenger Information package provides a harmonised structure for electronic information about passengers and crew arriving by sea. According to the WCO, the package fills a gap in the Model’s coverage of advance passenger information, which had previously addressed air travel.
The package is aligned with the International Maritime Organization’s Compendium on Facilitation and Electronic Business and the Convention on Facilitation of International Maritime Traffic. This alignment gives administrations a shared reference for developing maritime passenger messages that are consistent with the international maritime framework. An information package is a subset of the Data Model designed for a specific business context, allowing implementers to work with the definitions and structures relevant to that exchange.
Information exchange under AEO mutual recognition agreements
The new Authorized Economic Operator Mutual Recognition Agreement package provides the first building blocks for structured information exchange between Customs administrations that recognise one another’s AEO programmes.
Its practical relevance lies in translating that cooperation into a common data structure. Mutual recognition creates a context in which administrations need to exchange information; the package begins to define how that information can be represented consistently. The WCO has published it as a work in progress, with further contributions invited from Members. It should therefore be understood as an initial framework that remains under development.
JSON tags for implementation in web-based systems
Every class and data element now carries a JSON tag. These tags give developers ready-made building blocks for creating JSON messages that conform to the WCO Data Model, making the standard easier to use in web-based implementations.
The addition makes an important distinction clearer: a shared data model and a message format serve different purposes. The Model defines the information and its structure; JSON provides one way to represent it electronically. Providing tags helps developers carry those common definitions into the messages they build.
Broader support for digital supporting documents
Version 4.3.0 also supports the exchange of a wider range of digital supporting documents, including invoices, certificates and images. This extends its usefulness beyond the structured fields of a message to the supporting material that may accompany a border operation.
For Customs, the distinction matters. A declaration or other electronic submission can contain structured data while also requiring supporting documents. The release expands the Model’s ability to accommodate that material as administrations move away from paper-based processes.
Compatibility and continuing maintenance
The WCO describes Version 4.3.0 as fully compatible with the Version 4 series, allowing administrations already using that series to incorporate the additions without disrupting their existing implementations.
The release incorporates Data Maintenance Requests from the Netherlands, New Zealand and the United States. Requests submitted through the WCO Data Model App undergo review, modelling, quality assurance and publication. This process gives Members a formal route to bring operational needs into the standard while preserving consistency for administrations already using it.
Where the standard meets operations
Nigeria’s experience shows how the WCO Data Model can shape the design of a Customs system. During the webinar, the Nigeria Customs Service reported that its new Universal Customs Management System contains 612 harmonised data sets across 27 information packages, with 94% mapped directly to WCO Data Model classes. It also reported a 43% reduction in duplicated data fields, less reworking and faster integration. These results are specific to Nigeria’s implementation, but they illustrate a practical benefit of using shared definitions from the outset: fewer duplicated fields and less work to connect different parts of a system.
The maritime sector extends that logic across institutional boundaries. The IMO Compendium defines the information ships submit to government authorities. As the IMO explained during the webinar, aligning it with the WCO Data Model enables Customs and other authorities to reuse that information, reducing duplication and supporting interoperability across government systems. This alignment also supports maritime Single Windows. For Customs, its significance lies in establishing common definitions with the other authorities involved in maritime reporting, creating a foundation for information to serve more than one regulatory process.
New Zealand Customs demonstrated how the Model’s applications extend beyond goods declarations. A user since 2013, it has contributed to maritime advance passenger information and booking or reservation information packages, alongside implementation guidance. It also described pilot activities designed to provide practical evidence for developing these frameworks. Its experience highlights the role administrations can play in shaping the standard around operational needs.
Together, these examples suggest that data harmonisation belongs early in Customs modernisation, when administrations define requirements and design systems. A common standard can then guide implementation from the outset, reducing the need to reconcile incompatible definitions later.
The next question: can machines use the meaning?
The WCO’s next area of work concerns how software can use the meaning already contained in the Data Model. As explained during the webinar, the standard defines thousands of concepts, including what an exporter or consignee is and how they relate to a declaration. Much of that meaning, however, remains embedded in documents and spreadsheets that implementation teams must read and interpret.
The Data Model Projects Team is exploring how to publish those definitions and relationships in a structured, machine-readable form, known as a web ontology. Each concept would have a stable web identifier that systems could reference and reuse. According to the WCO, this could enable software to validate messages against official definitions and help administrations incorporate updates with less manual reworking. For Customs, the potential is to make the shared standard easier to implement and maintain as systems and requirements evolve.
This work also has implications for verifiable credentials, such as digital attestations accompanying cross-border transactions. Checking a credential’s authenticity answers one question; interpreting the information it contains answers another. The WCO identifies digital certificates of origin as a potential application: a shared vocabulary could help the issuing and receiving systems interpret the certificate consistently, regardless of the technology carrying it. The Model would provide the meaning and structure of the data, while remaining independent of the technology used to exchange it.
At the time of the webinar, this work was still in the design phase. The WCO said it would proceed gradually, be driven by Members’ needs and involve cooperation with other standards bodies. It is a future direction, rather than a capability delivered by Version 4.3.0.
After thirty years, the Data Model’s significance lies in what Customs can do with information once it arrives. A declaration, certificate or passenger record becomes more useful when its meaning can be carried consistently across systems and authorities. For Customs leaders and technology providers, that makes shared definitions an early design decision with lasting operational consequences. The next step is to turn that common understanding into information that can be reused within agreed procedures and fewer occasions on which businesses must supply the same details again.
