Carrier Integration

Carrier integration is the technical backbone of every automated shipping process in e-commerce. Without a working interface to DHL, DPD, GLS, UPS, or Hermes, labels remain manual work, tracking data arrives late, and multi-carrier strategies fail due to media breaks. A clean integration connects shipping software, WMS, and shop system with carrier APIs – turning every packed order into a franked, trackable shipment within seconds.

This guide explains the types of integration available, how to integrate carriers step by step, which data must be transmitted, and how to avoid typical integration errors from the start.

What Does Carrier Integration Mean in Fulfillment?

Carrier integration refers to the technical link between your fulfillment system (WMS, shipping software, OMS, or shop) and the IT systems of a shipping service provider. The goal is automated creation of shipping labels, booking of rates, return transmission of tracking numbers, and optionally retrieval of tracking events – without manually logging into carrier portals.

At its core, integration replaces three manual work steps:

1. Data entry – Address, weight, and product are taken from the order, not retyped
2. Franking – Rate and payment status are booked with the carrier, not corrected afterwards
3. Tracking return channel – Tracking numbers flow automatically into the shop and customer communication

Integration Types Compared

Not every carrier and not every shipping software supports the same interfaces. The choice of integration type determines flexibility, maintenance effort, and scalability.

For growing merchants with their own warehouse or 3PL, the combination of shipping software with native carrier APIs or an aggregator plus WMS integration is the standard. CSV and pure portal solutions are at best a transitional solution until around 20 shipments per day.

REST API vs. EDI – When to Use Which Interface?

1. REST API – Ideal for e-commerce: real-time labels, webhooks for tracking, fast test cycles in sandbox environments
2. EDI – Useful for fixed B2B volumes, long-term framework contracts, and when the carrier provides EDI as the primary channel
3. Hybrid – Large fulfillment operations use REST for day-to-day operations and EDI for billing or ASN confirmations

Details on structured B2B interfaces can be found under API and EDI Interfaces.

The Integration Process in 6 Steps

Carrier integration follows a recurring pattern – regardless of whether you connect DHL, DPD, or an international carrier.

Process Flow: Carrier Integration

Step 1: Contract and API Access

Before technical integration begins, you need a business customer contract with the carrier and explicit activation of the API or developer portal. Typical credentials:

• API key or OAuth Client ID / Client Secret
• Billing number (EKP) and participation in product programs
• Sandbox credentials (separate from production)
• IP whitelisting or certificate requirements (carrier-dependent)

Step 2: Sandbox and Test Environment

Every integration starts in the sandbox. There you create test labels without real franking and simulate tracking events. Check:

• Correct address validation and routing codes
• Return of PDF and print format (ZPL/EPL)
• Cancellation/void within the carrier time window
• Error codes for invalid shipment data

Step 3: Data Mapping

Your system must convert shipment data into the carrier schema. Required fields for almost all carrier APIs:

• Recipient: name, street, postal code, city, country (ISO-3166)
• Sender: return address or warehouse address
• Package: weight (kg), length/width/height (cm), reference (order number)
• Product: carrier product code (e.g. DHL Paket, DPD Classic)
• Additional services: insurance, cash on delivery, parcel locker ID

Step 4: Connect Label Workflow

The API integration culminates in the operational process at the packing station. After packing and weighing, a scan triggers the API call; the returned label goes directly to the thermal printer. The process is closely linked with label printing and automation – carrier integration provides the data, automation orchestrates the print.

Step 5: Go-Live

Before go-live, you should run a parallel test: first live shipments with manual verification, then gradually increase volume. Checklist for cutover:

• Production credentials stored and separated from sandbox
• At least 50 test labels in sandbox without errors
• Cancellation workflow tested
• Tracking return channel connected to shop and email template
• Escalation contact for carrier technical support documented

Step 6: Monitoring and Maintenance

Carrier APIs have downtime, rate limits, and version updates. Professional operations monitor:

• Response times – label creation under three seconds under normal conditions
• Error rate – HTTP 4xx/5xx, validation errors, timeout
• API version – deprecation notices in the developer portal
• Billing discrepancies – franked labels vs. actually shipped packages

Multi-Carrier Integration

Those who use multiple shipping service providers benefit from lower rates, higher delivery reliability, and redundancy. However, a multi-carrier strategy requires each carrier to be properly connected – or an aggregator to serve as an intermediary layer.

Routing rules should be stored in the shipping software – not in the packer's head. Examples:

• Domestic under 1 kg → small parcel or lightweight parcel
• Domestic over 5 kg → parcel service with highest delivery rate
• EU international → carrier with stable customs integration
• Express before cut-off → prioritized carrier with same-day product

Workflow: Multi-Carrier Routing

Common Errors and How to Avoid Them

Even experienced teams underestimate the complexity of carrier integration. These errors occur most frequently:

1. Confusing sandbox and production – Labels appear valid but are not accepted by the carrier
2. Wrong product codes – Rate does not match weight or destination zone; additional postage charges may apply
3. Incomplete return address – Label is created, but package cannot be assigned on return
4. No void process – Cancelled orders remain franked with the carrier and incur costs
5. Tracking pull only, no push – Status updates arrive late; customers see "shipment being prepared" for days
6. Missing peak tests – API rate limits break on Black Friday; labels pile up at the packing station

Security and Compliance

Carrier APIs process personal customer data: names, addresses, and possibly phone numbers for delivery notifications. Consider:

• Encryption – HTTPS/TLS only for API communication
• Credential storage – API keys in environment variables or secret manager, not in source code
• Access control – only authorized systems and employees may create labels
• Order processing – with 3PL, clarify who holds API credentials and who is the data protection controller
• Logging – API logs without unnecessary storage of complete address data

KPIs for Successful Carrier Integration

Measurable metrics show whether the integration delivers in daily operations:

ROI of Carrier Integration

Checklist: Successfully Implementing Carrier Integration

Preparation

• Business customer contract and API activation with carrier completed
• Shipping software or WMS with carrier module selected
• Sandbox access set up and documented
• Responsible person for technical and operational aspects assigned

Technical Integration

• Data mapping defined for all required fields
• Address validation implemented before API call
• Test labels created for all relevant products and zones
• Cancellation/void workflow tested
• Tracking return channel connected to shop and customer notification

Go-Live and Operations

• Parallel operation with manual verification in week one
• Monitoring for error rate and response time active
• Carrier support contacts and escalation path documented
• Packing station staff trained for error cases (fallback process)
• Quarterly review of API version and rate codes

Frequently Asked Questions (FAQ)

• Do I need separate software for each carrier? – No, multi-carrier shipping software bundles multiple APIs.
• How long does initial setup take? – Typically 2–6 weeks per carrier including tests.
• Can I integrate without developers? – Yes, via shipping software with preconfigured modules or aggregators.
• What happens during API outage? – Fallback to second carrier or manual portal as emergency process.
• Stick sandbox labels on real packages? – No, only production labels are validly franked.

Conclusion

Carrier integration is the decisive step from manual franking to scalable fulfillment. Those who cleanly integrate REST APIs or aggregators into shipping software and WMS reduce errors, speed up the packing station, and enable multi-carrier routing according to clear rules. Invest time in sandbox tests, data mapping, and monitoring – the operational benefit shows from the first day in live operation and increases with every additional carrier and every peak season month.

Related Topics

• Shipping Software and Multi-Carrier
• Label Printing and Automation
• Shipping Label and Carrier API
• Multi-Carrier Strategy
• API and EDI Interfaces

Last updated: July 7, 2026