Skip to main content
Talk to an expert
L

Linnworks integration for ecommerce fulfilment

Orders to dispatch synced in real time, stock stays accurate Linnworks centralizes warehouse operations, stock movements and despatch confirmations from receipt to tracking. Real-time order ingestion, stock sync and exception handling keep inventory accurate across channels and fulfilment stays on schedule. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

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

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

What a Linnworks integration gives you.

Orders reach the warehouse in time

Web orders flow cleanly from commerce into Linnworks without data loss or schema rejection, so picking starts within the target SLA window.

Stock stays in sync across channels

Real-time stock updates from Linnworks reflect in commerce and ERP within a predictable window, reducing oversell complaints and post-order cancellations.

Despatch tracking reaches shoppers

Tracking numbers and carrier links are reliably pushed back to commerce so customer service receives fewer 'where is my order' inquiries.

Returns flow back cleanly

Returned items are scanned, credited, and reconciled to the original order in ERP without manual line-item matching or duplicate credit notes.

Warehouse exceptions surface fast

Pick failures, address issues and carrier rejections are visible in Linnworks exception queues so warehouse managers and customer service can act before shipping deadlines slip.

02 · When it's worth it

Where a Linnworks integration earns its place.

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

Multi-location stock allocation and real-time inventory visibility to commerce
Automated pick-pack-ship workflows triggered by web orders from one or more sales channels
Carrier selection rules, label generation and tracking number propagation back to shoppers
Returns and RMA processing with stock reconciliation back to ERP
Channel-specific despatch confirmation and stock movement events feeding finance
Exception queue management for unshipped, mislabelled or damaged items
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.

Order ingestion schema mismatch

Linnworks expects orders in a specific structure; custom order attributes, non-standard shipping rules, or channel-specific line-item data often require mapping or transformation before orders can be safely queued for picking.

Stock sync latency and partial updates

Stock events from Linnworks may arrive out of order or be delayed in high-volume peaks; commerce platforms expecting synchronous inventory checks can experience oversell if the integration does not buffer or lock stock during the sync window.

Carrier and shipping rule conflicts

If carrier rules are maintained in both Linnworks and your commerce platform or ERP, changes to one are not automatically reflected in the other, risking mislabelled or slow shipments.

Returns and credit note reconciliation

Returned items must be matched to original orders and credit notes must be issued in ERP; without explicit reconciliation logic, return stock can be orphaned or credit notes duplicated.

Multi-warehouse allocation logic

Linnworks can split orders across multiple warehouses, but rules for which warehouse handles which postcode or product type are not standardized; custom business logic is often needed.

04 · The real work

Warehouse teams see orders arrive late or stock out of sync when order ingestion is not carefully mapped, but the integration is silent about which orders failed and why until customer service starts fielding complaints.

05 · Where it sits

Where this integration sits in your estate.

Linnworks 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.

One integration architecture, any storefront. Linnworks connects through the same governed layer whatever commerce core you run.

System of record
Source / owner
Linnworks
System of record for warehouse operations, stock availability and despatch state
  • Pick-pack-ship workflows and labour allocation
  • Stock movements and real-time inventory position
  • Despatch confirmations and tracking number generation
  • Carrier selection and label rules
  • Returns and RMA processing
  • Exception queue for unshipped and damaged items
iWeb integration layer
Customer-facing commerce
Commerce platform
Magento Open SourceAdobe CommerceShopify PlusBigCommerceOther storefronts
  • Catalogue and product display
  • Shopper checkout and order placement
  • Customer authentication and session
  • Order review and status visibility
  • Reorder history and saved items
Connected neighbours
Integration layer
ERP
General ledger, customer credit, invoicing and financial reconciliation. Stock corrections from Linnworks feed ERP for month-end close; credit notes for returns are generated in ERP and reconciled against RMA records.
Integration layer
PIM
Product attributes, images and descriptions are not central to Linnworks, but SKU reference data must be kept in sync so orders ingest cleanly without SKU mismatches.
Integration layer
Carrier platforms
Shipping rules and label generation are configured in Linnworks but communicated to carriers via API; tracking data is received back and pushed to commerce.
Integration layer
Customer service / ticketing
Returns and refund requests often originate in customer service systems and are routed into Linnworks as RMAs; resolved returns trigger credit notes visible back in the ticketing system.
Integration layer
Analytics / BI
Despatch metrics, stock movement events and return rates flow from Linnworks into BI for warehouse performance dashboards and demand forecasting.
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)
  • Magento Open Source
  • Adobe Commerce
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (Sage 100, SAP, NetSuite)
  • PIM (Syndigo, Salsify, Pimcore)
  • OMS (Manhattan, Blue Yonder)
  • Marketplace connectors (Amazon, eBay, Shopee)
  • Carrier APIs (DPD, Royal Mail, Parcelforce)
  • Customer service platform (Zendesk, Kustomer)
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 LINNWORKS
←From LINNWORKS
↔BOTH WAYS
Web orders and fulfilment instructions: Orders created on your commerce platform are sent to Linnworks with customer address, item SKUs, quantities and any special dispatch rules
Linnworks queues them for picking and triggers warehouse workflows.
Real-time stock movements and availability: Stock picks, receives, transfers and adjustments at the warehouse flow back to both commerce (to prevent oversell) and ERP (to keep financial records current)
Updates typically sync within minutes of warehouse scan.
Despatch confirmations and tracking: Once items are picked, packed and shipped, Linnworks sends shipment events (tracking number, carrier, items despatched) back to the commerce platform so shoppers see accurate order status and tracking links.
Carrier rules and label settings: Carrier selection logic, label templates, and shipping rules are configured in Linnworks and applied during the pack-ship cycle to ensure consistency across all orders.
Returns and credit notes: Return requests flow from commerce or customer service into Linnworks as RMAs; returned stock is scanned back in, triggering credit note generation and stock correction in ERP.
Pick and pack exceptions: Items out of stock, damaged goods, or address validation failures create exception records in Linnworks that require manual intervention before shipment can proceed.
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 order ingestion schema

    We map your commerce order attributes, shipping instructions and line-item metadata to Linnworks' expected format, including custom fields and channel-specific rules.

  2. 02
    Build stock sync pipelines

    We implement bi-directional stock sync from Linnworks back to commerce and ERP, with buffering, observability and fallback behaviour so oversell is prevented during peak traffic.

  3. 03
    Set up carrier integration

    We configure carrier connectors, label templates and shipping rule logic in Linnworks so despatch is fast and tracking data flows back to commerce automatically.

  4. 04
    Build returns and reconciliation

    We design RMA workflows that link returned items back to original orders, generate credit notes in ERP, and reconcile stock movements so finance close cycles are clean.

  5. 05
    Monitor exceptions and observability

    We instrument the integration so pick failures, address rejections, out-of-stock items and sync gaps are visible in dashboards and alerts, not discovered during post-ship customer service spikes.

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 and order picking rules
Source / ownerLinnworks
Maintained byWarehouse management team
NotesOrders flow from commerce into Linnworks; warehouse picks against these instructions and reports back despatch state and exceptions.
DataStock availability and warehouse inventory
Source / ownerLinnworks
Maintained byWarehouse operations
NotesStock moves are recorded in Linnworks and synced to both commerce (to prevent oversell) and ERP (for financial reconciliation) in near real-time.
DataDespatch confirmation and tracking
Source / ownerLinnworks
Maintained byWarehouse / carrier
NotesOnce items are shipped, Linnworks records the tracking number and pushes it back to commerce so shoppers and customer service see order status and tracking links.
DataCarrier selection and label rules
Source / ownerLinnworks
Maintained byOperations or logistics owner
NotesCarrier rules, label templates and shipping instructions are configured in Linnworks and applied during pack-ship; changes here must be communicated to commerce and ERP if they also hold carrier logic.
DataReturns, RMAs and credit notes
Source / ownerLinnworks and ERP
Maintained byCustomer service and warehouse
NotesReturn requests flow into Linnworks as RMAs; once items are received and scanned, credit notes are generated in ERP and stock is corrected in both systems.
DataPick and pack exceptions
Source / ownerLinnworks
Maintained byWarehouse manager
NotesOut-of-stock items, damaged goods, address failures and carrier rejections create exceptions in Linnworks that must be resolved before shipment can proceed.
DataIntegration transport and exception handling
Source / ownerIntegration layer
Maintained byeCommerce operations or IT
NotesFailed order ingests, stale stock syncs, dropped tracking feeds and orphaned returns are monitored and routed to the right team for rapid resolution.
10 · Experienced integrator

Built this before

iWeb has designed and built Linnworks integrations across retail, foodservice and industrial sectors. We understand how warehouse operations fit alongside commerce, ERP and multi-channel selling, and we know where the typical friction points are.

We design order ingestion schemas so orders reach the warehouse without rejections or manual rework, and we handle custom attributes and channel-specific shipping rules.
We build bi-directional stock sync pipelines with observability and fallback logic, so inventory stays accurate even when Linnworks or ERP is temporarily unavailable.
We set up carrier integration and tracking feeds so despatch confirmations and tracking numbers flow back to commerce reliably and shoppers see accurate order status.
We build returns and reconciliation workflows that match returned items back to original orders and prevent duplicate credit notes in ERP.
We instrument the integration with dashboards and exception routing so warehouse managers, operations and customer service see order flow health and act on exceptions before shoppers are affected.
11 · Before launch

What we test before launch.

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

Verify order ingestion schema: test orders from each commerce platform variant with all custom fields and shipping attributes map correctly and ingest without rejections.
Stock sync parity: confirm stock quantities in Linnworks match ERP and commerce within the target sync window, and out-of-stock items are reflected in commerce within seconds.
Oversell prevention: place simultaneous orders across channels that exceed warehouse stock and verify orders are either queued or cancelled, not despatched with false quantities.
Tracking data flow: ship orders through Linnworks and confirm tracking numbers and carrier links appear in commerce order status within the expected timeframe.
Returns reconciliation: process a return from cart to credit note and verify the RMA matches the original order in ERP, stock is restored, and the credit note is issued once without duplicates.
Exception handling: trigger pick exceptions (out of stock, address fail, damaged) and verify they surface in Linnworks exception queue and alert the warehouse manager within 2 minutes.
Fallback behaviour: stop the stock sync and place new orders; verify orders queue gracefully rather than overselling or blocking checkout indefinitely.
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 Linnworks queue

Orders fail to ingest because of schema mismatches, missing required fields, or invalid SKU references; they queue indefinitely without alerting warehouse or commerce teams, delaying picks and triggering missed despatch deadlines.

Stock oversell across channels

Stock updates from Linnworks arrive slower than web orders are placed, or sync fails silently; items sell out on multiple channels but Linnworks still has stale quantities, leading to cancellations and refunds after despatch.

Tracking numbers never reach customers

Despatch events are generated in Linnworks but the tracking feed to commerce fails or is delayed; customers see orders as 'in progress' indefinitely and contact support, creating noise and refund risk.

Returned items orphaned or double-credited

Returns are scanned into Linnworks but the RMA record does not match the original order reference in ERP; stock is credited twice or not at all, causing inventory miscount and finance reconciliation gaps.

Carrier rules drift silently

Shipping rules or carrier selection logic is changed in Linnworks but not in commerce or ERP; orders are mislabelled or routed to the wrong carrier, causing delays and increased shipping costs until the drift is discovered post-shipment.

Exception queue grows unmanaged

Pick failures, address validation errors, or out-of-stock items accumulate in Linnworks exceptions without routing to an owner; shoppers' orders sit unshipped for days and customer service is blind to the backlog.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Linnworks integrations.

How do orders flow from our commerce platform into Linnworks?

Orders are typically sent via API or flat-file integration as soon as they are confirmed on your storefront. We map your order schema (SKUs, quantities, shipping address, custom attributes) to Linnworks' ingestion format and monitor for rejections. Rejected orders are flagged so they can be resubmitted or manually corrected in Linnworks before picking starts.

How do we prevent oversell if stock updates are delayed?

We implement stock buffering and reservation logic: when an order is placed, we lock inventory in Linnworks immediately or reserve it in commerce until the warehouse confirms the pick. If Linnworks stock is stale or sync fails, the integration holds orders in a queue rather than passing them to the warehouse, preventing picks against non-existent stock.

What happens when Linnworks is unavailable or stock sync fails?

We design fallback behaviour based on your risk appetite: orders may queue in commerce waiting for Linnworks to come back online, or they may be held in a manual review queue if sync failures reach a threshold. Dashboards alert the operations team immediately so they can decide whether to retry, reroute, or manually intervene.

How do tracking numbers get back to our shoppers?

Once items are shipped in Linnworks, despatch events (with tracking number and carrier) are pushed back to your commerce platform. We monitor for dropped or delayed tracking feeds so customer service can see which orders are missing tracking data and chase them up before shoppers start contacting support.

Can Linnworks handle orders from multiple sales channels?

Yes. If you sell on multiple channels (web, marketplace, B2B), orders from each can be ingested into Linnworks with channel tags so the warehouse knows which channel owns each order. Despatch confirmations are then routed back to the correct channel so tracking reaches shoppers on the platform where they bought.

Who owns the carrier selection rules and shipping labels?

Carrier rules are typically configured in Linnworks and applied during pack-ship. If your commerce platform or ERP also holds carrier logic, we define which system is the source of truth to avoid conflicts. Changes to carrier rules must be synced across both systems or owned by one team so mislabelling does not happen silently.

How do returns and refunds flow back to ERP?

When a return is initiated in customer service or on the storefront, it flows into Linnworks as an RMA. Once the item is received and scanned into Linnworks, a credit note is generated in ERP, reducing the customer's invoice and restoring stock. We reconcile RMA numbers between systems so the original order can be matched and duplicate credits are prevented.

What happens if the warehouse runs out of stock on an item mid-pick?

Out-of-stock items create exceptions in Linnworks that block the order from being fully shipped. These exceptions are surfaced to the warehouse manager and customer service so they can decide whether to backorder, substitute, or cancel that line. We monitor exception queues so orders do not sit silently waiting for manual intervention.

Can Linnworks split orders across multiple warehouses?

Yes. If your inventory is spread across multiple locations, Linnworks can allocate and split orders so items are picked from the closest or most efficient warehouse. We define allocation rules based on your business logic (postcode proximity, inventory levels, specialization) so orders are distributed fairly and despatch times are minimized.

How do we monitor the health of the Linnworks integration?

We instrument the integration with dashboards and alerts covering order ingestion rates, stock sync latency, despatch confirmation timeliness, exception queue depth and any drops in data flow. If stock falls out of sync, tracking is missing, or orders are stuck, alerts notify the operations team so action can be taken before shoppers are affected.

What if our ERP is offline and we cannot sync stock?

We design the integration so Linnworks remains the warehouse source of truth and stock is not lost if ERP is temporarily unavailable. Orders can continue to flow to the warehouse and be despatch, but stock corrections are queued in ERP and reconciled once it comes back online. This prevents despatches being blocked by finance system downtime.

How do we handle custom shipping rules or business logic?

Custom rules around carrier selection, address validation, packaging, or special despatch handling can be configured in Linnworks or in the integration layer. We document which rules live where so changes propagate correctly and do not conflict with rules in commerce or ERP.

Can the integration handle same-day or next-day despatch windows?

Yes. If your business model requires very tight despatch windows, we can configure order ingestion to prioritize based on despatch deadline, alert the warehouse to high-priority orders, and track despatch time against the target window. This ensures peak-hour orders do not slip into the next despatch cycle.

What data validation happens before orders reach the warehouse?

We validate SKU references, quantities, shipping addresses and any required custom fields against your data model before passing orders to Linnworks. Invalid or missing data is flagged so it can be corrected in commerce before the order is queued for picking. This reduces warehouse exceptions and rework.

Next step

Have a Linnworks 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 →