Loading
Loading
Parts · purchasing · throughput
LiveAuthorised work without parts is fake progress. Reserve on approve, raise POs, and receive goods so stage AWAITING_PARTS means something operationally true.
Primary persona: Parts / advisor / manager
The problem
Stock lived in a separate spreadsheet; approved jobs still stall; techs cannibalise other jobs’ parts.
Why it matters
Reserve-on-approve protects committed stock for authorised lines.
Low-stock signals prevent surprise stockouts mid-job.
PO + receive closes the loop from supplier to bay.
Consume-on-invoice keeps inventory and COGS honest (money path alignment).
Proof from the live demo
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.

Stage sequence
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
Action
SKU list with qty, costs, and low-stock thresholds.
Why this stage
You cannot reserve what you cannot identify.
Action
When estimate part lines are approved, reserve available qty against the RO.
Why this stage
Stops double-selling the same filter to two jobs.
Action
Create purchase order, send to supplier process, track open POs.
Why this stage
AWAITING_PARTS should drive purchasing action, not hope.
Action
Goods receive updates qty; job can leave AWAITING_PARTS → IN_PROGRESS.
Why this stage
Throughput returns when the board stage matches physical reality.
Related search intent