- 6
- Request states
- Partial
- Approvals supported
- At request
- Stock captured
- To delivery
- Requisitions tracked
Everything you need. Nothing you don't.
Every part belongs to a job
The request carries its work order and the asset it touches, so consumption is attributable to something.
What was on the shelf when they asked
Each line records the quantity available at request time and whether it was in stock, low, or on backorder.
Approve three of the five
Partial approval is a real state, with quantities, a note, and who decided it when.
Start from a shortlist
The platform suggests the parts that job usually needs, so nobody types into an empty box.
Issued from somewhere specific
Stock comes out of a named location, which is how multi-store sites keep honest balances.
Shortfalls do not evaporate
What cannot be issued becomes a purchase requisition linked back to the job, tracked through ordered and received.
See where the stock policy is wrong
Approval and rejection patterns across requests, rather than a feeling about it.
How it works
- 01
Requested from the job
The technician picks from the suggestions or searches the catalogue, and says why.
- 02
Checked against the shelf
Live availability lands on every line and gets classified before anyone decides.
- 03
Decided on the record
All of it, some of it, or none, with quantities, a note and a name.
- 04
Issued or ordered
Approved quantities leave a named store. The rest becomes a requisition tracked to receipt.
Connects with the rest of Arckium
Every module is designed to work together: data flows automatically, no sync required.