Industries/ Wholesale/ ERP and accounts integration
One order, entered once, in every system that needs it
Orders, customers, prices, stock and account balances moving between your ERP or accounts package and everything around it, with one agreed system in charge of each. When a sync fails, the order is parked and a named person is told, instead of it disappearing between two screens.

- Used by
- Sales office, warehouse, credit control and finance
- Takes the place of
- Rekeyed orders, CSV exports and month-end matching
- Connects to
- Your ERP or accounts package, warehouse system and carriers
- Built with
- Our connecting systems service
Where it hurts today
A normal week, before it exists
Each system holds part of the picture. The ERP or accounts package holds customers, invoices and balances. A warehouse system holds stock and picking. A web shop or portal holds online orders, and a spreadsheet holds the prices. The same customer appears in three places under slightly different names and codes, and each system is sure its own version is right.
Moving data between them is somebody's job. Each morning someone exports online orders as a CSV, imports them into the ERP and fixes the rows that fail. Stock on the website is uploaded overnight, so a line that sold out at 10am still shows as available at 4pm. When an import stops halfway, nobody notices until a customer rings about a delivery that never came.
Month end is where it shows: portal orders that never became invoices, a credit note raised twice, stock figures that don't agree. Finance spends days matching one export against another. Replacing the ERP is expensive and disruptive, and often not what is needed. What is missing is the plumbing between the systems you already have, and something that watches it and speaks up.
What it does
ERP and accounts integration, feature by feature
Integration built so that it keeps working long after the people who set it up have moved on to other things.
- 01
A system of record for each kind of data
Before anything is connected we agree, in writing, which system is in charge of customers, products, prices, stock, orders, invoices and balances. Other systems read from the owner and never overwrite it, so there is one answer to every question about a number.
- 02
Sales orders from every channel
Orders from a portal, a rep app, email capture and the office all reach the ERP through the same path and the same checks, as proper sales orders with your account codes, delivery dates and the source recorded on each one.
- 03
Stock and balance sync
Stock positions and account balances flow from the ERP or warehouse system to wherever customers and reps see them, on a schedule that suits each: every few minutes for stock on fast lines, nightly for slower data. The age of each figure is always shown.
- 04
An error queue with retries and alerts
If the ERP is down or rejects an order, the order waits in a holding queue with the reason in plain words, is retried where that makes sense, and a named person is told when it doesn't clear. Nothing waits silently in a log file nobody reads.
- 05
Safe to send twice
Networks drop and systems time out halfway through a send. Every order carries a unique reference, and the ERP side checks it before creating anything, so a resend is recognised rather than turned into a second sales order, invoice or pick.
- 06
A full sync audit log
Each order, price change and stock update is logged with when it was sent, what the ERP replied and what changed. When a customer asks why an order arrived late, the answer is in the log rather than in somebody's memory.
A day with it
How the day runs instead
A normal day across the business with the integration running, mostly unseen.
- 6.00amThe integration
Overnight portal and email orders are already in the ERP. Account balances and the morning's stock positions have gone out to the portal and the reps' tablets. One order failed because its delivery address is new, and it waits in the parked queue.
- 7.30amSales office
The first person in sees one parked order with its reason in plain words: delivery address not set up in the ERP. They add the address in the ERP, press retry, and the order goes through in time for the morning pick.
- 11.00amWarehouse supervisor
A pallet of a fast-moving line is found damaged at goods-in. The supervisor adjusts stock in the warehouse system, and the next stock sync carries the lower figure to the portal, so buyers ordering at lunchtime see what is really there.
- 2.15pmFinance assistant
The ERP goes offline for a planned update. Orders from the portal keep arriving and queue up. When the ERP comes back, they are written in the order they arrived, and the finance assistant checks the sync screen to see the queue empty.
- Month endFinance director
Opens the reconciliation report: every portal order matched to an ERP sales order and an invoice, with any gaps listed by order number. The two credit notes raised this month each link to the original order and the person who raised them.
What it connects to
Works with what you already run
The systems that usually need to talk to each other in a wholesale business. We connect the ones you have and leave the rest alone.
ERP or accounts package
The system in charge of customers, invoices and balances, for example Sage, Xero, QuickBooks, NetSuite or Business Central, through its API where it offers one, or scheduled file imports where it does not.
Warehouse management system
Stock positions, picking and despatch. Orders flow in for picking, and despatch confirmations flow back, so the customer's record and the invoice reflect what actually left the building.
Ordering channels
A trade portal, a rep app, email order capture or a web shop, each writing through the same integration with the same checks, so a sales order looks the same in the ERP wherever it started.
Carriers and delivery tracking
Where you use a carrier or your own fleet software, despatch and proof of delivery details come back against the order, so buyers and the office can both see what was delivered and when.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- A written data ownership map agreed with your finance and operations leads
- Orders from one channel written to the ERP as sales orders
- Customers, products and prices read from the ERP on a schedule
- A parked queue with plain-language reasons and a retry button
- Alerts to a named person when items stay parked or a sync stops
Once it is in use
- Stock positions pushed to the portal and rep app every few minutes
- Despatch and proof of delivery details returned from the warehouse or carrier
- Further ordering channels routed through the same integration
- A month-end report matching every order to its invoice
Buyer's guide
Before you commission one
Four decisions worth making before connecting anything to the system that holds your books.
- 01
Connector, iPaaS or built for you
Pre-built connectors between popular platforms and ERPs, and integration platforms (iPaaS), are often the right buy for standard data moving between mainstream systems. Built for you earns its place when your own rules sit in the middle, such as credit checks or customer code mapping, when the ERP is old or customised, or when per-transaction fees outgrow owning it.
- 02
What to gather first
A list of every system orders and stock pass through, who uses each one, and where people export, import or retype today. Access to a test copy of your ERP and the contact at your ERP partner. And examples of the awkward cases: credit notes, part deliveries, new delivery addresses and customers with two accounts.
- 03
Who should own it
The finance or operations lead, because the ERP is usually the books. They sign off the data ownership map, decide what each alert means and who answers it, and approve changes. Day to day, a named person in the sales office or finance answers parked items, because alerts without an owner go unread.
- 04
How you will know it is working
Watch how many items sit in the parked queue and for how long, whether the same reason keeps appearing, how many exports and imports people still run by hand, and how long month-end matching takes. When people stop checking the ERP against the portal, they have started to trust it.
Terms worth knowing
The words you will meet
- API
- Application programming interface: the documented way one system lets another read and write its data. An ERP with a good API can be connected cleanly and close to real time. One without can often still be connected through scheduled files, but more slowly and with more checks.
- iPaaS
- Integration platform as a service: hosted tools for building connections between systems without running your own servers. They suit standard flows between mainstream products and are quick to start, and they usually charge by volume or connection, which is worth modelling against your order numbers first.
- E-invoicing and Peppol
- Invoices sent as structured data that the buyer's system reads directly, rather than as PDFs. Peppol is an international framework for exchanging them, run by OpenPeppol, a non-profit association, and it carries orders as well as invoices. Where customers or tax authorities ask for it, your integration has to plan for it.
Handled with care
The details that matter here
Integration touches the system your finance team relies on for invoices and the year-end accounts. These are the things we treat with the most care.
Testing against a copy, not your live books
We build and test against a sandbox or a copy of your ERP company, never the live one, using real but anonymised orders. We switch the live connection on only after your finance lead has watched orders, credits and the awkward cases go through and is happy with them.
Matching existing records first
Customers and products often exist in two systems under different codes. We match them with you before go-live, list every record that doesn't match cleanly, and agree what happens to each one, rather than letting the first sync create a crop of duplicates.
Access kept as narrow as possible
The integration gets its own user in your ERP with only the permissions it needs, such as creating sales orders and reading balances, not posting journals. Its credentials are stored in a secrets vault and rotated, and every action it takes is logged under its own name.
When the ERP changes
ERP updates and new versions can change how data is exchanged. We watch for unexpected responses, raise an alert rather than guess when something changes shape, and agree with you how updates are tested, so ordering is checked before an update reaches the live system.
Guides
Worth reading first
Questions
What buyers ask first
Do we need a new ERP to connect a B2B portal?
Usually not. Most wholesalers have an ERP or accounts package that does its core job well, and connecting to it is far less disruptive than replacing it. If it genuinely holds you back, for example it cannot hold contract prices or exchange data at all, we will tell you plainly and help you decide. We would rather not hide an ERP problem behind integration work.
Can you integrate with an old ERP that has no API?
Often, yes. Many older systems can import and export files on a schedule, read from a shared folder, or let a reporting tool read their database. Those routes are slower than an API and need more checks, but they are often enough for daily orders, stock and balances when they are monitored properly. We look at what your system allows and set out the limits of each route.
What happens when an ERP integration fails?
It is designed to stop safely rather than quietly. Anything that cannot be written to the ERP waits in the parked queue with its reason, and a named person is alerted. Your team keeps taking orders, and the queue is written in once the problem is fixed. We also agree in advance who gets called, and how, if the problem is on our side.
Do we need our ERP partner involved in an integration?
Usually, and that helps. Your ERP partner or reseller often knows the quirks of your setup, and may need to create the integration user or switch on an interface module. Your accountant may want a say in how credits and payments post. We work with them directly where you want us to, and share the data ownership map with everyone involved.
How does e-invoicing affect our ERP integration?
It depends where you sell. In the EU, the ViDA package adopted in March 2025 lets member states require e-invoicing at home, and its digital reporting for cross-border B2B sales applies from 1 July 2030. Saudi Arabia's ZATCA e-invoicing has applied in phases since December 2021. Elsewhere, timetables differ. Usually your ERP produces the e-invoice, so we design around it with your accountant.
Draw us a map of your systems
List the systems your orders pass through today and where people retype or export. We will reply within 48 hours with where the gaps are and which connection to make first.
More for wholesale
What else we build for wholesale and b2b
Trade ordering portals
A logged-in store for trade buyers with account-specific price lists, minimum quantities, pack sizes, order pads and one-click reorder from history. Customers order when it suits them, and orders arrive already checked against price and credit rather than in an inbox.
Ordering apps for reps
Your field reps take orders on a tablet at the customer's premises, with live prices, stock and the account's history to hand. The app keeps working in a cellar or a basement with no signal and syncs as soon as it is back online.
Email and PDF order capture
For customers who will always email: orders read from emails, PDFs and spreadsheets, matched to the right account and product codes, checked against price and stock, then created automatically or held for a person when something does not match.
Pricing and quoting tools
Your pricing rules, from contract prices and volume breaks to promotions and approval thresholds, taken out of a fragile spreadsheet and turned into a tool anyone on the team can use, with a full history of what was quoted to whom.
Demand forecasts and reorder alerts
Forecasts by product line that account for seasonality, promotions and supplier lead times, with reorder points and alerts when a line starts selling faster or slower than expected, so buying decisions start from a tested number rather than last year's gut feel.


