Evri API vs DPD API: Which Is Right for Your Business?

Evri and DPD are two of the most widely used courier APIs for UK ecommerce businesses. Both offer parcel delivery across mainland UK, both have REST APIs for programmatic shipping, and both require a business account with credentials provisioned by an account manager. The differences are in delivery experience, network characteristics, pricing model and the type of business they suit best. This comparison covers the practical differences and helps identify which is right for your operation — or whether using both makes sense.

Delivery experience: the key difference

This is where DPD and Evri diverge most clearly, and it matters for customer satisfaction.

DPD is built around its one-hour delivery window. When a DPD parcel is out for delivery, the recipient receives a notification with their specific delivery hour. They can then redirect to a neighbour, safe place or DPD Pickup shop without contacting anyone. Failed first deliveries are significantly less common with DPD because recipients can act on the notification. DPD is the carrier of choice where delivery experience is a competitive differentiator.

Evri provides delivery notifications but without the one-hour window precision. Evri’s network is built for cost-effective standard delivery — 3–5 days for standard service, next-day where available. Evri’s strength is volume and coverage rather than premium delivery experience. ASOS, Next, M&S and Etsy use Evri precisely because it handles very high volumes at competitive rates.

For ecommerce businesses where customers expect next-day delivery with a precise window, DPD is the stronger choice. For businesses where standard delivery at competitive postage cost is the priority, Evri is typically more cost-effective.

Parcel Shop and locker networks

Both carriers offer out-of-home delivery options, but the networks differ.

DPD Pickup operates through a network of local shops and convenience stores. DPD also has automated lockers in higher-density urban areas. The Pickup network is well-established and integrations for Pickup point selection at checkout are mature.

Evri ParcelShops are available in over 7,000 locations including convenience stores, supermarkets and newsagents. Evri also offers QR code drop-off — customers take their parcel to a ParcelShop and scan a QR code without needing to print a label. This is a genuine differentiator for returns in particular — customers can drop off without a printer, which significantly reduces the friction in the returns process. QR code functionality requires additional API credentials from Evri.

Coverage

Both DPD and Evri have strong mainland UK coverage. The differences are at the edges.

DPD covers the vast majority of UK postcodes for next-day delivery. Remote areas — Scottish Highlands, islands, some rural postcodes — may have extended delivery times or surcharges.

Evri has similar mainland coverage. Evri’s pricing to remote areas is generally competitive, though delivery times to remote postcodes are typically 3–5 days regardless of service chosen. For businesses with significant volumes to rural or remote addresses, both carriers should be compared on actual negotiated rates.

Neither carrier should be used as the only carrier for businesses that regularly ship to Scottish islands, Northern Ireland or other areas where surcharges apply — Royal Mail covers these addresses at standard rates.

Pricing

Both DPD and Evri use negotiated account-based pricing — the rates depend on your volume, mix of service types and commercial relationship with the carrier. Neither has published retail rates that apply to all business accounts.

As a general guide from market knowledge: Evri tends to be more cost-effective for standard 3–5 day delivery at moderate to high volumes. DPD tends to be more expensive but the delivery experience premium is reflected in lower failed delivery rates and fewer customer service contacts. For businesses that have costed the downstream cost of failed deliveries (redelivery charges, customer service time, negative reviews), DPD’s higher per-parcel rate sometimes works out cheaper in total.

API integration comparison

Both APIs follow similar patterns: OAuth 2.0 authentication, REST endpoints for shipment creation, label generation as base64 PDF or ZPL, tracking via consignment number. Both require credentials provisioned by an account manager — no self-serve developer portal. Both have sandbox environments.

The differences: DPD’s API is slightly more mature and better documented. Evri’s API requires test labels to be submitted for approval before production access — an additional step DPD doesn’t require. Evri’s parcel value field is mandatory; DPD’s equivalent is optional for most services. Both integrations take approximately the same time to build for equivalent functionality.

When to use Evri

Evri is the better choice when: your existing carrier is Evri and you’re automating an existing relationship; standard 3–5 day delivery is acceptable to your customers; postage cost per parcel is a significant margin consideration; or you want QR code returns for a label-free returns experience.

When to use DPD

DPD is the better choice when: next-day delivery with a one-hour window is a customer expectation; failed first deliveries are a current customer service issue; or you ship predominantly to business addresses where DPD’s timed services are a requirement.

Using both together

Many UK ecommerce businesses use both. DPD for next-day and premium services, Evri for standard delivery where cost-effectiveness matters. A multi-carrier integration selects the carrier automatically based on the service level chosen at checkout — the customer’s choice drives the carrier selection without any manual intervention. Combined with Royal Mail for letter-format items and remote addresses, a three-carrier integration optimises postage cost and delivery experience simultaneously.

For DPD integration, see the DPD API integration service. For Evri integration, see the Evri API integration service. For Royal Mail, see the Royal Mail API integration service. For the DPD vs Royal Mail comparison, see DPD API vs Royal Mail API.

Integration complexity and timeline

Both Evri and DPD require credentials provisioned by an account manager — no self-serve portal. Both have sandbox environments for development testing. The main additional step with Evri is the test label submission and approval process before production access, which adds a few days to the go-live timeline. DPD doesn’t have this step. Both integrations take approximately the same time to build for equivalent functionality once credentials are available.

The multi-carrier build combining Evri and DPD in the same integration is meaningful additional scope. Each carrier has different authentication, different service codes, different label formats and different error responses. A well-designed multi-carrier integration abstracts these differences behind a common interface so your platform doesn’t need to know which carrier is being used — the carrier selection logic handles it, and the result is always a label and a tracking number regardless of carrier.

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 →