39% measured completeness ·
40 scored features · measured at 3bfe3b23
on 2026-07-28. The percentage is recomputed from the scorecard, not stored here.
What it is
Stock Counts is how a store checks its recorded stock against what is actually on the shelf. Someone opens a count for one location, enters what they physically counted, and finalizes it; finalizing compares each count against the figure recorded when the count began and, wherever the two disagree, corrects the stock and records why. Where an adjustment is a correction someone decided to make, a count is the discovery that the figures had drifted.
What it does today
Open a count (scoped to a location)
Capture counted quantity per item
Snapshot expected on-hand
Automatic variance calculation
Post the count to stock + ledger
Variance becomes a posted correction
Document numbering
View count detail with variance
Role gating
What it does not do yet
List / filter / sort / search counts partly
Status lifecycle partly
Revise the count while open
Server-side count-scope generator
Full-count mode
Print / export a count sheet
Import counted quantities from a file
Barcode-scan capture
Valued variance (shrinkage in money)
Reason coding on the variance
Who counted / who closed
Recount / second pass
Concurrent-movement handling
Last-counted tracking per item
Multi-counter / team counting
Variance-only review
Count audit trail partly
Blind count
Scheduled / recurring cycle counts
ABC-class / risk-driven selection
Variance approval / tolerance threshold
Freeze transactions during a count
GL / journal posting of the write-off
Bin / shelf granularity
Serial / lot / expiry-aware counting
Merge multiple counts
Configurable sheet layout + count reports
Count-progress tracking
Reverse / unpost a finalized count
Offline count capture on the terminal
Count in a different unit of measure
A missing item means another system has it and QIIUB does not yet — not a commitment to build it. The scorecard calls this a comparison map, not a backlog.
Where it stops
Stock Counts owns the count document, the snapshot of what stock was expected, the difference that falls out of it, and — decisively — the act of turning a counted difference into a posted correction. It does not own the correction document it raises, the shared list of reasons it records against, the stock figures it changes, or the reporting built on top of the result.
Can a store use this today?
not operable
The registry claims no merchant-portal path for this module — whatever it does is reachable only through the API.
The registry also annotates it surface: backend-only, which agrees.
The clean operable state is owner-declared only — no measurement can produce it, and this module has no such declaration.
Plain-language wording approved by mgandia on
2026-08-14, drafted from the measurement at
3bfe3b23.
Going deeper
Feature detail — not publishedThis module has no feature-detail page yet;
15 known gaps are listed in its scorecard below.