Informationsfluss in der Logistik

What is information flow in logistics?

Information flow describes how data, status messages and documents are generated, transmitted and processed along logistics processes. It encompasses all relevant types of information: order data and line items, master data for articles and storage locations, movement data such as goods receipts and issues, advance shipping notifications and delivery announcements, as well as documents such as bills of lading, delivery notes or customs papers. Without a functioning information flow, physical goods flows can neither be planned nor controlled nor tracked.

An important distinction exists between information flow and material flow: while material flow describes the physical movement of goods, information flow controls and documents precisely that movement. Both flows must run in sync – delays or gaps in the information flow lead directly to disruptions in the material flow.

How does information flow work in practice?

In practice, information flow runs both forward and backward. Orders, delivery call-offs and transport instructions flow forward from the client to the service provider. Status messages, advance shipping notices, exceptions and acknowledgements flow back to the client. Modern logistics systems map this exchange via standardized interfaces – typically using EDI formats such as EDIFACT or ANSI X12, XML messages, or increasingly via REST APIs.

A typical example: as soon as a supplier picks a shipment, their system generates an electronic advance shipping notice (DESADV). This reaches the receiving warehouse before the goods arrive, enabling pre-registration, slot planning and resource management. If this notice is missing or contains incorrect data, queries, waiting times and manual rework result.

• Order data flows from the ERP into the WMS and TMS, controlling warehouse and transport processes.
• Status messages from the warehouse or carrier flow back into customer portals or ERP systems.
• Master data must be synchronized once and kept consistent, as discrepancies lead to posting errors.

What matters when designing information flow?

Several factors are critical when selecting and designing an information flow. First, data quality: information must be complete, accurate and timely. Incorrect master data or delayed status messages significantly reduce the value of even well-integrated systems. Second, interface standards: the formats and protocols supported by a partner or service provider directly affect integration effort. Third, error handling: robust processes detect data errors early, escalate automatically and enable swift correction. Fourth, data protection and compliance: particularly when sharing shipment data across national borders or with third parties, legal requirements must be observed. Whether a centralized or decentralized architecture is more suitable depends on the company structure and partner constellations – there is no universal answer here.