A great deal of what gets stored is not counted. A roll of fabric, a length of steel, a crate of produce and a carcass are all bought in one unit, held in another and sold in a third, and their weight can change between receipt and sale. A stock movement in Sudo carries the quantity and the weight together, not one of them with a correction later.
InventoryAccountingUnits of measureImportsDocumentsBackground jobs
What it stands on
Inventory does not run without these modules. The ones that always run are in every instance, and no plan that includes Inventory is accepted without the subscribable ones among them.
AccountingAlways on
Units of measureAlways on
ImportsAlways on
DocumentsAlways on
Background jobsAlways on
From the real module registry: what each module needs in order to run.
Weight and quantity travel together
Three tracking modes for an item: by quantity, by weight, or by variable weight
Moving weighted average cost to six decimal places: a receipt recalculates the average, an issue does not
Lots with production and expiry dates, a source and a tag reference, with quarantine and release
Issue first-expiry-first-out (FEFO) with a separate movement per lot, so a recall can name them
Multiple storage locations per branch, and trucks that carry stock
Full, cycle and spot counts on a document cycle: open, freeze, blind count, review, approve, post
Stock ageing, replenishment suggestions, and reorder levels per item and per location
A traceability record: received, produced, transferred, sold, written off, disassembled
How far this reaches today
No serial-number tracking
Locations are flat — no zones, no shelves, no capacities and no put-away routing
No barcode scanning and no handheld warehouse app
Transfers between branches have no in-transit state — stock leaves and arrives in one operation
Stock reservation is designed and nothing calls it yet: confirming a customer order checks availability and does not reserve