Why A items, and only A items
The 80/20 rule earns its keep here. Your A items are the SKUs where a counting error distorts real decisions: purchase orders placed against phantom stock, production scheduled against units that are not there, promises made on quantities that stopped being true. A C-item that is off by ten units is a rounding error. A C-item that is off by ten thousand units is still usually just a data-entry typo waiting to be found. The A items are where the money and the schedule live.
In Odoo, the ABC classification does this work for you. Set the A items to count monthly, and the system will generate the count list on whatever schedule you choose. In SAP Business One, cycle count codes and inventory postings do the same job, and the MRP run reads the corrected on-hand before it plans anything. Either way, the rule is the same: spend the counting effort where the money is.
Setting it up in either system
The setup is one-time and it takes an afternoon. In Odoo, turn on the cycle count feature, let the ABC classification run against your sales history, and set the A items to a monthly cadence. The system starts generating count lists automatically, and the counts show up in a queue your team can work through like any other task. In SAP Business One, assign cycle count codes to your A items and schedule the inventory postings. The cycle codes tell the system which items to count and how often; the postings record the corrections with a reason code so the variance history stays clean.
The part that matters in both systems is the same: the count list comes from the system, not from someone deciding what feels worth counting. That removes the judgment call that kills most counting programs — the one where Monday is busy, so counting waits, and waits, and waits.
What the Sunday check actually catches
Three things, every time:
- Receiving gaps. Units that landed on the shelf during Saturday's push but never made it into the system. The Sunday spot-check finds them before Monday's production schedule does.
- Pick errors that settled. A pick that pulled the wrong quantity Friday afternoon shows up as a variance by Sunday. Found Sunday, it is a correction. Found Thursday, it is a missed shipment.
- Stale reorder points. If an A item's on-hand has drifted, the reorder point feeding the purchase order is wrong, and the wrongness compounds every day it goes unfound.
The rule that makes it stick
The habit fails when it depends on remembering. Set the schedule in the system and let the system do the reminding. In Odoo, the cycle count rules generate the list; in SAP Business One, the inventory postings route themselves. The humans confirm and move on. Fifteen minutes, every Sunday, and the week starts against numbers that are real.
One honest edge, because I would rather hand you the sharp end: if units arrive without ever landing in the system, no counting schedule will save you. The Sunday check will find the gap — it is good at that — but receiving discipline is the cure. The count is the detector. Receiving is the fix.
Running on spreadsheets and want to see cycle counting against your own item list? Start with the free Odoo trial and see the count rules against your own item list — or grab a free 30-minute call and I'll tell you straight whether Odoo or SAP Business One fits your warehouse.
More from me on the Dead Brands blog.
Frequently asked questions
How long does the Sunday spot-check take?
Fifteen minutes for the top ten A items, once the list is set up. The list generation is automatic; the walking is what costs the fifteen minutes.
Does this replace the annual count?
No. The annual count becomes a confirmation instead of a reconciliation once the rolling checks are running. You still count everything — just never all at once, and never on a weekend you resent.
Which items belong on the Sunday list?
Your A items — the handful of SKUs where a counting error distorts real decisions: purchase orders, production schedules, and delivery promises. Pull the top ten by value and walk those. A C-item that is off by ten units is a rounding error; an A-item that is off by ten can bend a whole week.
What if the spot-check keeps finding the same gaps?
Then it is finding receiving problems, not counting problems. Units that land on the shelf without landing in the system will show up as a variance every single week. The check is the detector; receiving discipline is the fix.
