What Leading Planners Taught Me in Amsterdam: Issue 18

...and Why S&OP Is Non-Negotiable

IBF Learnings in Amsterdam Amsterdam

I had the opportunity to speak at IBF in Amsterdam about Agentic Supply Chains together with one of our customers, Bernd from Mammaly.

IBF is one of the largest events for Business Planning & Forecasting. I got to connect with leading planners from the largest flavor manufacturers, the worldโ€™s leading beverage company, and plenty of niche champions.

Demand and supply set the foundation

๐—ข๐—ป๐—ฒ ๐—ฏ๐—ถ๐—ด ๐˜๐—ฎ๐—ธ๐—ฒ๐—ฎ๐˜„๐—ฎ๐˜†: ๐—ณ๐—ผ๐—ฟ๐—ฒ๐—ฐ๐—ฎ๐˜€๐˜๐—ถ๐—ป๐—ด ๐—ถ๐˜€ ๐—ผ๐—ป๐—น๐˜† ๐˜€๐˜๐—ฒ๐—ฝ ๐Ÿญ.

โ†’ The real value comes from AI-driven exception management and scenario analysis, not just from a โ€œbetterโ€ forecast.

A few other key learnings from the sessions:

๐——๐—ฒ๐—บ๐—ฎ๐—ป๐—ฑ ๐—ฝ๐—น๐—ฎ๐—ป๐—ป๐—ถ๐—ป๐—ด ๐—น๐—ถ๐˜ƒ๐—ฒ๐˜€ ๐—ผ๐—ฟ ๐—ฑ๐—ถ๐—ฒ๐˜€ ๐˜„๐—ถ๐˜๐—ต ๐˜‚๐˜€๐—ฒ๐—ฟ ๐—ฎ๐—ฑ๐—ผ๐—ฝ๐˜๐—ถ๐—ผ๐—ป.

The most sophisticated model isnโ€™t always the best model, since it might not be used. Explainable, transparent models can drive faster adoption and impact.

๐—”๐˜ ๐˜๐—ต๐—ฒ ๐˜€๐—ฎ๐—บ๐—ฒ ๐˜๐—ถ๐—บ๐—ฒ, ๐—ฒ๐˜ƒ๐—ฒ๐—ป ๐—ฎ ๐Ÿญ% ๐—ฟ๐—ฒ๐—ฑ๐˜‚๐—ฐ๐˜๐—ถ๐—ผ๐—ป ๐—ถ๐—ป ๐—ณ๐—ผ๐—ฟ๐—ฒ๐—ฐ๐—ฎ๐˜€๐˜ ๐—ฒ๐—ฟ๐—ฟ๐—ผ๐—ฟ ๐—ฐ๐—ฎ๐—ป ๐˜‚๐—ป๐—น๐—ผ๐—ฐ๐—ธ ๐Ÿณ ๐—ณ๐—ถ๐—ด๐˜‚๐—ฟ๐—ฒ๐˜€ ๐—ถ๐—ป ๐˜ƒ๐—ฎ๐—น๐˜‚๐—ฒ.

For a โ‚ฌ300M business, that can easily mean several million in reduced write-offs and less working capital tied up in inventory.

But you only get there if itโ€™s measured consistently and correctly, and you actually visualise the impact on the business for all stakeholders.

โ†’ It is on the company to find their โ€˜equilibriumโ€™. One must-do is to understand how forecast accuracy is linked to business value โ€“ because only then:

  1. Sales has visibility on the value of their adjustments.

  2. We have a shared KPI with which we can measure success (e.g. MAPE-3).

๐—ฃ๐—น๐—ฎ๐—ป๐—ป๐—ถ๐—ป๐—ด ๐—ฎ๐—ป๐—ฑ ๐—ฒ๐˜…๐—ฒ๐—ฐ๐˜‚๐˜๐—ถ๐—ผ๐—ป ๐—ฎ๐—ฟ๐—ฒ ๐˜€๐˜๐—ถ๐—น๐—น ๐˜๐—ผ๐—ผ ๐—ผ๐—ณ๐˜๐—ฒ๐—ป ๐—ฑ๐—ถ๐˜€๐—ฐ๐—ผ๐—ป๐—ป๐—ฒ๐—ฐ๐˜๐—ฒ๐—ฑ.

They need to live together, not in separate workflows. One example is replenishment updates. Only by understanding when delays happen can we understand our supply gaps directly and react to them in real time.

For example, we might see a key PO or shipment slipping. We could:

  1. Call the coman to try to expedite.

  2. Send goods from one warehouse to another (but which?).

  3. Decrease marketing activities.

Or try all of the above?

This real-time scenario analysis โ€“ and then executing those decisions โ€“ belongs in one platform. Thatโ€™s why weโ€™ve built Spherecast to connect forecasting, exceptions, and execution in one place.

Today, these trade-offs live in emails, spreadsheets, and meetings โ€“ exactly where speed and accountability go to die.

Amazing to see what the IBF has built, bringing real pioneers in the industry into one room.

Already looking forward to the next Institute of Business Forecasting & Planning event.