Scenario planning that shows what a decision commits before you approve it
Build a promotion, a channel launch or a price change as a scenario on top of live demand. Planster runs it through the same ordering calculation as the live plan and shows the production it triggers and the cash it commits. Approve it into the plan or discard it.
The cost of a scenario before you commit
Before a scenario touches your plan, Planster runs it through the same ordering calculation as the live plan: which orders move, what inventory looks like week by week, and how much cash the change pulls forward. Adding 22,400 units commits about $292K in production runs, and you see that before anyone approves it.
Version history and roll-back
Approving a scenario (“promoting” it, in Planster) writes it into the plan as a version: who approved it, when, and exactly what changed, down to the cell. Approve the whole scenario or selected channels. Rolling it back restores the plan exactly as it was.
Every number traceable to its layers
Approved changes live as visible layers over your base forecast, not baked-in edits. Click any cell and see the arithmetic: base forecast × promo lift × channel launch = the number on screen, with the scenario, the person, and the date behind each layer.
Scenarios compared side by side
A promotional lift, a new channel, a price increase: each one is a scenario, a separate set of changes layered over live demand rather than a spreadsheet copy that goes out of date. Compare them side by side before choosing one.
A 60-day lock on near-term supply
The next 60 days are locked by default — the window where orders are already committed. Scenarios that reach inside it are flagged when you approve them, so near-term supply stays stable while you change the plan further out.
A baseline to measure against
Keep a base plan alongside the live plan that is actually driving orders, so you can see how far the working plan has moved from where you started.
What the agent does with master plan
Every night
The agent watches the plan for gaps and puts them on your morning list — a won deal nobody added to the plan, a scenario whose order-by date has passed.
What it can’t do
It cannot approve a scenario, roll one back, or change a plan. Approving is always a human step, and no setting delegates it.
Example: planning a 400-door retail launch
Take a brand preparing a 400-door retail launch. It builds the launch as a scenario: the fill order, the ramp, the supporting promotion. The preview shows it pulls two production runs forward and commits about $292K before anyone approves it. Three of those weeks fall inside the 60-day lock, so they are flagged. The team compares it with a slower rollout scenario, picks one, and approves it as version 13. When the retailer pushes the reset back a month, rolling back restores the earlier plan.
How it fits together
Every capability runs on the same demand forecast, so each one makes the others more useful.
Pipeline
Deals in your Pipeline overlay the Master Plan at full volume until you approve them, so open deals become demand you can plan against.
Explore PipelineDemand planningBase plan and live plan
Keep a baseline next to the live plan, so the combined effect of everything approved this quarter is a number.
Explore Base vs live planSee what your next big decision commits
Book a demo and see a scenario run against your own numbers.