Warehouse Management lifecycle architecture.
Demand
A sales order or transfer lands on the warehouse
Allocate
Stock reserves against the order, bin by bin
Pick
The pick list runs the floor, scan by scan
Deliver
The delivery order generates itself from what was picked
Ship
Goods leave with a carrier & status attached to the door
Reconcile
Shipment matches back to the order & stock closes clean
How stock actually moves.
Partially, if that’s the day you’re having
Allocation moves stock into a visible allocation state; picking confirms it; every step — allocate, pick, deliver, cancel — has a line-selective variant, so partial work is first-class, not a workaround.
What’s on the truck is on the books
Two-step outward/inward transfers with a real in-transit leg, partial receipt, and damage, shortage and excess captured on arrival into their own buckets.
Sites, warehouses, racks — and wheels
A storage-location hierarchy with typed levels, location-scoped stock and lots — including mobile van locations with vehicle and capacity details for direct-store delivery.
The conveyor — partial at every step.
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Warehouse Management |
|---|---|
| Location hierarchy to rack and bin | Native |
| Vans as mobile stock locations | Native |
| Demand-driven allocation | Native |
| Picking as a stock state | Native |
| Partial picks, deliveries and invoices | Native |
| Capability | xMatix Warehouse Management |
|---|---|
| Delivery orders and documents at dispatch | Native |
| Shipment tracking with carrier and status | Native |
| Two-step transfers | Native |
| Typed damage, shortage and excess capture | Native |
| Floor cycle counting | Native |
Everything in Warehouse Management.
Location hierarchy to rack level
Every item has an exact address.
Zones, aisles, racks, bins — stock lives at a findable spot, and the picker walks straight to it.
Mobile van locations
The van is a warehouse on wheels.
Vehicles are stock locations too — what's on the truck shows on the books, all day.
Demand-driven allocation
Stock reserves itself for real demand.
Orders claim stock as they're confirmed — the second salesperson can't promise the same pallet.
Picking as a stock state
Picked stock can't be sold twice.
The moment goods are picked, the system knows — no phantom availability between floor and dock.
Selective/partial everything
Ship what's ready; the rest waits intact.
Partial picks, partial deliveries, partial invoices — real operations, handled as the normal case.
Delivery orders & documents
Paperwork that writes itself at dispatch.
Delivery orders and documents generate from the fulfilment itself — the driver leaves with everything correct.
Shipments
Every dispatch tracked to the door.
Shipments carry their contents, carrier and status — "where is it" has an answer at every step.
Two-step transfers
Transfers that can't lose stock in between.
Goods leave one branch and arrive at another as two recorded steps — the road in between is on the books.
Damage/shortage/excess capture
Discrepancies recorded the moment they're found.
Damage, shortage and excess capture at receipt or count, typed and approved — shrinkage stops being a mystery.
Floor cycle counting
Count while the floor keeps moving.
Rolling counts run without freezing operations — accuracy stays high, business doesn't stop.
Operational registers
The floor's whole day, on record.
Every movement lands in operational registers — the answer to any "what happened" is a lookup.
The questions evaluators ask.
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.
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.
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.
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.
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.
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.
