Inventory

Inventory accuracy as a real workflow, not a quarterly fire drill

Schedule counts by location, product, or flagged-for-recount. Counters scan through the work; variance review and adjustments stay on the cycle count and write to the same Inventory History the rest of the warehouse already reads.

Count queue

The same Cycle Counts table operators run from `/teams/inventory/cycle-count`

Number, name, products, locations, status, progress, discrepancies, due date, assignee, recount source — same columns Warehouse Ops works with. Variance shows on the row so dispatchers know what to push to the front of the line.

  • Filter by status, type, warehouse, or assignee
  • Sort by due date or discrepancy count
  • Click a row to start counting or review

Cycle counts

DAL-01
Active + scheduled
Number
Name
Products
Locations
Status
Progress
Discrepancies
Due Date
Assigned User
Recount Last Counter
Started At
Ended At
Created At
Notes

CC-8821

Aisle A · weekly

124 locations

In Progress
48%

3x

Quantity

Warehouse Ops

CC-8822

Hot SKUs · top 50

0 locations

Not Started
0%

Warehouse Ops

CC-8823

Recount · CC-8819 flagged items

0 locations

In Progress
64%

7x

Quantity
Lot Code

Warehouse Ops

Warehouse Ops

CC-8824

Aisle B · monthly

96 locations

Completed
100%

2x

Quantity

Warehouse Ops

CC-8825

Returns bench · ad-hoc

18 locations

Not Started
0%

Warehouse Ops

Variance review

CC-8821
LocationProductExpectedCountedAction
L-A07-04

Cybership Hoodie · L · Black

SKU-4491

2826
Recount
L-A12-04

Cybership Beanie · One Size

SKU-2210

8484
Adjust
L-A15-02

Cybership Tee · M · White

SKU-8810

4139
Pending
L-A03-11

Cybership Socks · L

SKU-5512

1518
Adjust

Count timeline

CC-8821
LH

Count scheduled · Aisle A weekly

124 locations · 412 products · due Apr 30

1 day ago

WO

Counter started · Bay 2 scanner

Warehouse Ops claimed CC-8821 · scan-driven flow

45 min ago

WO

Variance flagged · L-A07-04

SKU-4491 expected 28 · counted 26 — short by 2

12 min ago

Recount queued

L-A07-04 added to flagged-for-recount run CC-8823

10 min ago

Adjustment posted

SKU-5512 +3 at L-A03-11 · cycle count adjustment

Just now

Counting model

What cycle counting actually looks like, in Cybership

The counting workflow operators run, the variance review the supervisor uses, and the audit trail your finance team eventually pulls — same model, one source of truth.

Location, product, or recount runs

Three real run types: count by location, count by product, or pull only the items flagged from the prior count. Each one drives a different operator UX.

Scheduled cadence

Set up weekly, monthly, or merchant-specific schedules. The system creates the next run on cadence so accuracy doesn't depend on someone remembering.

Scan-driven counter UX

Counters scan into the location, scan items, type the quantity. No flipping between tabs, no re-entering location codes, no back-button surprises.

Variance review before adjust

Discrepancies surface in a review queue with the option to adjust on the spot or send the item back into a flagged-for-recount run.

Adjustments hit the same Inventory History

Cycle-count adjustments write to the same Inventory History table picks and replenishments do — actor, location, delta, reason, all on the same row.

Inventory exclusion and freeze rules

Active counts can lock affected stock, exclude items with no inventory, or run on top of live picking — the rule is on the count, not the warehouse.

Adjustments write straight into Inventory History — same actor, location, delta, and reason your operators see for picks and replenishments.

Make accuracy a workflow, not an event

Show us the inventory you can't reconcile and we'll model a cycle-count cadence that surfaces variance before it ships.

Schedule a Demo