Counting is how you find out
A discrepancy is discovered at stock-take, weeks after it happened, with no way left to trace which movement caused it.
Inventory
Every receipt, transfer, reservation and dispatch writes to the same stock record. The number you are looking at is the result of those movements, not a count someone reconciles at the end of the month.
The problem
Inventory problems are rarely about the software failing. They are about stock moving in the real world and the record hearing about it later, or not at all.
A discrepancy is discovered at stock-take, weeks after it happened, with no way left to trace which movement caused it.
The on-hand figure is visible but what is genuinely free to sell is not, because reservations are held somewhere the number does not know about.
Stock in the second warehouse is a spreadsheet someone maintains. Transfers between them are an email and a hope.
The batch a customer received is reconstructed from delivery notes when a recall or a quality query arrives.
Capabilities
From the live stock figure to the reports that explain how it got there.
One figure, and the parts it is made of.
Where the stock physically is, not just how much there is.
Which unit, from which batch, went where.
The rules that keep the figure honest.
What is sitting still and what is running out.
Workflow
Each stage writes to the same stock record. The figure changes because something moved.
One item moves through six stages: goods receipt, putaway, reservation, picking, dispatch and the resulting stock posting.
01 Goods receipt
SKU-4471
Received
02 Putaway
SKU-4471
Stored
03 Reservation
SKU-4471
Reserved
04 Pick
SKU-4471
Picked
05 Dispatch
SKU-4471
Shipped
06 Stock
SKU-4471
Posted
Use cases
A main warehouse, a branch godown and goods in transit between them, read as one availability figure or examined one at a time.
Pharma, electrical and food stock where a batch, an expiry or a serial number has to be answerable months after it left.
Reorder levels set per item and per warehouse, so purchase is triggered by the stock position rather than by someone noticing a gap.
Works with
These read and write the same Core OS records, so a handover between them passes a reference rather than a retyped copy.
Requests, purchase orders, supplier pricing and goods receipt.
Bins and locations, putaway, picking and stock counts.
Quotations, price lists and the order everything downstream reads.
Planning, picking, loading and proof of what actually left.
FAQ
Both, per item. An item can be batch-tracked, serial-tracked or neither, and whichever applies follows it through receipt, transfer, reservation and dispatch rather than being recorded separately.
Warehouses and locations are Core OS records, so stock is held per warehouse and per location within it. Availability can be read for one warehouse or across all of them, scoped by the branch a user belongs to.
Reservations. When stock is committed to an order it comes out of available, so the next person quoting sees what is genuinely free rather than what is merely present.
Yes, but as a check rather than as the source of truth. Counts and adjustments are recorded as movements with a reason and an audit trail, so a discrepancy is traceable instead of quietly absorbed.
Have a different question? Talk to us.
Bring an item whose number is always wrong. We will show what the movement history behind it would look like.