Staff raise a material request from their phone, in their own words. It goes through your approval chain, with senior approvers added for high-value requests, and approved requests become purchase orders with a suggestion of the cheapest vendor. Everyone can see where each request is waiting, and who has it.
The problem
In many companies a requisition is a paper form, an email or a message in a group chat. It waits on a desk for a signature, gets lost between departments, or is approved by someone who can’t see what is already in stock.
The person who needs the part keeps calling to ask where it is, purchasing types the request again into another system, and nobody can show who approved what when the auditors ask.
How it works
Every request follows the same recorded path, so nothing depends on someone remembering to pass it on.
The requester describes the item, adds a photo or records a voice note. Purchasing matches it to your item list, and live stock by store shows before anything is ordered.
The request follows your approval chain. The path can change with the value, site or type of purchase, so large requests go to senior approvers.
Purchasing collects quotes from vendors, who reply on their own portal page, and compares them line by line.
Approved requests become purchase orders, with a PDF ready to send to the vendor. Each request line can go on only one order.
Goods are received against the order and posted to stock, so the requester can see that the item has arrived.
What you get
Requesters describe what they need in their own language, without knowing the item code.
Stages, approvers and limits follow your authority matrix, with extra approvers for high-value requests.
Each request shows its approval timeline: who acted, when, their remarks and how long each step took.
Managers approve or reject in the mobile app with remarks, even without signal. The decision syncs when they are back online.
A rejected request goes back to the right earlier stage for correction, and keeps its history.
Vendor prices sit side by side with price history, and an AI summary of the bids is a suggestion for the buyer to decide on.
Approved orders come out as PDFs in your layout, ready to send.
Each request line can go on only one purchase order, and live stock shows before anyone orders.
Proof
Numbers from an operator in the GCC that runs its purchasing and stores on Fieldmaster.
500+
Each one traceable from the first request to the final payment.
85,000+
Every item tracked across stores, from requisition to issue.
Part of Purchase & Material Management
Purchase requisitions are part of Fieldmaster Purchase & Material Management, together with vendor quotes, purchase orders, goods receipt and stock.
Your approval chain, item list and stores are set up around how you buy today, and a typical app is live in 10 to 18 working days.
FAQ
Software that replaces paper or emailed requisition forms. Staff request what they need, the request is approved according to your rules, and approved requests become purchase orders, with a record of every step.
A requisition is an internal request to buy something, raised by the person who needs it. A purchase order is the document sent to the vendor once the request is approved and a vendor is chosen.
Yes. The approval path can change with the value, the site or the type of purchase, so high-value requests go to more senior approvers.
Yes. Approvals and rejections can be done in the mobile app, with remarks, and are queued and synced if there is no signal.
Yes. Fieldmaster can handle the requests and approvals while your ERP keeps the accounts. Lists export to Excel, and a direct link to your ERP can be built as part of your app.
