Which DHL service applies?

It depends on your account and lanes. DHL Express, eCommerce and Supply Chain expose different interfaces; the applicable service is confirmed in scoping before any commitment.

Does this work with on-premise Sage X3?

Where a supported integration path is available on your deployment, yes. The available objects and access method are confirmed against your environment first.

Can you write tracking numbers back into Sage X3?

Yes — onto the fields agreed during scoping, which depend on how your X3 environment is configured.

Who works the exceptions?

APIWORX works the queue and escalates to your named contacts when a business decision is needed.

International shipping · Operations

Sage X3

DHL

Connect Sage X3 + DHL

Automate delivery, service and account mapping, package and weight detail, label and tracking number, delivery status between Sage X3 and DHL — with monitoring and managed support from APIWORX.

See How It Works

APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.

ERP + eCommerce Specialists

Managed & Monitored Integrations

Expert Integration Team

APIWORX Provides the Service

Yes. APIWORX connects Sage X3 and DHL.

But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.

APIWORX automates that process end to end — the objects moving between Sage X3 and DHL, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.

Order-to-cash automation Fulfillment automation Inventory synchronization

How it works

From requirements to a managed integration

Tell Us What You’re Connecting

Provide the systems, workflow and business requirements.

We Design the Integration

APIWORX recommends the integration architecture, mappings and implementation approach.

We Build, Monitor & Support It

APIWORX implements the integration and provides ongoing monitoring and support as applicable.

Who this is for

This page is for operations teams running Sage X3 as the ERP of record with international shipping executed through DHL.

What needs to be in place

Sage X3 with an integration path available on your deployment — on-premise or cloud — and a service account permitted to read deliveries and write shipment data.
A DHL account with integration credentials for the service you ship on.
Agreed rules for service selection, packaging and ship-from location.
A named operations contact for hold, split and re-ship decisions.

When you may not need this

A single site with low parcel volume can work from the DHL portal. Managed integration earns its place when several ship-from locations, service rules or tracking writeback obligations make manual handling a standing cost.

What is out of scope

DHL is a group of businesses — DHL Express, eCommerce and Supply Chain each expose different interfaces. Which one applies to your account, and in which countries, is confirmed in scoping before any commitment.
APIWORX does not negotiate your DHL rates, hold your carrier contract, or act as a freight broker.
Rate shopping and landed-cost calculation are only in scope where your DHL account exposes them and the behaviour is agreed before build.
Customs and commercial-invoice content stays owned by the system and team that produce it; we move the values those systems hold.
Sage X3 customisations differ by deployment; which objects are safely writable is confirmed against your environment before build.

What actually moves, and who owns it

A representative scope. Exact records, DHL service and writeback fields are confirmed before build.

Sage X3APIWORX (mapping, retries, exception queue)DHL

Objects exchanged between Sage X3 and DHL, with system of record, trigger, failure handling and owner
Object	From	To	System of record	Trigger	If it fails	Owner
Delivery	Sage X3	DHL	Sage X3	Delivery reaches the agreed ready-to-ship state	Held in exception queue with the validation error	APIWORX
Service and account mapping	Agreed rule set	DHL	Rule set agreed in scoping	At shipment creation	Shipment held for an operations decision	APIWORX
Package and weight detail	Sage X3	DHL	Sage X3	At shipment creation	Missing dimensions reported before the request is sent	APIWORX
Label and tracking number	DHL	Sage X3	DHL	Shipment confirmed	Retried, then queued for review	APIWORX
Delivery status	DHL	Sage X3	DHL	Status change	Last known status retained; gap reported	APIWORX
Freight charge reference	DHL	Sage X3 or finance	DHL	Charge published on your account	Queued with the shipment reference	APIWORX

Three decisions that make or break this integration

Shipments are re-keyed into the carrier portal

Manual entry is where addresses, weights and service levels drift. Deliveries are validated in Sage X3 and sent once, with the label and tracking written straight back onto the delivery record.

One source of address and weight data.
Tracking numbers on the delivery, not in a spreadsheet.
Failed requests reported with the specific field at fault.

Several ship-from locations

Each site can carry its own DHL account, service rules and packaging defaults. Mapping is held as configuration so adding a site is a change request, not a project.

Account and service mapped per location.
Packaging defaults applied per site.
Unsupported lanes held rather than defaulted.

Customer service cannot see where a parcel is

Delivery status is written back against the Sage X3 delivery, so the answer is in the ERP rather than in a carrier portal someone has to log into.

Status updates on an agreed cadence.
Exceptions — held, undeliverable, returned — surfaced for action.
Every update carries the DHL shipment reference.

Reliability and ownership

The operating rules that apply to this workflow after go-live.

Every run is logged with the source record reference so a shipment can be traced end to end.
Failed messages are retried on a defined schedule; anything still failing lands in an exception queue rather than being dropped silently.
Duplicate prevention keys on the source system's own identifier so a replayed message does not create a second shipment or a second posting.
Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
Mapping changes — new service levels, new ship-from locations, new accounts — are handled inside the ongoing engagement.
Support windows and response commitments live in your agreement; this page does not state an SLA.

How a shipment is traced

Illustrative — not customer data

An illustrative reference trace from Sage X3 delivery to DHL shipment and back.

How a shipment is traced
Sage X3 delivery number	DHL shipment reference
DHL tracking number	Sage X3 delivery record
Ship-from location	Mapped DHL account
DHL status event	Sage X3 status field

Scope and questions

Which DHL service applies?: It depends on your account and lanes. DHL Express, eCommerce and Supply Chain expose different interfaces; the applicable service is confirmed in scoping before any commitment.
Does this work with on-premise Sage X3?: Where a supported integration path is available on your deployment, yes. The available objects and access method are confirmed against your environment first.
Can you write tracking numbers back into Sage X3?: Yes — onto the fields agreed during scoping, which depend on how your X3 environment is configured.
Who works the exceptions?: APIWORX works the queue and escalates to your named contacts when a business decision is needed.

Your integration plan