The Question Every Planning-Heavy Company Now Faces
Five years ago this decision did not exist for most mid-market companies. Supply chain planning software was bought by supply chain organizations and invisible to finance until the invoice arrived. Finance planned money, supply chain planned units and the two met once a quarter in a deck.
Two things changed. First, EPM platforms started selling supply chain planning as part of connected planning for the office of the CFO. Pigment ships demand and inventory planning, S&OP and scenario modeling with direct P&L impact, and names Unilever, Danone and BJ's Wholesale Club among the customers using it in supply-facing contexts. Anaplan has sold mature supply planning and S&OP solutions for years. Board pitches a unified platform with retail and supply use cases. The pitch to the CFO is simple: one model from volume to P&L to cash, one governance layer, one vendor.
Second, the dedicated SCP vendors started pitching finance. o9, Kinaxis, Blue Yonder and Logility now sell integrated business planning stories with financial dashboards and CFO-facing slides. Their pitch is equally simple: planning that ignores machine capacity, material constraints and multi-echelon stock positions amounts to a spreadsheet with opinions.
Both pitches contain real truth, which is what makes the decision hard. And it lands on the CFO's desk more often than it used to, because the budget lines converged. When the EPM renewal, the S&OP project and the inventory problem sit in the same planning cycle, someone has to decide whether this is one purchase or two. That someone is usually you.
The cost of deciding badly runs in both directions. Buy an enterprise SCP suite for a co-packed CPG business and you will pay seven figures over three years for solver capacity you never use, run by planners you do not employ. Force a 40,000-SKU manufacturer to plan supply inside a finance model and the planning team will quietly go back to spreadsheets while the platform becomes an expensive reporting layer. We have watched both failures from the inside.
The honest version of the answer, before the detail: most companies under roughly $500M with simple supply models belong in the EPM lane. Most manufacturers past real constraint complexity need a dedicated tool, plus an EPM platform for finance. The six-question diagnostic below tells you which one you are, and the worked profiles show the scoring applied to real company shapes.
What EPM Platforms With SCP Are Actually Good At
Start with what the EPM camp genuinely does well, because the marketing undersells the real strength. These platforms usually do not forecast demand better than dedicated engines. Their strength is connecting the volume plan to the financial plan in one place, with finance-grade governance around the whole thing.
One model from units to P&L and cash
In an EPM platform, a demand plan is a set of driver inputs in the same model that produces the revenue plan, the margin bridge and the cash forecast. Change the volume assumption for one product family and the P&L impact, the working capital impact and the covenant headroom move in the same session. Dedicated SCP tools structurally lack this, because their financial layer is a costing translation bolted onto a units engine.
The practical payoff shows up in scenario work. When Evenflo modeled tariff scenarios in Pigment, the useful output was the landed cost and margin consequence of each sourcing response, priced through the P&L. Ankorstore's executives credit Pigment with a 20 to 25% improvement in forecast accuracy, and the mechanism worth noting is process rather than algorithms: one shared model that commercial, operations and finance all update instead of three reconciled spreadsheets.
Finance-grade governance
EPM platforms grew up under audit. Versioning, approval workflow, access control, audit trails and a defensible plan of record are native behaviors, not add-ons. When the S&OP output becomes the number the CFO signs and the board sees, this matters more than most supply chain evaluations admit. SKU-level profitability views in a tool like Pigment also let finance interrogate the plan (which products, customers and channels earn their inventory) rather than receive it.
Speed and reach
Modern EPM implementations for supply-facing use cases typically run 2 to 4 months on a platform like Pigment, and the module lands inside a tool budget owners already use. Adoption beyond the planning team is the quiet advantage: a sales director will update a demand assumption in a planning platform with a consumer-grade interface. They will never log into a supply chain suite.
Where the lane ends: EPM platforms model supply. They do not solve it. There is no multi-echelon inventory optimizer, no constraint-based supply solver and no purpose-built statistical forecasting engine tuned for intermittent SKU-location demand. A skilled modeler can approximate capacity checks and safety stock logic, and for simple networks that approximation is honestly enough. Past real complexity it is not, and no amount of model elegance changes that.
What Dedicated SCP Tools Are Actually Good At
The dedicated camp (o9, Kinaxis, Blue Yonder, Logility and SAP IBP at enterprise scale; Netstock, GMDH Streamline and John Galt in the mid-market) earns its cost on three capabilities that finance-platform modeling cannot replicate. It helps to understand each one in plain terms, because vendor demos hide them behind interface polish.
Statistical forecasting at scale
A demand planner cannot hand-forecast 40,000 SKUs across nine warehouses. Dedicated engines run families of statistical methods per SKU-location, pick the best fit, handle intermittent and seasonal patterns and flag which forecasts a human should actually review. The output is a triaged workload as much as a better forecast: the planner touches the 5% of items where judgment beats the machine and leaves the rest alone.
Multi-echelon inventory optimization
MEIO answers a question spreadsheet safety-stock rules cannot: given service targets, demand variability, lead times and costs, how much stock should sit at each level of the network, considered together? Stock held upstream at a plant warehouse can cover variability for many downstream locations at once, so optimizing each location separately systematically overstocks the network. For multi-node distribution businesses, the difference between rule-based and optimized stock targets is measured in points of working capital. For a business shipping from one warehouse, MEIO is a slide in a deck.
Constraint-based supply planning
This is the deepest moat. Given demand, a constraint-based engine builds a production and distribution plan that respects machine capacity, labor, material availability, alternate routings and lead times, and tells you what to make where and when. When demand exceeds feasible supply, it allocates: which orders, customers or regions get shorted, against rules you set. An EPM model can tell you a plan is over capacity. A solver tells you the best plan that is not. Kinaxis built its reputation on recalculating exactly this within minutes of a disruption.
Where this lane ends: everything financial. Costing in these tools is standard-cost translation, not driver-based financial planning. There is no budget workflow a controller would accept, no versioned forecast the board recognizes and no path from the supply plan to opex, workforce or cash. The finance dashboards these vendors demo are views, not a planning layer. They live outside the finance stack, and buying them does not change that.
The two lanes side by side
| Dimension | EPM platform with SCP | Dedicated SCP tool |
|---|---|---|
| Core question answered | What does this plan do to revenue, margin and cash? | Can we actually make and move this volume, and at what service level? |
| Planning grain | Product family or SKU group, monthly or weekly. SKU-level works but has practical limits. | SKU by location by week or day, across thousands to millions of combinations. |
| Inventory logic | Inventory as a modeled driver: days on hand, safety stock rules, working capital impact. | Multi-echelon inventory optimization: computed stock targets per SKU per node. |
| Supply feasibility | Assumed or approximated with capacity checks the modeler builds. | Solved. Constraint-based engines respect machine time, labor, materials and lead times. |
| Financial governance | Native: versions, workflow, audit trails, one model from volume to P&L and cash. | Limited. Costing is standard-cost based and outputs need translation for finance. |
| Who lives in it daily | FP&A, finance business partners, budget owners. | Demand planners, supply planners, S&OP managers. |
| Typical implementation | 2 to 4 months for planning use cases on a Gen-3 platform. Longer on legacy suites. | 4 to 12+ months depending on data readiness, network complexity and vendor. |
Neither column is the better column. They answer different questions, which is exactly why the right choice depends on which questions your company actually struggles with. That is what the diagnostic measures.
The 6-Question Diagnostic
Answer the six questions below honestly, with your supply chain lead in the room. Each answer scores 0, 1 or 2 points. Higher scores point toward a dedicated SCP tool, lower scores toward the EPM lane. The total lands you in one of three bands at the end. This takes 20 minutes and will save you a quarter of vendor meetings.
Two rules for scoring. Score the company you are today plus 24 months, not the company in the five-year strategy deck. And where two people in the room disagree on an answer, take the lower score. Optimistic self-assessment is how companies buy solvers they cannot feed.
How hard is it to answer: can we make and deliver what the plan assumes?
This is the single biggest separator. EPM platforms model the financial outcomes of a supply plan. They do not solve for feasibility across machines, materials, shifts and lead times. If feasibility is your daily argument, you need a solver, not a model.
We buy finished goods or use co-packers. Supply risk is mostly lead time and supplier reliability. Nobody debates production feasibility in planning meetings.
We run our own production but constraints are stable and known. A capable planner manages capacity in spreadsheets or the ERP without constant firefighting.
Multiple plants or lines, shared capacity, alternate routings, long or volatile lead times. Feasibility questions regularly change the plan.
At what grain does planning actually have to happen to be useful?
EPM platforms handle SKU-level data, and Pigment customers plan SKU-level profitability. But there is a difference between reporting at SKU level and optimizing at SKU-by-location-by-week level. Past roughly 10,000 active SKU-location combinations, statistical forecasting and inventory optimization engines start earning their cost.
Planning at product family level is fine for most decisions. SKU detail matters for a handful of hero products.
SKU-level demand plans matter, but one or two distribution nodes. Forecasting is judgment plus history, not heavy statistics.
Large assortment across multiple warehouses or channels. Manual forecasting at this grain is not credible. Stock targets need computing, not guessing.
How clean and connected is the data a planning engine would run on?
Dedicated SCP tools are hungry. MEIO and constraint solvers need accurate lead times, bills of material, routings, transfer costs and demand history at item-location level. Feeding a solver bad master data produces confident nonsense. EPM platforms degrade more gracefully because humans stay in the loop at a coarser grain.
Item master and lead time data are unreliable. Demand history sits in exports. An honest data audit would hurt.
ERP master data is mostly trusted. History is accessible. Some cleanup needed but no rebuild.
Item-location master data is governed, history is clean and someone owns data quality. A solver would have real inputs.
Who will run this tool every day, and who is funding it?
Tools bought by finance for supply chain, or by supply chain for finance, get abandoned. If FP&A will drive S&OP and the supply chain team is two people, an EPM platform they already know beats a planner-grade tool nobody can staff. If you employ career supply planners, they will reject a finance tool as too shallow within a quarter.
FP&A runs S&OP. Supply chain input comes from operations managers, not dedicated planners. The CFO owns the budget line.
A small planning team exists inside operations. Finance and supply chain co-own the S&OP cycle and would co-fund the tool.
A dedicated planning organization with demand and supply planners exists. They have their own leadership, budget and requirements.
What is already installed, and what does it make cheap or expensive?
Stack gravity is real. An EPM platform already running FP&A makes adding an SCP module fast and politically easy. A SAP ERP core makes SAP IBP the default conversation whether you like it or not. Two disconnected point tools make the case for consolidation. The right answer on a whiteboard can be the wrong answer in your architecture.
A modern planning platform (Pigment, Anaplan, Board or similar) already runs budgeting and forecasting. Adding volume planning extends a model that exists.
Planning lives in spreadsheets on both sides. Greenfield choice, so the diagnostic questions decide, not the stack.
A dedicated planning tool, APS module or SAP planning footprint already runs supply. Ripping it out for an EPM module would lose real capability.
What can you fund in year one, software plus implementation plus people?
Enterprise SCP deployments are expensive. Software is only part of it: SI-led implementations, data work and planner hiring often exceed the license. An EPM SCP module on an existing platform is usually the cheaper path to a working S&OP process. Under-funding a dedicated tool is worse than not buying it, because you pay enterprise money for a half-configured solver.
Low six figures all-in for year one, and no appetite to hire planners. The tool must run with the team you have.
Mid six figures available if the case is strong. One or two planning hires are possible.
A board-level supply chain program with seven-figure multi-year budget, executive sponsorship and headcount attached.
Reading your score
Run supply chain planning inside your EPM platform. Demand planning, inventory drivers and S&OP in one model with the P&L. A dedicated tool would add cost and a second data model without adding decisions you can act on.
Start in the EPM lane but name your trigger points. Usually one or two questions scored high while the rest scored low. Solve the high scorers with process or a narrow point tool (a mid-market inventory tool like Netstock or GMDH Streamline) before buying an enterprise SCP suite.
You need real algorithmic depth: statistical forecasting, MEIO and constraint-based supply planning. Buy a dedicated SCP tool for the planners and keep (or add) an EPM platform for financial planning. Then wire them together the way the two-tool architecture chapter describes.
One override outranks the arithmetic. If question 1 scored 2 (real constraint complexity), no total below 8 should talk you out of evaluating a dedicated tool for supply planning specifically. Feasibility problems do not average away against a strong EPM stack and a thin budget. They just go unsolved more cheaply.
Three Worked Profiles
Frameworks earn trust when you watch them run. Here are three company shapes we see repeatedly in evaluations, scored through the diagnostic with the reasoning shown. Find the one closest to you and steal the logic, not the answer.
Branded food products, co-packed manufacturing, 1,200 SKUs, sells through retail and distributors.
| Question | Why | Pts |
|---|---|---|
| Supply complexity | Co-packed. Feasibility is a purchasing question, not a solver question. | 0 |
| SKU count and grain | 1,200 SKUs, two DCs. SKU-level planning is manageable in a model. | 0 |
| Data maturity | NetSuite item data workable, history exportable. | 1 |
| Who owns the decision | FP&A runs S&OP. One planner sits in ops. | 0 |
| Existing stack | No EPM yet, no SCP. Greenfield. | 1 |
| Budget | Low six figures all-in. No planner hiring planned. | 0 |
This company should buy one platform, not two. An EPM platform with SCP capability (Pigment is the obvious evaluation, Board and Anaplan the alternatives) gives it demand planning, inventory as a working capital driver and an S&OP cycle that lands in the P&L and cash forecast. Implementations of 2 to 4 months fit the budget and the team.
The finance-led angle matters most at this size. The company's real problem is three disconnected spreadsheets: the volume plan, the trade spend plan and the financial forecast. Putting them in one model fixes the disease. Vita Coco and Ken's Food run supply-facing planning on Pigment at comparable profiles.
What it should not do: buy an enterprise SCP suite. At 1,200 co-packed SKUs there is no constraint problem to solve and no planning team to staff it. If forecast accuracy at SKU level becomes a genuine pain later, a mid-market statistical forecasting tool can bolt on for far less than a suite.
In demos, make vendors show SKU-to-P&L flow with this company's own item hierarchy and NetSuite data, not a demo dataset. Ask exactly what the NetSuite connector syncs and how often.
Industrial components, four plants, shared machining capacity, global distribution through nine warehouses.
| Question | Why | Pts |
|---|---|---|
| Supply complexity | Shared capacity and alternate routings. Feasibility drives the plan weekly. | 2 |
| SKU count and grain | 200,000 SKU-locations. Human-grain planning is not credible. | 2 |
| Data maturity | Master data decent in the core ERP, weaker in the acquired one. | 1 |
| Who owns the decision | A real planning organization with its own VP. | 2 |
| Existing stack | Heavy ERP planning footprint, no modern EPM. | 2 |
| Budget | Board-sponsored program to fix service and inventory. | 2 |
This is a dedicated SCP purchase, and pretending otherwise wastes a year. The planners need statistical forecasting at SKU-location grain, MEIO to reset stock targets across nine warehouses and constraint-based supply planning across shared work centers. That shortlist is Kinaxis, o9, Blue Yonder and Logility, with SAP IBP in scope only if the ERP consolidation lands on SAP. No EPM module computes an answer to this company's alternate-routing problem.
The CFO should not sit this purchase out. The business case is financial: 18% inventory growth is a cash story, and finance should define how the tool's inventory projections get measured against the balance sheet. This company also has no modern financial planning platform, and the SCP tool will not become one. The right architecture is a dedicated SCP tool for the planners plus an EPM platform for FP&A, with volumes and inventory flowing from the first into the second.
Sequencing matters. Fix master data in the acquired ERP before or during the SCP implementation, not after. Expect 9 to 12 months to full value on the SCP side and hold vendors to a phased plan: forecasting first, then inventory targets, then constrained supply planning.
Make SCP vendors run a pilot on one product family with real routings, and make them show the financial view a CFO would use. If the finance output is a raw units export, budget for the EPM side sooner rather than later.
Three regions, owned plants plus co-packers, 25,000 SKUs, existing Anaplan footprint in finance.
| Question | Why | Pts |
|---|---|---|
| Supply complexity | Owned plants in two regions, co-packers in one. Mixed but real constraints. | 2 |
| SKU count and grain | 25,000 SKUs, multi-region networks. | 2 |
| Data maturity | SAP core is governed. Satellites vary. | 1 |
| Who owns the decision | Established planning teams and a group S&OP function. | 2 |
| Existing stack | Both categories already partly installed. | 2 |
| Budget | Funded, but consolidation of tools is a board expectation. | 2 |
At this scale the question shifts from which category to how the two categories divide the work and where the seams sit. The pattern that works: one SCP standard across regions for demand, inventory and supply planning, and the EPM platform as the single financial layer where S&OP gets a P&L attached (some vendors call this integrated business planning).
The trap here is the everything-platform pitch from both sides. The Anaplan account team will propose extending into supply planning, and Anaplan SCM is genuinely mature, so that deserves a real evaluation. But replacing a working regional Blue Yonder deployment with EPM-based supply planning trades solver depth for model elegance, and the planners will feel it. Equally, the SCP vendors will pitch their finance dashboards as an FP&A replacement, which they are not.
The practical program: pick one SCP standard for all regions, keep Anaplan as the finance layer (or Pigment, if the group is already evaluating it for cost and usability reasons) and fund the integration between them as a permanent capability with an owner. The two-tool chapter below describes which numbers flow which way.
Ask each vendor pair to demo the handoff itself: constrained supply plan out of the SCP tool, priced and landed in the EPM P&L, with one scenario changed on each side. Most vendors have never been asked to demo the seam. The ones who can are the ones to keep.
The Two-Tool Architecture Done Right
If you scored into the dedicated lane, or you are the $2B profile, you will run two planning systems. Most companies do this badly: two tools, two versions of every number and a monthly reconciliation meeting that nobody believes. The fix starts with deciding, in writing, which numbers flow which way and which tool owns what.
Numbers that flow from the SCP tool into the EPM platform
The volume baseline finance prices and costs into the revenue plan. Monthly, at the grain finance plans at (family or SKU group), aggregated from the SCP tool's SKU-location forecast.
What operations can actually deliver, after capacity and materials. The gap between demand and constrained supply is the revenue-at-risk number the CFO should see monthly.
Feeds the working capital and cash flow forecast. This is the number that makes the balance sheet forecast real instead of a ratio assumption.
Committed spend drives the cost and cash timing in the financial forecast, and exposes commitments made against demand that has since softened.
Numbers that flow from the EPM platform into the SCP tool
The budget or latest forecast volume by family, so planners know what the company has promised the board and can flag divergence early.
So the SCP tool's scenario trade-offs (service versus inventory versus expedite) can be expressed in money, not just units and percentages.
Finance and commercial usually know about launches, promotions and discontinuations before the demand history does.
Inventory budget ceilings and capex decisions that change capacity. The solver needs to know the wall exists before it plans through it.
Five rules that keep it working
The SCP tool owns units and feasibility. The EPM platform owns money and the approved plan of record. The moment both tools claim the same number, planners and finance rebuild their private spreadsheets and the architecture is dead.
Finance does not need 200,000 SKU-location rows. It needs volumes at the grain the P&L is planned at, with drill-back available in the SCP tool. Pushing full grain into the EPM model bloats it and helps nobody.
The full plan handoff follows the S&OP calendar, monthly. Exceptions (a plant down, a supplier failure, a demand spike) should flow to finance within the week with a quantified P&L impact, not wait for the next cycle.
Run supply scenarios in the SCP tool and financial scenarios in the EPM platform, but agree the named scenarios that exist in both (base, upside, constrained), so the S&OP meeting compares like with like.
Someone must own the pipes after go-live: mappings break when the item hierarchy changes, and it will change. Modern APIs and warehouse-native sync help, but named ownership is what keeps the flow alive after the project team leaves.
The test of a healthy two-tool architecture is a single question at the monthly S&OP review: does anyone in the room have a private spreadsheet reconciling the two systems? If yes, one of the five rules is broken. Find which one before buying more software.
Red Flags in Vendor Pitches, From Both Camps
Both camps have practiced answers for why you do not need the other camp. After 15 years of sitting in these demos from the vendor side, here are the lines that should raise your guard, and what is actually behind each one.
When the EPM vendor is pitching
Sometimes true, and exactly what a vendor without a solver would say. If your planners spend their week resolving capacity conflicts, visibility does not resolve them. Test with your own constraint problem in the demo.
Family-level demos hide the grain problem. Ask to see the platform at your real SKU-location count, with recalculation times shown live, before believing the platform handles your scale.
For a 1,000-SKU single-warehouse business, arguably yes. For multi-echelon networks the difference is measured in working capital points. If a vendor dismisses a technique instead of scoping when it matters, that is positioning, not advice.
AI features on EPM platforms are real and improving (Pigment's Analyst and Modeler agents are useful for risk surfacing and model build). They are not a substitute for statistical engines tuned on intermittent, seasonal, SKU-location demand. Ask which forecasting methods run under the hood and how accuracy is measured.
When the dedicated SCP vendor is pitching
SCP finance modules translate units into standard-cost money. They do not do driver-based P&L planning, workforce and opex planning, versioned budget workflow or anything a consolidation-adjacent process needs. No CFO closes the books or runs a board reforecast from an SCP suite.
Inventory reduction claims of 15 to 30% are the standard pitch. Some customers achieve them. Ask what the reference company's starting condition was, over what period the reduction held and what service level did during it. One-time destocking is not a capability.
If the statement of work has no line for master data cleanup, lead time validation and history preparation, the timeline is fiction. This is the most common cause of SCP implementations doubling in length.
If the vendor cannot show a scenario's impact in money by the second demo, your finance organization will be doing that translation manually forever. The units-to-money seam is exactly where these projects fail.
One habit defeats most of these: bring your own scenario to every demo, at your own grain, with your own constraint. A vendor who handles it live has the capability. A vendor who asks to take it away and come back has a slide. For the broader evaluation process, our FP&A and EPM buyer's guide covers demo scripting, reference calls and negotiation in detail.
Frequently Asked Questions
Continue Your Evaluation
Ready to Score Your Own Shortlist?
Build your shortlist in the CFO Shortlist app: vendor profiles, comparison data and the evaluation frameworks from our reports in one place.