A ledger, not a spreadsheet.
An inventory ledger you can’t fudge
Append-only and immutable: corrections post reversals, never edits. Every movement, auditable forever. A negative-stock guard on every bucket, including in-transit.
Numbers your auditor accepts — in three books
FIFO, LIFO, weighted average, moving average or specific identification — per book: statutory, tax and management, with accounting-standard guardrails and lower-of-cost-and-NRV write-downs.
DCs, stores, vans — and the truck between them
Two-step transfers hold real in-transit stock both legs must reconcile; vans are mobile storage locations on the same ledger.
A ledger you can’t fudge — feeding three books at once.
The slow movers have nowhere to hide.
Seeded reports cover overstock items, stock reaching minimum level, stock ageing with a dead-stock bucket, and an FSN × ABC × branch movement-analysis pivot. The Inventory dashboard carries the same signals — ageing buckets, FSN and ABC breakdowns, stock-out and fast-moving flags — and Sense turns idle stock into nudges with the evidence attached.
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Inventory |
|---|---|
| Immutable stock ledger — corrections are new entries | Native |
| Accounting posting rules set by finance | Configurable |
| Five valuation methods across three books | Native |
| Batch, serial and expiry tracking | Native |
| Multi-location stock, including in-transit | Native |
| Cycle counting without a floor freeze | Native |
| Typed, approved adjustments | Native |
| Reorder policies with ABC/FSN analysis | Native |
| Period balance snapshots | Native |
| Barcode scanning on receipt, pick and count | Native |
| Stock ageing analysis | Native |
| FSN and ABC classification | Configurable |
| Overstock and slow-mover reporting | Native |
| Idle-stock and stocking nudges | Integrated — Sense |
Everything in Inventory.
The questions evaluators ask.
Is stock shared across sales, service and warehouse, or copied?
Shared — there is one stock ledger on one data model. The order that allocates stock, the service job that picks a part and the warehouse count that adjusts a bin all move the same record, so there is no sync job to run and no morning where two systems disagree about what is on the shelf. The ledger itself is immutable: corrections are new entries, never edits, so every figure carries its own history.
Does it support multiple warehouses and locations?
Yes — stock tracks across every location, down to zone, aisle, rack and bin, so each item has an exact, findable address. Vehicles count too: vans are stock locations in their own right, and what is on the truck shows on the books all day. Goods in transit between branches stay visible as well — nothing goes dark mid-transfer.
How are transfers and adjustments controlled?
Deliberately. Transfers move as two recorded steps — goods leave one branch and arrive at another — so the road in between is on the books and stock cannot be lost in the middle. Adjustments are typed: damage, shortage or excess, each carrying its reason and its approval. Because the ledger is immutable and no location may go negative, the audit trail explains itself.
Does procurement run a three-way match?
Yes — the bill, the purchase order and the goods receipt must agree before payment goes out, so the classic overbilling simply cannot clear. Receiving itself is checked: goods arrive against the order with quality inspection built in, and rejects turn around at the gate rather than after payment. The received-not-billed gap clears systematically instead of being chased at month-end. Explore xMatix Procurement.
Does warehouse support pick, pack and dispatch?
Yes — picking is a stock state, so the moment goods are picked the system knows, and there is no phantom availability between floor and dock. Partial picks, partial deliveries and partial invoices are the normal case. Delivery orders and documents generate from the fulfilment itself, and shipments carry their contents, carrier and status to the door. Explore xMatix Warehouse Management.
Are serial and batch numbers tracked?
Yes — batch, serial and expiry lots are native. Every unit knows where it came from and when it expires, which turns a recall from a crisis into a query. Barcode scanning covers receipt, pick and count, so the tracking survives contact with a busy floor: fewer keystrokes, fewer wrong SKUs, and a trace you can actually rely on.
Can it show what is not moving?
Yes — stock ageing ships with a dead-stock bucket, and the seeded reports include Overstock Items and an FSN × ABC × branch movement analysis, so slow and non-moving stock is visible per branch, not just in total. The Inventory dashboard carries the same ageing buckets, class breakdowns and movement flags. FSN and ABC classes are maintained as item attributes, which keeps the classification under your control and makes every report’s grouping explainable.
How does it help decide what to stop stocking?
The reports make the case — ageing with a dead-stock bucket, overstock, and movement analysis by class and branch — and the nudge layer brings it to the person who can act: idle-stock findings arrive with structured evidence and a suggested action, applied under the user’s own permissions and written to the audit trail. What it deliberately does not do is per-SKU capital allocation — the decision stays with you, with the arithmetic in view.
