Setting Up the DHL Interface

The DHL interface is the technical core of automated shipping in e-commerce. Once more than a dozen parcels leave the warehouse daily, manual franking in the portal is no longer sufficient. A properly configured interface transfers order data from shop, WMS or shipping software directly to DHL, generates labels in seconds and writes tracking numbers back automatically – without media breaks at the packing station.

This guide walks you through setup step by step: from the business customer contract to API credentials and production deployment in your shipping software. You will learn what prerequisites are required, how sandbox and live environments are kept separate, and which errors occur most frequently in practice.

Why Set Up the DHL Interface?

Without a technical connection, the same bottlenecks arise every shipping day: addresses are entered twice, weights typed manually, tracking numbers copied and pasted into the shop. This costs time, increases the error rate and prevents scaling during peak seasons.

A configured DHL interface automates the entire cycle between order and trackable shipment:

1. Data transfer – recipient address, weight and reference come from the order, not from memory
2. Product selection – parcel, small parcel or Warenpost is chosen by rule or manually
3. Label creation – PDF or ZPL is printed directly at the packing station
4. Tracking feedback – tracking number flows into shop, marketplace and customer email

Prerequisites Before Setup

Before you start the technical configuration, organizational and contractual foundations must be in place. If any of these building blocks is missing, integration will fail even in the sandbox.

Business Customer Contract and Portal Access

You need an active DHL business customer contract with access enabled to the DHL Business Customer Portal. Relevant data from the contract:

• EKP (billing number) – unique identifier for your customer account
• Participation ID and, if applicable, billing code per shipping product
• Enabled products: DHL Paket, Kleinpaket, Warenpost, returns, Packstation
• Valid return address for automatic return labels

Request API Access

The DHL Paket API is not active by default. In the developer area of the business customer portal, request:

• API key and API secret (OAuth2 client credentials)
• Access to the sandbox (separate credentials from production)
• Activation of required endpoints (label, tracking, returns)

Details on architecture and endpoints can be found under DHL API and Shop Integration.

Technical Infrastructure

DHL Interfaces: Which Option Fits?

DHL offers several paths for technical integration. The choice depends on IT resources, shop system and shipping volume.

For most retailers with their own warehouse, shipping software with integrated DHL module is the fastest and most stable path. More on the strategic comparison of all carrier integrations: Carrier Integration.

Comparison of DHL Integration Paths

Step-by-Step: Setting Up the DHL Interface

The following seven steps apply regardless of whether you use a shop plugin or professional shipping software. The sequence is mandatory – sandbox before production.

Process Flow: Setting Up the DHL Interface

Step 1: Enter Contract Data and EKP

Enter all contractual identifiers in the shipping software backend:

1. EKP (10-digit billing number)
2. Participation ID per product program
3. Sender address (warehouse or returns center)
4. Default shipping product (e.g. DHL Paket domestic)
5. Cut-off time for daily closing

Step 2: Enter OAuth2 Credentials

The DHL Paket API uses OAuth2 client credentials. In your shipping software, enter:

• Client ID (API key from the developer portal)
• Client Secret (API secret, visible only once upon creation)
• Environment: Sandbox or production (strictly separate)

The software automatically obtains an access token with limited validity. Verify that token refresh is correctly implemented – expired tokens cause sporadic label errors.

Step 3: Map Shipping Products

DHL product codes must be mapped to your shipping rules. Typical mapping:

Step 4: Configure Label Format and Printer

Align print format and hardware. Details on the packing station workflow: Label Printing and Automation.

• PDF (A4/A6): Laser printer or thermal printer with PDF rendering
• ZPL/EPL: Direct thermal printing, faster at high volume
• Label size: 100 × 150 mm or 100 × 200 mm depending on product

Step 5: Run Sandbox Tests

The sandbox does not create real shipments, but simulates API responses realistically. Mandatory tests:

1. Standard domestic parcel with valid address
2. Packstation with post number and branch number
3. Kleinpaket and Warenpost at dimension limits
4. Return label with correct return address
5. Error case: invalid postal code, missing required fields
6. Void/cancellation within DHL time window
7. Tracking query with sandbox tracking number

Pay particular attention to Address Format and Routing Code – incorrect addresses are the most common cause of API rejections.

Step 6: Go-Live

After successful sandbox phase:

1. Enter production credentials (do not reuse sandbox keys)
2. Accompany first live shipment manually and verify in DHL portal
3. Test tracking number feedback in shop and marketplace
4. Verify customer notification with tracking link
5. Define daily closing/manifest process

Typical ROI After Interface Setup

Step 7: Monitoring and Maintenance

A DHL interface is not a set-and-forget project:

• API versions: DHL announces deprecations – follow shipping software release notes
• Rate changes: Update mapping for new product codes or changed weight limits
• Error rate: Analyze rejected labels daily (address, weight, product)
• Token errors: Check OAuth expiry and retry logic in logs

Integration with WMS and Shop

When shipping software, WMS and shop are separate systems, you need clear interface rules. The typical data flow:

Workflow: DHL Interface in the Fulfillment Stack

1. Order released – shop or OMS reports order ready to ship
2. Pick completed – WMS or packing station scan triggers label creation
3. Weight/dimensions – scale or master data flows into API request
4. Label printed – tracking number is written back to WMS and shop
5. Tracking event – status changes trigger customer email

For complex setups: WMS Integration.

Common Setup Errors

More DHL-specific pitfalls: Common DHL Shipping Errors.

Checklist: DHL Interface Production-Ready

Organizational

• DHL business customer contract active and products enabled
• API access requested in developer portal
• EKP, participation ID and sender address documented
• Return address configured for return labels

Technical

• OAuth2 client ID and secret entered in shipping software
• Sandbox tests passed for all relevant products
• Label printer configured with correct format (PDF/ZPL)
• Product mapping for Paket, Kleinpaket, Warenpost and Packstation

Go-live

• Production credentials active (sandbox disabled)
• First live shipment verified in DHL portal
• Tracking number appears in shop and customer email
• Error monitoring set up for the first 14 days

When Is Which Effort Worth It?

As a rule of thumb:

1. Up to 15 shipments/day – Online Franking or CSV import is often sufficient
2. 15–50 shipments/day – shop plugin or shipping software module pays off quickly
3. 50+ shipments/day – native DHL interface in shipping software or WMS is mandatory
4. Multi-carrier – middleware or shipping software with carrier integration for DHL plus alternatives

The term Shipping Label and Carrier API describes the automated cycle you achieve with a correctly configured DHL interface.

Frequently Asked Questions About the DHL Interface

• Do I need a developer? – Shop plugins: no, direct API: often yes
• How long does setup take? – 3–7 days with shipping software, 2–6 weeks for in-house development
• Can I use sandbox and live in parallel? – Yes, with separate credentials
• What does the API cost? – No separate API fee, only shipping rates per contract
• Does Packstation work via the interface? – Yes, with post number and branch number in the order

Related Topics

• Shipping Software and Multi-Carrier
• Carrier Integration
• Label Printing and Automation
• DHL API and Shop Integration
• Address Format and Routing Code

Last updated: July 7, 2026