ERPs were built primarily to record, not to decide. Every order and stock movement lands in the ERP correctly. The choices behind them still happen in spreadsheets. Two customers want the same press slot next Tuesday. A planner lines up three reports to pick one. The category built for that choice is supply chain planning software. The software sits above the ERP, reads its data, and helps planners trade off capacity and customers against each other. This guide names nine decisions an ERP hands back to people. Each comes with one question you can put to your IT team this week.
Why Does an ERP Propose but Not Decide?
ERP planning logic proposes quantities. The logic does not weigh competing constraints, locations or customers against each other. In our implementation work, three design features explain the gap, and a reader who knows their ERP’s planning screens will recognise each one:
- Step by step, location by location. MRP runs each level and each site in turn, against infinite capacity and fixed lead times.
- Proposals without trade-offs. It creates planned orders but cannot choose between two customers for one slot, or between two depots for one batch.
- Planning sold separately. The largest ERP vendors sell their advanced planning as a product separate from the ERP itself.
So a planner still settles each trade-off by hand. None of this is a fault in the ERP, which does its job of keeping the transaction record. The decision that produces the transaction sits upstream of it, and supply chain planning software works at that point.
What Is Supply Chain Planning Software?
Supply chain planning software is a decision layer that sits above the ERP. It turns ERP data into plans a planner can commit to. A typical product forecasts demand, sets stock targets across locations, schedules against finite capacity, and flags the exceptions worth acting on. The ERP stays the system of record.
The APICS Dictionary, maintained by ASCM, treats advanced planning and scheduling as its own class of system, built on optimisation and simulation against finite capacity. The definition draws the line between a transaction system and a planning system. A supply chain planning platform covers several of these jobs in one model, for end-to-end planning from demand through to the shop floor. A point tool covers one job and leaves the hand-offs to spreadsheets. Planning-to-execution is the stretch where those hand-offs cost the most. Buyers comparing supply chain planning software will find both kinds on one shortlist. Check which one you are looking at.
What Are the 9 Decisions an ERP Was Never Built to Make?
The nine decisions run from demand and inventory through supply to execution, with one that cuts across all of them. Each is a choice between options. Every one of them starts from ERP data, and none of them is settled by the ERP alone.
| # | Function | Decision |
|---|---|---|
| 1 | Demand | Which demand number the business commits to |
| 2 | Inventory | How much of each SKU to hold at each location, and when that target should change |
| 3 | Inventory | Whether to move stock between locations or place a new order |
| 4 | Supply | What to make this week given finite capacity and material |
| 5 | Supply | How much to build ahead of a seasonal peak, and when to start |
| 6 | Supply | What delivery date to promise a customer |
| 7 | Execution | Which order gets a scarce capacity slot, and in what sequence |
| 8 | Execution | Which open purchase order is a real risk to production |
| 9 | Across functions | Which exception to act on first, including which OTIF miss to fix |
1. Which demand number the business commits to
Sales says 12,000 units for the quarter. The statistical baseline says 10,500, and finance has budgeted 11,000. The ERP stores whichever figure someone keys in. Nothing more. Choosing between them needs all three side by side, with the reasons behind each and an S&OP step to agree on one. Sales figures deserve the most scrutiny, since a study of more than 60,000 forecasts found upward adjustments much less likely to improve accuracy than downward ones. Our guide to integrated business planning covers that decision in full.
- Test question for IT: can our ERP hold three competing demand numbers for one item and show where they differ?
2. How much stock to hold at each location
A coverage norm of 30 days set two years ago still drives replenishment at every depot. Demand at one site has doubled since. At another it has halved. The ERP applies the norm faithfully. Deciding when the target should change needs current demand, lead time, and service level for each location, read together. Good supply chain planning software recalculates each site’s target from those inputs.
- Test question for IT: does our ERP recalculate stock targets by location when demand shifts, or do we edit them by hand?
3. Move stock or place a new order
The south depot holds 6 weeks of an item, and the north depot, 400 km away, is down to 4 days. MRP at the north depot raises a new purchase order because it plans one site at a time. A transfer would be cheaper and faster. Depots that each order on their own also feed the bullwhip effect. Lee and colleagues described it in 1997, showing that order swings can grow at every step upstream. Redistribution needs both positions on one screen. The move-or-buy call gets a full worked example in our distribution planning guide.
- Test question for IT: can our ERP show every depot’s stock position together and suggest a transfer before raising a new PO?
4. What to make this week
The plan calls for 900 hours on a line that has 720 this week, because MRP assumed infinite capacity, and material for two of the jobs only arrives on Thursday. Someone has to choose which work fits the hours and the parts actually available, and that choice needs finite capacity and material status in the same calculation.
- Test question for IT: does our ERP produce a weekly build plan that fits the line’s real hours and the material on hand?
5. How much to build ahead of a seasonal peak
A festive peak needs 3 months of extra volume, and the plant can only add 20% capacity. Starting the pre-build in August ties up working capital. October is too late. Finding the latest safe start means testing several build-up plans against capacity and cash, and the ERP runs one plan at a time.
- Test question for IT: can our ERP compare two pre-season build plans side by side, with the capacity and stock each one needs?
6. What delivery date to promise
A customer asks for 5,000 units in 3 weeks. The ERP quotes the item master’s standard lead time. A real answer checks free capacity and components against orders already promised. In supply chain planning software, this is capable-to-promise, and it needs the order book and finite capacity in one calculation. Without it, sales promises dates the plant cannot meet.
- Test question for IT: when sales enters an order, does the promised date come from real capacity or from a fixed lead time?
7. Which order gets the scarce slot
Two key accounts both need the paint line on Tuesday. The ERP accepts both orders and books neither against the line. Both look confirmed. The planner has to weigh margin, contract penalties, and how each customer would take a 2-day slip. Changeovers then set the sequence.
- Test question for IT: can our ERP show which orders compete for one constrained machine, and rank them by a rule we set?
8. Which open PO is a real risk
The buyer has 300 open purchase orders, 40 of them unconfirmed by the supplier, and the ERP lists every one by PO date. The one that matters is a gasket due on Friday for a job that starts Monday. Ranking by production consequence needs the PO and the schedule linked, which is routine work for supply chain planning software. Our purchase order management guide covers these detection gaps.
- Test question for IT: can our ERP rank unconfirmed POs by the production they would stop?
9. Which exception to act on first
A planner starts the day with 60 alerts, and only three of them threaten customer orders this week. Exception management means ranking alerts by impact. An OTIF miss then needs root-cause attribution across the supply and logistics records.
- Test question for IT: does our ERP rank today’s exceptions by the customer orders they put at risk?
What Does a Planning Layer Need from Your ERP?
A planning layer needs three things from the ERP. The layer needs clean master data, a sync on a known schedule, and a route to write decisions back as ERP transactions. IT raises this objection before any supply chain planning software goes live, so settle it before the demo.
Master data. Item codes, bills of materials, routings, lead times, and supplier records drive every calculation. A planning layer exposes bad master data fast, because a stale lead time now changes a decision. Agree who owns each field before go-live.
Sync schedule. An ERP overlay reads orders and stock positions on a set schedule, such as nightly or once per shift. Planners then work between syncs. A sync that takes 3 hours cannot run every shift. Ask how long one sync takes on your data volume.
Write-back. A decision only counts once it becomes a transaction. An approved transfer becomes a stock transport order in the ERP, and an agreed build becomes a production order that the shop floor can run against. The execution layer stays in the ERP, so confirm which transaction types the planning layer can create there.
Where Does Oritiq Fit Above the ERP?
Oritiq is the decision intelligence layer above the ERP. Planners make the nine decisions, and Oritiq gives them the numbers to make them quickly. The confirmed examples are capable-to-promise dates, exception prioritisation by impact and pre-season build-up plans. All three start from data the ERP already holds. The work runs across S&OP reconciliation, constraint-based supply planning, multi-echelon inventory optimization, and production and procurement execution.
FAQs on Supply Chain Planning Software
1. What is supply chain planning software?
Supply chain planning software is the layer that turns ERP data into decisions planners commit to, such as this week’s build or the date to promise a customer. A plant with 400 SKUs across 6 depots runs these calculations every cycle. The ERP keeps the transaction record underneath.
2. What is the difference between an ERP and supply chain planning software?
An ERP records what happened, from a purchase order to a 500-unit stock movement. Planning software decides what should happen next, such as which of two orders takes a line on Tuesday. A business with both keeps the ERP as the record. Decisions are made in the supply chain planning system, then go back into the ERP.
3. Can an ERP be configured to make these decisions instead?
Partly. Finite scheduling and planning add-ons exist for the larger ERPs, and the vendors sell them as separate products. They need well-maintained routings and calendars to work. Test one decision from the list above, such as decision 3 on depot transfers, before buying any configuration project.
4. Does supply chain planning software replace the ERP?
No. The ERP keeps orders and financial records. A planning layer reads that data on a set schedule, such as every 24 hours, plans against it, and writes approved decisions back as transactions. Replacing the ERP is a separate project with its own budget, and a planning layer does not require one.
5. What is a supply chain planning platform, and how is it different from a point tool?
A platform runs several planning jobs in one model, so a forecast change flows into stock targets and the build plan. A point tool handles one job, such as forecasting. Single-job supply chain planning tools each keep their own copy of the data. With 3 point tools, a planner rebuilds the links in spreadsheets each cycle.
6. How does supply chain planning software connect to an existing ERP?
Through an API, file transfer, or direct database connection, on a set sync schedule such as nightly. The connection reads orders and master data, then writes approved decisions back as transactions. Ask each vendor how long one full sync takes on 2 years of your order history.
7. Is supply chain planning software worth it for a business that already has strong ERP reporting?
Reporting shows last month. Planning software chooses next week’s actions. If planners still settle capacity clashes or depot transfers in spreadsheets, the gap is in decisions. Count the hours your planners spend on the 9 decisions above in one month before you price supply chain planning software.
Which Decision Should You Test First?
Start with decision 3. Pick one item that sits in two depots and check how your ERP handled the last shortage at one of them. If it raised a purchase order while the other depot held weeks of cover, the case for supply chain planning software is already in your own data.
Talk to the Oritiq team about a scoped pilot on that decision.