Skip to main content

DHL UK EDI: requirements and onboarding

Choose the DHL business unit before designing a UK carrier connection. DHL Express, DHL eCommerce UK and DHL Freight publish different shipping and billing interfaces, so account scope matters more than a shared brand or generic EDI label.

Quick answers

Can SignalEDI help me connect to DHL UK?
SignalEDI helps prepare mappings, sample validation, and the workflow required for your DHL UK program. Scope is confirmed during setup. Production connection requires the applicable partner approval; this guide is not evidence of a live connection or certification.
What determines the DHL UK onboarding timeline?
The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule. Agree the schedule after requirements and testing scope are confirmed. This is not a guaranteed go-live date.
Which ERP systems can I use for DHL UK?
Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Review integration scope

Plan the integration workflow

SignalEDI provides EDI integration preparation, document validation, and workflow visibility. Confirm connector, document, transport, and approval scope before production.

  1. 1. Your business system

    Identify the source records, system edition, data owner, and allowed access.

  2. 2. SignalEDI preparation

    Map and validate safe samples against the agreed requirements. Review errors and acknowledgements.

  3. 3. Partner testing and approval

    Complete the partner-controlled tests and retain permission before enabling live exchange.

Conceptual workflow only. A diagram or catalog listing does not establish certification or an active production connection.

Build your onboarding checklist

Download the onboarding worksheet (text)

Public sources reviewed 2026-11-09

What the public record confirms

  • DHL's official developer portal brings together APIs from different divisions. MyDHL API is identified with DHL Express, while the eCommerce UK API is identified with DHL eCommerce and UK-origin domestic or international parcel shipping.
  • The eCommerce UK API page describes shipment creation, tracking and product/service information. It requires an active DHL eCommerce UK customer account and provides a dedicated test environment. Those conditions do not establish access to a different DHL division.
  • DHL Freight's UK shipping-tools page separately describes road-freight APIs, EDI for booking, visibility and invoice information, and eBilling. It does not publish a universal group-wide X12 transaction matrix on that page.
  • Public sources were reviewed on November 9, 2026. Assigned UK account agreements, private EDI maps and production approval were not inspected. This guide is not evidence that SignalEDI is a DHL partner, certified provider or operator of a live connection for any DHL division.

Document and workflow scope

Use the cited source boundaries below, then confirm your current assigned program: Exact specifications come from your partner packet. Treat this as a planning checklist, not a substitute for the current implementation guide.

  • Division and contract record: identify the contracting DHL business, UK account, shipment origin, service family and payer. Do not select a mapper from the word DHL alone; a parcel-export account and a road-freight relationship can involve different interfaces and operating rules.
  • Shipping execution specification: obtain the current guide for the selected product, including shipment identity, package or handling-unit structure, labels, booking and permitted corrections. Confirm which API or EDI functions are enabled instead of assuming the full developer catalog is available.
  • Visibility and event contract: determine how tracking references, carrier events, timestamps and exceptions are exposed by the assigned service. Keep the external event and its interpretation separate so a generic status label does not falsely indicate delivery or handover.
  • Billing and cross-border information: confirm the appropriate invoice route and reconciliation references. If the shipment crosses a border, obtain the data requirements for that exact lane and service; a UK API or freight page is not a complete customs or tax specification.

Connectivity and testing requirements

Connectivity

Confirm whether the current DHL UK program uses AS2, SFTP, VAN, or another named transport.

Onboarding window

Not verified on this page.

Certification focus

The current supplier packet, account setup, data readiness, testing availability and partner approval determine the schedule.

  • DHL's official developer portal brings together APIs from different divisions. MyDHL API is identified with DHL Express, while the eCommerce UK API is identified with DHL eCommerce and UK-origin domestic or international parcel shipping.
  • The eCommerce UK API page describes shipment creation, tracking and product/service information. It requires an active DHL eCommerce UK customer account and provides a dedicated test environment. Those conditions do not establish access to a different DHL division.
  • DHL Freight's UK shipping-tools page separately describes road-freight APIs, EDI for booking, visibility and invoice information, and eBilling. It does not publish a universal group-wide X12 transaction matrix on that page.
  • Public sources were reviewed on November 9, 2026. Assigned UK account agreements, private EDI maps and production approval were not inspected. This guide is not evidence that SignalEDI is a DHL partner, certified provider or operator of a live connection for any DHL division.

Questions to resolve from the current buyer packet

  • Name the DHL division in the project scope, acceptance record and operational dashboard. Confirm account and service eligibility before reusing credentials, endpoints, message layouts or examples from another DHL program.
  • Record the current technical guide, format and environment for each function. Where details are available only through onboarding, keep them as explicit dependencies rather than filling the gap with a generic carrier transaction set.
  • Map customer order, shipment, parcel or handling unit, carrier reference and invoice identity. Review which identifiers remain stable after a booking change, relabeling or service adjustment.
  • Agree how service selection is validated for origin, destination, package characteristics and the actual contract. Do not let a fallback service silently change the commercial commitment or international handling.
  • Keep label creation, booking, collection, delivery and billing as distinct operational states. Assign owners to resolve missing events or conflicting references rather than treating an available label as evidence that goods moved.
  • Complete the selected division's testing and approval before production. State which accounts, lanes and functions were verified, and keep unsupported services outside the readiness claim.

How SignalEDI handles it

  • Prepare a versioned mapping and testing checklist from the requirements you provide.
  • Validate synthetic or scrubbed samples before partner testing.
  • Review acknowledgement and exception handling before production cutover. Scope is confirmed during setup.

Review mapping and validation in the self-serve workspace before partner testing. Developer quickstart

Pricing

SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Compare current plans

Practice the workflow before partner testing

These are recommended preparation exercises, not additional partner requirements or a customer success story. Use synthetic or scrubbed samples and adapt each exercise to the current guide assigned to your program.

Prevent cross-division routing

Prepare synthetic Express, eCommerce UK and road-freight project records with their intended account and guide. Deliberately attach a document or service reference from the wrong division. Review the control that validates scope before a request can enter a live transmission queue.

What a useful result looks like

A common DHL brand name does not override the selected business contract. Conflicting account, service or interface information is held with a clear explanation. The configuration and readiness record identify exactly which division and functions were checked rather than claiming group-wide connectivity.

Validate a UK-origin parcel scenario

Create domestic and international examples for the selected UK parcel program, plus a deliberately out-of-scope origin. Review product eligibility and required information using the current account guide. Keep customs decisions with the responsible business owner and avoid inventing mandatory fields from an unrelated API.

What a useful result looks like

Only scenarios within the confirmed service and account scope proceed. Missing cross-border information creates an actionable dependency, and an unsupported origin is not silently rerouted. A technical sample remains separate from actual carrier acceptance and legal or tax compliance for the shipment.

Track a booking change without duplicate movement

Model a shipment whose package details change before physical collection. Determine the permitted update, cancellation or replacement workflow for the assigned interface. Follow old and new shipment references, labels and booking state through the local example without making real carrier requests.

What a useful result looks like

The warehouse can identify the valid shipment record and avoid using obsolete labels or duplicate bookings. A successful document-generation step does not imply pickup or delivery. Unsupported correction behavior remains visible for confirmation instead of being borrowed from another DHL business unit.

Reconcile events and billing separately

Use a synthetic shipment with an initial tracking event, a later delivery event and an invoice that arrives on a different schedule. Add a repeated event and a charge discrepancy. Review which records are authoritative for movement, accounting and exception resolution.

What a useful result looks like

Repeated status input does not create duplicate customer updates or financial entries. Delivery evidence does not automatically approve the charge, and billing does not manufacture a missing delivery event. Each unresolved obligation retains its owner and source references until the appropriate business process resolves it.

Common integration questions

Can I keep my existing ERP or accounting system?
Start with your existing system, its version, and the records you need to exchange. SignalEDI builds to your trading partner's requirement. Scope is confirmed during setup. Review the integration catalog for the specific connector and workflow before assuming production availability; an ERP name alone does not establish support for every edition or document.
Does validation mean my partner has approved production?
No. Passing document validation checks your sample against the configured rules. Partner certification, enrollment, transport approval, and permission to send live documents are separate steps controlled by the applicable partner program. Use synthetic or scrubbed samples while preparing and keep the approval evidence before switching to production.
Where can I see SignalEDI pricing?
SignalEDI publishes flat monthly EDI pricing: Seasonal $99, Starter $199, Growth $999, and Enterprise $1999 per month. There are no per-document fees inside your allowance. Finite plans alert you at 80% and 100% of the included monthly allowance and keep processing; each document beyond the allowance is billed at $0.30 per document. Enterprise includes 20,000 documents per month.

Authoritative sources

Source review date: 2026-11-09. Links below establish only the facts described; your current buyer-issued materials remain authoritative for program-specific technical requirements.

DHL UK questions

Is there one DHL UK EDI specification for every shipment?
The public sources do not establish one. Start with the contracting division, service and account, then obtain its current technical packet. DHL's shared developer portal is a useful catalog, but it does not make Express, eCommerce and Freight interchangeable. Confirm the scope before committing to document codes, endpoints or a production schedule.
Can DHL UK eCommerce API access be reused for DHL Express?
Do not assume that it can. Treat each division's account and interface as a distinct authorization and configuration boundary. Reusable software may be possible, but service eligibility, credentials, payloads and acceptance need to be checked separately. A successful request in one program is not proof that another division's shipping or billing function is available.
What should a DHL UK integration verify before sending live shipments?
Verify the account, division, service, lane, package structure and required business data, then exercise recovery and reconciliation. Keep any partner test acceptance separate from internal mapping results. The advisory scenarios below cannot establish customs compliance, a commercial partnership or permission for SignalEDI to create production bookings on the account.

Related EDI resources

Prepare your side for partner testing

SignalEDI can validate the documents and requirements your team controls. Partner approval follows the partner's schedule.

Connect now

Topics: DHL UK EDI requirements · DHL UK supplier EDI · DHL UK EDI UK

© 2026 SignalEDI Inc. All rights reserved.