fb-image

Explore More Across Our Network

Linnworks and ERP Integration: What Should Be Automated?

Linnworks and ERP Integration: What Should Be Automated?

Linnworks runs the order side of the business: channels, stock, picking and despatch. An ERP or accounting system runs the money side: invoices, payments, purchasing, stock value and reporting to the business owners. Between the two sits a gap that many sellers fill by hand.

A Linnworks ERP integration can close that gap, but connecting everything isn’t always the right answer. This post explains which data flows are usually worth automating, which are better left to people, and how to decide for your business.

Signs the gap between Linnworks and your ERP is costing you

  • Finance re-keys daily sales or invoices from Linnworks exports.
  • Stock levels or stock value in the ERP never quite match Linnworks.
  • Purchase orders are raised in one system and typed again into the other.
  • Refunds and returns are reconciled at month end, not when they happen.
  • Product details, prices or costs are updated in two places, and drift apart.

What is usually worth automating

1. Sales orders and invoices

This is normally the biggest win. Decide whether finance needs an invoice per order or a daily summary by channel, then post that automatically. Per-order detail suits B2B and VAT-sensitive sales. Daily summaries keep high-volume marketplace sales manageable.

2. Payments, fees and refunds

Marketplace fees, payment provider charges and refunds are where reconciliation usually breaks down. Posting them with the sales they relate to makes the month-end close much faster.

3. Stock levels and movements

If the ERP values stock or plans purchasing, it needs accurate quantities. Agree which system is the master for stock and sync the other on a schedule that suits your volumes.

4. Purchase orders and goods-in

Raise purchase orders once, in the system your buyers use, and send them to the other. Booking goods in should then update both, so stock and supplier balances stay aligned.

5. Product and cost data

Choose one system as the owner of SKUs, descriptions, prices and costs, and push changes to the other. Without a single owner, margin reports and stock valuations slowly become unreliable.

What is often better left to people

  • Rare, complex transactions such as one-off write-offs, disputed charges or large B2B credit notes, where judgement matters more than speed.
  • Corrections and adjustments, which should be checked and approved rather than pushed automatically.
  • Flows that happen a few times a month, where the cost of building and maintaining an integration is higher than the manual effort.

The aim is to automate the high-volume, rule-based flows and keep people focused on the exceptions. Our post on reviewing manual order exceptions in Linnworks uses the same principle.

What the gap costs

  • Time: hours each week re-keying sales and purchase data, and days at month end reconciling the two systems.
  • Cost: stock bought too early or too late because the ERP’s figures are out of date, and margin decisions made on wrong cost data.
  • Risk: VAT and accounting errors from manual entry, and financial reports the business can’t fully rely on.

A practical example

Imagine a seller using Linnworks for orders and an ERP such as Odoo for accounting and purchasing. Each morning, the finance assistant exports the previous day’s sales, totals them by channel and enters them into the ERP. Purchase orders are raised in the ERP and typed again into Linnworks. Refunds are matched up at month end. This is an illustration, but the pattern is common.

After mapping the flows, the business automates four of them: daily sales summaries by channel with fees, refunds as they are processed, purchase orders from the ERP into Linnworks, and stock levels back to the ERP each night. Large B2B credit notes stay manual, because they need approval.

The finance assistant’s morning goes from data entry to checking a short exceptions list, and the month-end close gets shorter because the two systems already agree. The exact result depends on your systems and volumes.

How to plan your Linnworks ERP integration

  1. Map every flow. List each piece of data that moves between Linnworks and the ERP, in which direction, and how often.
  2. Choose a master for each type of data. Orders, stock, products, costs and suppliers each need one system that owns them.
  3. Agree the level of detail. Per order or summarised, per channel or combined, with finance before anything is built.
  4. Prioritise by volume and risk. Start with the flows that take the most time or cause the most errors.
  5. Plan for exceptions. Decide what happens when a product, customer or tax code doesn’t match.
  6. Reconcile regularly. A simple report comparing totals in both systems catches problems early.

Our Linnworks API integration services cover this kind of work, and as an Odoo partner we also work on the ERP side. If you’re deciding between an existing connector and a custom build, see when a custom Linnworks API integration makes sense. For reconciliation reports, see Linnworks reporting.

Not sure what to automate first?

We offer a free, no-obligation 30-minute Linnworks Efficiency Review. We look at how data moves between Linnworks and your ERP or accounting system today and point out which flows are worth automating first, before any work is discussed.

Book your free Linnworks Efficiency Review

To see everything we do for Linnworks users, from integrations and reporting to macros and support, visit our Linnworks services page.

Table of Contents

Get Started With Us
Get Started With Us
Scroll to Top