Cycle Counting in Odoo 19:
Perpetual Inventory Audits Without Shutting Down

Cycle Count Scheduling Strategies: ABC Analysis, Random, and Location-Based

The scheduling strategy determines which items get counted and when. Choose the wrong strategy and you'll either over-count low-value items or miss high-risk discrepancies entirely. Here are the three proven approaches.

ABC Analysis (Value-Based Frequency)

ABC analysis classifies products by their inventory value contribution. The principle: count high-value items more frequently because discrepancies in those items have a larger financial impact.

In Odoo, you implement ABC classification using product categories or a custom field on product.template. Create three categories (ABC-A, ABC-B, ABC-C) and assign products based on their value contribution. Then schedule inventory adjustments filtered by category.

from odoo import api, models


class ProductTemplate(models.Model):
    _inherit = "product.template"

    def _cron_update_abc_classification(self):
        """Recalculate ABC class based on last 12 months of sales."""
        products = self.search([("type", "=", "product")])
        # Sum delivered qty * cost for each product
        ranked = []
        for p in products:
            moves = self.env["stock.move"].search([
                ("product_id.product_tmpl_id", "=", p.id),
                ("state", "=", "done"),
                ("picking_code", "=", "outgoing"),
                ("date", ">=", fields.Date.today() - relativedelta(months=12)),
            ])
            total_value = sum(m.quantity * m.product_id.standard_price for m in moves)
            ranked.append((p, total_value))
        ranked.sort(key=lambda x: x[1], reverse=True)

        cumulative = 0
        grand_total = sum(v for _, v in ranked) or 1
        abc_a = self.env.ref("my_module.product_categ_abc_a")
        abc_b = self.env.ref("my_module.product_categ_abc_b")
        abc_c = self.env.ref("my_module.product_categ_abc_c")

        for product, value in ranked:
            cumulative += value
            pct = cumulative / grand_total
            if pct <= 0.80:
                product.categ_id = abc_a
            elif pct <= 0.95:
                product.categ_id = abc_b
            else:
                product.categ_id = abc_c

Random Sampling

Random sampling selects a fixed number of products each count period regardless of value. This approach is simpler to implement and removes bias, but it doesn't prioritize high-value or high-risk items. Best for warehouses where all items have roughly similar values or where regulatory requirements mandate unbiased sampling.

import random
from odoo import models


class StockQuant(models.Model):
    _inherit = "stock.quant"

    def _cron_random_cycle_count(self):
        """Select 50 random quants for today's cycle count."""
        quants = self.search([
            ("location_id.usage", "=", "internal"),
            ("quantity", ">", 0),
        ])
        sample_size = min(50, len(quants))
        selected = random.sample(quants.ids, sample_size)
        selected_quants = self.browse(selected)

        # Set inventory_quantity_set to trigger count
        for quant in selected_quants:
            quant.inventory_quantity_set = True

Location-Based (Zone Counting)

Location-based counting rotates through warehouse zones on a fixed schedule. Monday you count Zone A (receiving area), Tuesday you count Zone B (fast-pick shelves), Wednesday you count Zone C (bulk storage), and so on. This approach works well for large warehouses with distinct zones because it keeps the counting team moving through a logical path without backtracking.

In Odoo, implement this by filtering inventory adjustments by location_id. Create child locations under your main warehouse that represent physical zones, then schedule counts per zone.

Barcode-Assisted Cycle Counting: Speed and Accuracy on the Warehouse Floor

Manual data entry is the number one source of counting errors. A warehouse associate typing "47" instead of "74" creates a phantom discrepancy that triggers an investigation, wastes supervisor time, and ultimately gets written off as a counting mistake. Barcode scanning eliminates keystroke errors and cuts counting time by 60-70%.

Setting Up Barcode Scanning for Inventory Adjustments

Odoo 19's Barcode module integrates directly with inventory adjustments. Here's the configuration checklist:

• Enable the Barcode module — Install stock_barcode from the Apps menu. This adds the barcode scanning interface to inventory operations.
• Assign barcodes to products — Every product that will be cycle-counted needs a barcode on the product.product record. Use EAN-13, UPC-A, or internal barcodes—Odoo supports all three.
• Assign barcodes to locations — Print barcode labels for each warehouse location. When the counter scans a location barcode, Odoo filters the adjustment to that location only.
• Configure the scanning hardware — USB barcode scanners work out of the box (they emulate keyboard input). For mobile devices, use Odoo's mobile app or a Bluetooth scanner paired to a tablet.

The Barcode Counting Workflow

1. Open Inventory > Operations > Physical Inventory
2. Scan the LOCATION barcode  →  Odoo filters to that zone
3. Scan a PRODUCT barcode      →  Odoo finds the quant, sets counted qty to 1
4. Scan the SAME product again →  Increments counted qty by 1
5. (Or manually enter qty for bulk items)
6. Repeat steps 3-5 for all products in the location
7. Tap "Apply All" to confirm the count

Odoo automatically:
  - Compares counted qty vs on-hand qty
  - Highlights discrepancies in red
  - Creates stock moves for adjustments
  - Posts journal entries if perpetual valuation is enabled

Accounting Impact: How Cycle Count Adjustments Flow to the General Ledger

Every inventory adjustment in Odoo creates stock moves. When your inventory valuation is set to Automated (perpetual), those stock moves generate journal entries. Understanding this accounting flow is critical because cycle count adjustments directly impact your balance sheet and income statement.

The Journal Entry Flow

# Account configuration path in Odoo 19:
# Inventory > Configuration > Product Categories > [Category]

# Account Properties tab:
#   - Stock Valuation Account:   1400 - Inventory (Asset)
#   - Stock Input Account:       1401 - Stock Interim (Received)
#   - Stock Output Account:      1402 - Stock Interim (Delivered)

# The adjustment account is set at:
# Inventory > Configuration > Settings > Inventory Valuation
#   - Inventory Adjustment Account: 5100 - Inventory Adjustments (Expense)

# When a cycle count adjusts -6 units of a product
# costing $25.00/unit, Odoo generates:
#
#   Debit:  5100 Inventory Adjustments    $150.00
#   Credit: 1400 Inventory Asset          $150.00

Valuation Method Considerations

The valuation method on your product category determines how the cost per unit is calculated for the journal entry:

• Standard Price — uses the fixed cost on the product. Simple and predictable. Adjustments always use the same unit cost regardless of when the item was received.
• Average Cost (AVCO) — uses the current weighted average cost. A negative adjustment reduces both quantity and total value proportionally. Watch for edge cases where adjusting down to zero resets the average cost.
• FIFO — uses the cost of the oldest layer. Negative adjustments consume the oldest cost layers first. This can create unexpected cost differences if old layers have significantly different costs than recent purchases.