Skip to main content
Question

ABC Codes, Cycle Counting, and Physical Inventory Locking Questions

  • June 5, 2026
  • 0 replies
  • 7 views

Forum|alt.badge.img

We are trying to develop a more systematic physical inventory process and are looking for advice on best practices within Acumatica.

We are currently using Acumatica 2025 R2 (Classic UI).

Our challenge is that we do not want to lock the entire warehouse when performing a physical inventory. Ideally, we would like to count only specific Inventory IDs or locations at a time.

I realize that Physical Inventory Types can be filtered by location, and the Prepare Physical Count process allows us to further filter by locations and inventory items when generating a count. However, with approximately 1,300 active Inventory IDs and 1,500 warehouse locations, it still feels like a very manual process to decide what should be counted and when.

From what I have seen so far, setting up and managing Physical Inventories appears to be heavily manual. Am I missing something, or does Acumatica really lack the ability to generate and manage cycle counts in a more systematic way?

This has led me to investigate ABC codes and cycle counting, but I have some questions about how others are using them:

  • If I assign hundreds of SKUs to an "A" class, does Acumatica lock all of those items when the count is generated?

  • If I assign hundreds of SKUs to an "A" class, can Acumatica subdivide that class into smaller counting groups? For example, if SKUs 1–15 are all A-class items, could I set them up so that:

    • Count Group A counts SKUs 1–5

    • Count Group B counts SKUs 6–10

    • Count Group C counts SKUs 11–15

  • Can Acumatica automatically select only a small subset of items for each cycle count rather than requiring us to count an entire ABC class at once?

  • Am I understanding the frequency correctly? If an item is assigned to a weekly cycle, does that mean it will be counted once every week?

  • When a physical inventory is active and inventory is locked/frozen, how does that affect warehouse operations? Will pickers still be able to scan and pick the affected items? Will packers still be able to confirm shipments that contain those items, or are those transactions blocked until the physical inventory is completed?

For those of you running cycle counts in larger warehouses, how are you structuring your Physical Inventory Types and cycles to avoid locking large portions of inventory while still maintaining inventory accuracy?

Any recommendations or examples of how you've configured this would be greatly appreciated.