Most businesses that invest in ERP expect it
to solve their planning problems. It does not.
Here is why And what actually does.
The data is all there. So why is the planning still broken?
Ask any operations or supply chain leader in manufacturing, distribution or wholesale whether their ERP gives them what they need to make confident planning decisions. Most will pause before answering. Because the honest answer is complicated.
The ERP is working. The data is being captured. Transactions are recorded, inventory is tracked, orders are processed. On paper, the system is doing its job.
But when it comes to making the actual calls: how much to order, when to reorder, where stock is tight, what demand looks like next quarter. Something breaks down. Teams default to spreadsheets. Planners work from different numbers. Decisions get made on gut feel and experience rather than a clear, shared view of the business.
This is not a people problem. And it is not an ERP problem. It is a planning gap, and it exists in the vast majority of businesses that rely on ERP as their primary planning tool.
ERP systems are designed to record what has happened. They are not designed
to guide what should happen next.
What ERP does well. And where it runs out of road.
ERP platforms are exceptional at what they were built for: capturing transactions, maintaining a system of record, and providing visibility into what the business has done. This is genuinely valuable. Without it, modern operations would be impossible.
But forward-looking planning is a different discipline entirely. It requires scenario modelling, optimisation across competing objectives, and the ability to evaluate trade-offs at scale: cost versus service, inventory versus availability, margin versus growth. These are not problems ERP was designed to solve.
The hidden cost of the planning gap
The cost of disconnected planning rarely shows up as a single line item. It is distributed across the business in ways that are easy to normalise and hard to quantify. Until you start looking.
On the P&L, the impact shows up in excess inventory tied up in the wrong locations, expediting costs from emergency freight and inter-branch transfers to cover stockouts, and margin erosion from decisions made without a full picture of demand and supply.
On the operational side, the cost shows up in planner time. In most businesses running ERP-plus-spreadsheet planning, the majority of a planning team’s time is spent extracting, transforming, uploading and organising data, leaving a fraction of their time for actual decision-making. The goal of a connected planning environment is to flip that ratio entirely.
A planning team that spends most of its time making decisions rather than preparing data becomes a fundamentally different asset for the business.
” Most businesses aren’t actually lacking the data, they’ve got plenty of it. It’s just that it’s not connected in a way that supports decision making.”
– Robert Jurcec, Group CEO and Sales Director, OneKloudX
The goal is not better data. It is more time making decisions. And better decisions when you do.
What connected planning actually looks like
In a connected planning environment, the ERP remains the system of record. It continues to do what it does well: capturing transactions, maintaining inventory records, processing orders. Nothing changes there.
What changes is the layer between that data and the decisions your business makes.
A dedicated planning system sits alongside the ERP, drawing on its data and transforming it into something the business can act on. Key data, including sales history, open orders, purchase orders, inventory across locations and supply lead times, flows into the planning system, which uses it to run scenarios, model trade-offs, and produce outputs that planners can actually work with.
Those outputs then flow back into the ERP as executable transactions, including purchase requisitions and replenishment orders, ready to be approved and actioned.
The practical result is a planning process that looks like this:
- A single, aligned view of demand, inventory and supply across every team
- Forecast accuracy that improves over time rather than degrading through manual handling
- Inventory levels that reflect what the business actually needs, not what was ordered six months ago
- Faster decisions, fewer surprises, and a planning team that is ahead of the curve rather than permanently catching up
- A consensus process, often aligned with S&OP or IBP, where leadership can sign off on a single version of the plan
Integration is the foundation. And it is rarely straightforward.
The biggest barrier to connected planning is not the technology. It is the data.
Real-world ERP data is messy. Item master records are incomplete. Lead times are inconsistent. Sales histories contain noise. Getting clean, reliable data flowing between an ERP and a planning system requires rules, transformation logic, mapping, and ongoing adaptation as the business changes.
This is where experienced integration partners make a material difference. Not just in setting up the technical connection, but in building the data infrastructure that makes planning outputs trustworthy enough to act on.
The good news is that data perfection is not a prerequisite. Waiting for clean data delays progress. The practical approach is to start with a representative subset of the business. Start with a product group, a category, or a distribution centre, and run the planning logic across it, review the outputs, and use the results to build the business case for broader rollout.
” In our experience, analysing as little as 10 to 20 percent of your product range is enough to run a meaningful ROI analysis and build a compelling business case for connected planning.”
– Elton Brown, Senior Business Consultant, Demand Management Systems
Where to start without overengineering it
The businesses that make the most progress on connected planning share a common approach: they start small, prove the value, and expand from there.
A practical starting point involves three steps:
- Identify where the planning gap is costing the business most: stockouts, excess inventory, forecast errors and expediting costs
- Select a representative subset of products or categories and run planning algorithms across them using existing ERP data
- Review the outputs, including predicted demand, recommended order quantities and projected inventory, and calculate the return on investment before committing to a broader rollout
This approach removes the risk of a large, disruptive implementation and gives leadership something concrete to evaluate before making a full commitment. It also tends to surface data quality issues early, when they are easier and cheaper to address.