Stock takes
Overview
A stock take is more than a series of adjustments: on creation it freezes the target figure — from then on, only what is counted counts. That is precisely what makes it evidence; a count against a continuously changing target is not.
The sequence is always the same: count, review differences, post.
Core tasks
Create a stock take. New stock take requires a label and a kind; on creation the count lines are generated and the target figure is frozen.
Count blind — or not. With blind counting, the target figure stays hidden during the count and appears only after completion.
The reason is stated verbatim in the application: with the target visible, people confirm rather than count. Somebody who sees the expected number will find it — that is not an accusation but human. Counting blind is the only route to a dependable result.
Review differences. The lines with differences only filter shows what matters. A comment per line records what explains the deviation.
Post. Completion transfers the counted values into stock.
Produce the protocol. Protocol (PDF) generates the evidence — the document that makes the count provable.
Count conditions. The count list shows in the Item condition column which line is new goods and which is B-stock — the same item has its own line per condition, and the difference is booked to exactly that condition. When creating, Item conditions limits which conditions are counted; without a selection all of them are counted.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Creating a stock take
| Field | Required | Values / format | What it does |
|---|---|---|---|
Name name | yes | text, max. 120 characters | What the stock take is called. It remains on record — a name with a date saves searching later. |
Type type | no | cut-off, permanent, location-based | How counting works. Cut-off freezes a point in time, permanent counts continuously through the year, location-based takes on individual bin locations. |
Scope scope | no | warehouses, areas, locations, item conditions | What is counted. Without a restriction, everything — B-stock included: each item condition gets its own count line, and the difference is booked to exactly that condition. With conditions you count only certain conditions. |
Articles productIds | no | several articles | Limits the count to certain articles — the usual route for a permanent stock take. |
Blind count blind | no | yes/no | Set to yes the counter does not see the expected quantity. That is the whole point: whoever knows the target count unconsciously counts towards it. For a dependable stock take, blind is the right choice. |
Brand brandId | no | one of your brands | Which brand is counted for. |
Comment comment | no | text | A note on the stock take, such as occasion or peculiarities. |
The difference between counted and expected stock is written as a correction booking on completion — traceable per article, instead of silently overwriting the stock.
Settings & permissions
- Module
module.products. - Permission
products.stocktake.bookfor posting — separate from counting, so that
four-eyes working is possible.
- The frozen target figure is the reference point. Movements after creation do not change it.
- Every step appears in the audit log.
FAQ & troubleshooting
The counted values deviate substantially. That is exactly what a stock take is for. First check whether movements happened between creation and counting — the target figure is frozen, reality is not.
The target figure is not shown. Then a blind count is running. It appears after completion.
I cannot post. Then products.stocktake.book is missing.
Are individual stock adjustments enough? For day-to-day work yes, for evidence no. A stock take freezes the figure and produces a protocol; individual adjustments do neither.