The engine

The promo is an object, not a number someone typed in.

Dates, the SKUs it covers, the warehouses it ships from, the lift you expect. Build it once and it enters demand as a promotion — which means when it moves, everything downstream moves with it.

Dates, SKUs, warehouses, 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.

It reads as a promotion afterwards

When the quarter is over, the lift is still labelled as the promo that caused it rather than sitting in history as an unexplained spike the forecast will now try to repeat next year.

Stack it in a scenario first

Build the promo inside a Master Plan scenario and see the production it triggers and the capital it commits before you promote it into the plan.

Overnight

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.

The spike the forecast learned from

A BFCM push doubled velocity on four SKUs for eleven days. Typed into the plan as a raw number, it became history the model tried to repeat the following November — and nobody remembered why. As an object, the lift stays attributable to the promotion that caused it.

Plan the promo before you buy for it

See what a lift commits in production and cash before it is a purchase order.