Ecommerce ERP Integration for UK Stores and Wholesalers

It is the link that lets your online store and your ERP (enterprise resource planning software, the system that runs stock, purchasing and accounts) share records without anyone retyping them. Orders flow from the store into the ERP. Stock, prices and despatch details flow back. The work that decides whether it holds up is agreeing which system owns each record before a line of code is written.

In most cases, the one your finance and warehouse teams already run. Replacing an ERP to suit a website is a far bigger project than linking the two. For a fresh choice, test three points first: does the maker publish a connector for your store platform, does a UK partner support it near you, and can it hold your trade price lists. Business Central, NetSuite, Odoo and Brightpearl each publish a Shopify connector; NetSuite also has one for BigCommerce.

No. A CRM (customer relationship management system, such as HubSpot or Salesforce) tracks leads, deals and conversations. An ERP tracks stock, orders, invoices and the ledger. Many UK firms run both, and the store then talks to each one: new trade accounts to the CRM, orders and stock to the ERP. The owner map we write says which system holds the customer record.

Yes. Microsoft’s own documentation describes a Shopify Connector app for Business Central, preinstalled on all new sign-ups and trials, and says you can connect one or more Shopify stores. It also notes that the connector’s refresh token (the key that keeps the two systems signed in to each other) stays valid for up to 90 days without a successful refresh; past that, the shop has to be reconnected. We check the connector’s settings against your rules before building anything beside it.

Yes, and Oracle makes both connectors itself. The Shopify one sits in the Shopify App Store and covers products, prices, stock, sales orders and fulfilment, for online stores and Shopify POS alike. BigCommerce stores get the NetSuite Connector by Oracle NetSuite on the BigCommerce App Marketplace. When a connector cannot follow a rule, such as trade price breaks or a bundle split, we build that part as a custom link.

Yes. Limely, an agency in Chester, describes Sage 200 integrations for Magento 2 that carry orders, stock, trade accounts with credit limits, customer pricing and nominal codes. Patchworks, a UK integration platform, also names Magento 2 beside NetSuite, Sage and Microsoft Dynamics on its own site. For Adobe Commerce we write the same eight-record owner map first, then pick the connector or build the gaps.

Yes. Odoo’s documentation says its Shopify connector syncs orders, products, inventory, deliveries, returns and refunds. It also states two limits worth knowing: the connector runs on scheduled jobs rather than real-time webhooks, and when Odoo handles deliveries, returns started in Shopify do not sync automatically. If your stock moves fast, or Odoo ships your orders and most returns begin online, plan for those gaps before launch.

Yes, through a connector or a custom build. Limely, a Chester agency, describes Sage 200 integrations for Shopify and Magento 2 that carry orders, stock, trade accounts with credit limits, customer pricing and nominal codes. For Sage 50, Zynk’s Shopify and Sage 50 UK solution moves customers, products and sales orders into Sage 50, and stock levels back to Shopify. Your accountant or Sage partner sets which nominal code each line hits.

Yes. Brightpearl’s page says Shopify and Shopify POS stay as the storefront while Brightpearl runs the back office: inventory, orders, purchasing and fulfilment. It also says the Shopify refund follows once returned stock is received. That suits retailers who want refunds tied to goods coming back. Where you need something its page does not mention, we scope that piece separately.

Yes. WooCommerce sends webhooks, event notices to a URL you choose, when orders, products, coupons or customers are added, edited or deleted. Its documentation adds that a webhook is disabled automatically after more than five consecutive delivery failures. So a WooCommerce to ERP link needs a nightly check that catches any order the webhook missed. We build that check into every WooCommerce job.

No, but Plus gives the link more room. Shopify’s developer documentation lists GraphQL Admin API limits (the cap on how much data an app can read or write each second, counted in points) of 100 points a second on standard plans, 200 on Advanced, 1,000 on Shopify Plus and 2,000 on Shopify for enterprise. So a Plus store gets ten times the API allowance of a standard one. That matters for wholesalers with thousands of SKUs and customer-specific prices.

Into the same ERP, through one route. Some firms feed marketplaces through a multichannel tool: Linnworks, for example, lists Amazon, eBay and Shopify among its integrations. Others send marketplace orders straight to the ERP. The rule we hold to is one owner for stock, so Amazon, eBay, OnBuy or the B&Q marketplace never sell the same last unit twice.

Line by line, each with its own rate. The UK has three: standard at 20%, reduced at 5% and zero at 0%, per GOV.UK. For every sale, HMRC’s MTD notice wants a tax point, a net value and the rate applied in the digital record. So each order line should land in the ERP carrying a VAT code your accountant mapped once.

As credit notes at the VAT rate of the line being reversed. GOV.UK’s guidance on returned goods allows a credit or debit note, or a replacement invoice, and asks you to record whichever you issue. The open question is timing: does the credit post when the refund is issued online, or when the goods reach the warehouse? Your accountant picks one, and the link follows it.

It helps, but MTD covers your whole set of records, so no single link settles it. VAT Notice 700/22 lists API transfer and automated data transfer as digital links, and says HMRC does not count copy and paste as one. A store to ERP link that moves orders by API sits on HMRC’s accepted list. Ask your accountant to check the full chain from store to VAT Return.

GOV.UK says at least six years, or ten if you use the VAT One Stop Shop scheme (an HMRC scheme for reporting VAT on certain sales to EU consumers). That covers the orders, credit notes and invoices the link writes into your ERP. It is also why we log every record the link moves, with the time and the source, so an auditor can trace any figure back to the store order it came from.

Yes. Each provider pays out on its own schedule and takes its own fees before the money reaches your bank. So each one gets its own clearing account in the ERP: sales and refunds post there as they happen, and each payout clears it to the bank line. When a payout and the clearing balance disagree, you know which provider to ask.

Yes, if the map names the selling company on every order. Each store or channel is tied to one trading company, and its orders post to that company’s ledger with that company’s VAT codes. Stock can still have one owner across the group. Where two companies sell the same SKU, we agree in writing which one invoices the buyer before any order moves.

Three things set the price: how many records move, in which direction, and how many rules no connector covers. A Business Central or NetSuite connector with light set-up is a small job. A custom link carrying trade prices, bundles and marketplace orders is a project. FactoryJet quotes a fixed price in writing after a short scoping call, phase by phase, so you see the cost before you commit.

Limely, a Chester agency, says Sage 200 integrations typically take six to ten weeks. Our plans move with three things: how many records travel, how many custom rules sit on top of the connector, and how fast your ERP partner can give us a sandbox. The plan and dates go in writing with the quote, and each phase is signed on its own.

Yes. You see working software on your own data before any contract. We copy ten or so of your real SKUs into a development store, place a trade order and a refund, and let both land in a sandbox of your ERP with VAT codes and a credit note attached. Your finance lead opens every record it created and signs off only when they match.

Yes. Send your written brief, an RFP, a field list or an export of the records you move today. Name the store platform, the ERP and its version, any warehouse or marketplace tool, and your order volume. The reply carries an owner map for every record and a fixed price for each phase, or the name of the maker’s connector if that already does the whole job.

You own the code and the repository from day one. Hosting can run in your own accounts at cost, with no markup. Defects are fixed inside the build price for a cover period agreed before work starts. Support is optional: each change is quoted and approved, and there is no monthly minimum. If you want, we keep managing the servers, APIs and maintenance after launch.

Yes, and we want them on the first call. Your accountant decides the nominal codes and VAT treatment. Your Sage, NetSuite, Business Central or Odoo partner knows how the ERP is configured and who changes it. We build to their decisions, so nobody discovers a custom field or a locked period in week six.