Running a Supply Chain Planning Software RFP: A Ten-Step Selection Playbook
Most planning RFPs reward the best slide deck, not the best fit. This ten-step playbook fixes that with a weighted scorecard, scripted demos on your own data and sharper reference questions.
Map the Planning Decisions Before You Write a Single Requirement
A supply chain planning software RFP usually goes wrong in the first month. The team downloads a 400-line requirements template, sends it to six vendors, and gets back six spreadsheets that all say "Yes, standard." Nobody learns anything. Start with the decisions your planners make, not the features you think you need.
Step 1: Scope the planning processes. For each planning horizon, list the decisions, who makes them, how often, and what a wrong call costs. For example: monthly consensus demand at product-family level, a weekly constrained supply plan by plant, daily allocation when supply is short. Flag which ones run on spreadsheets today and which hurt most. Two or three processes usually carry most of the business case, and those become the core of your evaluation.
Step 2: Assemble the team and the data. You need a business owner (usually the head of planning or S&OP), an IT architect who knows your ERP, a finance partner who'll own the business case, and two working planners who'll use the tool every day. Start pulling history now: orders, shipments, past forecasts, bills of materials, lead times and inventory. Two years is the minimum. Get three if your demand is seasonal. Data prep always takes longer than planned, and your demos depend on it.
Build a Longlist and an RFP Vendors Can't Answer With Boilerplate
Step 3: Build a longlist of five to seven vendors. Large-enterprise platforms include Kinaxis, o9 Solutions, Blue Yonder, SAP IBP and Oracle Fusion Cloud SCM. Specialist and mid-market options include OMP, Logility, ToolsGroup, RELEX (strong in retail and grocery) and Anaplan for finance-led connected planning. Filter early on three things: industry fit, your ERP, and whether the vendor or its partners have delivery teams in your regions. A platform with a deep partner bench in Germany may have only a few certified partners in Brazil, Saudi Arabia or Indonesia, and that limits your choices at implementation time.
Step 4: Write a short RFP built around scenarios. Keep it to 60 to 100 questions, and replace feature checklists with open scenarios: "Describe how your system re-plans when a key supplier cuts allocation by 30% mid-month. Which users act, in which screens, and how long does a re-plan take at our data volume?" Ask for hosting regions and data-residency options. These matter under GDPR in Europe, India's DPDP Act, Saudi Arabia's PDPL, Brazil's LGPD and similar laws elsewhere. Also ask for named implementation partners in every country where you operate. Then use the written responses to cut the list to three finalists.
A Weighted Scoring Template That Rewards Fit Over Polish
Step 5: Agree on the weights before any vendor presents. If you set weights after the demos, the most charismatic presenter wins. Adapt the template below to your priorities and lock it in. Then have every evaluator score on their own before the group discusses.
| Criterion | Suggested weight | What a top score looks like |
|---|---|---|
| Process fit in scripted demo | 30% | Runs your scenarios on your data with minimal workarounds |
| Implementation partner and method | 15% | Named team with relevant industry projects in your regions |
| Three-year total cost | 15% | Clear subscription, services and internal effort, few unknowns |
| Data model and ERP integration | 15% | Proven connectors to your ERP version, clear master-data needs |
| Scenario speed and what-if | 10% | Re-plans at your volume in minutes, side-by-side comparison |
| Planner usability | 10% | Your planners finish tasks without vendor help after brief training |
| Vendor viability and roadmap | 5% | Stable ownership, credible investment in your modules |
Score each criterion from 1 to 5 and multiply by its weight. As a rule of thumb, if two finalists land within about 0.3 points of each other, call it a tie. Reference checks and commercial terms then decide.
Script the Demo Around Your Own Data
Step 6: Run scripted demos, not vendor showcases. Send each finalist the same anonymized dataset and the same script three to four weeks ahead. Build four to six scenarios straight from Step 1. Here's a hypothetical script for a mid-sized food manufacturer:
- Load 200 SKUs across two plants and three distribution centers and generate a statistical baseline forecast. Show forecast accuracy against our holdout months.
- A key retail customer adds a promotion that lifts volume 40% for six weeks. Show how sales input flows into the consensus plan.
- Line 2 at Plant A goes down for ten days. Re-plan constrained supply and show the impact on service and margin.
- Compare two scenarios side by side in the format our monthly executive S&OP meeting uses.
Have your own planners run the system for at least one scenario. If a vendor asks to pre-configure more than you supplied, log every change. That's configuration effort you'll pay for later. Since every vendor works the same problem on the same data, this is the fairest demand planning software comparison you can run.
Where Kinaxis vs o9, Blue Yonder and SAP IBP Actually Diverge
Step 7: Test the differences that matter for you. The finalists' marketing will sound alike, but their architectures and strengths are different. Build the script to expose those differences.
- Kinaxis is built around concurrent planning, meaning fast what-if analysis on a single data model. It tends to suit complex, constrained supply networks in high-tech, aerospace, automotive and life sciences. Check how far its statistical forecasting goes for your demand patterns.
- o9 Solutions offers a broad, highly configurable platform that links demand, supply, commercial and financial planning. All that flexibility means more design work, so judge the partner as hard as the software.
- Blue Yonder is strong in retail, consumer goods, and demand and replenishment, and it also sells warehouse and transport products. The portfolio grew through acquisitions and re-platforming, so ask how well the modules work together within your scope.
- SAP IBP is the natural shortlist pick for companies on S/4HANA because of its native integration. Planners also get an Excel add-in alongside the web interface. Test scenario speed and how it handles non-SAP data sources.
On Kinaxis vs o9 specifically, the deciding question is usually whether your bigger problem is fast supply response or broad cross-functional planning design. Buy for that problem.
Reference-Check Questions That Expose Real Fit
Step 8: Talk to customers who look like you. Ask each finalist for three references in your industry, at similar scale, live for more than a year, and ideally in your regions. Bring your own questions instead of following the vendor's agenda:
- How long did it take from contract signature to the first process live, compared with the original plan?
- What share of planners use the tool daily, and what still runs in spreadsheets?
- Which partner did you use, and would you hire the same team again?
- What did you have to customize that you expected to be standard?
- How did your subscription change at renewal or when you added users?
- What would you scope differently if you started over?
Be wary if every reference sits on the vendor's advisory board or went live less than six months ago. Also ask for one customer who struggled and then recovered. How the vendor responds to that request tells you a lot.
S&OP Software Pricing and the Real Three-Year Cost
Step 9: Model total cost, not list price. S&OP software pricing is almost always a negotiated annual subscription. It's driven by the modules you buy, the number of planners or users, data volume (SKU-location combinations) and the number of environments. The figures below are indicative 2026 market ranges in USD. They vary widely by contract, region and scope, and local pricing differs, so confirm with each vendor.
| Cost element | Mid-market scope | Large enterprise scope |
|---|---|---|
| Annual subscription | $75,000 to $400,000 | $500,000 to $3M+ |
| Implementation services | Roughly 1x to 2x annual subscription | Roughly 1x to 3x annual subscription |
| Internal team effort | 3 to 6 FTE during rollout | 8 to 20+ FTE during rollout |
| Time to first process live | 4 to 8 months | 6 to 12+ months |
Watch out for contracts priced in a currency other than your reporting currency. In some countries, cross-border software fees can also trigger withholding tax or local registration requirements. Ask a qualified tax adviser to review the structure before you sign.
Negotiate the Terms That Protect Year Three
Step 10: Negotiate the full lifecycle, not the first-year discount. Vendors give up headline discounts easily. The terms that actually protect you are harder to win and worth more:
- A cap on annual renewal increases (buyers commonly push for low single digits) plus locked pricing for modules you may add later.
- A phased ramp so you aren't paying the full subscription before go-live.
- Named partner staff, and fixed-fee or capped milestones for the first phase.
- Data-residency, data-export and exit terms that meet the data-protection laws in every country where you operate, reviewed by counsel in each relevant jurisdiction.
- Success criteria from your scripted demo, written into the statement of work.
The decision rule: if one finalist leads on demo process fit and its references back that up, take it into negotiation and keep the runner-up active until you sign. If no finalist scores at least 3.5 out of 5 on process fit, don't buy yet. Run a paid, time-boxed pilot with the top two on your most painful process.
Frequently asked questions
How long should a supply chain planning software RFP take?
Three to six months from scoping to signature is typical, and most of that goes to data preparation and scripted demos. If you squeeze it under about eight weeks, you'll usually have to drop demos on your own data, and those demos are where the real differences between vendors show up.
Is Kinaxis or o9 the better choice?
Neither wins across the board. Kinaxis is often favored when fast re-planning of constrained supply is the main problem. o9 is often favored when a company wants broad, configurable planning that links demand, supply, commercial and finance. Let your scripted demo and reference checks decide, not analyst rankings.
Should we pay for a proof of concept?
A paid, time-boxed pilot of four to eight weeks makes sense when finalists score close together or the process is high-risk. Paying gets you a committed vendor team working on your real data. Put the success criteria in writing before the pilot starts.
Do we need an independent advisor for vendor selection?
You don't need one, but an advisor with no reseller ties can help you write demo scripts and benchmark pricing, especially on a first planning project. Before you hire one, make sure they don't earn implementation or referral fees from any vendor on your shortlist.
How do data-protection laws affect a planning software selection?
Planning data can include customer and employee information, so hosting location and cross-border transfers matter under laws such as GDPR, India's DPDP Act, Saudi Arabia's PDPL and Brazil's LGPD. Ask each vendor for its hosting regions, sub-processors and data-export terms, and have counsel in each jurisdiction where you operate review the contract.
Written by the Port Cloud Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.