Retail looks simple from the shop floor. A customer picks an item from the shelf, pays at the till and leaves. Behind that moment sit stock figures for each location, prices that change by date and by store, deliveries that arrive at the wrong branch and sales that must be brought together at head office. ERP for retail is about keeping those moving parts in step without someone reconciling them by hand every evening.
Many retail businesses grow unevenly. A second shop opens, then an online store, then a stockroom that is not quite a warehouse. Each addition brings its own spreadsheet, its own copy of the price list and its own idea of how many units are on hand. Head office ends up collecting figures from several places and trusting none of them completely.
This guide looks at what an ERP for retail should cover, from store-level stock and transfers to pricing, buying, till connection and reporting. It is written for owners and operations leads who run more than one site and want fewer surprises in the monthly numbers.
Stock by store in a retail ERP, not just in total
A total stock figure can look healthy while individual shops run out of the lines customers ask for. The first job of a retail ERP is to hold stock by location, so the business can see what each store has, what is on order for it and what is travelling between sites.
Per-store stock positions
Each store needs its own on-hand figure for every product it carries, updated as sales are rung up, goods are received and stock is moved. Stock sold online should come from a named location or a defined share of stock agreed in advance, rather than from whichever count was taken last. Without that discipline a store can show stock that has already gone, and a customer can be promised an item that does not exist.
Stock counts and shrinkage
Counts reveal the gap between what the system says and what is on the shelf. Shrinkage is the term for stock that disappears through theft, damage or admin error. A retail ERP should make counts easy to run store by store, record the reason for every adjustment and show trends by location. That lets the team tell whether a shop has a process problem or simply a handful of awkward lines.
Rather than one large count that closes a shop for a day, many retailers prefer cycle counting, where a small set of lines is checked each week. The results show quickly which products keep drifting out of line, and the team can fix the cause while it is still small.
Stock transfers between shops that reconcile at both ends
Moving stock between shops is a common reason a retail system goes wrong. A transfer leaves one store, travels in a van or a staff member's car, and arrives at another. If the system records only the departure or only the arrival, the figures drift apart within days.
Sending and receiving with matching quantities
A transfer should be created at the sending store and confirmed at the receiving store, with the two sides compared. Short or damaged items are logged as exceptions rather than quietly absorbed into the count. It is a small discipline with a large effect on how far the team trusts the stock figures.
Approvals, in-transit stock and transfer rules
Some transfers need approval, particularly when a store would give up its last units of a popular line. Stock in transit should show as its own status, so a manager can see that goods are on the road rather than missing. Useful rules usually cover:
- Who can raise a transfer and who can approve it
- The minimum stock each store keeps before giving items away
- How long stock can sit in transit before someone checks on it
- Where returned or damaged goods go for a decision
Pricing that works in shops and online
Price is where the business meets its customer. Shelf prices, online prices and till prices must agree, and every change has to reach each place at the right moment. A retail ERP should treat price as controlled data rather than a number retyped into each system.
Shelf prices and VAT
In the UK, prices shown to consumers generally need to include VAT. The system should therefore store the VAT rate with each product and calculate the shelf price from the net price, so a rate change is made once rather than in every shop. Ask your accountant how VAT applies to particular goods, as the rules have exceptions.
Promotions and dated price changes
Promotions and markdowns are where errors creep in. A price that changes on Monday in one shop and on Wednesday in another, or a promotion that runs past its end date, is a common cause of complaints and lost margin. Dated price changes, promotions with set start and end times, and a record of the price in force at each till solve most of that problem.
Buying and replenishment for each store
Buying decides what each store can sell. A central buy is not enough when one shop needs different products or quantities from another. A retail ERP should support planning at store level as well as at group level.
Range plans and store ranging
A range plan sets out which products each store carries and in what depth. Ranging decisions often depend on store size, local demand and the space available. Keeping the plan in the system means a new line can be added to the right stores in one step, and a discontinued line can be removed everywhere it appears.
Replenishment rules and open-to-buy
Replenishment can run on minimum and maximum stock levels for each store, so orders go out when a shop runs low rather than when someone remembers. Many retailers also plan buying against an open-to-buy budget, which sets how much stock can be bought in a period for each category. Seeing that budget beside committed orders stops buying drifting past what the business can afford.
Direct-to-store and centrally received deliveries
Some suppliers deliver straight to each shop, while others deliver to a central stockroom that sends stock out to the stores. The ERP should record which route applies to each supplier, because it decides when stock becomes available to sell in a particular shop. A delivery booked as received at head office but not yet sent on is stock the shop cannot sell, and the figures should show it that way.
Connecting the tills to a retail ERP
The till is where most of the day's activity is recorded, so how its data reaches the ERP shapes how quickly head office sees sales and how much the team has to reconcile. The link can be a live connection or a scheduled file, and the choice affects when stock and sales figures become current.
What the till should send
A sensible link carries more than the day's total. It should send each sale line with its product code, quantity, price and discount, along with returns, voids, the payment method, and the store and time of each transaction. Without line detail, the ERP can only show totals, and stock and margin reports cannot be relied on.
Daily close and cash-up
At the end of each day, takings should be reconciled against the till totals, the card settlements and the bank deposits. Any difference needs an owner and a reason. A retail ERP can hold the daily close as a checklist and show the gap for each store, so small differences are caught in the week they happen rather than at the quarterly review.
Returns and refunds at the till
A return made in a shop should be linked to the original sale wherever the till allows it, so the stock comes back into the right location and the refund is recorded against the right day. Returns without a receipt need a clear rule and a manager's sign-off, and the reason should be captured so that patterns can be spotted later. Returned stock that is not ready to sell should go to a holding status rather than straight back onto the shelf.
Reporting by store, category and team
Reports earn their keep when they answer the questions managers ask on a Monday morning. Those are usually about store performance, category mix, stock that is not moving and the margin each store is earning. The answers should come from the same records the tills and the stockroom update, not from a separate file that someone builds at the weekend.
Store performance and margin
A useful store report puts sales, gross margin and stock levels side by side, by week and by category. That helps a manager see whether a drop in takings came from fewer transactions, a smaller average basket or heavier discounting. Comparing stores of a similar format is usually fairer than setting a city centre shop against an out-of-town site.
A store report is more useful when it answers a short, fixed set of questions each week:
- Are sales up or down on the same week last year?
- Which categories grew or shrank, and by how much?
- What was the gross margin, and did discounting change it?
- Which lines are overstocked and which ran out?
Different views for store managers and head office
Store managers need to see their own stock, orders and sales. Head office needs the group view, with the ability to drill into any shop. Giving each role only what it needs keeps the screens simple and reduces the chance of changes being made in the wrong place. Permissions should follow the same logic as the stores themselves.
FAQ
What does ERP for retail include?
A retail ERP usually covers stock by location, transfers between shops, purchasing and replenishment, pricing, sales from the tills or online channels, and reporting by store. Some retailers also link customer and loyalty records. The right scope depends on how many locations you run and how your sales channels work together.
Can an ERP connect to our EPOS tills?
Many ERP systems can receive sales data from EPOS tills, either through a live connection or a scheduled file. Before deciding, check which sales details your tills can send, such as line items, discounts and returns, because the ERP is only as detailed as the data it receives. Ask the supplier to show the link working with your own till set-up.
How does an ERP help with stock transfers between shops?
It records the transfer at the sending shop, shows the stock as in transit, and confirms the quantities when it arrives. Any difference is logged as an exception, so stock figures at both sites stay accurate. Approval rules can also be set for transfers that would take a shop below its minimum stock.
Do small retailers need an ERP, or is an EPOS system enough?
An EPOS system records sales at the till, while an ERP joins sales with stock, purchasing, pricing and finance. A single shop with simple stock may be well served by its till and a careful stock routine. An ERP becomes more useful once there are several locations, an online store or a team that needs shared records.
Can one ERP run both physical shops and an online store?
Yes, and that is one of the main reasons retailers look at an ERP. Stock, prices and orders from both routes can sit in one set of records, so a sale in a shop is reflected in the online figure. The set-up depends on the platform your online store uses, so check that connection in detail before you commit.
What should a retailer review in its reports each week?
Retail teams usually look at sales and margin by store, which lines are selling and which are not, stock that is building up, transfers that have not been received and the results of stock counts. A short weekly pack keeps the team focused on decisions rather than on finding the numbers.
Final thought
ERP for retail makes the most sense when stock, prices and sales are spread across more places than one person can keep in step. The goal is a single set of records that the shops, the online store and head office all trust. It is not about adding screens. It is about making the daily numbers agree without a weekend of spreadsheet work.
Stock by store and transfers between shops are where a retail system usually shows strain first, so they make a good place to begin. Pricing and the till link can follow once the team trusts the basic figures.
Where shops and online sales run on separate tools, a short conversation about how stock, prices and tills should connect is a sensible next step. Mirex Agency can help you map that flow, and our ERP solutions service is built to bring the records together so the team spends less time checking and more time selling.
