Skip to content

Cycle counting

Count the stock in a location, and correct it when the number on the shelf doesn't match the number on the screen.

Before you begin

You need access to the Cycle Counts page — typically given to warehouse staff and inventory managers. Budget 15–30 minutes per location. Use your mobile device or a barcode scanner if you can.


Inventory Page

Cycle counting vs. physical inventory

A cycle count checks a subset of inventory on a rotating schedule, without stopping the warehouse. A physical inventory counts everything at once and needs a shutdown.

Cycle counting Physical inventory
Continuous process Once or twice a year
Counts a subset daily or weekly Counts everything at once
No business interruption Requires a shutdown
Catches problems early Corrects problems after the fact
Part of daily operations A special event

Before you start

  • Review your assigned count locations or products.
  • Make sure the counting area is organized and accessible.
  • Have your mobile device or barcode scanner ready.
  • Know what products should be in the count area.
  • Clear any active work from the count area.

Timing

Schedule cycle counts during slower periods. Avoid locations with active picks or putaways.


Receiving a count assignment

Counts are usually assigned one of three ways:

Method How it works
ABC classification (most common) Count frequency depends on the product's value class — see the count schedule below.
Location-based Count every product in a specific location, rotating systematically through all locations.
Random selection The platform picks products at random for an unbiased sample.
  1. Open the Zora Tech app.
  2. Tap Cycle Counts in the menu.
  3. Open your assigned count tasks.
  4. Tap a task to begin.
  1. Go to Inventory → Cycle Counts.
  2. Open the assigned counts queue.
  3. Click a count to start.

Preparing the count area

  1. Clear active work from the location — complete pending picks, finish putaways, and remove empty pallets or containers.
  2. Organize the products: face them forward, stack neatly, and separate different SKUs.
  3. Check the lighting, clear the pathways, and make sure you can safely reach every item.

Freeze the location

Nobody should pick from the location, put away to it, or move items in or out while you're counting. Tell nearby workers you're counting.


Counting physical inventory

Best for most situations.

  1. Scan the product barcode. The platform identifies the product.
  2. Count the physical units.
  3. Enter the count.
  4. Repeat for every product in the location.

Use when a barcode isn't available.

  1. Identify the product by its label.
  2. Enter the SKU by hand.
  3. Count the physical units.
  4. Enter the count.
  5. Repeat for every product.

Count systematically — left to right, top to bottom — and count twice if you're unsure. Open boxes and check behind items for hidden stock, verify the SKU matches the physical product, and use a scale for bulk items where you have one.

Don't rush, estimate instead of counting, miss items behind the front stock, count the wrong SKU, or count a display sample as inventory.

For each product: scan or enter the SKU, count the physical quantity, enter the count, and note anything worth flagging — damage, a wrong location, expired stock, or anything questionable.

Zero counts

If the system shows a product that isn't physically there, double-check you're in the right location, look nearby, and check whether it was recently picked. Record zero only once you've confirmed it's genuinely not there.

Serial-tracked products

If your count... Then
Matches the expected quantity Skip serial scanning — the platform assumes the serials are correct. This keeps routine counts fast.
Doesn't match Scan every serial number present. The platform compares them to what's expected and flags what's missing or unexpected.
Expected Serials: SN-001, SN-002, SN-003
Found Serials: SN-001, SN-004

Issues:
❌ SN-002 missing (expected but not found)
❌ SN-003 missing (expected but not found)
⚠️ SN-004 unexpected (found but not in system)

Missing serials. Check whether the item was recently picked, look in adjacent locations, and verify it wasn't mislabeled. Report it to your supervisor if it's genuinely missing.

Unexpected serials. Confirm the product SKU matches, check whether it belongs to a different location, and look it up in Serial number lookup.

graph TD
    A[Start Cycle Count] --> B{Serial Tracked?}
    B -->|No| C[Count Units]
    B -->|Yes| D[Count Physical Units]
    D --> E{Count Matches?}
    E -->|Yes| F[Skip Serial Scan]
    E -->|No| G[Scan All Serials]
    G --> H[System Identifies Discrepancies]
    H --> I[Resolve Issues]
    F --> J[Complete Count]
    I --> J
    C --> J

    style F fill:#e8f5e9
    style G fill:#fff3e0
    style H fill:#ffebee

Serial efficiency

Skipping the serial scan when the count already matches keeps routine counts fast — only a discrepancy needs the detailed serial check.


Handling discrepancies

After you enter your counts, the platform compares them to the system quantity:

Product: Widget A (SKU: PROD-001)
Location: A-01-A

System Quantity: 50
Your Count: 48
Variance: -2 units
Variance What happens
Within tolerance (usually ±2%) The platform may auto-accept it, or ask you to confirm. Move to the next item.
Outside tolerance You're prompted to recount.

If you need to recount:

  1. Stop and recount.
  2. Verify you're in the right location.
  3. Check the system record for recent transactions.
  4. Count more carefully — open boxes, check behind items, look for partial units, and verify the SKU.
  5. Enter the recount.

If it's still different, note the reason for the discrepancy. Your supervisor may need to verify it.


Completing the count

Before you finalize:

  • Every product is counted.
  • Discrepancies have been recounted.
  • Notes are added for anything worth flagging.
  • Damaged items are documented.
  • Nothing was missed.

Review the count summary and choose Complete Count.

The platform accepts counts within tolerance, flags large discrepancies for review, updates inventory quantities, creates adjustment transactions, records count-accuracy metrics, and assigns your next count location.


Following up

For significant variances:

  1. Review recent transactions — check whether items were recently moved, and whether picks or putaways were processed on time.
  2. Check for a process issue — a receiving error, a picking mistake, location confusion, or a data-entry problem.
  3. Take corrective action — retrain staff, improve labeling, fix the location, or update the procedure.
Issue found What to do
Damaged items Set them aside, create an adjustment to remove them, document the damage, and follow your disposal process.
Wrong location Note the correct location, transfer the items, and update the system.
Expired products Remove them from sellable inventory, create an adjustment, and follow your company's expiration policy.

See Inventory adjustments for how to make the correction.


Cycle count schedule

Class Count frequency Examples Financial impact
A — high value Monthly Electronics, high-cost materials Highest
B — medium value Quarterly Standard products Moderate
C — low value Annually Supplies, low-cost items Minimal

Typical daily targets:

Warehouse size Locations per day
Small 10–20
Medium 20–50
Large 50+

Consistency

Regular small counts beat infrequent large ones. Aim for steady daily progress.


Getting it right

Count during slow periods, with the same person recounting for consistency, using a scale for bulk items and good lighting. Organize the area before you start.

Improve the process by tracking accuracy per counter, analyzing variance patterns, reviewing high-variance items, and documenting what you find.

Pattern What it might mean
Frequent variances overall Theft, shrinkage, or a process problem in receiving or picking
One location keeps varying A location-management or labeling issue
One product is always wrong A receiving process problem
A product is damaged often A storage issue

Reporting

  1. Go to Reports → Inventory.
  2. Select Cycle Count Report.
  3. Review count accuracy by user, variance trends, coverage completion, and problem products or locations.
Metric Target How it's measured
Count accuracy 98%+ first-count accuracy Correct counts ÷ total counts × 100
Cycle count coverage Every location counted on schedule A items monthly, B quarterly, C annually
Variance rate — Dollar value of variances, tracked over time
Time per count — Tracked to spot training needs

Troubleshooting

Problem What to check
Product not in the location It may already be picked for an order, moved to a different location, still mid-receiving, or a data-entry error. Look nearby, verify with your supervisor, and record zero only once you've confirmed it's genuinely not there.
Can't scan the barcode Clean the barcode, switch to camera mode, or enter the SKU by hand. Report a damaged barcode.
System shows a different location Confirm you're in the right location and check whether the item was moved — a product can exist in more than one location. Report it if it's genuinely misplaced.
Recount still shows a variance Have someone else recount it, check for partial units, and review recent transactions. Get a supervisor to verify, or accept the count if it holds up.

Counting from your phone

  • Count without going back to a desk.
  • Scan barcodes with your device's camera.
  • Updates sync to the system immediately.
  • The number pad is sized for touch entry.
  • Keep counting without WiFi — results sync once you're back online.

  • Open your count assignment.

  • Go to the location.
  • Scan the location to confirm it.
  • Scan each product.
  • Enter the count on the number pad.
  • Submit when you're done.

Need more help? Email support@zoratech.io, or check the FAQ and troubleshooting guide.