How do I see stock across multiple storerooms?
Each part record carries its own holdings. A holding is a part-and-location pair: Storeroom A, Storeroom B, Mobile Unit. Each holding has its own on-hand, reserved, and available counts, its own reorder point, and its own status.
Replenishment requests are scoped to a holding, so the order goes to the storeroom that needs it. Inter-location transfers are handled as a manual step on a work order, not as an automatic routing engine.
What happens when a part drops below the reorder point?
The holding shows a low-stock state on the part record. A person, the parts coordinator or the maintenance supervisor, raises a replenishment request against that holding.
The reorder point is a visibility marker, not a daemon. The flag prompts the action; a person takes the action; the auto-approval option bridges the work order step after the request is raised.
Can I link parts to specific assets?
The inventory page owns the asset-type library: which parts are compatible with which asset types. The assets page owns the per-asset record. The work-orders page owns the usage history.
Three pages, three jobs, one operating record. No page pretends to do all three.
How is parts cost captured per work order?
When a technician issues a part to a work order, the system writes a transaction. The transaction captures the part, the holding, the work order, the linked asset, the actor, the timestamp, the unit cost, and the total cost.
Asset-level, site-level, and period-level rollups belong in analytics. The inventory page is the source-of-truth side: parts on the work order with cost on the transaction.
Do I need a barcode scanner?
No. Every part record carries a barcode field. The lookup is a typed input that accepts manual entry or a handheld reader keystroke output.
If your team works without a reader, manual typing or paste is the supported path. Either way, the lookup is the affordance, and the matched SKU lands on the work order.
