How to Use Cycle Counts

In Warehance, a cycle count is a structured process for verifying inventory accuracy at specific warehouse locations. Instead of shutting down operations for a full physical inventory, cycle counts let you count targeted subsets of your warehouse on a rolling basis. Warehance handles location selection, counting workflow, discrepancy detection, recounting, variance review, inventory adjustment, team assignment, and full audit history from one unified workflow.

What Is a Cycle Count and Why Does It Matter?

A cycle count answers one question: "Does the quantity we think is in a location match what is actually there?"

Over time, inventory records drift from reality. Products get misplaced, quantities get miscounted during receiving, items are picked from the wrong bin, or shrinkage occurs. These small errors compound and eventually cause problems: orders ship short, replenishment triggers incorrectly, and customers receive the wrong items.

Cycle counting catches these errors early. Rather than halting your entire warehouse for a wall-to-wall count once a year, you count smaller groups of locations on a recurring cadence. This keeps your inventory data clean, reduces fulfillment errors, and gives your team confidence in system quantities.

Common scenarios where you would run a cycle count:

• Quarterly or monthly audits — Count all locations in a warehouse zone on a recurring schedule to maintain overall accuracy.
• Post-receiving verification — After a large inbound shipment lands in putaway locations, run a cycle count on those locations to confirm quantities match the purchase order.
• High-velocity SKU checks — Your top-selling items move constantly. Count the locations where they live more frequently than slow-moving stock.
• Discrepancy investigation — A customer reports a missing item, or a picker flags an empty bin. Create a cycle count targeting that specific location to investigate.
• Pre-peak preparation — Before a busy season (Black Friday, holiday, back-to-school), run counts across pickable locations to ensure accuracy before order volume spikes.
• New warehouse zone validation — After reorganizing a section or setting up a new warehouse area, count those locations to confirm the system reflects reality.
• Tote and putaway audits — Verify that totes and putaway staging areas have been cleared properly after batch operations.
• Empty location confirmation — Run a count filtered to empty locations to verify that locations the system thinks are empty truly have nothing in them.

Prerequisites and Permissions

Organization feature

Your organization must have the cycle_counts feature enabled. This feature is included by default on 3PL and Brand plan types. If you do not see Cycle Counts in your navigation, contact your Warehance administrator or support to enable it.

View mode

Cycle Counts are only accessible in Org View. If you are currently in Client View, you will see a restricted-access message instead of the Cycle Counts page.

User permissions

Two permissions control cycle count access:

• Manage Cycle Counts (manage_cycle_counts) — Required to create, view, count, assign, remove items, resolve reviews, and complete cycle counts. Without this permission, the Cycle Counts page is not accessible.
• View Expected Counts (view_expected_counts) — Controls whether expected quantities are visible during counting. When this permission is not granted, the user counts in Blind Count Mode (more on this below).

Tip: For most warehouse teams, grant both permissions to supervisors and managers. For associates who should count without seeing expected quantities (to prevent bias), grant only Manage Cycle Counts and withhold View Expected Counts.

Opening the Cycle Counts Page

Step 1: Navigate to Cycle Counts in the left sidebar.

Step 2: The Cycle Counts table displays all cycle counts for your organization. Each row shows:

• Name — Descriptive label you gave the count
• Status — Current state (In Progress, Completed, or Cancelled)
• Type — Locations or Products
• Warehouse — Which warehouse this count targets
• Created — When the cycle count was created
• Last Updated — When any activity last occurred

Step 3: Click any row's name to open the cycle count detail page.

Tip: The table defaults to sorting by Created descending (newest first). You can click column headers to re-sort.

Creating a Cycle Count

Step 1: Open the creation modal

Click the Create button in the top-right toolbox area of the Cycle Counts table.

Step 2: Enter basic information

• Name (required) — Give the cycle count a descriptive name. Good names include context about what you are counting and when.
  • Examples: Q1 2026 Zone A Audit, Post-Receiving Check - PO #4521, Weekly High-Velocity SKU Count, Tote Clearance Verification
• Warehouse (required) — Select the warehouse you want to count. This defaults to your primary warehouse.

Step 3: Choose the cycle count type

The creation modal has two tabs:

• Locations (available now) — The cycle count generates one item for every location that matches your filters. Each item represents a single warehouse location and includes all products currently at that location.
• Products (Coming Soon) — Product-based cycle counting will be available in a future update.

Step 4: Configure location filters (optional)

When the Locations tab is selected, you can optionally narrow which locations are included:

• Location Types — Multi-select dropdown. Choose one or more location types (e.g., Shelf, Bin, Rack, Floor). Only locations of these types will be included.
• Location Name Contains — Text field. Enter a partial name like A- to include only locations whose name contains that string. This is useful for targeting specific aisles or zones.
• Empty Locations — Toggle on to include only locations the system considers empty (zero inventory). Useful for verifying that "empty" locations are truly empty.
• Pickable — Toggle on to include only locations flagged as pickable.
• Sellable — Toggle on to include only locations flagged as sellable.
• Is Tote — Toggle on to include only tote-type locations.
• Is Putaway — Toggle on to include only putaway-type locations.

Important: If you leave all filters blank, Warehance includes every location in the selected warehouse. For large warehouses, this can generate hundreds or thousands of cycle count items.

Important: If your filter combination returns zero matching locations, creation fails. Double-check your filter choices if you see an error.

Example filter combinations:

Step 5: Submit

Click Create Cycle Count. Warehance creates the cycle count record and generates one cycle count item for every matching location. You are redirected to the cycle count detail page.

Understanding Statuses

Cycle count statuses

Cycle count item statuses

Each item (location) within a cycle count has its own status that progresses through the counting workflow:

Item flags

In addition to statuses, items can have flags:

• Skipped — The item was skipped during counting. It remains in its current status but is removed from the active counting queue until explicitly included.
• Unexpected Product — During counting, a product was scanned that was not expected at that location. This flags the item for visibility but does not block counting.

The Cycle Count Detail Page

After creating a cycle count or clicking into one from the table, you see the detail page. This is the central hub for managing the count.

Header area

• Title — The cycle count name
• Back button — Returns to the Cycle Counts table
• Start Cycle Counting button — Launches the counting flow (only visible while the cycle count is In Progress)
• Complete button — Finalizes the cycle count (only visible while In Progress)

Items table

The main area shows a table of all cycle count items (locations). Each row represents one location and can be expanded to show the products at that location.

Parent row columns (location level):

Expanded sub-row columns (product level):

Info sidebar

The right-hand sidebar shows:

• Status badge
• Name
• Type (Locations)
• Warehouse
• Completion/Cancellation information (timestamps, if applicable)
• Created By (user avatar, name, and creation timestamp)
• Timestamps (created and last updated)

Assigning Items to Team Members

Assignment lets you divide counting work across your team. When a user starts counting with Only items assigned to me, they only see items assigned to them, which prevents duplicate effort.

How to assign items

Step 1: On the cycle count detail page, select one or more location rows using the checkboxes.

Step 2: Click the Assign button in the table toolbox.

Step 3: In the modal, select a user from the dropdown.

Step 4: Click Assign.

All selected items are now assigned to that user. The Assigned To column updates to show the user's name and avatar.

When to use assignments

• Large counts across zones — Assign Zone A locations to one user, Zone B to another.
• Shift-based counting — Assign morning shift locations to morning staff, afternoon locations to afternoon staff.
• Specialized counters — Assign high-value or complex locations to more experienced team members.
• Accountability — Assignments create a clear record of who was responsible for counting each location.

Tip: You can re-assign items at any time while the cycle count is In Progress. Select items and assign them to a different user, or assign to clear an existing assignment.

Removing Items from a Cycle Count

If locations were included that should not be counted (e.g., a location is temporarily inaccessible, or you realize a filter was too broad), you can remove them.

How to remove items

Step 1: Select one or more location rows using the checkboxes.

Step 2: Click the delete/remove action.

Step 3: Confirm the removal in the modal. Note the warning: "Any counting progress on these items will be permanently lost."

Step 4: Click Remove Items.

Warning: Removal is permanent. If an item had already been counted, that count history is deleted. Only remove items you are certain should not be part of the cycle count.

Counting Workflow

Starting a count session

Step 1: On the cycle count detail page, click Start Cycle Counting.

Step 2: Choose your counting scope:

• All Items — You will be served all items that need counting, regardless of assignment.
• Only items assigned to me — You will only see items assigned to your user account.

Step 3: Click Start Counting. Warehance navigates you to the counting flow.

How the counting queue works

Warehance automatically determines which item to serve next based on:

• Status — Only items with status Not Counted or Needs Recount are queued.
• Skipped items — Skipped items are excluded from the queue by default.
• Assignment — If you chose "Only items assigned to me," only your assigned items appear.
• Priority — Items are ordered by total count attempts (ascending), so items counted fewer times are served first. This ensures fresh items are counted before recounts.

You do not need to manually navigate between items. After submitting a count or skipping, Warehance automatically loads the next item.

The counting screen

When an item loads, you see:

Instruction banner:

• In standard mode: "Start Counting — Scan items or manually adjust counts below to update the cycle count. Each scan will increment the actual count for the matching product."
• In blind count mode: "Blind Count Mode — Scan items to count them. Products will appear as you scan them. Expected quantities are hidden in this mode."

Stats bar (three cards):

• Location — The name of the location being counted (highlighted in purple)
• SKUs Counted — How many unique SKUs you have counted so far vs. total expected (e.g., "2 / 5"). In blind mode, only the counted number shows.
• Units Counted — Total units scanned/entered vs. total expected (e.g., "14 / 20"). In blind mode, only the counted number shows.

Scan indicator:

• After each successful scan, a green banner briefly shows: "Scanned: Product Name (+1)" (or the alias quantity if applicable).
• If a barcode is not recognized, a red banner shows: "Unexpected product barcode scanned. Barcode: [barcode]"

Products list:

• In standard mode: Shows all products expected at this location with their image, name, SKU, barcode, expected count, and an actual count input.
• In blind count mode: Products only appear after being scanned. Expected counts are hidden.
• Each product has an increase/decrease input control for manual adjustment.

Summary bar (sticky at bottom):

• Shows total expected count (standard mode only).
• Skip Item button.
• Confirm Count button.

Scanning barcodes

Warehance listens for barcode scanner input in real time. When you scan:

1. The scanned barcode is matched against the main barcode and all product aliases for every product at that location.
2. If a match is found, the actual count for that product increments by the alias quantity (or 1 for a main barcode).
3. A green scan indicator briefly appears showing the product name and quantity added.
4. In blind count mode, the product card appears in the list after its first scan.

Example: Location A-01-03 has Widget X (barcode 12345, expected 10) and Widget Y (barcode 67890, expected 5). You scan 12345 ten times and 67890 five times. The actual counts match expected counts. No discrepancy.

Example with aliases: Widget X has a case-pack alias barcode 12345-CASE with quantity 6. Scanning 12345-CASE once increments the count by 6.

Manual count entry

You can also type counts directly:

• Use the + and − buttons on each product's input control.
• Or click the number field and type a value.
• Counts cannot go below zero.

Tip: Combine scanning and manual entry. Scan most items, then manually adjust if you miscounted or if a barcode is damaged.

Handling discrepancies during counting

When you click Confirm Count and there is a discrepancy (actual does not match expected for any product), Warehance shows a Discrepancy Detected confirmation modal:

"There's a discrepancy between the counted and expected quantities. Do you want to save the count anyway?"

• Click Save Count to submit the count with the discrepancy.
• Click Cancel to go back and adjust your counts.

This confirmation prevents accidental submissions. You are always aware when your count does not match.

Handling unexpected products

If you scan a barcode that does not match any product expected at the current location:

Step 1: Warehance searches your entire product catalog for that barcode.

Step 2: If one product is found, Warehance shows a confirmation modal: "The scanned barcode doesn't match any products expected at this location. However, it matches the following product. Is this the correct product?" You see the product image, name, SKU, and barcode.

Step 3: If multiple products match, you see a selection list and must choose the correct one.

Step 4: Click Add to Count. The product is added to the current location's count as an "extra" product with an Unexpected badge. Its expected count is 0.

Step 5: Continue scanning. The unexpected product now appears in the products list and can be scanned or manually adjusted like any other product.

Step 6: When you submit, the item is flagged with Unexpected Product for visibility in the items table.

If no products match the scanned barcode at all, you see a red error indicator: "Unexpected product barcode scanned. Barcode: [barcode]". The barcode is not added to the count.

Example: You are counting Location B-02-01 which should have Widget A and Widget B. You scan a barcode for Widget C, which is not expected here. Warehance finds Widget C in your catalog, you confirm, and it appears in the list with an "Unexpected" badge and expected count of 0. You count 3 units of Widget C. The item is now flagged so a supervisor can investigate why Widget C ended up in that location.

Skipping items

If you cannot count an item right now (the location is blocked by a forklift, inventory is being moved, etc.), click Skip Item.

Step 1: Click Skip Item in the summary bar.

Step 2: Confirm in the modal: "Are you sure you want to skip this item? It will be removed from the queue until you explicitly include skipped items."

Step 3: Click Skip Item to confirm.

The item:

• Receives the Skipped flag.
• Its skip count increments.
• It is removed from the active counting queue.
• Its status does not change (it stays Not Counted or Needs Recount).
• A skip event is recorded in the count history.

Tip: Skipping is for temporary situations. Before completing the cycle count, consider going back and counting skipped items. You can see which items are skipped in the items table via the Skipped flag badge.

When all items are counted

When there are no more items in the queue (all are Completed, Review Required, or Skipped), Warehance shows an "All Items Counted" empty state with a green checkmark. Use the back button to return to the detail page.

How the Discrepancy and Recount Logic Works

Understanding the status progression is critical for managing cycle counts effectively.

First count

Second count (and beyond)

When an item in Needs Recount is counted again, Warehance compares the new count's discrepancies against the previous count's discrepancies product by product:

"Pattern matches" means: Every product that had a discrepancy in the previous count has the same discrepancy value in the new count, and no new discrepancies appeared.

Worked examples

Example 1: Clean count

• Location A-01 has Widget X (expected 10).
• Count 1: You count 10. No discrepancy. → Completed.

Example 2: Discrepancy resolved on recount

• Location A-02 has Widget Y (expected 20).
• Count 1: You count 18. Discrepancy of −2. → Needs Recount.
• Count 2: You count 20. No discrepancy. → Completed.
• Interpretation: The first count was likely a miscount. The recount confirmed the correct quantity.

Example 3: Consistent discrepancy triggers review

• Location A-03 has Widget Z (expected 15).
• Count 1: You count 12. Discrepancy of −3. → Needs Recount.
• Count 2: You count 12 again. Same discrepancy of −3. → Review Required.
• Interpretation: Two independent counts agree there are only 12. This is likely a real variance that needs a supervisor decision.

Example 4: Changing discrepancy stays in recount

• Location A-04 has Widget X (expected 10) and Widget Y (expected 5).
• Count 1: Widget X = 8 (−2), Widget Y = 5 (0). → Needs Recount.
• Count 2: Widget X = 9 (−1), Widget Y = 5 (0). Discrepancy changed for Widget X. → Needs Recount.
• Count 3: Widget X = 9 (−1), Widget Y = 5 (0). Discrepancy matches Count 2. → Review Required.

Example 5: Multi-product location with mixed discrepancies

• Location B-01 has Product A (expected 50), Product B (expected 30), Product C (expected 10).
• Count 1: A = 50 (0), B = 28 (−2), C = 12 (+2). → Needs Recount (discrepancies on B and C).
• Count 2: A = 50 (0), B = 28 (−2), C = 12 (+2). All discrepancies match. → Review Required.
• A supervisor can now decide: accept (adjust B down by 2 and C up by 2) or decline (keep system quantities unchanged).

Resolving Review-Required Items

When an item reaches Review Required, it means two consecutive counts produced the same discrepancy. A decision is needed.

How to resolve a review

Step 1: In the items table, find items with the Review Required status badge.

Step 2: Click the actions dropdown on that row and select Resolve Review.

Step 3: The Resolve Review modal opens showing:

• The location name.
• A table of products with their Expected, Counted, and Adjustment values.
• Adjustment column shows the inventory change that would be applied (e.g., "+2" in green, "−3" in red, "No change" in gray).

Step 4: Choose an action:

• Accept Adjustments — Warehance applies an inventory adjustment for every product with a non-zero discrepancy. The system quantity at that location is updated to match the counted quantity. The item moves to Completed.
• Decline — No inventory changes are made. The system quantities remain as they were. The item moves to Completed.

When to accept vs. decline

Tip: For high-value items or large variances, consider having a supervisor physically verify the location before accepting. Accepting is irreversible — it changes your inventory record.

Tip: Declining does not reset the item for recounting. It simply closes it out. If you want to recount after declining, you would need to create a new cycle count targeting that location.

Viewing Count History (Audit Trail)

Every count attempt and skip is recorded and viewable for audit purposes.

How to view count history

Step 1: In the items table, click the actions dropdown on any row.

Step 2: Select View All Counts.

Step 3: You are taken to the item detail page showing:

Sidebar information:

• Status badge
• Location name
• Total count attempts
• Times skipped (if any)
• Assigned To
• Created timestamp

Count history cards (main area):

Each count attempt appears as a numbered card showing:

• Count # (sequential number)
• Counted By — User avatar and name
• Counted At — Timestamp
• Is Skip — If this was a skip event, the card shows "Item was skipped — no products counted" instead of a products table

For non-skip counts, each card contains a products table:

This gives you a complete timeline of everything that happened at that location.

Example audit trail:

Completing a Cycle Count

When you are satisfied that all necessary counting and reviews are done, you can finalize the cycle count.

How to complete

Step 1: On the cycle count detail page, click Complete.

Step 2: If there are still incomplete items (Not Counted, Needs Recount, or Review Required), Warehance shows a warning: "Not all cycle count items have been completed."

Step 3: Click Complete Cycle Count to confirm.

What happens on completion

• The cycle count status changes to Completed.
• The completed_at timestamp is recorded.
• All further actions are locked: no counting, assigning, removing, skipping, or reviewing.
• The cycle count and all its data remain viewable for audit purposes.

When to complete

• All items are Completed — The ideal scenario. Every location was counted, discrepancies were resolved, and adjustments were made.
• Most items are Completed, some are skipped — Acceptable if the skipped locations are genuinely inaccessible or irrelevant. The warning ensures you are making a conscious choice.
• Some items are still Not Counted — This happens if you created a broad cycle count but only needed to count certain locations. The warning ensures you do not finalize prematurely by accident.

Tip: Before completing, filter the items table by status to review any items that are not yet Completed. Address Review Required items first, then decide if remaining Not Counted or Needs Recount items need attention.

Standard Mode vs. Blind Count Mode

Warehance supports two counting modes, controlled by the View Expected Counts permission.

Standard mode (View Expected Counts enabled)

• The counter sees expected quantities for each product.
• Stats show progress as fractions (e.g., "3 / 5 SKUs Counted", "14 / 20 Units Counted").
• The instruction banner reads: "Start Counting."
• All products at the location are visible before any scanning.
• The total expected count is shown in the summary bar.

Best for: Supervisors, experienced counters, quick verification passes, or situations where speed is more important than preventing bias.

Blind count mode (View Expected Counts not enabled)

• Expected quantities are completely hidden.
• Stats show only counted numbers (e.g., "3 SKUs Counted", "14 Units Counted") without denominators.
• The instruction banner reads: "Blind Count Mode."
• Products only appear in the list after they are scanned. Before scanning, the list shows "No products scanned yet — Scan a barcode to start counting."
• The total expected count is hidden from the summary bar.

Best for: Ensuring unbiased counts, compliance-driven audits, situations where you want the counter to report what they actually see without being influenced by what the system expects.

Tip: You can mix modes across your team. Give supervisors the View Expected Counts permission for oversight while warehouse associates count in blind mode.

Barcode Scanning Details

How scanning works

Warehance uses real-time barcode scan detection. When the counting flow is open, the system listens for rapid keyboard input (which is how USB and Bluetooth barcode scanners send data). A scan is detected when characters arrive in under 200ms intervals with a minimum length of 3 characters.

What barcodes are recognized

For each product at the current location, Warehance builds a lookup map including:

• The product's main barcode (increments count by 1)
• All product alias barcodes (increments count by the alias quantity)

Example: Product "Widget X" has:

• Main barcode: WX-001 (scan adds 1)
• Alias barcode: WX-001-CASE-12 with quantity 12 (scan adds 12)
• Alias barcode: WX-001-INNER-6 with quantity 6 (scan adds 6)

Scanning WX-001-CASE-12 once adds 12 to Widget X's count.

Scan indicator feedback

After each scan:

• Green indicator: "Scanned: Widget X (+1)" — Successful scan, product recognized.
• Red indicator: "Unexpected product barcode scanned. Barcode: [code]" — Barcode not found in product catalog at all.
• Product Not Expected modal — Barcode found in catalog but not expected at this location. You can confirm and add it.

The indicator disappears after 2 seconds (4 seconds for errors).

Tips and Best Practices

Planning your cycle counts

• Start small — If you are new to cycle counting, begin with a single zone or aisle. Learn the workflow before scaling up.
• Name meaningfully — Good names make the Cycle Counts table useful months later. Include the date, zone, or purpose: 2026-04 Zone C Monthly, Post-Receiving PO-7812.
• Use filters strategically — Rather than one massive cycle count, create focused ones. A count of 50 locations is easier to manage and complete than one with 500.
• Schedule recurring counts — Establish a cadence (weekly, biweekly, monthly) for different warehouse zones. Rotate through the warehouse so every location is counted at least once per quarter.

Assigning and delegating

• Assign before counting starts — This prevents two people from accidentally counting the same location.
• Use "assigned to me" mode — When assignments are in place, each counter should choose Only items assigned to me to keep sessions focused and avoid overlap.
• Balance workloads — Divide locations evenly based on expected complexity (locations with many SKUs take longer to count).

During counting

• Test your scanner first — Before starting a count session, scan a known barcode to verify the scanner is connected and working.
• Count physically, then confirm — Physically count all items at a location before starting to scan. This reduces back-and-forth.
• Use manual adjustment sparingly — Scanning is more accurate. Only use manual input for damaged barcodes or items without barcodes.
• Do not rush discrepancy confirmations — When the discrepancy modal appears, take a moment to verify. It is easier to recount now than to fix an incorrect submission later.
• Skip wisely — Skip is for genuine blockers (forklift in the way, active picking happening). Do not skip items just because the count is difficult.

Resolving reviews

• Two-person rule — Have someone other than the original counter resolve the review. Fresh eyes catch errors.
• Check for in-transit inventory — Before accepting a negative adjustment, verify that the "missing" inventory is not on a pick cart, in a shipping lane, or being putaway.
• Document large variances — For significant adjustments, note the reason (shrinkage, receiving error, misplacement) in your internal records.

Completing cycle counts

• Review before completing — Always check for leftover Review Required items before hitting Complete.
• Do not leave cycle counts open indefinitely — An In Progress cycle count with stale data is worse than no cycle count. Complete or cancel counts that are no longer relevant.
• Use completion timestamps — The completed_at timestamp is useful for reporting how long counts take. Use this to improve planning.

Frequently Asked Questions

General

Q: Can I edit a cycle count after creating it (change the name, add locations)? A: You cannot add new locations after creation. The name and other metadata are set at creation time. If you need to add locations, create a new cycle count with the appropriate filters.

Q: Can I delete a cycle count? A: Cycle counts are completed or cancelled, not deleted. This preserves the audit trail.

Q: How many locations can a single cycle count have? A: There is no hard limit. Warehance processes locations in batches of 500 during creation. However, for practical management, counts with fewer than 200 locations are easiest to work with.

Q: Can I run multiple cycle counts at the same time? A: Yes. You can have multiple In Progress cycle counts simultaneously, even for the same warehouse. However, be careful not to count the same location in two active cycle counts simultaneously, as this could cause conflicting adjustments.

Counting

Q: What happens if two people count the same item at the same time? A: Use assignments to prevent this. If it does happen, the second submission overwrites the first as a new count attempt.

Q: Can I go back and re-count an item that is already Completed? A: No. Once an item reaches Completed status, it cannot be recounted within the same cycle count. Create a new cycle count if you need to recount that location.

Q: What happens if I scan a barcode that matches multiple products? A: If the barcode is expected at the location, it increments the matching product. If it is an unexpected barcode that matches multiple catalog products, Warehance shows a selection modal so you can choose the correct one.

Q: Does scanning work with Bluetooth scanners? A: Yes. Warehance detects barcode input from any scanner that emits keyboard-style input (USB, Bluetooth, or wireless).

Q: Can I count from a mobile device or tablet? A: The counting flow works on any device with a browser. For scanning, you need a connected barcode scanner. Manual count entry works on any device.

Q: What does "All Items Counted" mean? A: This empty state appears in the counting flow when no more items need counting in the current queue. All items are either Completed, Review Required, or Skipped.

Discrepancies and reviews

Q: Why does a first-time discrepancy go to Needs Recount instead of Review Required? A: A single count could be a human error. Requiring a recount ensures that genuine variances are confirmed by at least two counts before triggering a review.

Q: What if the third count still shows a different discrepancy than the second? A: The item stays in Needs Recount. Warehance always compares the current count to the immediately previous count. Discrepancies must match consecutively to trigger Review Required.

Q: Does accepting a review actually change my inventory? A: Yes. Accepting applies real inventory adjustments. For each product with a discrepancy, Warehance creates an inventory adjustment with the reason "Cycle Count Adjustment." This changes the on-hand quantity at that location.

Q: What if I accept a review by mistake? A: The adjustment is applied immediately. To reverse it, you would need to manually create an opposite inventory adjustment through the Inventory section.

Q: Can I recount after declining a review? A: No. Declining marks the item as Completed. If you need to investigate further, create a new cycle count for that location.

Skipping

Q: Does skipping count as a count attempt? A: No. Skipping does not increment the count attempts number. It increments a separate skip counter and records a skip event in the history.

Q: How do I go back and count skipped items? A: Skipped items remain in the cycle count with their original status. They are excluded from the counting queue by default, but they will still show in the items table with the Skipped flag. To count them, the queue can be configured to include skipped items, or you can start a new counting session.

Q: Is there a limit to how many times an item can be skipped? A: No. Each skip increments the skip counter and adds a history record.

Permissions

Q: Can a client-mode user run cycle counts? A: No. Cycle Counts are only accessible in Org View.

Q: What can a user with Manage Cycle Counts but without View Expected Counts do? A: They can do everything — create, count, assign, review, complete — but they count in Blind Count Mode (expected quantities are hidden during counting).

Q: Can I give someone view-only access to cycle counts? A: Currently, the Manage Cycle Counts permission grants full access. There is no read-only cycle count permission.