Skip to content
ITEMRA
Documentation menu

The movement ledger

Every stock change as an auditable movement: reading the ledger, movement detail, reversing, correcting, and bulk entry.

One ledger for everything

Every stock change in Itemra — receive, move, adjust, transfer, pick, count correction, build, quarantine — is a movement: who, what, how many, from where, to where, when, and why. Movements (Operate group) is that ledger, filterable by kind, item, location, person, and period.

Mixed movement kinds in time order — the source of truth.

The same ledger appears sliced per item (the item's Movements tab), per location, per container, and per vehicle. When a number looks wrong anywhere in Itemra, the ledger is where the explanation lives.

Movement detail

Clicking a movement opens its detail: quantities and units, source and destination records, the actor, reason code, notes, references (a PO, a count, a transfer), and links to everything involved.

Every movement links to its context.

Reverse and correct

Mistakes stay in the ledger — they get compensated, not erased:

  • Reverse creates the exact opposite movement, linked to the original. Plain moves and adjustments are reversible; movements with side effects (receipts against POs, count corrections) are corrected at their source instead.
  • Correct fixes the quantity of a movement with a correction entry — used when the movement was right but the number wasn't.

Both require their own permissions and a reason, and both keep the audit trail intact: anyone reading the ledger later sees what happened and how it was fixed.

Bulk entry

Movements → Bulk enters many lines of the same kind — move, adjust up, adjust down — in one screen, with per-line validation before anything is committed. Pick sources and destinations by searching, or paste rows from a spreadsheet using the identifiers you already have — SKUs, barcodes, location codes — and Itemra resolves each row to the matching item, stock, and place before you commit, flagging anything it can't match. Use it for shelf reorganizations and cleanup sessions; for recurring large corrections, prefer a count, which documents the variance properly.

Validate all lines, then commit once.