WooCommerce and Evri is one of the most common shipping integrations for UK ecommerce businesses. Evri is widely used by small to mid-size UK online retailers for standard parcel delivery, and automating the connection between WooCommerce orders and Evri despatch removes one of the most time-consuming daily tasks in running an ecommerce operation. This post covers how a WooCommerce Evri integration works, what it automates, and when a custom integration is worth more than a plugin.
What a WooCommerce Evri integration automates
Shipment creation. When a WooCommerce order reaches the trigger status — typically “Processing” for paid orders — the integration creates the shipment in Evri automatically. Recipient name, address, phone number, package weight and parcel value are all read from the WooCommerce order. Evri validates the address and returns the consignment number and tracking reference.
Label generation. Labels are generated immediately after shipment creation. For businesses using thermal printers (Zebra, Dymo, BIXOLON), labels are routed directly to the print queue in ZPL format without anyone downloading or clicking print. For desktop printing, labels are stored as PDF against the order and available on demand.
Tracking number write-back. The Evri tracking number is written back to the WooCommerce order automatically. It appears in the order detail in WooCommerce admin, is available to customer service staff, and is included in the despatch confirmation email sent to the customer. A customer clicking the tracking link goes directly to Evri tracking for their parcel.
Order status update. When the label is generated, the WooCommerce order status updates automatically to Shipped or a custom despatch status. WooCommerce sends the configured despatch notification email with the tracking number included.
Service selection in WooCommerce
A custom WooCommerce Evri integration can select the right Evri service automatically rather than requiring manual service selection at despatch. Common patterns:
Checkout-driven. The customer selects standard or express delivery at checkout. The service selected maps directly to the appropriate Evri service code — no manual decision required at despatch time.
Weight-based routing. Orders under a weight threshold use Evri’s standard parcel service. Orders above the threshold route to the large parcel service or flag for manual handling. Configured once, applied automatically to every order.
Cut-off time logic. Orders placed before a configured cut-off time are created with the same-day collection service. Orders placed after cut-off are created for next-day collection. The integration applies this automatically based on the order timestamp without any manual assessment.
ParcelShop delivery. Where a customer selects ParcelShop delivery at checkout, the integration passes the chosen ParcelShop location to the Evri API and generates a label for that delivery address. Requires the ParcelShop location ID to be captured at checkout — typically via a map-based ParcelShop finder widget integrated with checkout.
Evri WooCommerce plugins vs custom integration
WooCommerce Evri plugins exist — several third-party options handle basic shipment creation for standard WooCommerce setups. They’re adequate for simple requirements. The limits appear when:
Custom trigger logic is needed. Plugins fire on standard WooCommerce order status changes. A custom integration can fire on any condition in your system — a specific product category, a minimum order value, a fulfilment location condition, or a combination of factors a plugin can’t express.
Thermal printer routing matters. Plugins generate PDFs. Automatic ZPL routing to a thermal printer requires a custom build. At high despatch volumes, printing labels automatically rather than clicking print on each PDF saves significant time.
Multi-carrier routing is needed. Plugins are single-carrier. A custom integration routes orders to Evri, Royal Mail or DPD automatically based on service level, weight and destination. This is particularly valuable for businesses that use Evri for standard parcels and Royal Mail for lightweight or remote-address shipments.
Non-standard workflows. Businesses with a separate warehouse management system, multiple fulfilment locations, or custom order statuses need the integration to hook into their specific workflow events rather than standard WooCommerce transitions.
Parcel value mapping in WooCommerce
Evri requires every shipment to include a parcel value for insurance purposes. In a WooCommerce integration, this maps from the WooCommerce order total. The integration reads the order subtotal and passes it to Evri’s parcel value field. For orders with discounts applied, the post-discount order total is the appropriate value. This mapping is straightforward but must be explicit — a shipment without a valid parcel value will be rejected by Evri.
For businesses with a mix of high and low value orders, the parcel value field also affects Evri’s carrier liability. For particularly high-value orders, flagging them for manual review before shipment creation — rather than automatically creating a label — is worth considering during scoping.
Error handling in WooCommerce
A production Evri WooCommerce integration will encounter failed shipment creation. Common causes: postcode that doesn’t validate against the address, phone number missing from the billing details, parcel dimensions that exceed the service limit, or Evri API unavailability.
Each failure needs a defined handler. Address validation failures flag the WooCommerce order with a custom status and an order note showing the specific Evri error message. Missing phone numbers prompt a customer data check. API unavailability triggers an automatic retry and escalates to an internal alert if retries are exhausted. Without explicit error handling, failed shipment creation leaves orders silently unshipped — found only when the customer asks where their parcel is.
For the full Evri service and pricing, see the Evri API integration service. For the complete Evri API guide, see Evri API integration guide. For how Evri compares with DPD, see Evri API vs DPD API. For what the build costs, see Evri API integration cost.
Related posts
- Evri API integration: a complete guide
- Evri API vs DPD API
- Evri tracking API integration
- Evri API integration cost
Batch despatch and high-volume processing
For businesses processing significant order volumes, the integration can handle batch despatch. Rather than creating Evri shipments individually as orders are placed, a batch run processes all orders in the trigger status at a configured time — typically before the daily Evri collection window. All labels are generated in the batch, orders are updated, and a summary report shows what was despatched, what failed and what needs manual attention.
Rate limit management is included in the batch processing logic to ensure the integration doesn’t exceed Evri’s API call limits during a high-volume batch. Requests are spread over the batch window rather than firing simultaneously. For businesses with highly seasonal volumes — Black Friday, Christmas — the rate management means the batch processes correctly even at peak.
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 →