Rank locations by exposure and consequence

Count locations more often when stock moves frequently, units are easy to confuse, or an error would interrupt an important order. An open picking bin may need more attention than sealed reserve cartons of the same product. Start with recent picking failures, unclassified returns, repeated quantity corrections and transfers between floors or nearby storage rooms. Ask the people doing the work where the record stops matching reality; product value alone will miss some operationally expensive errors.

A single monthly count is easier to administer, but gives every location the same attention regardless of risk. Counting only after a complaint saves scheduled time while leaving quiet errors undiscovered. Combine a regular due date with extra counts after a known incident. Start with a manageable pilot area and retain a register of every other location with its own due date. A pilot should not leave reserve stock unchecked indefinitely.

Turn priorities into a workable schedule

These intervals are proposed starting assumptions for a small wholesaler, not benchmarks or measured results. Assign a location code, interval, counter, backup and next due date to each row in your own plan. Include unexpected items found on the shelf, not only products already shown on the screen. Separate returns from saleable stock physically and in the location records so staff know exactly what they are counting.

Illustrative location-count plan
Open picking bins with frequent split packsEvery 7 daysFrequent handling; shorten if confirmed discrepancies recur.
Returns awaiting inspectionEvery 7 days, plus after a recorded mix-upCounting does not itself authorise release for sale.
Accessible valuable or order-critical partsEvery 14 daysSmall shortages can matter; review unexplained losses.
Sealed reserve cartons with few movementsEvery 30 daysReassess when cartons are opened or transfers increase.
Download CSV

All intervals are editorial assumptions in calendar days. Arrange coverage for due dates on closed days. This is an operational pilot, not a statement of audit or statutory requirements.

Check capacity before entering the intervals. Suppose six locations each take ten minutes to count and record: that is 60 staff-minutes for the initial pass. A proposed 30-minute allowance for recounts and investigation makes 90 staff-minutes, excluding normal picking, travel between premises and system setup. Replace these assumptions with timed observations. If the work does not fit the shift, reduce the pilot size or spread due dates instead of making everything due on a busy dispatch morning.

Verify the first scheduled date

Odoo 19.0 documents cycle counts by location. Enable Storage Locations, open Configuration → Locations and set Inventory Frequency in days. Complete the first count and apply the reviewed inventory adjustments: this establishes the next scheduled count date. Operations → Physical Inventory supports filtering or grouping by location. Check the resulting date before treating the schedule as active. This is a documented workflow example for an existing installation, not a software selection recommendation.

Odoo 19.0 official documentation: cycle counts

Keep a modest configuration budget focused on location labels, responsibilities and a repeatable test. Test one location through counting, review, posting and checking the next date on your installation. Confirm who can enter a count and who can apply a correction; do not assume those duties are automatically separated. If your current software lacks location scheduling, a shared due-date register can coordinate the work while approved corrections remain in the inventory system of record.

Recount before changing the record

Protect a short counting window for the selected location. Pause movements there where practical; if dispatch cannot stop, record every movement and its time so the count and system balance refer to the same point. Compare physical stock with on-hand quantity, not a balance reduced by order reservations, and distinguish pieces from cartons. Ideally the first counter records the quantity without seeing the expected figure. A discrepancy starts an investigation; it is not permission to overwrite the record.

Prepare a discrepancy log before the first count
Count identityLocation, product, lot or serial where used, unit, count time and counter
QuantitiesSystem on-hand snapshot, first count, intervening movements and signed difference
RecountNamed recount owner, quantity and completion time
Evidence and decisionDocument references, cause or unresolved status, reviewer and approved action
ClosurePosted adjustment reference if any, process-fix owner and next review date
Download CSV

For example, a fictional shelf shows 24 pieces in the system and 22 on the first count. A second person confirms 22 and finds a two-piece transfer awaiting posting. Reconcile the transfer and timing before considering an adjustment, otherwise both actions could reduce stock twice. If the cause remains unknown, keep that status visible and have the designated reviewer decide the correction under your internal policy. In a two-person business, the owner can review the evidence before applying an adjustment when no separate supervisor is available.

Review the workload and recurring causes

At the end of a proposed four-week pilot, review completed versus due counts, staff-minutes, confirmed discrepancies and unresolved cases by location. Keep the number of counts beside the discrepancy total so extra checking is not mistaken for worsening accuracy. Repeated errors justify investigating labels, pack sizes or late transfers as well as shortening an interval. Stable counts may support a longer interval, but a quiet month alone is weak evidence for high-consequence stock.

For the next shift, choose one problematic picking location and one quiet reserve location, name the counter and recount owner, and reserve time for the first counts. Bring the log to the review before posting corrections. If errors trace to delayed updates between warehouse and sales systems, use the related integration guide to establish record ownership. Request a narrowly scoped integration review when the logs show that configuration or data flow is the constraint.

Related guide: connecting business systems without duplicate recordsSystem integration and ERP services for a defined stock-record workflow

Before you proceed

  • Every location has a justified interval, an owner and a next due date.
  • The first count is completed and the next scheduled date is verified.
  • Movement timing and units are reconciled before discrepancies are approved.
  • A named person recounts discrepancies and a reviewer approves adjustments.
  • Pilot timings and causes will replace the illustrative assumptions.

Sources & further reading

Put this into practice