Promotional planning, with each promotion planned as its own event
Each promotion carries its dates, SKUs, warehouses and expected lift. It enters demand as a promotion, so when the dates change, the orders that depend on it change too.
Dates, SKUs, warehouses and lift
A promotion carries the things that determine its consequences. Push the start date two weeks and the demand shape moves with it, along with every order date that was feeding it.
Promotional lift kept apart from baseline history
After the quarter, the lift is still labelled with the promotion that caused it, so the forecast does not treat it as a pattern to repeat next year.
Test it in a scenario first
Build the promotion inside a Master Plan scenario and see the production and cash it commits before you approve it into the plan.
What the agent does with promotions
Every night
A promotion changes the forecast, so the overnight run re-checks cover against the new shape and flags the SKUs that will not make it in time to order.
What it can’t do
It cannot create, edit, or cancel a promotion. Promotions are yours to build.
Example: a Black Friday spike the forecast tried to repeat
Take a Black Friday push that doubles velocity on four SKUs for eleven days. Typed into the plan as a raw number, it becomes history the model tries to repeat the following November. Planned as a promotion, the lift stays attached to the event that caused it.
How it fits together
Every capability runs on the same demand forecast, so each one makes the others more useful.
Master Plan
Build the promotion as a scenario and read the consequence — production triggered, capital committed — before you commit.
Explore Master PlanDemand planningDemand forecasting
The baseline the lift sits on top of: one model per SKU, fitted to its own history.
Explore Demand forecastingPlan the promotion before you buy for it
See what a lift commits in production and cash before it is a purchase order.