Skip to Content
Inventory & WarehouseCycle counting

Cycle counting

Cycle counts in APEX are a mobile workflow: the counter walks the bins with a phone, scans each stock unit’s label, and keys any difference on the spot. Every count adjustment lands in the part’s movement ledger as an ADJUSTMENT entry with the reason CYCLE_COUNT — the audit trail writes itself.

Roles: Any workspace member can count. The mobile app uses the same sign-in as the console.

Counting a unit

  1. On your phone, open the APEX mobile app and tap the Cycle count tile (or the Count tab).
  2. Tap Scan stock unit and point the camera at the unit’s label. If the label won’t read, type the code into the manual entry field instead.
  3. Compare the physical count against the system quantity, and enter the difference in Qty delta (+/-) — the adjustment, not the counted total. Counted 7 where the system says 9? Enter -2. Found one extra? Enter +1.
  4. Tap Adjust. The operation is queued and synced — the confirmation reads “Count queued — syncs when online.”
  5. If the count matches, enter nothing and move on — a zero adjustment is not accepted, and no entry is needed.

Screen: The mobile Cycle count screen — a Scan stock unit camera button with a manual-entry fallback, a Stock unit field showing the scanned code, the Qty delta (+/-) number field, and the full-width Adjust button. A badge in the header shows operations waiting to sync.

What an adjustment does

  • The stock unit’s quantity changes by the delta you keyed.
  • An ADJUSTMENT entry is written to the part’s movement ledger with reason CYCLE_COUNT, the signed quantity, and who booked it.
  • The part’s on-hand quantity and on-hand value recompute immediately.

APEX refuses an adjustment that would push a unit’s quantity below zero — if the shortage is bigger than the unit, something else is wrong (a missed issue or shipment); investigate before forcing the number.

Offline and double-tap safe

The mobile app is built for warehouse reality:

  • Offline works. Counts queue on the device and sync automatically when the connection returns; the header badge shows how many operations are waiting.
  • Retries can’t double-book. Every queued operation carries a one-time key, so a lost connection mid-sync or an accidental double-tap results in exactly one adjustment.

There is no counting screen in the desktop console — counting is deliberately mobile-only, at the shelf, where the stock is. Review the results afterwards in the part’s movement ledger.

Tip: count little and often. A few bins per day keeps accuracy high without ever freezing the stockroom, and the CYCLE_COUNT entries in the ledger document the program for auditors.

See the Mobile guide for installing the app and the scanning basics, and the Warehouse quick start for the crew’s day-one workflow.

Serials, lots & scrapValuation & planning