Manage Inventory Counts

Cycle Counts verify warehouse inventory without requiring a full physical inventory shutdown. A Product Count checks products wherever they are stored, while a Location Count checks everything in selected locations. A discrepancy is the difference between the recorded and counted quantity; an accepted count creates an inventory adjustment.

Go to ShipOS → Inventory → Cycle Count (opens the Cybership dashboard in a new tab).

Create a cycle count

Click Create Cycle Count and choose:

• Product Count to count stock in pickable locations across the warehouse. Narrow it with location prefixes, location types, Only items below minimum, or Only flagged locations. 3PL teams can also choose merchant teams.
• Count by Location to count everything in specific locations, or in every location whose name starts with a prefix.
• Items Flagged for Recount to create a follow-up count from unresolved discrepancies.

A count uses the warehouse you are working in. Enter a name your counters will recognize, assign a counter, and set a due date. For Count by Location, choose Specific locations to pick locations, or Location prefixes and add a prefix such as B- to include every matching location. Click Create Cycle Count to open the new count with the stock it will count.

Perform a count

Counting happens in the Cybership mobile app. The assigned counter opens the count, visits each location, enters the physical quantity for every stock row, adds notes or location issues when needed, and saves the location. See Cycle Count on Mobile.

On the web, the count shows its progress as locations are saved. Use To Count, Counted, Discrepancies, Locations, and Notes to follow the work.

ShipOS prevents the same stock from being added to overlapping active cycle counts. Inventory movements can still happen while a count is open, so picks, transfers, receipts, or adjustments may create discrepancies that require review or recount.

Blind count

When blind count is enabled in the resolved configuration, the expected quantity is hidden while the worker counts. This reduces the chance that the system value influences the physical count.

The expected quantity becomes available where the workflow needs it for discrepancy review.

UoM quantities

Cycle Count keeps the unit-of-measure profile saved on the stock row while comparing quantities as individual base units (eaches). Count the physical container quantity shown by the workflow and confirm the profile before saving.

See Units of Measure.

Resolve discrepancies

A discrepancy appears when the counted quantity does not match the expected quantity. Open the count's Discrepancies tab to see those rows and the Notes tab to read what the counter recorded.

When a counter saves a location, Cybership adjusts stock to the counted quantity. If Recount Discrepancy is on under ShipOS → Settings → Configuration (opens the Cybership dashboard in a new tab), a row that doesn't match is flagged for recount instead, and its stock doesn't change until a recount confirms the same difference.

Before ending the count:

1. Recheck the physical stock and location.
2. Review inventory movement that occurred after counting began.
3. Read the counter's notes.

Click End Cycle Count to close the count. Ending marks the count Completed and doesn't change stock. Flagged rows stay flagged for recount. When Auto Generate Recounts is on, Cybership creates a recount for them as the count ends.

Create a recount

Use Items Flagged for Recount to create a separate follow-up cycle.

The dialog shows how many products are currently flagged for recount. Choose All flagged items or Select specific products, assign the recount, set its due date, and click Create Recount Cycle.

Assign the recount to someone other than the first counter. The recount shows who counted the item last, so the second counter can verify the result without editing the first count. When the recount finds the same difference, Cybership adjusts the stock and clears the flag. A different result keeps the item flagged for another recount.

Schedule recurring counts

Go to ShipOS → Inventory → Cycle Count → Schedules (opens the Cybership dashboard in a new tab) and create a schedule.

Schedule configuration

Choose:

• Schedule name
• Warehouse
• Optional assignee
• Timezone
• Due-in days
• Active or paused state

Schedules can run daily, weekly, every 2 weeks, monthly, or quarterly.

Generation modes

Velocity classes use recent fulfillment demand to group faster- and slower-moving products. Select one or more classes that match the counting frequency you want.

Both modes can exclude inventory already in an active cycle count. Use this to prevent recurring schedules from duplicating open work.

If a schedule creates no count, check that inventory matches its filters and is not excluded by active counts or inventory-exclusion rules.

Review Labor Hours

When Labor is enabled, open a cycle count and select Labor Hours to review the time attributed to that count.

The report shows workers currently clocked into the count, all attributed activity, total workers, total duration, status, and notes. Use Export CSV for a count-specific file. In edit mode, authorized managers can Log Hours, correct a completed entry, or delete an incorrect entry.

Cycle Count Auto Tracking can connect normal count work to the count and its Labor job. Cycle-count labor is available for operational reporting, but it does not create automatic customer charges.

See Workflow Attribution and Labor Billing for how linked work and manual corrections are handled.

Count history

Open Count History (opens the Cybership dashboard in a new tab) to review historical stock counts, including:

• Cycle count
• Product and location
• Expected and counted quantities
• Counter
• Count time
• Resulting status

Use the source cycle-count link to return to the operational record when available.

Mobile counting

The mobile workflow is designed for warehouse scanning:

1. Open the assigned cycle count.
2. Scan or select the next location.
3. Count each product stock row.
4. Add notes or skip the location with a reason.
5. Save and continue.

Skipped locations return to the queue with their reason recorded.

See Cycle Count on Mobile.

Other inventory adjustments

Use a cycle count when you need a controlled physical-verification workflow. For a known one-off correction, use Product Stock or the mobile stock-adjustment workflow instead.

• Product Stock
• Upload Inventory
• Mobile Stock Adjustments