Evri API · Courier Integration · UK
Evri API Integration.
Custom Evri API integration for UK ecommerce businesses — automated shipment creation, label generation, service selection, tracking and returns built directly into your platform or WooCommerce store. Fixed price. You own the code.
Or describe what you need in one line — I’ll reply within one business day.
What it does
What the Evri API provides.
The Evri API provides programmatic access to Evri’s UK parcel delivery network — creating shipments, generating labels, retrieving tracking events and managing returns without anyone logging into Evri’s business portal manually. Evri is one of the UK’s largest dedicated parcel carriers, handling millions of parcels per week for ASOS, Next, M&S, Etsy and thousands of UK ecommerce businesses.
A custom integration connects Evri directly to your WooCommerce store or platform: order placed, shipment created automatically, label generated and printed, tracking number written back to the order, despatch confirmation sent to the customer. Nobody logs into a portal. Nobody manually enters an address. The daily despatch process runs without manual intervention.
Who it’s for
Who uses an Evri API integration.
WooCommerce stores shipping with Evri
Orders trigger Evri shipment creation automatically on payment. Weight, address and parcel value read from the WooCommerce order — no manual entry. Labels print automatically for thermal printers or route to PDF for desktop printing. Tracking numbers write back to the order and go into the despatch email. For stores currently spending 30+ minutes per day on manual Evri portal work.
Ecommerce businesses with custom platforms
A bespoke ecommerce platform, custom order management system or non-standard WooCommerce setup that doesn’t have an Evri plugin available. The integration hooks into your platform’s order events and despatch workflow — wherever the trigger lives, the label generates and the tracking number comes back.
Businesses wanting branded tracking pages
Live Evri tracking status on your own customer-facing tracking page — not Evri’s website. Automated notifications triggered by Evri events: despatch confirmed, out for delivery, delivered, delivery attempted. Your customers stay on your domain throughout the post-purchase experience.
Businesses needing label-free QR returns
Evri’s QR code returns allow customers to drop a parcel at any Evri ParcelShop by scanning a QR code — no label required. For clothing, footwear and high-return-rate products, removing the print-at-home label step reduces returns friction significantly and increases completed return rates. Requires additional credential setup with Evri.
Multi-carrier operations using Evri alongside DPD or Royal Mail
Evri for standard delivery, DPD for next-day, Royal Mail for lightweight or remote-address items. A single integration layer selects the carrier automatically based on service level, weight and destination. No manual carrier decisions — the right carrier is selected on every order, every time.
Why custom
Why a plugin won’t cut it.
Custom service selection
Plugins offer a fixed default or a dropdown. Custom logic — cut-off time, weight band, checkout option — selects the right Evri service automatically on every order.
Thermal printer routing
Plugins generate PDFs. A custom integration routes ZPL labels directly to thermal printers at the moment of shipment creation. Labels print without anyone clicking anything.
Multi-carrier in one build
Plugins are single-carrier. A custom integration can route to Evri, DPD or Royal Mail automatically — one integration point, optimal carrier on every order.
QR code returns
Plugins don’t support Evri’s QR code return flow. A custom integration generates the QR code and delivers it to the customer digitally — no printer required.
The process
How an Evri API integration is built.
Note: Evri API credentials are provisioned by your Evri Account Manager and require test label approval before production go-live. Start both processes early.
Scoping
We map your despatch workflow, service selection rules, label format, tracking requirements and whether QR returns or ParcelShop delivery are in scope.
Fixed-price quote
Clear, itemised quote before work begins. Scope agreed in writing.
Evri sandbox setup
OAuth authentication, Evri sandbox credentials configured and all shipment creation, label generation and tracking logic built and tested in sandbox before any production access.
Test label submission
Test labels generated using Evri’s provided test address list and submitted to Evri for approval. Development continues while approval is pending.
Production and handover
Switch to production credentials on approval. End-to-end testing with real shipments. Full documentation. You own the code.
The deliverable
What’s included.
What I build
- Evri OAuth 2.0 authentication with token caching
- Shipment creation triggered by your order events
- Label generation — PDF or ZPL for thermal printers
- Parcel value mapping from your order data
- Custom service selection rules
- Tracking number write-back to your order record
- Live tracking data retrieval
- Customer notification triggers from tracking events
- Returns label generation (standard or QR code)
- Error handling — address failures, weight limits, API unavailability
- Technical handover document
What’s not included
- Evri Corporate Business account — you need an active account meeting Evri’s volume threshold
- Evri API credentials — provisioned by your Evri Account Manager
- Test label approval — submitted as part of the build, approved by Evri
- QR code credential setup — separate request to Evri required if in scope
- Evri per-parcel shipping rates — negotiated with Evri directly
- Thermal printer hardware — integration supports your existing printer
Pricing
Fixed-price builds. No hidden costs.
Evri API access is free. Per-parcel shipping rates are negotiated with Evri directly and are not part of the build cost.
Standard
£995
~3–5 days
Shipment creation and label generation triggered by your order events. Service selection to your rules, parcel value mapping, tracking number write-back, order status update and error handling. Assumes standing daily Evri collection.
- OAuth 2.0 authentication
- Shipment creation from order events
- Label generation (PDF or ZPL)
- Parcel value mapping
- Custom service selection rules
- Tracking number write-back
- Error handling and logging
- Tracking event notifications
- Returns label generation
- Multi-carrier routing
Platform Integration
£1,595
~1 week
Everything in Standard, plus live tracking on customer-facing pages, automated notifications triggered by Evri events, returns label generation (standard and QR code), and full OMS or warehouse system integration.
- Everything in Standard
- Live tracking on customer pages
- Automated customer notifications
- Returns label generation
- QR code returns (if Evri credentials allow)
- OMS or warehouse integration
- Thermal printer ZPL routing
Multi-carrier
£2,295
~2 weeks
Evri plus Royal Mail or DPD from the same integration layer. Automatic carrier selection based on service level, weight, dimensions and destination. One integration, multiple carriers, optimised postage cost on every order.
- Everything in Platform Integration
- Second carrier API integration
- Automatic carrier selection logic
- Weight and format-based routing
- Service-level routing
- Technical handover document
Payment terms: 50% on agreement, balance on completion. Evri API credentials and test label approval are managed by Evri — start both processes when commissioning the build. Evri Corporate Business account required.
Common questions
Evri API FAQ.
How do I get Evri API credentials?
Contact your Evri Account Manager to request API access. They’ll provision your Client ID, Client Secret, username and password for both sandbox and production environments. Evri requires a Corporate Business account with minimum volume thresholds before API access is granted. Start this process at the same time as commissioning the build.
What is the test label approval process?
Before Evri grants production API access, you must create test labels using a list of addresses Evri provides and submit them for approval. Evri reviews the labels to confirm correct formatting and data. Approval typically takes a few days to a week. Development continues in the sandbox while approval is pending, so it doesn’t hold up the build itself — just the production go-live.
Can I use Evri QR code returns?
Yes — Evri’s QR code return flow (label-free drop-off at ParcelShops) is supported in the Platform Integration tier. It requires additional API credentials from Evri specifically for the Print in Store API. Request this from your Evri Account Manager alongside the standard API credentials. Without the additional credentials, standard returns labels are generated instead.
Can it work with WooCommerce?
Yes — WooCommerce integration is the most common Evri build. Orders trigger shipment creation on status change, labels generate and print, tracking numbers write back to the WooCommerce order, and despatch emails go to the customer automatically. See Evri API WooCommerce guide.
How does Evri compare to DPD?
DPD offers a one-hour delivery window and premium delivery experience. Evri is more cost-effective for standard delivery volumes. Many businesses use both — DPD for next-day, Evri for standard. The multi-carrier tier handles automatic selection between both. See the Evri vs DPD comparison for the full picture.
How long does the build take?
Standard takes 3–5 days. Platform Integration takes approximately one week. Multi-carrier takes approximately two weeks. Go-live depends on Evri’s test label approval timeline alongside development.
An Evri integration fits straight into the websites I design in Blackburn, and works best alongside SEO that gets you found by more local shoppers.
Need Evri API integration built?
Describe your despatch workflow, your platform and your approximate daily volume — I’ll come back with a clear answer on what’s involved and what it costs. Fixed price, no obligation.
