Let Skuvelo tell you what to count

Skuvelo keeps a ranked "Due for count" list on Inventory → Cycle Counts so you don't have to guess what to physically check. It's built from three things: how much sales value a SKU carries, how long it's been since it was last counted, and whether its data looks wrong.

The ABC classes

Every SKU is classified A, B or C by its trailing 90-day sales value — the Pareto split. Ranked by value, class A is the SKUs that make up the first share of total value (80% by default), class B the next share up to a second cutoff (95% by default), and everything after is class C. A SKU with no sales in the window is always class C.

Cadence: how often each class is due

Each class has its own count cadence, days since it was last counted (or since it was first stocked, if it's never been counted):

• Class A: every 30 days
• Class B: every 90 days
• Class C: every 180 days

A SKU appears on the due list once it passes its class's cadence at any location that carries it.

Two more reasons a SKU can show up

Beyond the cadence, a SKU is also listed when:

• Data health gap: it has no recorded unit cost, or a channel listing that isn't matched to it — the same gap Inventory's "Data health gaps" tile counts.
• Forecast miss: its selected forecast model missed by more than 40% in backtest — the same threshold Inventory's "Forecast risk" tile uses for a scored SKU.

A SKU counted recently enough (the recount pause, 30 days by default) is not re-listed for either of these two reasons, so a fresh count isn't immediately followed by another suggestion for the same gap. The line above the list still shows each signal's full total, split into listed and counted recently, so its data-health number always matches the Inventory tile.

Auto-plan

By default, Skuvelo only lists what's due — planning the count is still up to you, from the button next to each row. Turn on auto-plan for a class and Skuvelo plans that class's due counts for you on a schedule, without you opening the app; auto-plan only ever plans a count for the cadence reason — it plans a SKU that's overdue by its class's cadence even when it also has a data-health or forecast-miss reason, but never plans a count for one of those two reasons on its own.

If you cancel a count Skuvelo auto-planned, that SKU goes back on the due list and is auto-planned again once the recount pause has passed, rather than staying stuck until someone counts it by hand.

Where to change any of this

The class shares, the cadence per class, auto-plan per class, and the recount pause all live on Settings → Count Schedule. Only roles with the counts management permission can change them; every other role can view the current settings.