Evri (formerly Hermes UK) ↔ Sage 200 Integration

Evri (formerly Hermes)Courier

High-volume economy UK parcels — ParcelShop drop-off + courier collection with lighter-weight B2C profile; API consignment booking, label print, tracking writeback.

Evri (formerly Hermes UK) is the UK's high-volume economy parcels network. They offer both ParcelShop drop-off locations (where customers drop off parcels) and courier collection (where drivers pick up). The B2C profile is lighter-weight than the full Metapack or UK Mail services — suited to e-commerce and small businesses who want cost-effective UK-wide coverage. The integration connects Sage 200 to Evri's API for consignment booking, label printing, and tracking writeback. The key is keeping Sage 200 in sync with which orders are ready to despatch, mapping Sage delivery methods to Evri service options, and ensuring tracking updates flow back so despatch notes can be closed as 'carrier confirmed' rather than manually updated.

Data Flows

  1. 1

    Despatch → consignment

    On despatch-complete in Sage 200, orders are booked via Evri's consignment API. Service type (ParcelShop drop-off vs courier collection) is selected based on the Sage delivery method mapping table; weight defaults from packaging rules where Sage stock items don't carry them. Each consignment gets a unique reference that links back to the Sage despatch record for audit.

  2. 2

    Labels

    Evri returns the label PDF (and optionally ZPL for thermal printers) at the moment the consignment is created. The label is available immediately so pack stations can print and attach before the parcel leaves the warehouse, even for ParcelShop drop-offs where the customer needs to present the label at the shop.

  3. 3

    Collection & manifest

    End-of-day manifest closes against Evri's collection routing. Missed manifest cut-offs are surfaced to Sage (despatch team gets a review queue for late bookings). For courier collection bookings, drivers get the manifest with pickup routes optimized for the day.

  4. 4

    Tracking writeback

    Evri's tracking events (picked up, in transit, delivered, failed) flow back into Sage — either onto the despatch record or a tracking table per SOP. Customers see the 'where is my order' status in Sage (or integrated into the e-commerce store) without logging into Evri's portal.

Where These Integrations Go Wrong

The failure modes we design around — most Evri (formerly Hermes) ↔ Sage projects hit at least two of these.

Consignment pooling

Evri groups multiple parcels into a single consignment for cost efficiency (especially for courier collection). If Sage's ERP model is one-tracking-number-per-order, the mapping breaks accountability. Use a 'consignment per despatch' rule or overlay a consolidation step in Sage to match Evri's grouping.

ParcelShop vs courier choice

Customers choose the drop-off option at checkout; the integration should expose that choice in Sage so you can charge appropriately (ParcelShop is cheaper per parcel, courier collection costs more). If your business model defaults one way, a simple mapping table in Sage can drive the selection automatically.

Weight/dimension defaults

Evri needs parcel weight and dims for pricing. Sage 200 usually lacks this data. We default from a packaging rules table (carton type per order value/line count) and let the pack station correct it rather than blocking bookings on missing data.

Cut-off times and service windows

Evri has strict manifest cut-off times (typically 4pm for next-day). Despatching after cut-off must roll to tomorrow's manifest or the collection request fails. Build the cut-off into Sage's despatch logic, not as an afterthought error queue.

What's Included

  • Despatch-triggered Evri consignment booking with service-type (ParcelShop/courier) mapping
  • Label printing integration (PDF and ZPL) for pack bench or warehouse printers
  • Manifest close with cut-off handling and next-day rollover for late bookings
  • Tracking writeback into Sage despatch records + optional tracking table
  • Failed-booking queue with validation errors (address, weight, cut-off) surfaced for fixing
  • Test-company UAT against your live Evri account (ParcelShop network and courier service)

Who It's For

E-commerce and small business owners who need UK-wide parcel coverage at economy prices — they want the simplicity of one API for both drop-off and collection options, and they don't need multi-carrier rate shopping (that's Metapack's sweet spot). Typically, businesses that use Sage 200 for order processing and want tracking to flow back without manual updates, and those whose customers choose between ParcelShop drop-off and courier collection at checkout.

FAQ

Evri vs Hermes — which API do we use?

Evri (formerly Hermes UK) uses the same modern API surface across the UK. If your contract says Hermes UK, you still use the Evri API — the old Hermes SOAP gateway is retired. The Sage-side logic is identical for both branding.

Can we charge for courier collection vs ParcelShop?

Yes — the mapping table can tag each delivery method as either 'ParcelShop' or 'courier', and we can apply different surcharges in Sage (or via the Evri API pricing). The customer sees the option at checkout, and Sage records the choice.

What if the customer chooses ParcelShop but we need courier collection for the route?

We expose the constraint during Sage despatch: if the mapped service is ParcelShop but weight/dims exceed what's practical for collection, we surface a warning and allow an override to courier collection (with appropriate cost adjustment). This is done in a validation queue before booking.

EKM ↔ Sage 200Interlink Express / DPD Local

Scope Your Evri (formerly Hermes) Build

Fixed quote once we know your Sage version, the flows you need and the volumes.

Sage 200 ServicesTalk to Us