Welcome to Inventory
AxisSynapse Inventory is the physical-goods module — every SKU, receipt, transfer, count, and shipment of every part, supply, or finished good flows through a single ledger so the on-hand quantity you see in the system matches what's actually on the shelf. Because the same ledger feeds finance (cost of goods, valuation, write-downs) and operations (replenishment, picking, fulfilment), the discipline of "every move gets a transaction" is the cost of entry — and the value the module returns.
TL;DR — Open Inventory → Dashboard to see on-hand, open receipts, exceptions, and the day's counts. Items live in Catalog; movement happens in Receipts, Transfers, Counts, and Shipments. Finance reconciles in Valuation.
What the module covers
| Field | What it does | Accepted values / default |
|---|---|---|
| Item catalog | The master record for every part, supply, or finished good. | Covered in [Items and catalog](/inventory/items-and-catalog). |
| Receiving | Inbound from suppliers — receipt, inspection, putaway. | Covered in [Receipts and putaway](/inventory/receipts-and-putaway). |
| Counts | Cycle counting + annual physical + reconciliation. | Covered in [Cycle counts and physical inventory](/inventory/cycle-counts-and-physical-inventory). |
| Transfers + shipments | Moving inventory between locations or out to customers. | Covered in [Transfers and shipments](/inventory/transfers-and-shipments). |
| Valuation | Cost layers (FIFO / LIFO / weighted-average / standard) for the financial close. | Reads through Fixed Assets month-end close in [Depreciation and month-end close](/fixed-assets/depreciation-and-month-end-close). |
The three audiences
| Field | What it does | Accepted values / default |
|---|---|---|
| Operational staff | Receive, count, pick, ship. | Mobile-first scan flows under **Inventory → Floor**. No back-office screens needed for line work. |
| Inventory admin | Maintain the catalog, configure locations, run counts, reconcile exceptions. | Full UI. The default landing for the role. |
| Finance + auditor | Read valuation, the cost-layer ledger, and exception history for the close. | Read-only with export to support journal entries + audit work papers. |
Two-tier credential model
Inventory floor work uses two credentials side-by-side:
- A workspace login (the same account the worker uses for HR and benefits) — proves identity.
- A floor PIN — short, station-bound, for fast scan flows where a full sign-in would slow the line.
The floor PIN by itself cannot edit catalog records or move money in the valuation ledger; it can only do the floor actions (scan, receive, count, transfer, ship) attributed to the already-signed-in workspace identity. The pairing is what makes floor work fast and the audit trail attributable.
Where to start
- New to the module? Items and catalog shows the master record every other surface reads from.
- About to receive an inbound? Receipts and putaway.
- Running a count? Cycle counts and physical inventory.
- Moving stock? Transfers and shipments.
How Inventory pairs with other modules
- Procurement raises the PO that becomes the receipt. See Procurement → Purchase orders.
- Fixed Assets picks up capital purchases the moment they cross the in-service threshold. See Fixed Assets → Asset lifecycle.
- HCM owns the people doing the work — including their floor-PIN provisioning under HCM → Employee lifecycle.
Common gotchas
- "On-hand doesn't match what I see on the shelf." Don't edit on-hand directly. Open a count adjustment — the difference, its cause, and your approval form the audit record finance needs to defend the valuation.
- "A unit got received twice." Open the receipt, void one. Don't try to compensate by shipping a phantom. Every void is logged with a reason.
- "Inventory moved to a different location without a transfer." Open a transfer after the fact with the actual move date — don't backdate silently. The lateness is the metric; the move itself is the data.
Related