Stock take statuses, fields & list

A stock take is a warehouse-scoped count document that reconciles what SKU.io thinks is on your shelves with what a physical count finds. Every take carries a status, a mode, a count date, a variance direction, and a set of items — one line per product. This page is the field-level lookup for all of it: the three statuses and what each allows, the variance-direction and root-cause codes, the list (filters, sorts, tabs, view modes) and detail sub-views, the CSV export, and every field on the take, its items, and its reconciliation.

For why the model works the way it does — full-count vs adjustment mode, the snapshot-vs-count-date split, and what finalizing does to your books — read the concept How stock takes work. For the tasks themselves, see Create a stock take, Count stock, Finalize a stock take, and Amend a stock take.

You manage stock takes under Inventory → Stock Takes.

Two modes decide the path

The mode is chosen when you create a take and never changes. It decides which statuses a take passes through and how each item records its variance.

Mode	On-screen label	Item records	Lifecycle
full_count	Full Count	A counted quantity per line; variance is counted minus system on-hand.	Draft → Open → Closed (a snapshot is captured at Open).
adjustment	Adjustment	A signed adjustment quantity per line; the delta is the variance.	Draft → Closed (finalized directly, no snapshot).

The status tables below call out which actions apply to which mode.

Status

A stock take has exactly one status at a time. New takes start Draft.

Value	On-screen label	Meaning	Inventory effect
draft	Draft	Editable staging. Items are added and scoped; adjustment-mode deltas are entered here.	None — no snapshot, no movements, no accounting.
open	Open	Full-count only. A system snapshot is captured and counters enter their counted quantities.	Snapshot recorded; no movements yet.
closed	Closed	Finalized. Variance is written to stock, cost, and the books.	Movements and FIFO layers created; value and accounting posted.

draft — staging, no inventory effect

Draft is the editable staging state. You add items, set the warehouse, and — in adjustment mode — enter each line's adjustment quantity. Nothing is committed: there is no snapshot, no movement ledger entry, and no accounting transaction. A draft take is freely editable and freely deletable.

Where a draft goes next depends on mode:

• Full-count draft → Open. Initiate captures the snapshot and moves the take to Open. Initiate is rejected on an adjustment-mode take with a clear message (use finalize-adjustment instead), and a take must have at least one item to initiate.
• Adjustment draft → Closed. Finalize adjustment posts the deltas and closes the take directly, skipping Open.

open — snapshot taken, counting in progress

Open exists only for full-count takes. When you initiate, SKU.io stamps the take and each of its items with a point-in-time snapshot of on-hand, available, and committed quantities. Counters then enter a counted quantity per line. Available actions while Open:

Action	What it does
Re-snapshot	Recaptures the system quantities against current stock, re-baselining the count if inventory moved since Open.
Zero out	Bulk-sets the counted quantity for every line, in one of three modes: zero all (0 everywhere), keep submitted (each line's submitted / committed-to-fulfillment quantity), or keep all allocated (each line's full allocated total — pending + submitted). Keep all allocated preserves stock that orders have already claimed rather than counting it to zero.
Revert to draft	Clears the snapshot fields and value, returning the take to Draft for re-scoping.
Finalize & reconcile	Posts the variance and closes the take. Every item must be counted first — finalize is blocked while any line is uncounted.

Movements that happen after the snapshot but before you finalize are tracked separately as during-count movements — see Detail sub-views and the reconciliation flow in Finalize a stock take.

Blind counts hide the system quantity

When a take is created with blind on, the system on-hand for an item that hasn't yet been counted is withheld, so the counter records what they physically find without anchoring to the expected number. Once a line is counted, its snapshot is revealed for variance review.

closed — finalized, inventory and accounting posted

Closing is terminal. Finalizing (full count) or finalize-adjustment (adjustment) writes the variance into FIFO layers and the movement ledger, sets the take's value change and variance direction, and posts the accounting transaction. A closed take isn't re-approved, but it supports these post-close actions:

Action	When it's available
Reverse	Undoes all inventory effects — allowed only while no FIFO layer created by the take has been consumed, and not for channel-managed (Amazon FBA/AWD/WFS) stock.
Compensating adjustment	Creates a child adjustment take to correct a closed take whose FIFO layers have already been consumed (so it can't be reversed).
Cost correction	Re-costs the closed take's lines and reposts accounting, without touching quantities.
Edit notes / re-date	Edits the notes or moves the count date. Re-dating replays FIFO consumption and COGS; preview the impact first with the reallocation preview.

Delete on a closed take reverses its inventory effects, but is blocked when any FIFO layer it created has already been drawn from. The take reports whether it's deletable and, per item, what's blocking it; the list's Deletable check gives you the same answer in bulk.

Re-dating into a locked period is refused

Moving a closed take's count date into a locked accounting period is rejected, as is a reallocation that would cross a locked period. Amend the accounting period first.

variance_direction

At finalize, SKU.io summarizes the whole take's variance into a single variance direction. It compares each item's variance — the adjustment quantity in adjustment mode, the counted quantity for an initial count, otherwise counted minus snapshot — and rolls the signs up.

Value	On-screen chip	Chip color	Set when
(null)	(no chip)	—	No item had a non-zero variance.
positive	Positive	Green	Every non-zero item was a gain.
negative	Negative	Red	Every non-zero item was a loss.
mixed	Mixed	Amber	The take had both gains and losses.

Variance direction is stored on the take, so you can filter and sort the list by it. It's empty until the take closes.

Variance root-cause codes

Each item can optionally carry a variance reason — a cycle-counting root-cause code that records why the counted quantity differs from the system on-hand, so variance can be analysed by cause rather than as one undifferentiated adjustment. It's optional: leaving it blank is fine.

Value	On-screen label	Typical use
receiving_error	Receiving Error	Stock was mis-counted or mis-booked at receipt.
picking_error	Picking Error	A pick took the wrong quantity or wrong SKU.
mislabel	Mislabel	Product was labelled as the wrong SKU.
damage	Damage	Units were damaged and pulled from sellable stock.
shrinkage	Shrinkage	Loss with no identified cause (theft, spoilage).
unknown	Unknown	Cause not determined.

The reason is chosen per line on the count table and stored on the item; it doesn't change the quantity or cost math, only the analytics.

The stock takes list

The list at Inventory → Stock Takes is server-paginated (10 per page by default) and built on the standard datatable stack — search, filters, saved views, sorts, column selector, and three view modes (table, grid card, and mobile card).

Filters

The following filters are exposed, most also as quick tabs and dropdowns above the table:

Filter	Type	Notes
Search	text	Matches take ID (exact), notes, and warehouse name.
Status	tab / select	All, Draft, Open, Closed.
Mode	select	All, Full Count, Adjustment.
Warehouse	select	Filters by warehouse.
Initial count	select	All, Yes, No.
Variance direction	select	All, Positive, Negative, Mixed.
Count date	date range	Count date between two dates.
Created / Updated	date range	Created and updated date ranges.
Value change	numeric	Filters on the take's value change.
Archived	select	Default hides archived; only shows archived, all shows both.

Sorts

Sortable columns: ID, Count Date, Status, Value Change, Variance Direction, Created, and Updated. The default sort is newest first.

Columns

The table shows ID, Status, Mode, Warehouse, Count Date, Value Change, Variance Direction, Notes, Created, and Updated. The list omits the item lines — those load only on the detail page.

Detail sub-views

Open a take to its detail page. Beneath the header, a set of tabs exposes the take's data. Which tabs appear depends on status:

Tab	Shown when	Contents
Items	Always	One row per product — SKU, snapshot, counted/adjustment quantity, unit cost, variance reason, and lot fields. Includes the Export action.
FIFO Layers	Closed	The FIFO layers the take created, with product, warehouse, and cost.
Inventory Movements	Closed	The movement ledger entries the take wrote (type Stock Take).
Reconciliation Log	When entries exist	The audit of reconciliation actions taken at finalize (see below).
Activity	Always	The activity log filtered to this take as subject.

While a take is Open, the header separately surfaces a Movements Since Snapshot count and dialog — the during-count movements that landed after the snapshot (and aren't this take's own). These feed the reconciliation preview when you finalize.

Reconciliation log actions

The Reconciliation Log records what finalize did when a count collided with in-flight orders. Each entry records one action:

Action	Meaning
adjustment_applied	The item's variance was written to stock.
count_adjusted	A line's counted quantity was changed during reconciliation (for example, to absorb during-count movement).
item_removed	A line was dropped from the take during reconciliation.
fulfillment_cancelled	An open shipment was cancelled to free stock the count removed.
fulfillment_cancel_failed	A cancellation was attempted but failed (see the entry detail).
order_deallocated	An order's allocation was released.
order_backordered	An order line was pushed to the backorder queue because the count left it short.
allocation_downgraded	A committed allocation was downgraded to planned.

Export count lines

The Export button on the Items tab downloads the take's lines as CSV (stock_take_lines.csv). The columns depend on status:

Column	Always	Notes
id	Yes	The product ID.
sku	Yes	Product SKU.
barcode	Yes	Product barcode.
name	Yes	Product name.
snapshot_inventory	Past draft only	The captured system quantity.
qty_counted	Past draft only	The counted quantity.
adjustment	Past draft only	The counted quantity minus the snapshot.
unit_cost	Past draft only	The item's unit cost (falls back to the product's).

A Draft take exports only the four identity columns — it has no snapshot yet. The same shape is the round-trip template for the import-lines upload, so an exported file can be edited and re-imported.

What a stock take records

The take itself carries:

Detail	What it holds
ID	The take's reference number.
Count date	The effective date the count applies to — this drives FIFO placement and the accounting date.
Snapshot taken	When the system snapshot was captured. Full-count takes only; adjustment takes have no snapshot.
Warehouse	The warehouse being counted. Every line and movement is scoped to it.
Mode	Full Count or Adjustment.
Condition	An optional condition label. Combined with the warehouse, it's what keeps initial counts unique.
Initial count	Marks an opening count that establishes stock from zero.
Blind	Hides the system quantity for uncounted lines while counting.
Status	Draft, Open, or Closed.
Value change	Total cost value the take moved, once finalized.
Variance direction	Positive, Negative, Mixed, or none.
Notes	Free-text notes; searchable, and editable after close.
Corrects	Links a compensating adjustment back to the take it corrects.
Created from	What created the take, when another process created it — for example an FBA inbound.
Accounting transaction	The accounting transaction the finalized take posted into.
Archived	Set when archived; archived takes are hidden from the default list.

A take also reports whether it's deletable and, if not, what's blocking deletion; how many movements happened during an open count; and a summary of its parent and child takes.

What each counted item records

One item per product on the take:

Detail	What it holds
Product	The counted product.
Counted quantity	The physical count, in full-count mode. Empty until the line is counted.
Adjustment quantity	The signed delta, in adjustment mode.
Variance	Counted quantity minus the system snapshot — the effective variance for a full count.
Unit cost	The cost basis, saved at snapshot time from the best available cost.
Realized unit cost	The actual per-unit cost realized from FIFO once the take closed. Closed takes only.
Variance reason	A root-cause code.
Bin	The counted bin, stamped onto the item's variance movements.
System on hand	On-hand captured at Open. Zero for an initial count.
Available at snapshot	Available quantity at the time of the snapshot.
Rsv (Submitted)	Units committed to fulfillment at snapshot.
Rsv (Pending)	Allocated units not yet submitted — the total allocated at snapshot minus the submitted portion. This is also what the Keep all allocated zero-out mode preserves. Zero for an initial count.
Lots	Batch number, manufacture and expiry dates, quantity, and notes, for lot-tracked products.
Lot allocation	The FIFO layers chosen to consume for a negative-variance override.

Each item also carries the product's lot settings — whether it's lot-tracked, its tracking method, shelf life, and expiry thresholds — so the count table can enforce lot entry where it's required.

"Reserved" on a count means allocated, not a stock state

SKU.io has no "reserved" inventory status — the product list column that once read "Reserved" is now On Hold. On a stock take, Rsv (Pending) and Rsv (Submitted) are allocation figures, not a status: Submitted is the portion already committed to fulfillment at snapshot, and Pending is the rest of the allocated total. For the real states — on-hand, available, allocated, on-hold, non-sellable, incoming, and in-transit — see Stock states and the stock states and fields reference. On-hand reconciles as Available + Allocated + On Hold + Non-Sellable.

What the reconciliation preview shows

When you finalize a full count, SKU.io builds a preview of the variance against current stock and any orders it touches, then reports the outcome after you execute. This is what powers the reconciliation dialog in Finalize a stock take.

Per counted item

Shown	Meaning
Snapshot and Counted	The system quantity at snapshot and what you counted.
Variance	Counted minus snapshot.
Movement during count	Net stock movement between the snapshot and finalize.
Adjusted snapshot and adjusted variance	Snapshot and variance re-based to absorb that during-count movement.
Available now, On hand now	Current stock, so you can see what the count would do to it.
Allocated now	Allocations pending, and those already submitted to a shipment.
Shortfall	How far the count falls below what open orders need.
Affected orders	The orders a negative variance would disrupt — see below.
Movements during count	The individual movements that landed while counting.

Per affected order

Shown	Meaning
Order	The sales order and its reference.
Lines	The affected order lines.
Quantity	Units in contention.
Order date and status	When the order was placed and where it stands.
Shipment and status	The shipment, if one exists, and its status.
Shipping provider	The provider, and whether the shipment was already dispatched to them.
Cancellable	Whether SKU.io can cancel it as part of reconciliation.

After you execute

The result reports whether reconciliation succeeded and the take closed, the total cost value moved, which shipments were cancelled and any that couldn't be, which lines had their counted quantity adjusted or were dropped from the take, which order lines were pushed to backorder, which allocations were downgraded from committed to planned, and the error message if finalize failed.

Next steps

• How stock takes work — the model behind these fields
• Create a stock take and Count stock
• Finalize a stock take — the reconciliation flow
• Amend a stock take — reverse, re-date, and delete
• Stock states and the stock states and fields reference
• FIFO layers & how COGS is realized and the FIFO/COGS reference
• The inventory movement ledger and the movement types & fields reference