Cycle Counts

A cycle count is a scheduled partial count — instead of closing the store for a day to count everything once a year, you count one slice (a vendor, a case, a category) on a regular cadence. Over the course of a quarter or year, every slice gets covered.

Scheduling

Cycle counts are configured in Settings. Each schedule defines:

• Scope — which items it covers (e.g. all diamonds at Store 1, or all items from Vendor X).
• Frequency — how often it runs (weekly, monthly, quarterly).

When a cycle count comes due, it appears as a badge on the Inventory Count nav item. Overdue counts also surface in the dashboard so they can’t be quietly ignored.

Best practices

• Stagger schedules so multiple cycle counts don’t all come due the same week.
• Count the highest-value or fastest-moving sections more often.
• Treat overdue cycle counts as a real signal — if one slips for two cycles, it usually means the schedule was set too aggressively.

The Cycle Count Variance report

The Cycle Count Variance report (Reports module) pulls together every discrepancy found across your closed count sessions. One row per variance — Session, Closed date, Stock #, Stock Type, Description, Expected Qty vs Counted Qty, the resulting Variance Qty, the Variance Type (over/short), and Status. Filter by date range, a specific session, and status. It’s the audit trail of “what didn’t match” — review it for shrink patterns (a category or location that keeps coming up short) rather than treating each variance in isolation.