Inventory

Inventory operators trust because every change is on the record

On-hand, committed, available, inbound — per location, per warehouse, per SKU. The same model the picker, seller, buyer, and counter all read from, with a real audit trail that lives next to the record it describes.

Inventory History

Every change to inventory is on the same row

The same Inventory History table operators read from `/teams/inventory` — picks, replenishments, cycle-count adjustments, transfers, manual edits, and PO receives. Actor, location, product, delta, reason, and reference entity all on the row.

  • Filter by location, product, warehouse
  • Color-coded delta for + / -
  • Click reference to jump to PO / FO / RMA

Inventory History

DAL-01
SKU-4491
DateProductLocationTypeDeltaActorDescription

Cybership Hoodie · L · Black

SKU SKU-4491

L-A12-04
Pick
-3Lauren H.
Picked for FO-11929 - Single Item Batch · 4 lines

Cybership Hoodie · L · Black

SKU SKU-4491

L-BULK-08
Replenishment
+24System
Replenishment from bulk to pick face

Cybership Hoodie · L · Black

SKU SKU-4491

L-A12-04
Cycle Count Adjustment
-1Warehouse Ops
Cycle count recount

Cybership Hoodie · L · Black

SKU SKU-4491

RECEIVING
Manual Create
+96Warehouse Ops
PO PO-3398 received

Cybership Hoodie · L · Black

SKU SKU-4491

L-A12-04
Transfer
-6Api Key
Transfer to ATL-02 - Tote T-104

Inventory model

The model is the source of truth

No reconciliation between systems. The picker, the seller, the buyer, the counter, and the auditor all read and write to the same Inventory model.

On-hand · committed · available · inbound

Four real stages of inventory state per location, per warehouse, per SKU. The same model the picker, the seller, and the buyer all read from.

Location-aware everywhere

Every transaction (pick, transfer, adjust, receive) writes against a real location row — so SKU 4491 at L-A12-04 isn't the same record as SKU 4491 at L-BULK-08.

Inventory History is the audit

No separate adjustments log. Every change writes to the same Inventory History the warehouse already reads, with actor, type, delta, and reason.

Cycle counts close the loop

Counts can adjust on the spot or feed flagged-for-recount runs — both flow through the same Inventory History, no shadow ledger.

Inbound (POs) hits the same model

Receiving posts directly into Inventory History at the receiving location — no separate warehouse vs procurement ledger to reconcile.

Trace any unit back to the order

Lot, expiration, serial, and reference entity (FO, PO, RMA, Tote, ReplenishmentTask) on every row makes any forensic question answerable.

See your real inventory questions answered on the record

Bring the SKU you can never reconcile — we'll show you how Cybership's Inventory History puts the answer next to the record.

Schedule a Demo