An online sale looks simple from the customer's side. They choose a product, pay, and a parcel arrives. Behind that moment sit orders from more than one channel, stock figures that must match across sites and marketplaces, couriers, refunds, supplier deliveries and accounting entries. Each piece can work well on its own, yet the gaps between them are where orders get lost and stock gets oversold.
ERP for ecommerce business is about that back office. It does not replace the storefront or the design of product pages. It connects the order, warehouse, returns and finance processes so that one record follows each sale from the first click to the final payment, including any refund.
This guide covers what to connect, what to keep manual, and how to test an ecommerce ERP setup before it carries live orders. It is written for founders, operations managers and finance teams running online stores that have grown beyond a single storefront and a shared spreadsheet.
What the storefront does not solve on its own
Storefront platforms are good at taking orders, showing products and processing payments. They are not designed to be the place where warehouse staff, customer service, suppliers and accountants all work. Without a back-office layer, the business ends up copying data between tools by hand, and that copying is where many errors begin.
Where the spreadsheet creeps back in
A new store usually starts with exports. The team downloads orders each morning, pastes them into a warehouse sheet, updates stock by hand and sends a summary to the accountant at month end. It works while volumes are small. Then the export takes longer, the stock sheet falls behind, and refunds are keyed twice. The warning signs tend to look like this.
- Daily order exports pasted into a warehouse sheet
- Stock levels updated by hand after sales and deliveries
- Refunds recorded in the storefront and again in accounts
- Marketplace fees calculated from a separate report each month
Channels multiply the work
Adding a marketplace or a second storefront multiplies the risk. Each channel has its own order numbers, status names and stock counts. Without a central record, the same item can be sold twice, once on each channel, from the same shelf.
One order record from every channel
The starting point for a sound setup is a single order record that every channel feeds into. Each order should carry its channel, the channel's own reference, the customer, the lines, the payment status and the fulfilment status. That lets staff find any order by any reference and see its full history.
Keeping references without duplicates
Orders can arrive more than once, for example after a retry or a delayed update. The ERP should recognise the channel reference and update the existing order rather than create a second one. Cancellations and edits should also arrive as changes to the same record, not as new orders that need manual clean-up.
Statuses that match the warehouse
Storefront status names rarely match what happens on the warehouse floor. A useful ERP defines its own clear statuses, such as paid, allocated, picked, dispatched, delivered, returned and refunded, and maps each channel's status to them. Everyone then uses the same language when they talk about an order. The core set is usually these.
- Paid, meaning funds have been received
- Allocated, meaning stock has been reserved for the order
- Picked and packed, ready for dispatch
- Dispatched, with a carrier and tracking reference
- Returned or refunded, with the outcome recorded
Stock sync without overselling
Overselling is one of the most damaging ecommerce problems. A customer orders an item the business cannot send, the order is cancelled, and trust drops. Preventing it depends on how often stock is updated across channels, and on where stock is reserved at the moment of sale.
One stock figure per location
The ERP should hold stock per location and allocate it to channels using rules the business controls. For example, a share of stock might be reserved for a marketplace while the rest is available on the storefront. Safety stock can be held back, so the last few units are not sold while a delivery is still on its way.
Timing the sync
Stock sync can run on a schedule or be triggered by events such as a sale or a goods receipt. Either way, there is a short gap in which two channels can show the same unit. The shorter and more controlled that gap, the lower the risk, so the sync approach should be tested during a busy sales period, not only on a quiet afternoon. Build these controls in from the start.
- Stock reserved at checkout or when the order is created
- Safety stock held back from each channel
- Receipts and adjustments pushed to every channel
- A daily reconciliation comparing system and warehouse counts
Fulfilment in-house, outsourced or both
Fulfilment is the stage where the online promise becomes a physical parcel. Some businesses pick and pack in their own warehouse, some use a third-party fulfilment provider, and many use a mix as they grow. The ERP needs to show where each product sits and who is holding it.
Picking and packing in-house
For an in-house operation, the ERP should generate pick lists, record packing and produce dispatch documents or carrier labels. Batch picking can help when many orders share the same products, but it needs clear rules for splitting the batch back into individual orders.
Working with a third-party fulfilment provider
When stock sits with a provider, the ERP must still show the true position. That usually means regular stock reports from the provider, clear rules for inbound deliveries, and a reconciliation process that explains differences. Ask any provider what data they send, how often and in what format before you commit. In particular, check that the feed covers the following.
- Stock levels received from the provider on an agreed schedule
- Shipment confirmations linked back to the original order
- Inbound delivery records showing what arrived and what was accepted
- A named contact for resolving stock differences
Returns, refunds and restocking
Returns are where ecommerce operations often lose control. A returned parcel can sit unopened for days, a refund can be issued before the item is checked, and the stock figure can stay wrong for weeks. A clear returns process treats each return as a sequence of recorded steps rather than a quick fix.
Returns as their own workflow
Each return should have its own reference, linked to the original order. The item should be received, inspected and graded, and then either restocked, sent for repair or written off. The condition and the decision should be recorded, so that stock and finance reflect what actually happened.
Refunds that match the original sale
A refund should point to the sale it relates to. Partial refunds, shipping refunds and goodwill credits each need their own lines, so the accounts can explain the difference between what was charged and what was returned. A refund booked only in the storefront is a frequent cause of mismatched totals. Each refund line should show the following.
- Return reference linked to the original order
- Inspection result and condition grade recorded
- Restock, repair or write-off decision logged
- Refund split into product, shipping and goodwill where relevant
The link to accounting
Accounting for an online store is busy. Sales arrive in large numbers, payments come through processors in batches, marketplaces take their fees before paying out, and refunds appear days later. The aim of the ERP link is to send summarised, accurate entries to the accounting software, not thousands of raw transactions that nobody can reconcile.
Payments, fees and payouts
Payment processors and marketplaces often pay out one total for many orders at once, after deducting fees. The ERP should match each payout to the orders and fees it covers, so the bank entry can be reconciled to the sales it represents. Without that match, the bank statement and the sales ledger will never quite agree.
VAT on online sales
VAT on online sales can be more complex than it looks, because the rate and treatment depend on what is sold, where it is delivered and whether the buyer is in the UK or abroad. Thresholds and rules for cross-border sales also need checking. Your accountant should confirm the treatment for each sales route, and the ERP should carry the agreed tax rate on every line. The summary posted to the ledger should include the following.
- Daily sales summarised by channel, tax rate and currency
- Refunds posted against the same tax treatment as the original sale
- Marketplace and processor fees posted as separate expense lines
- Payouts matched to the orders and fees they cover
Planning and testing an ERP for ecommerce business
A sensible project starts small and proves each piece before adding the next. The aim is to get one channel, one warehouse and one accounting route working reliably, then extend the setup to the rest.
Start with the busiest channel
The busiest channel is where errors cost the most, so it is usually the best place to start. Once orders, stock and refunds flow correctly through it, the same design can be applied to smaller channels with less effort.
Test the awkward orders
Test split shipments, pre-orders, bundles, gift cards, partial refunds and cancellations after dispatch. These are the orders that break simple integrations. Test them with real product records and real stock, not only with a sample item that has no variants.
Plan the cut-over around peak periods
Avoid switching over just before a major sales period. Run the old and new processes side by side for a short time, reconcile the differences daily, and only then close the old route. A calm cut-over protects customer service while the team learns the new screens.
FAQ
Can an ERP connect Shopify and WooCommerce orders?
Shopify and WooCommerce both make orders and products available to other systems, but the set-up of each connection depends on your store and the ERP you choose. The important questions are which order fields pass across, how updates and cancellations are handled, and what happens when a sync fails. Ask for a live test with your own store before committing.
How does an ERP prevent overselling across channels?
It holds one stock figure per location and reserves stock at the point of sale, so every channel draws from the same pool. Safety stock can be held back, and the sync frequency should be tested during busy periods. A daily reconciliation against the warehouse count catches drift early.
Does an ERP replace accounting software for an online store?
Usually not. Many online stores keep a dedicated accounting package for the ledger, tax and reporting, and the ERP sends it summarised, accurate entries. The ERP holds the operational detail that the ledger does not need to see line by line.
How should returns be handled in the system?
Each return should have its own reference, linked to the original order, with a record of inspection, condition and outcome. Refunds should be recorded against the original sale, and stock should move only once the returned item has been checked. That keeps stock and accounts aligned even when returns arrive in small batches.
Do we still need an ERP if a fulfilment provider holds our stock?
Often yes, because the business still needs one view of orders, sales, refunds and accounting. The provider's stock reports must be reconciled with your own records, and the ERP is the natural place for that work. Agree the data feed and reconciliation routine with the provider before you start.
Should we start with one sales channel or all of them?
Starting with the channel that carries the most volume or risk is usually the most practical approach. Proving the order, stock and refund flow on one channel makes the next ones much easier to add. Connecting everything at once tends to hide problems until they reach real customers.
Final thought
An online store's back office is where good customer experience is either kept or lost. Accurate stock keeps promises honest, a single order record keeps customer service calm, and clean accounting keeps the owner's numbers credible. ERP for ecommerce business earns its place when those three things work together every day.
For many growing stores, the first gains come from connecting orders and stock, then from tidying returns and accounting. Start with the channel that carries the most risk, test the difficult orders, and extend the setup once the basics hold.
Mirex Agency builds ERP solutions for UK small and mid-sized businesses that need orders, stock, finance and operations to work from one clearer system. If your online sales run across several tools, a short conversation about your channels and fulfilment set-up is a useful next step. The service page is mirexagency.com/services/erp-solutions.
