The whole planning cycle, in one system.
Demand planning stays where the business already runs. There is no separate planning system to buy, populate or reconcile, no extract to schedule and no copy of the data to keep in step. Planners open a Fiori app in S/4HANA, work the plan, and release it to supply planning.
Solution demonstration
A walkthrough of the planning cycle inside S/4HANA — producing the forecast, reviewing history and forecast side by side, adjusting where judgement differs, and releasing the result to supply planning.
Where this fits
This add-in is intended for organisations whose demand plan already lives in S/4HANA and that want a modern forecast there without standing up a separate planning system for it. It works on the history already held in the system, and hands the agreed plan to the MRP run that is already scheduled.
Planning that happens where the data already lives.
What it changes for the planning team
A forecast arrives without anyone having to choose a model or maintain one, so the team spends its time on the products that need judgement rather than on keeping a statistical setup alive.
Nothing reaches supply planning until it is agreed. Planners review the numbers, adjust where they know better, and release when the plan is ready — and what MRP receives is exactly what was signed off.
Capabilities
Pretrained Foundation Model
A model that already knows how to forecast, so there is nothing to train, nothing to tune, and no data-science project to fund before the first plan.
Native, In-System Add-In
A clean-core extension running on live S/4HANA data. Nothing to integrate, nothing to reconcile, and no impact on upgrades.
Judgement Stays Visible
A planner's changes sit alongside the model's numbers rather than replacing them, so it is always clear what the business decided and why.
Straight Into Supply Planning
The agreed plan is released to MRP as Planned Independent Requirements, weekly or monthly, with no rekeying and no hand-off between systems.
Demand and Supply on One Screen
Demand and the supply response side by side, period by period, so the effect of a planning decision is visible before it becomes a problem.
Secure by Design
Only anonymous numbers ever leave the system — no master data, no descriptions, no customer names. Business data stays within SAP.
Also included: lifecycle planning for products with no history of their own, forecasting on demand or on a schedule, and an Excel round-trip for planners who prefer to work a cycle in a spreadsheet.
Demand planning for Shopify 3PLs
A growing share of demand is placed in an online store and shipped from a third-party warehouse. It settles in the ledger as revenue, but it never arrives in S/4HANA as a sales order — so it is absent from the history the demand plan is built on, and nothing forecasts it. The add-in reads that demand from the store and plans it with the same pretrained tabular foundation model that plans the rest of the business.
The channel nobody plans
Where e-commerce fulfilment sits outside the ERP, the units are real and the replenishment is real, but the demand signal is not in the system that plans it. The result is a plan that is complete for one channel and blind to another — often the fastest-growing one.
Channel demand is read straight from the store, mapped to the plant that actually replenishes it, and forecast on its own pattern before it joins the plan released to supply planning. Only the article, the quantity, the date and the fulfilling location are ever read — no names, no addresses and no contact details are requested at any point.
A forecast is only as complete as the demand it can see.
Sell-Through Demand Planning
Planning on what consumers actually bought, rather than on what was shipped into the channel — the demand signal at the point it is created.
Integration by Design
The connection to the store is part of the add-in. There is no integration platform in between, no middleware to licence and no service to host.
Turnkey Implementation
Stores, locations and articles are mapped once as configuration. No development project, and no change to how the planning cycle already runs.
The store, the ERP and the model — integrated
Available as an additional feature.
Onboarding
Install once, connect once. After that it forms part of the ordinary planning cycle — run, review, release.
Install
Installed into the customer's existing S/4HANA Cloud system. No third-party installer, and no new platform to stand up.
Set the Scope
Agree which products and locations are planned, and how far ahead. A one-time setup, adjusted later as the business changes.
Run, Review, Release
Forecast, review, adjust and release — every planning cycle, without leaving S/4HANA.
Delivered as a subscription service
The solution is delivered as a managed subscription rather than a licence. It is set up around how the business already plans, and kept current for the term.
Three versions are available, to suit every need and budget — from running entirely inside the customer's own S/4HANA, through to a fully hosted option in which Integrated Business Planning Solutions operates the planning cockpit. Forecasting capability is identical across all three; the versions differ only in how much the customer chooses to operate.
Pricing is scoped per customer and issued as a private offer through SAP Store — a quote raised for the named customer, accepted in the Store, transacting alongside the customer's other SAP subscriptions.