Where a request comes from
Two paths, same form underneath:
An ad hoc request carries no reorder reasoning, so it asks for one — what it is for, and why now.
Request states
Approved does not mean bought. It means somebody with authority agreed the spend may be pursued.
The buying decision — which vendor, at what price — is what the RFQ and purchase order record next.
The approval chain
Every request routes through an approval chain — see Approvals for how chains are configured. Chains are set per organisation, typically by amount, category or site, so a request for a filter and a request for a compressor need not travel the same path. The request’s detail view shows the chain itself, not just the current step:- Every approver in order, and whether their step is pending, approved or rejected.
- Who actually signed off, and when — not just who was assigned to.
- Any comment an approver left, particularly on a rejection or a return for information.
Columns
Raising a request
New on this screen, or + Create → Purchase request from anywhere. The minimum is what is wanted, a quantity, and why. Reorder-sourced requests arrive with the part, quantity and reasoning already filled in.Reorder recommendations
What is running low, and why the system thinks so.
Requests for quotation
What happens once a request is approved.