Demand forecasting
For every SKU, customer and region, 30–90 days ahead, factoring in history, seasonality and sales channel.
Home · Case studies · FMCG
Case study · FMCG, commercial planning
An international personal care products manufacturer unified forecasting, pricing, discounts and promotions in a single tool — instead of dozens of scattered Excel files.

An international personal care products manufacturer ran commercial planning in scattered spreadsheets — forecasting, pricing, discounts and promotions each lived separately.
Forecasting, pricing, discounts and promotions were kept in separate Excel files with no single source of truth.
Collecting and reconciling data from different files and systems took up most of the cycle.
There was no unified picture of what was shipped to the customer versus what was actually sold to the end buyer.
Specifics
Users work with interfaces, not data exports: forecasting, pricing, discounts and data automation — in one tool, with country-specific price lists and forecast versioning.
For every SKU, customer and region, 30–90 days ahead, factoring in history, seasonality and sales channel.
A discount and terms builder: rules, recommendations and a change history by customer, region, volume and promotion.
Sales, prices, ASP, stock levels, turnover and plan-vs-actual in a single window. Excel, 1C and BI — updated daily.
Results
A unified commercial planning platform instead of scattered spreadsheets.
Growth from accurate forecasting and unified prices and discounts for every SKU and customer.
A reduction from more accurate demand forecasting and stock planning.
Data updates automatically — less manual reconciliation and fewer exports.
The platform grew out of the data warehouse: first the data, then the models, then the interfaces.
In the interface
We plan what to ship and at what price, and see what is actually being sold to the end buyer — in a single window, broken down by channel and period.

AI assistant
A team of agents works on top of the unified data. The question is asked in plain language, and the system breaks it down and assembles queries according to a verified contract.


The model does not write SQL itself — it describes what needs to be calculated, and the query is assembled by code following a verified contract. Every figure is traceable to a specific query and data rows. The connection is read-only. Example run: 3 of 5 waves, 14 queries, 21 facts, 7 hypotheses, coverage 7 of 7.
The company got a connected commercial planning system: forecasting, pricing, discounts, promotions and AI analytics — on one platform, with transparent sell-in and sell-out.