Counting Is the Easy Part: Bin Tagging at Receipt, a Bin-Level Book, and the Variance a Physical Stock-Take Actually Owes

1.1The four error terms

Four failure modes recur every year, and they map cleanly onto distinct terms in a count's error budget.

1.2Contributions

1. Bin decomposition stated as a conservation constraint, fixing the granularity at which a count is checkable (Section 4.1).
2. The bin-level book: the book position of a part as the sum of per-bin positions maintained by every movement (Section 4.2).
3. Coverage as a set operation over tags — the requirement a count over tagged bins must meet (Section 4.3).
4. Absolute against net variance, and why a reconciled total is not evidence of an accurate record (Section 4.4).
5. An eight-dimension capability reference framework for inventory tagging systems (Section 6.3).

2.1Trueness and precision are different failures

ISO 5725 separates trueness — the closeness of a mean to a reference value — from precision, the scatter of repeated measurements. The distinction is routinely collapsed in stock-take reporting, and collapsing it is the source of the most common misreading of a variance report.

A count with poor trueness is systematically wrong in one direction: a scanner configured for the wrong pack size, a bin standard that counts crates as pieces. A count with poor precision is scattered: some locations high, some low, no pattern. The first is a configuration defect and is cheap to fix; the second is a process defect and is not.

Section 4.4 shows that net variance measures only the first and absolute variance measures both, which is why reporting one number lets a poor count pass.

2.2Control against warning at the point of error

Shingo distinguishes the control function of an error-proofing device — the next action becomes impossible — from the warning function, where the operator is told and may proceed. The distinction is decisive in a stock-take because the environment is the worst case for warnings: temporary staff, unfamiliar layout, time pressure.

It is also the right lens for the transactions of Section 3. Most of what the web release does is record rather than refuse: it keeps invoice and actual quantity, bin, location, user and time, and leaves the decision with the operator. Recording is what makes a later count attributable; refusing is what stops an error being made. Section 6 returns to where a control would earn its place.

2.3What makes an object countable

A count presupposes a set of distinguishable objects. GS1 provides the Global Trade Item Number for a trade item class and the Serial Shipping Container Code for an individual logistic unit; ISO/IEC 15459-1 covers transport units outside a GS1 scheme; the General Specifications govern symbology selection and print quality, which decide whether a tag scans at all on the first attempt.

The class-against-instance distinction is what makes bin-level counting possible. A tag identifying only the part number tells a counter what is in front of them; a tag identifying this bin tells the system which of forty identical bins has been counted, which is the fact any count over bins depends on.

The event model is EPCIS, standardised as ISO/IEC 19987, with its vocabulary in ISO/IEC 19988. A movement or a count observation is an event with a business step and a disposition like any other, which means a stock-take can integrate into a traceability record rather than sitting beside it as a spreadsheet.

3.1Receipt, decomposition and tagging

A receipt is captured against its invoice, with the part, its storage location, its standard bin quantity, its unit and its shelf life in days where one is set. Two quantities are recorded: the quantity the invoice claims and the quantity actually received. Beside them the screen shows the part's maximum and minimum level, stock in hand and remaining capacity.

The two-quantity pattern recurs throughout this library and does the same work here as elsewhere. A single received quantity records what was accepted and destroys the evidence of a supplier discrepancy; two record both, and the difference is a supplier performance fact rather than a rounding error absorbed at the dock.

The received quantity is then decomposed into bins at the standard bin quantity, and the screen shows the breakdown before the receipt is saved. Saving prints one barcode sticker per bin. Section 4.1 states the conservation constraint the decomposition must satisfy.

Each sticker carries the part number and description, the quantity in that bin, the storage location, the vendor and invoice, the date, a barcode unique to the bin with its number printed beneath, and the bin's place in the receipt — 1/5 to 5/5 on the captured example. Stickers can be reprinted from the inward history.

3.2Movements booked against the bin

Every transaction after receipt names a bin. A pick list is built from a production schedule imported from Excel, or part by part with a quantity and a line-side location, and the system previews which bin barcodes to pick in first-in-first-out order. At dispatch, scanning a picked bin marks it on its list, with a running count of bins scanned against the total.

A direct issue scans one bin, shows its bin quantity and remaining balance, and issues all or part of it to a line-side location; the outward history records the date and time, bin barcode, quantity, line-side location, mode, pick list and the user who issued it. A stock adjustment lists a part's bin barcodes, acts on one of them with a quantity in or out, and records a written reason. A bin moved to another rack is re-pointed by its barcode, and the change is kept in a changed-locations log.

3.3First-in-first-out, shelf life and the dashboard

First-in-first-out is applied where it is cheapest to apply — at pick-list creation, as a preview of which bins to take. Shelf life is carried per part in days, and a shelf-life expiry report lists bins expiring within 30 days, with barcode, inward and expiry date, days left, remaining quantity, location, vendor and invoice.

The interaction between the two rules is worth being explicit about, because they are not the same rule. First-in-first-out selects by receipt date; expiry-based selection selects by remaining life. They coincide only where every receipt of a part carries the same shelf life, which is the common case and not the general one.

Between counts, the dashboard classifies parts as OK, about to be short — stock within 20% above the minimum level — short, or excess; bands stock on hand by age into 0-30, 31-90, 91-180 and over 180 days; and ranks the parts furthest below their minimum.

4.1Bin decomposition and its conservation constraint

A receipt of quantity Q is split into bins at the part's standard bin quantity, with one residual bin holding any remainder.

For the captured receipt, 8,000 pieces at a standard bin quantity of 2,000 give n = 4 and r = 0: four bins, which is what the inward screen shows as 2000 X 4.

The decomposition's real function is granularity. A count can verify only what is independently identified, so a receipt held as one undifferentiated quantity can be verified only in total, while four tagged bins can be verified four times. This is the same argument as the traceability tier structure elsewhere in this library: resolution is decided at capture and cannot be recovered afterwards.

4.2The bin-level book

Because every movement names a bin, the book position can be held per bin, and a part's position is the sum of its bins'.

Holding the book per bin changes what a discrepancy can tell you. A part-level book can say only that a part is short; a bin-level book says which barcodes should exist, where each should be and what each should hold, so a count can point at the bin that disagrees. It also defines the tag population T that Section 4.3 needs: every bin of the part with a non-zero balance.

4.3Coverage: what a count over tagged bins must do

The two dominant errors in a manual count are both coverage errors: a container counted more than once, and a container never reached. Both are closed by treating the count as a set operation over tags rather than a walk over aisles.

Two consequences follow that procedure alone cannot deliver. Double counting becomes impossible rather than discouraged, and the missed set is known while counters are still on the floor, so flagged bins are recounted before the team leaves rather than the following week from memory.

The book must also be drawn at the count's timestamp. Because the release records every issue and dispatch against a bin with its date and time, movements across the count window can be separated from variance instead of being booked as shrinkage.

4.4The variance the reconciliation owes

Once the count closes, counted quantity is compared to book quantity per bin. How the differences are aggregated decides whether the result is evidence or reassurance.

The failure this prevents is specific and common. A store with one bin over by 400 pieces and another under by 400 has a net variance of zero and an absolute variance of 800. Reported by net alone, the count reconciles and the store concludes its records are sound; in fact it has two errors, both of which will cause a pick failure, and neither of which it now knows about.

Record accuracy — the fraction of bins whose count matched exactly — is the figure a store should manage against, because it is the probability that any given pick will find what the system promised. It is also the only one of the three that cannot be improved by compensating errors.

In the web release the correction itself is a stock adjustment booked against one bin barcode, with quantity in or out and a written reason. That is what keeps the adjustments that close a count attributable afterwards, whichever instrument produced the counts.

5.1Observed properties of the web release

What the release does not show matters as much. There is no count mode — no tag locking and no missed-bin list — no variance report, no separate two-scan putaway, and no first-in-first-out violations report. Version 1.0 of this paper described those features from the earlier desktop release; they are withdrawn here rather than carried forward, and Sections 4.3 and 4.4 present the count's side as method.

5.2Figures published for this module

The count-duration figure was the one a buyer would weigh most heavily and the one carrying least evidence: a range with no facility size, no container population and no definition of what the phase included. It described a count mode the current release does not have, so it is withdrawn rather than repeated.

5.3Modelled effort avoided

The published return model for this product is stated as stock-take and reconciliation time saved. Its assumptions are printed here so a reader can substitute their own.

Two observations. The model's window is sixty days, not the count weekend — so what it prices is the reconciliation tail rather than the count itself, which is where a bin-level book does its work. And it prices only labour: the shutdown hours of production and shipping are excluded, and in most facilities those dominate.

The 70% is an assumption of the model, not a measurement of this release. A buyer computing this properly should substitute their own share, and add the shutdown: recovered production hours are likely to exceed the entire labour saving the published model reports.

6.1The annual count is a symptom

A store that must halt for days each year to discover what it holds is telling you that its records were not trusted for the rest of the year. The count is a consequence of that distrust, not a cause of accuracy.

This reframes what a tagging system is for. Its most valuable output is not a faster count but a record good enough to measure: the record accuracy figure of Section 4.4 is what determines whether counts can eventually become sampled rather than exhaustive. A store at 99.5% record accuracy can verify a stratified sample and defend it; one at 92% cannot, and will be counting everything for as long as that holds.

Sections 4.1 and 4.2 describe what moves that figure, and both operate during the year rather than during the count. A system evaluated only on how fast it counts is being evaluated on the least important thing it does.

6.2Enforcement, recording and verification are different jobs

The release applies first-in-first-out as guidance at pick-list creation and records what was actually picked and issued. It does not report violations of the rule. That is a reasonable first step and an incomplete one.

Any enforcement that passes through human hands has a bypass. A picker facing an empty designated location and a full one behind it will take the accessible stock, and a sensible system lets them — blocking the pick would stop the line. Because every issue is recorded against a bin with its inward date, the data needed to report such exceptions already exists; a standing violations report is what would turn that necessary flexibility from an untracked leak into a measured exception with a location attached.

The same logic recommends caution with shelf life. Where receipts of a part carry different remaining lives, first-in-first-out and expiry-first selection diverge, and a store enforcing the first while an operator believes it enforces the second will issue expiring stock in strict receipt order.

6.3A capability reference framework for inventory tagging systems

The framework deliberately measures the year, not the count. A buyer who also needs the count itself run by the system should add three questions this release does not answer: does a second scan of the same bin change the count, can unscanned bins be listed before the count closes, and does the report give net variance, absolute variance and record accuracy.

6.4Generalisability

The coverage argument of Section 4.3 generalises to any exhaustive verification over an identified population: asset registers, tool cribs, library stock, calibration inventories. The absolute-against-net variance argument generalises further still, to every reconciliation where compensating errors are possible — which is most of them.

What does not generalise is any count-duration figure. Duration depends on facility size, container population, counter numbers and layout, and a store adopting another site's figure as a plan would be planning against another site's geometry.

Appendix B.1Decomposition, and what it buys

An illustrative receipt of 1,000 pieces arrives for a part whose standard bin quantity is 120.

Applying Equation (decomp): n = floor(1000 / 120) = 8, r = 1000 — 960 = 40. Nine tagged bins — eight of 120 and one of 40 — and the identity closes: 8 x 120 + 40 = 1,000.

Now consider what each arrangement permits at count time. Held as one quantity, the receipt admits exactly one verification, which passes if the total is right however the stock is distributed. Held as nine bins, it admits nine, and a bin in the wrong rack produces a variance in two places rather than none.

Appendix B.2One bin through the book

An illustrative bin is created at receipt holding 500 pieces. A direct issue takes 100 to the line: Equation (book) gives 500 — 100 = 400, the balance the issue screen then shows for that bin. Later, ten damaged pieces are written off as an adjustment out on the same barcode: 400 — 10 = 390.

At the count, the bin is expected in T with a book of 390 at its current location. If it is found with 390, it matches; if it is found with 370 in another rack, the variance of -20 and the location difference both point at one barcode, and the adjustment that closes it is booked against that barcode with its reason — rather than against a part total that four other bins also contribute to.

Appendix B.3Three numbers from one count

An illustrative count covers 2,400 bins. 2,352 match exactly. Of the remaining 48: 22 are over by an average of 31 pieces at 18 currency units each, and 26 are under by an average of 27 pieces at 19 units each.

Applying Equation (variance): the positive value variance is 22 x 31 x 18 = 12,276 and the negative is 26 x 27 x 19 = 13,338. Net variance is -1,062. Absolute variance is 12,276 + 13,338 = 25,614. Record accuracy is 2,352 / 2,400 = 98.0%.

Reported by net alone the count looks excellent: a shortfall of 1,062 on a population of 2,400 bins is well inside any materiality threshold, and the ledger reconciles. Reported honestly, the store has 48 wrong bins, an absolute error twenty-four times the net, and a two-percent probability that any given pick will not find what the system promised.