DPD API Integration Cost: What to Expect in the UK

The DPD API is free to use once your DPD Business account has API credentials provisioned. The cost of integration is the development work: building the connection to your platform, implementing service selection logic, generating and routing labels, connecting tracking data, and handling edge cases correctly. That development cost ranges from £995 for a standard label generation integration to £2,295 for a multi-carrier build combining DPD with Royal Mail or another carrier.

Build tiers

Standard integration: £995

Shipment creation and label generation triggered by order events on your platform, tracking number written back to your order record, and order status updated on despatch. Service selection based on a defined ruleset. Error handling for address validation failures, weight limit errors and API unavailability. Technical documentation included.

Collection booking is not included in the standard tier as standard — most businesses have a standing daily DPD collection that doesn’t require API booking. If on-demand collection booking via the API is needed, this is scoped as an add-on based on whether a date/time slot selection UI is required. Timeline: approximately 3–5 days.

Platform integration: £1,595

Everything in the standard tier, plus the integration wired into your existing platform workflow. Results stored to your database or OMS. Display built to your design. Lookup triggered by your existing workflow events rather than just WooCommerce status changes. Live tracking status on customer-facing order pages. Customer notification emails triggered by DPD tracking events. Returns label generation on request or automatically on return approval. For businesses with a separate OMS, warehouse management system or custom platform.

Timeline: approximately one week.

Multi-carrier: £2,295

DPD plus Royal Mail (or another carrier) from the same integration layer with automatic carrier selection logic. Orders route to DPD or Royal Mail based on service level chosen at checkout, package dimensions, weight band and destination. Large letter format items route to Royal Mail automatically to take advantage of the lower postage rate. Next-day orders route to DPD. Standard orders route to the most cost-effective carrier for that package profile. A single integration point handles both carriers — your platform doesn’t need to know which carrier is being used.

This is the highest-value tier for ecommerce businesses shipping significant volumes with a mixed service requirement. The carrier selection logic typically recovers its build cost in postage savings within a few months. Timeline: approximately two weeks.

Collection booking as an add-on

If you need to book DPD collections via the API — rather than relying on a standing daily collection — the scope depends on how the booking needs to work. Automatic booking using a fixed collection address and the next available slot is relatively simple to add. A UI that queries available slots and lets a user select a date and time window is more involved. Both are available as add-ons to any tier, priced during scoping based on your specific requirements. If you’re unsure which approach you need, the scoping conversation will clarify it.

What drives the cost up

Complex service selection logic. Routing orders based on weight, dimensions, order value, service level and destination is fast to implement for a few simple rules. Multi-factor logic combining many conditions takes longer to design and test.

Thermal printer integration. Routing ZPL labels directly to thermal printers requires additional configuration for the print server communication, but eliminates the need for anyone to manually trigger label printing.

Legacy or bespoke OMS. Connecting DPD to a well-documented modern platform is fast. Integrating with a legacy order management system with limited API access, unusual data structures or restricted credentials takes more time.

International shipping configuration. Domestic UK shipping is the standard scope. Adding international service configuration — DPD International service codes, customs data requirements for non-UK destinations, address validation for international formats — adds scope.

Ongoing costs

The DPD API is free to use. DPD’s per-parcel shipping rates are negotiated directly with DPD through your business account — these are not part of the build cost. An optional retainer of £49/month covers API monitoring and updates if DPD changes their API endpoints or authentication requirements. DPD doesn’t change their API frequently but API credentials occasionally need rotating.

For the full service details, see the DPD API integration service. For WooCommerce integration, see DPD API for WooCommerce. For the DPD vs Royal Mail comparison, see DPD API vs Royal Mail API. For the Royal Mail integration service, see the Royal Mail API integration service.

DPD API vs plugin cost comparison

WooCommerce DPD plugins typically cost £50–£150 per year. They handle basic shipment creation for standard WooCommerce setups. The custom integration at £995 is a one-time build cost that pays for itself in time savings and operational reliability within a few months for any business shipping more than 20–30 parcels per day.

Manual despatch processing — logging into DPD’s portal, entering order details, generating labels — takes approximately 2–3 minutes per shipment at best. At 50 shipments per day that’s 100–150 minutes of daily overhead, or roughly 2.5 hours. At a conservative £15/hour labour cost, that’s £37.50 per day in time spent on manual despatch — over £9,000 per year. A £995 integration cost against £9,000 annual labour saving is a straightforward decision.

The plugin alternative adds annual recurring cost without eliminating the manual workflow entirely — plugins still require manual intervention for edge cases, non-standard orders and service selection decisions. A custom integration handles these automatically.

Getting DPD API credentials

Unlike many APIs on this site, DPD doesn’t have a self-serve developer portal. API credentials are provisioned by DPD through your business account manager. If you don’t yet have a DPD Business account, that needs to be established first — DPD has minimum volume requirements for business accounts, typically around 30–50 parcels per week. If you have an existing DPD account, contact your account manager to request API access.

DPD typically takes a few days to a couple of weeks to provision API credentials. Starting the credential request at the same time as commissioning the build means the credentials are ready by the time development and sandbox testing are complete.

If you need help with a custom API integration for your website or business application, I can help. I build bespoke API integrations for UK businesses. See API integration pricing or get in touch to discuss your project.

Need a custom integration built?

I build custom API integrations — Stripe, Companies House and bespoke data pipelines. Reliable, well-documented, no agency overhead.

Discuss your project →