What a DHL integration gives you.
Orders move from payment confirmation to despatch instruction in minutes, not hours. Labels print automatically, warehouse teams despatch the same day, and customers see tracking numbers in their order confirmations.
Order records stay in sync with DHL despatch status. Reconciliation against despatch confirmations happens automatically, so you catch unshipped orders and avoid duplicate shipments before they become customer escalations.
Return labels reach customers automatically, DHL pickup consolidation runs on a schedule, and inbound returns reconcile back to original orders without warehouse staff re-keying reference numbers or chasing delivery scans.
Customs declarations, HS codes and origin statements live in your product master data, not in spreadsheets or DHL web forms. Each international order pulls the right data without buyer or warehouse involvement.
If DHL capacity is constrained or latency exceeds threshold, orders shift to fallback carriers with tracking lineage preserved. Customers and your back-office see a single tracking experience across carriers.
Where a DHL integration earns its place.
If two or more of these are true, the integration usually pays for itself quickly.
Where off-the-shelf connectors fall short.
Vendor connectors are fine for simple cases. Here's where the real ones need more.
DHL's standard API does not embed your business rules for carrier selection, service downgrades or surcharges. You must build the logic that decides whether an order ships via DHL Express, DHL Parcel or a hybrid approach, and how weight, destination or value thresholds map to service levels.
DHL returns shipment failures, address corrections and delivery exceptions, but does not provide intelligence about which exceptions require human intervention versus automatic retry. You need custom routing to separate silent failures from actionable alerts.
DHL can generate return labels, but linking returns to inbound pickup consolidation, managing your return address pool and reconciling return parcels back to original orders requires custom orchestration outside the standard API.
If DHL is unavailable or capacity-constrained, the standard integration does not automatically trigger fallback to alternative carriers. You must build the business logic that decides when to switch carriers mid-shipment.
DHL requires customs declarations, HS codes and origin statements for international shipments. Mapping product data, item values and tariff classifications from your PIM into DHL's compliance payloads is not handled by default.
Despatch latency is often the invisible margin killer: orders sit in print queues while labels are generated manually, tracking numbers trickle in late, and returns consolidation becomes a chasing game rather than a scheduled process.
Where this integration sits in your estate.
DHL holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.
Commerce platform agnostic. Connect DHL across your entire technology stack.
- Label generation and printing
- Tracking number assignment and updates
- Proof of delivery and event capture
- Carrier-specific compliance checks
- Returns label generation and consolidation
- Order confirmation and customer details
- Service level and carrier selection logic
- Customer notification timing and content
- Return authorisation workflow
- Fallback carrier routing logic
Systems this integration usually sits next to.
Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.
- Adobe Commerce
- Magento Open Source
- Shopify Plus
- BigCommerce
- Other storefronts
- Order management system (OMS)
- ERP (NetSuite, SAP, Sage)
- Warehouse management system (WMS)
- Returns management system
- Product information system (PIM)
- Shipping rules engine
- Customer notification platform
Not sure if this works with your stack?
Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.
The data flows we wire.
Each flow has a direction and an owner. We agree both before a line of code is written.
How iWeb configures the integration around your business.
Same method on every integration. The decisions come before the code.
- 01Carrier and service selection logic
We map your business rules - destination, weight, service SLA, margin targets - into the routing engine so that each order finds the right DHL service or fallback automatically, with no threshold guesswork.
- 02Label and manifest automation
We connect your order data to DHL's label API and route the output directly to your warehouse management system or print queue, so labels are ready before warehouse staff touch the parcel.
- 03Tracking and proof-of-delivery capture
We ingest tracking numbers, scans and proof-of-delivery events from DHL and route them to order records, customer notifications and your ERP so your back-office and customers stay in sync with reality.
- 04Returns and reverse logistics orchestration
We design the return label flow, link returns to inbound consolidation schedules, and reconcile return parcels back to original orders so returns move from customer hands to warehouse restock without manual chase.
- 05Exception routing and observability
We separate silent failures from actionable exceptions and route them to the right team queue - customer service for address errors, warehouse for missing items, operations for carrier delays - so exceptions surface as alerts, not surprises.
- 06Customs and international compliance integration
We pull HS codes, item values and origin statements from your PIM and feed them into DHL's international shipment payloads so customs declarations are governed by product data, not manual forms.
Who owns what.
The single most important table in any integration. One system owns each field; everything else reads it.
Built this integration multiple times
iWeb has built DHL integrations for retailers, foodservice distributors and manufacturers across multiple commerce platforms and order management systems. We understand how DHL sits between your OMS, warehouse and ERP, and how to route despatch instructions, tracking events and exceptions reliably.
What we test before launch.
Every one of these is rehearsed before a customer ever sees the integration.
Common risks and where they bite.
We name these on day one. A risk written down is a risk you can plan around.
If label generation fails silently or DHL API latency spikes, orders sit in your OMS with no despatch instruction. Warehouse staff have no signal that the label exists or has been delayed, so despatch window closes without the shipment going out.
If the tracking number callback from DHL is delayed or lost, your commerce platform shows the order as processed but the customer sees no tracking link. If tracking updates stop arriving, customers believe the parcel is lost when it is simply not being scanned.
If the return label generation fails or the email to the customer does not include the correct reference number, the return shipment either does not arrive at DHL or arrives without a link to your original order. Returns reconciliation then breaks and inventory does not update.
DHL returns address corrections and customs declaration errors, but if your integration does not route these exceptions to the right team with clear SLAs, remediation happens after the despatch window closes or the shipment is held at a border.
If DHL raises surcharges or downgrades service level on an expensive order but your integration does not capture the change, the customer pays next-day rates and receives standard-delivery, triggering chargeback disputes or escalations.
If your integration has no logic to detect DHL rejection or rate limits and automatically offer alternative carriers, orders queue until DHL capacity returns, despatch deadlines slip, and customers see escalating delays.
Relevant services and sectors.
Common questions about DHL integrations.
How do we decide which DHL service level each order ships via?
iWeb builds rules that map destination, weight, service SLA and cost targets to DHL Express, DHL Parcel or alternative carriers. Service selection happens automatically at order confirmation, with fallback routing if DHL capacity fills or rates spike.
What happens if a customer address fails DHL validation?
DHL returns address correction suggestions or rejection. iWeb routes these exceptions to your customer service queue with the customer contact details and suggested correction, so the team can reach out before the despatch window closes.
How do tracking numbers get back to the customer?
DHL returns tracking numbers via API callback after label generation. iWeb captures the tracking reference, updates your order record, and triggers your transactional email system to send the customer a tracking link with delivery timeline.
What happens if label generation fails or DHL is unreachable?
iWeb detects generation failures and API timeouts and routes them to your operations queue with retry logic and fallback carrier options. If DHL remains unavailable, orders can shift to an alternative carrier without losing order lineage or customer communication.
How do we handle international shipments with customs requirements?
iWeb retrieves HS codes, item values and origin statements from your PIM and injects them into DHL's customs declaration payload for each international shipment. Compliance data lives in your product master, not in manual forms or spreadsheets.
How do returns labels reach customers and get reconciled?
When a return is authorised, iWeb triggers DHL return label generation and routes the label to your returns email template or customer portal. When the customer ships the return to DHL, iWeb captures inbound tracking and reconciles the returned parcel back to the original order so inventory updates automatically.
What if DHL raises a surcharge or downgrades service level?
DHL notifies us of rate changes and service downgrades in the API response. iWeb captures these events and routes them to your operations team so you can decide whether to accept the new rate, switch carriers or absorb the cost before the shipment leaves your warehouse.
How do we know if an order was shipped or is stuck?
iWeb reconciles orders against DHL despatch confirmations on a schedule. If an order sits in your OMS without a despatch confirmation after a threshold time, an alert goes to your operations queue so you can investigate before the despatch window closes.
Can we use DHL as our primary carrier and shift orders to another carrier if DHL is full?
Yes. iWeb monitors DHL capacity and rates in real time and can automatically trigger failover to your secondary carrier (FedEx, UPS, UK Mail, etc.) if DHL rejects the request or surcharges exceed threshold. Tracking lineage is preserved across carriers.
How often do tracking updates arrive and how fresh is the data?
DHL pushes tracking events (label created, picked up, in transit, delivered, exception) via API webhooks. iWeb captures these events in near real time and updates your order records and customer notifications within minutes of each DHL scan.
What happens if a shipment is delivered but DHL's proof of delivery is missing?
iWeb monitors for late or missing proof-of-delivery events and flags them as exceptions. If proof is not received within a service window, your operations team is alerted so they can contact the customer or DHL to confirm the delivery and close the order.
How does this integrate with our ERP and OMS?
iWeb sits between your commerce platform and DHL. Despatch instructions flow from your OMS to DHL, tracking and proof-of-delivery flow back to your OMS and ERP for order status and invoicing reconciliation. Your ERP remains the system of record for shipment acknowledgement and financial reconciliation.
What data do we need to provide to DHL for each order?
Recipient name, address, phone number; shipper reference (your order number); item weight and dimensions; declared value; and service level preference. iWeb maps your order data to DHL's payload structure so you do not need to re-key or reformat.
How do exceptions get resolved and who is responsible?
iWeb routes exceptions to queues owned by customer service (address errors), warehouse (missing items), operations (carrier delays) or finance (rate disputes). Each exception includes customer contact data, suggested resolution and SLA so the responsible team can act immediately.
Projects with a similar shape.
A luxury homeware PIM project built around launch speed, product accuracy and catalogue control.
Product launches supported by cleaner data, less spreadsheet work and faster routes to market.
A consumer goods commerce experience built around multi-brand retail and product merchandising.
Enterprise consumer brand commerce implementation.
A construction supplies commerce platform rebuilt around trade purchasing and product depth.
Trade product complexity handled through a faster, more effective ecommerce experience.