There is no single day when a retailer outgrows its systems. The change is gradual, which is exactly why most retailers replace their ERP six to eighteen months later than they should. The delay is expensive, because the pain of the old systems is at its worst right before a replacement, and a replacement done in crisis is a worse project than one done calmly. The way out is to recognise the signals early. Here are the eight I have seen most often in client work.
Signal 1: the stock record needs constant rescue
If your team is correcting stock figures weekly, and the corrections are accepted as normal life, the record has already failed. The stock accuracy article describes the discipline that keeps a record honest, but when the rescue work becomes routine, the systems are the problem. A platform change will not fix a broken counting process, but the right platform makes the honest process possible, which is the point.
Signal 2: the copying tax is a job title
Someone in your business spends their day moving numbers between systems: orders from the marketplace into the ERP, stock from the ERP into the website, sales from the till into the accounts. If you can name that person, you have found the real integration cost. The system silo cost article prices this labour, and it is usually the first number that makes the ERP business case stand up on its own.
Signal 3: reports are assembled by hand
When the monthly board pack takes the finance team three days because the numbers come from four systems and two spreadsheets, that is not a reporting problem, it is an architecture problem. The Retail Economics insights library shows how much of UK retail decision making now depends on fast, trusted data, and a hand built report is neither fast nor trusted by the time it is printed.
Signal 4: channel decisions happen blind
The buying team orders for the shop, the web team plans the website and the marketplace team runs promotions, and nobody can see the total stock position at once. When channel decisions are made from channel silos, the business is running several small retailers that happen to share a warehouse. The unified commerce model describes the single record that ends this, and readiness means the leadership team is already frustrated enough to want it.
Signal 5: overselling is a routine event
If the customer service team has a standard process for oversell cancellations, complete with template email and refund path, the business has normalised a failure that should be exceptional. The oversell fix article covers the fixes, but the signal itself is a readiness marker: the current architecture cannot protect the stock record across channels, and no amount of process will change that.
Signal 6: peaks break the process every year
Every November the same collapse: the warehouse cannot see the web orders, the marketplace stock runs out, the reports stop being produced, and the team survives on heroics. A system that only works at 60% of your actual demand is undersized, and the peak planning article shows what a properly supported peak looks like. When warehouse visibility is the breaking point, the question is whether the ERP's module is enough or a standalone warehouse system earns its keep. The UK Warehousing Association news is a useful window into how professionally run fulfilment operations handle peak, and the contrast with the spreadsheet driven operation is instructive.
Signal 7: new channels are declined
The clearest signal of all. If the business is turning down sales channels because the systems cannot support them, the systems are deciding the strategy. A retailer ready for an omnichannel ERP is usually facing a concrete opportunity, a new marketplace, a wholesale line, a store network expansion, and finding that the answer to "can we do it" depends on a new integration project of unknown cost.
Signal 8: the spreadsheet is the system
The final signal is the most honest. If the daily stock position, the open order list or the margin report lives in a spreadsheet that someone maintains by hand, the business is running its core operation in a tool that has no audit trail, no controls and one point of failure. The spreadsheet is not a stopgap, it is the system, and the people who maintain it know it better than anyone else in the business, which is itself a risk.
What to do with the signals
Count the signals that apply to you. Three or more means the planning should start, and planning takes longer than anyone expects. Start with the candidate vendor questions, which will shape the requirements document, and the platform architecture guide, which shapes the shortlist. Read the implementation schedule so the board hears realistic dates, and buying mistakes show the project plan how to avoid the standard failures. Then run the selection calmly, because the worst time to choose an ERP is the moment the old one finally dies, and the signals above exist to make sure you never reach that moment.