Demand planning

Forecast exceptions: the SKUs running above or below plan

Set a tolerance per SKU. Planster compares actual sales against the forecast and flags the SKUs running outside it, with the size of the miss, while there is still lead time to act.

A tolerance set for each SKU

A 15% swing on a slow mover is noise. The same swing on the SKU that carries a third of your revenue is next quarter’s problem. Tolerances are set per SKU so the list you get is the list that matters.

The size and direction of each miss

The exception carries the size of the miss and the direction. Running 40% above forecast for three straight weeks is a different decision from a single spike, and you can see which one you are looking at.

Flagged while there is lead time to act

An exception found at month end is too late to act on. Planster checks against your lead times, so the question is still whether to move an order up, not how long the stockout will last.

Overnight

What the agent does with exceptions

Every night

Exceptions are what the agent ranks the morning digest around. It re-checks every SKU overnight and the ones outside tolerance are what lands at the top of the email.

What it can’t do

It cannot change your tolerances or decide an exception is not worth telling you about. You set the thresholds and you can silence any check yourself.

Example: a SKU running 40% above forecast

Take a mint SKU whose Amazon velocity runs 40% above forecast for three straight weeks. Nobody is watching it, because it has never been a problem. The exception puts it in front of the planner in week one with the size of the miss attached — in time to move a purchase order forward rather than explain an eighteen-day stockout.

See which SKUs are outside tolerance

Connect your data and see which SKUs are running outside their tolerance today.