Skip to main content
Talk to an expert
Evri logo

Evri integration for ecommerce fulfilment

Dispatch orders to Evri and track returns reliably. iWeb routes confirmed orders to Evri with the right service level, pulls tracking updates for customer visibility, and closes returns through automatic receipt and credit posting. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: shipping connector, warehouse integration, fulfilment plugin, app.

EvriiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Evri integration gives you.

Customers see live tracking immediately

Tracking numbers and delivery updates appear in customer accounts and email notifications within minutes of Evri's shipment acceptance, reducing support inquiries about dispatch status.

Returns close quickly without manual rework

Return labels generate automatically via Evri, customers drop off parcels, receipt flows into ERP, and credits post without manual queue review.

Dispatch queues never silently backlog

Failed shipments (address issues, weight errors, restrictions) surface with clear exception detail and automatic retry logic, not buried in logs.

Finance and operations stay synchronized

Dispatch confirmations trigger invoice generation at the right moment; return receipts trigger credit notes without duplicate or missed postings.

Carrier service rules adapt to business rules

Delivery speeds, service levels, and special handling are governed by your fulfillment strategy, not Evri's defaults, without manual per-order override.

02 · When it's worth it

Where a Evri integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Route orders from commerce checkout to Evri dispatch queue with carrier rules applied
Pull live tracking updates and delivery confirmations back to customer orders
Manage returns authorizations, label generation, and return receipt into ERP stock
Handle carrier service-level selection based on delivery postcode or customer tier
Reconcile dispatch and tracking events against order records for fulfillment visibility
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Carrier rule selection not dynamic

Most standard Evri connectors require upfront configuration of service-level rules by postcode or spend threshold. Real-time carrier selection based on live capacity, weather, or campaign rules typically requires custom logic.

Return condition capture limited

Evri's standard return feed includes receipt confirmation but limited detail on parcel condition or damage assessment. Custom workflows for photo capture, condition codes, or routing damaged returns to QA require additional integration.

Exceptions and failed despatch queuing

If Evri rejects a shipment (address issues, weight mismatch, etc.), standard connectors often leave the order in a holding state without clear exception handling or automatic retry logic.

International shipping constraints

Evri's standard UK and some EU service levels have limited international reach. Cross-border returns and non-EU shipping typically require fallback carrier rules or manual intervention.

Real-time stock sync on return

Return receipt confirmation reaches ERP, but stock availability in commerce may lag if inventory is not updated in real time or if ERP processing queues build up during peak returns periods.

04 · The real work

The gap between shipment dispatch and first tracking update often reveals whether exception handling and polling frequency are tuned for your customer expectation, not just integration defaults.

05 · Where it sits

Where this integration sits in your estate.

Evri holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Commerce platform agnostic. Connect Evri across your entire technology stack.

System of record
Source / owner
Evri
Parcel carrier and returns handler; executes dispatch and return receipt
  • Service-level execution and last-mile delivery
  • Tracking number generation and tracking events
  • Return label generation and depot receipt
  • Carrier-side shipping rules and restrictions
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Fulfillment instruction authoring and order capture
  • Return authorization initiation
  • Customer notifications (dispatch, tracking, return labels)
Connected neighbours
Integration layer
ERP / finance
Receives dispatch confirmation to trigger invoicing; receives return receipt to post credits and stock movements
Integration layer
Inventory / warehouse
Supplies dispatch instructions with pick quantities; receives return receipt to trigger put-away and stock adjustment
Integration layer
Order management system (OMS)
Sources fulfillment instructions with address and service preference; updates order status from Evri tracking events
Integration layer
Returns management system
Issues return authorizations to Evri; receives return tracking and receipt confirmation
Integration layer
Customer notification platform
Receives tracking updates and delivery events from iWeb to send dispatch, tracking, and delivery confirmation messages
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (SAP, NetSuite, Sage, Infor)
  • Order management system
  • Inventory management system
  • Returns management platform
  • Warehouse management system (WMS)
  • Finance / invoicing system
  • Customer notification platform
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into COMMERCE & ERP
←From COMMERCE
Order and shipment detail: Confirmed orders and fulfillment line items flow to Evri with recipient address, weight, service level and any special handling instructions
The connector extracts order data from your commerce platform and maps it to Evri's shipment creation format.
Tracking and dispatch confirmation: Once Evri accepts a shipment, tracking numbers and carrier-specific events flow back to the order record in commerce
Customers receive tracking links, and your operations team sees confirmed pickup and in-transit milestones.
Dispatch and delivery events: Dispatch confirmation and final delivery events flow into ERP for fulfillment acknowledgement and invoice triggering
This ensures finance and operations have a consistent view of what has actually left the warehouse.
Return authorization requests: When customers initiate returns, return authorizations and label generation requests flow to Evri
Evri generates labels and return tracking, which feed back to commerce for display in customer portals.
Return receipt and reconciliation: When Evri receives a return, receipt confirmation and condition data flow back to ERP to trigger credit note generation and stock put-away instructions
This closes the returns loop in finance and inventory.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Design carrier and service-level logic

    We map your fulfillment strategy (next-day, weekend, special delivery) to Evri's service codes and build rules around postcode, spend, or customer segment so every order routes correctly.

  2. 02
    Handle shipment rejections and retries

    We implement exception queues for address validation failures, weight mismatches, and restricted postcodes with automatic retry or escalation to your fulfillment team.

  3. 03
    Synchronize tracking and dispatch events

    We poll Evri's tracking feed and write delivery milestones back to your order records and customer notifications in real time, without gaps or duplication.

  4. 04
    Build return label and receipt workflows

    We integrate return authorization capture, label generation via Evri, and return receipt confirmation so credits and stock movements land in ERP automatically.

  5. 05
    Monitor fulfillment health and exceptions

    We build dashboards and alerting so you see shipment acceptance rates, tracking lag, return receipt lag, and unprocessed exceptions at a glance.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataDispatch instructions (address, weight, service level, special handling)
Source / ownerCommerce platform / OMS
Maintained byFulfillment operations team
NotesiWeb integration carries these to Evri; ERP inventory holds the stock to be shipped.
DataCarrier service rules and postcode routing
Source / ownerFulfillment strategy (often held in commerce or OMS config)
Maintained byFulfillment manager and iWeb
NotesiWeb encodes rules in the integration; changes must be versioned and tested before live deployment.
DataTracking numbers and dispatch confirmation
Source / ownerEvri
Maintained byEvri API (automated)
NotesiWeb pulls and writes these into commerce order records in near-real time for customer visibility.
DataDelivery and in-transit events
Source / ownerEvri
Maintained byEvri API (automated)
NotesiWeb polls Evri's tracking feed and updates order status and customer notifications; ERP invoicing may depend on delivery confirmation.
DataReturn authorizations and return labels
Source / ownerCommerce platform / returns management system
Maintained byFulfillment operations team
NotesiWeb sends return requests to Evri; Evri generates labels and tracking which feed back to commerce for customer portal display.
DataReturn receipt confirmation and condition
Source / ownerEvri
Maintained byEvri API (automated)
NotesiWeb captures return receipts from Evri and triggers ERP credit notes and stock put-away; condition detail may need manual assessment for damaged items.
DataFulfillment exception and failure events
Source / owneriWeb exception queue (transient)
Maintained byiWeb integration and fulfillment operations team
NotesRejected shipments, validation errors, and Evri API failures are logged; operations team must review and resolve (reattempt, cancel, escalate) within SLA.
10 · Experienced integrator

Built this before

iWeb has built fulfillment integrations with Evri across multiple commerce estates. We understand how dispatch instructions, carrier rules, tracking events, and return receipts need to flow reliably without leaving orders stranded or credits unposted.

We know how to encode carrier service rules so orders route to the right service level and postcode restrictions are respected without manual override
We have built exception handling for address rejections and shipment failures that keeps your fulfillment queue clear and ops team informed
We design return workflows so labels generate automatically, receipts trigger credits in ERP, and stock is reconciled without manual rework
We monitor dispatch acceptance, tracking lag, and return receipt delay so you see fulfillment health at a glance
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify shipments with valid addresses are accepted by Evri and tracking numbers appear in commerce within 30 minutes
Confirm rejected shipments (bad address, weight mismatch) land in an exception queue with actionable detail and trigger ops alerts
Test delivery confirmation events update order status in commerce and trigger customer notifications without duplication
Validate return authorizations generate Evri labels and return tracking appears in customer portal within 15 minutes
Confirm return receipt from Evri triggers ERP credit note posting and inventory put-away within your finance close window
Check integration survives Evri API timeouts and recovers without manual intervention or data loss
Verify service-level rules (postcode, weight, speed) apply correctly to a mixed batch of test orders
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Orders stuck in dispatch queue after address validation fails

When Evri rejects an address as incomplete or undeliverable, the standard connector may leave the order in a pending state without notifying the warehouse or customer. Unhandled, shipments never despatch and customers never receive tracking.

Tracking lag causes customer support churn

If tracking events are not polled frequently enough or if polling fails silently, customers see no tracking for hours or days after dispatch, triggering support tickets and reshipping requests.

Return receipts do not trigger credit notes in ERP

If the return receipt feed breaks or is not monitored, ERP credit notes may be generated manually weeks later, or not at all, leaving customer refunds unposted.

Stock does not reconcile after return receipt

Return receipt confirmation may reach ERP, but if stock movements are not triggered or if ERP batch processes lag, inventory in commerce may show overstated availability until the next sync cycle.

Carrier service-level rules drift silently

If carrier rules (e.g., next-day for orders under 2kg, weekend service for specific postcodes) are configured in Evri without version control or audit, rule changes may apply to live orders without notification.

Duplicate shipments created during retry logic

If retry logic is not idempotent or if shipment creation is not keyed by order ID, transient timeouts can cause duplicate shipments to Evri, leading to oversend and double-charged carriers.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Evri integrations.

How does the integration decide which Evri service level to use for each order?

iWeb encodes carrier rules into the integration based on your fulfillment strategy: typically postcode bands, order weight, spend threshold, or customer segment. These rules are configured at launch and versioned; changes require testing and deployment approval.

What happens if Evri rejects a shipment due to a bad address?

The rejection is logged in an exception queue with clear detail (address missing, postcode invalid, etc.). Your fulfillment team reviews the exception, corrects the address in commerce, and triggers a retry without manual rebatch.

How long does it take for tracking numbers to appear in customer accounts after dispatch?

Tracking numbers flow back from Evri to commerce within minutes of shipment acceptance. iWeb's polling cycle ensures updates appear in your order management system and are sent to customers via email or SMS within the same window.

Can the integration handle both standard and special-delivery services in the same order batch?

Yes. iWeb maps order attributes (e.g., gift, fragile, signature-required) to Evri service codes so mixed batches are routed correctly without manual sorting.

How are return labels generated and provided to customers?

When a return authorization is issued in commerce, iWeb sends the return request to Evri, which generates a unique label and tracking number. The label and Evri tracking URL are immediately displayed in the customer portal or sent via email.

What triggers a credit note in ERP when a return arrives at Evri?

Evri sends a return-receipt event when the parcel is scanned in at a returns depot. iWeb captures this event, updates the return status in commerce, and posts a credit note in ERP if your policy allows automatic credits.

How is stock reconciled in the warehouse after a return is received?

Return receipt confirmation flows from Evri to iWeb to ERP, where it triggers a stock put-away instruction. The warehouse team scans items back into inventory; iWeb ensures commerce stock levels are refreshed within your sync interval.

What happens if Evri is down or not responding during peak trading?

iWeb implements a fallback queue: orders destined for Evri are held pending with clear visibility and a configurable retry interval. Once Evri recovers, queued orders are sent in batch without manual intervention. Critical orders can be escalated to your team.

Can the integration support multiple Evri service levels or carrier fallbacks?

Yes, within Evri's service catalog. iWeb can route orders by service level and implement rules that change service or carrier if Evri is unavailable (e.g., switch to another carrier for urgent orders). This requires upfront configuration and carrier account setup.

How are returns with damage or missing items handled?

Evri's receipt event includes basic condition flags. For detailed damage assessment or photo evidence, iWeb can integrate with a returns management system where your team documents condition; the assessment is then linked to the ERP credit and RMA.

How often does iWeb sync tracking updates from Evri?

By default, iWeb polls Evri's tracking feed every 15-30 minutes; more frequent polling is possible for critical orders. Configuration is set at launch based on your customer notification SLA and infrastructure load.

What visibility does my fulfillment team have into shipment exceptions?

iWeb builds a dashboard showing shipment status, exception counts, unprocessed returns, and SLA drift. Exceptions are also logged and can trigger alerts via Slack, email, or your ops ticketing system.

How does the integration handle international or restricted postcodes?

iWeb validates addresses against Evri's service area before attempting shipment. Orders to restricted or non-serviceable postcodes are flagged in the exception queue; your team can choose manual handling, alternative carrier, or customer notification.

Can order line items be split across multiple Evri shipments?

Yes. If your ERP or fulfillment system creates multiple dispatch instructions from one order (e.g., split by warehouse), iWeb sends each shipment to Evri separately and correlates tracking back to the original order.

Next step

Have a Evri integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →