Integrations in logistics

In logistics, shipment data goes from the ERP to parcel carriers, shipping platforms and freight forwarders, while tracking numbers and status come back. Parcel carriers mostly offer REST APIs, while freight forwarders often work with EDIFACT or FORTRAS files. Ready-made platforms are often enough for parcel shipping. We build the connection where the forwarder, a special format or the ERP does not fit the pattern.

Typical system landscape

Two examples from the documentation: the DHL Parcel DE Shipping API creates shipments and labels, cancels shipments that are not yet completed and closes the day with a manifest. Testing takes place in a sandbox, and DHL has to approve production use. Sendcloud describes an API through which labels are created directly from the ERP, orders are imported and shipments are tracked.

Typical data flows

1. Shipment is handed over with address, weight and packages on shipping release
2. Label is retrieved and printed immediately
3. Transport order is sent to the forwarder, for example as EDIFACT IFTMIN or a FORTRAS file before pickup
4. Tracking number and status go back to the ERP and the shop hourly

With freight forwarders, the return path follows the transport order: status messages, proofs of delivery and billing data. Which messages a forwarder sends and in which format is written in its interface description. That description is the starting point of every project.

Typical problems

• Forwarders without an API

  Some forwarders expect files in fixed formats via SFTP. A standard connector for parcel shipping does not help here.

• Feedback

  Tracking number and delivery status do not arrive in the ERP. Customer service searches by hand.

• Format variants

  EDIFACT is a broad standard. Every partner uses its own selection of fields and codes.

• Errors go unnoticed

  A rejected file or an expired access is noticed only when goods are left sitting.

• Access expires

  Parcel carriers change their sign-in methods. DHL, for example, announces that it will no longer offer Basic Auth in future API versions and recommends OAuth 2.0.

Examples of connections

• JTL-Wawi to a forwarder via FORTRAS file over SFTP
• Business Central to a parcel carrier via REST API, tracking number back to the order
• Legacy system without an API to a shipping platform, see integration without an API

How a forwarder integration works

• Obtain the specifications

  The forwarder provides the format description, a test access and a contact person. We clarify mandatory fields, codes and file names.

• Exchange test files

  We generate test shipments from your ERP. The forwarder checks them until no more errors come back.

• Go live and monitor

  After that, the exchange runs automatically. If a response fails to arrive, the monitoring raises an alarm.

What we build

We connect your ERP directly to the shipping service or the forwarder. With parcel carriers through their API, with forwarders through the agreed file, for example EDIFACT or FORTRAS, with pickup and drop-off via SFTP. Every shipment is logged, and we report rejected files and errors immediately. We write responses back to the ERP. On request we take over ongoing operation, see operation and monitoring.

Updated: 10/20/2026