How are XML interfaces versioned?

Common approaches include the use of namespaces in which the version is encoded, or maintaining separate schema files per version. Clear documentation of which systems expect which version is essential so that changes can be rolled out in a controlled manner.

Can XML be used directly between ERP and WMS?

Yes, many ERP and WMS systems support XML-based interfaces natively or via middleware. The critical factor is that both systems use the same schema, or that a transformation layer bridges the differences.

What is an XSD and what is it used for?

An XSD (XML Schema Definition) is a formal specification of which elements, attributes, and data types an XML document may contain. Systems can automatically validate incoming XML messages against the XSD and reject invalid data at an early stage, before it enters downstream processes.

Is XML still current, or is it being replaced by more modern formats?

XML continues to be used in many established integration and industry standards and is firmly embedded in enterprise landscapes. New projects more frequently adopt JSON or REST APIs; however, both worlds coexist in practice – particularly where complex document structures or validation requirements are present.

← Back to glossary

XML

Also: Extensible Markup Language, XML-Format, XML-Schnittstelle, XML-Datei, XML-Dokument

AI-generated

In brief

XML (Extensible Markup Language) is a text-based, hierarchical data format that enables the structured exchange of information between different IT systems.

Key facts

XML is a W3C-standardized, text-based data format for the structured exchange of information between IT systems.
XML schemas (XSD) enable automatic validation of incoming messages, thereby improving data quality at interfaces.
In intralogistics, XML is commonly used for advance shipping notifications, order transmissions, and master data synchronization between ERP and WMS.
Compared to more compact formats such as JSON, XML generates greater data volume, but offers stronger expressiveness for complex, hierarchical structures.

What is XML?

XML stands for Extensible Markup Language and is a format standardized by the W3C for describing and transmitting structured data. Unlike HTML, which governs the presentation of content, XML exclusively describes the meaning and structure of data. Tags and attributes can be freely defined, which is why XML is considered extensible. This makes the format flexible enough to represent virtually any data content – from orders and delivery notes to machine parameters and master data.

An XML document consists of a root element into which all other elements are nested. This tree structure can be read, validated, and transformed by machines. To ensure data quality, schemas are used – either as a DTD (Document Type Definition) or as an XML Schema Definition (XSD). A schema defines which elements are permitted, the order in which they may appear, and which data types apply. Systems can validate incoming XML documents against a schema and reject invalid messages at the point of receipt.

XML in intralogistics and data exchange

In intralogistics, XML is encountered primarily in interfaces between ERP, WMS, and TMS systems, as well as in the integration of partners along the supply chain. Many established interface standards – such as EDIFACT mappings via XML, RosettaNet, or industry-specific formats – use XML as their underlying technology. DESADV messages are also transmitted as XML in some implementations.

Typical use cases include:

Transmission of order data between purchasing and suppliers
Advance shipping notifications and delivery announcements in goods receipt
Master data synchronization between ERP and WMS
Machine communication in conveyor systems and automated warehouses
Configuration files for middleware and integration layers

What matters when selecting and implementing XML

Whether XML is the right choice for an interface depends on the use case. XML is expressive and highly validatable, but generates more data volume compared to more compact formats such as JSON or binary protocols. At high message throughput – such as in real-time systems for conveyor systems – this can be a relevant factor. For exchanging complex, hierarchically structured business documents, XML remains a robust choice.

Key considerations when designing XML interfaces include schema versioning, the error-handling strategy for invalid messages, and documentation of the namespaces used. When connecting multiple systems or partners, a central schema repository is recommended to make changes traceable. Middleware solutions vary by vendor in how conveniently they support schema validation, transformation, and monitoring – this should be explicitly evaluated during system comparisons.

Frequently asked questions

Both formats serve the purpose of structured data exchange but differ in syntax and primary focus. XML is more expressive and natively supports schemas, namespaces, and attributes – making it ideal for complex business documents. JSON is more compact and widely used in web APIs. Which format is the right fit depends on the system and use case.

Related terms

API
An API (Application Programming Interface) is a defined interface through which two software systems can exchange data in an automated and standardized way. In intralogistics, it connects systems such as WMS, ERP, or TMS with one another and with external services.
Artikelstammdaten
Item master data refers to the permanently valid base data of an item – such as dimensions, weight, packaging units, hazardous goods classification, and best-before date relevance. It forms the foundation for all logistical, procurement-related, and system-driven processes along the supply chain.
Bewegungsdaten
Movement data captures all transactions and physical goods movements in the logistics process – from goods receipt and stock transfers to dispatch. It contains timestamps, quantities, locations and the units involved, and forms the basis for transparency, control and analysis in warehouse and…
Blockchain
Blockchain is a cryptographically linked, distributed data structure in which transactions are stored in a tamper-resistant manner and are traceable by all participants.
DESADV
DESADV (Dispatch Advice) is a standardized EDI message in EDIFACT format that electronically announces an upcoming delivery. It transmits structured information on packaging units, items, quantities, and identifiers such as the SSCC to the goods recipient.
Datenbank
A database is a structured system for the persistent storage, management, and querying of data. In intralogistics, it forms the technical foundation for WMS, ERP, and TMS by reliably maintaining master data, transactional data, and historical records.
Datenfunkgeräte
Data radio devices are mobile or stationary hardware components that transmit data wirelessly via radio protocols such as WLAN or cellular. In warehouse and transport environments, they form the operational interface between employees and IT systems such as WMS or ERP.

Matching categories

Data, IT & Integration Integrating Systems & Interfaces Connect ERP, WMS & TMS Managing carrier & service provider integrations Improve Data Quality & Master Data

XML