Automating Purchase Requests and Purchase Orders for Distributors
In many distribution businesses a purchase request travels by WhatsApp, paper and email before it becomes an order. Automating it well makes buying faster and leaves a record of every approval.

How long does it take your company to turn “we need more of this” into a purchase order the supplier has received? In many distribution businesses the honest answer is somewhere between two days and two weeks, and nobody can say exactly where the time goes. The request starts as a message, becomes a printed form, waits for a signature, gets retyped into the ERP (enterprise resource planning) system and is finally emailed to the supplier, often after the stock has already run out.
What the manual version really costs
The obvious cost is time. The less obvious costs are the ones that show up elsewhere: emergency orders at worse prices, split shipments because the order was placed late, and stock that arrives after the customer has bought from someone else. There is also a control cost. When approvals happen in a chat group, there is no reliable record of who approved what, at what price, or against which budget.
Picture a consumer goods distributor in Zarqa with three warehouses and a buying team of four. Branch supervisors send requests by WhatsApp. A buyer collects them, checks stock in the ERP, prepares a request form in Excel and walks it to the operations manager for signature. Orders above a certain value also need the finance manager, who is often out of the office. Once signed, the buyer types the order into the ERP and emails a PDF to the supplier.
Each step makes sense on its own. Together they produce delays, lost requests and orders nobody can trace six months later when the supplier disputes a price.
Fix the process before you automate it
Automating that flow as it stands would only make the confusion faster. Before building anything, settle four questions with the people involved.
- Request rights. Branch supervisors may request stock items for their warehouse. Only buyers may request new items or new suppliers.
- Required information. Item code, quantity, required date, warehouse and reason. A request without an item code goes back to the requester rather than being guessed at.
- Approval levels. Write thresholds down. Vague rules such as “big orders go to finance” produce arguments and bypasses.
- Cover for absent approvers. Name a delegate for each approver, and decide how long a request can wait before it escalates.
A practical approval structure
Thresholds should reflect your own risk and volume. The table below is an example structure, not a recommendation for your specific figures.
| Order value in Jordanian dinars (example) | Condition | Approval |
|---|---|---|
| Up to 2,000 | Existing item, existing supplier, price within agreed list | Approved automatically; buyer places the order |
| 2,000 to 15,000 | Existing item and supplier | Operations manager |
| Above 15,000 | Any | Operations manager, then finance manager |
| Any value | New supplier or price above the last purchase by a set margin | Finance manager review added |
The important feature is that most routine orders (repeat items from known suppliers at known prices) should not need a senior signature at all. Senior attention is reserved for the orders that carry real risk.
What the automated flow looks like
Once the rules are agreed, the flow can run inside most modern ERPs, including Odoo, SAP Business One and Microsoft Dynamics, which support purchase approval rules either as standard or through configuration and add-ons. The detail varies by product and edition, so check it against your own thresholds. Where the ERP cannot do it well, a workflow tool such as Power Automate or n8n can sit alongside it. A typical sequence:
- Request. The supervisor submits a request through a short form or the ERP’s own request screen. Item codes come from a drop-down list, so nothing is misspelled.
- Automatic checks. The system shows current stock, open orders and the last purchase price for the item, and flags if a similar request is already open.
- Routing. Based on value and conditions, the request goes to the right approver, who receives a notification and can approve from a phone.
- Escalation. If nothing happens within an agreed time, say 24 hours, the request goes to the delegate and the requester is told.
- Conversion. On approval, the request becomes a purchase order in the ERP without retyping, grouped by supplier where possible.
- Sending. The order is emailed to the supplier from the system, and the sent copy is attached to the record.
- Follow-up. If the supplier has not confirmed within a set period, the buyer gets a reminder.
Each step leaves a time-stamped record. When finance asks who approved an order at a particular price, the answer takes seconds.
Two refinements are worth adding once the basic flow is stable. For items bought every week from the same supplier, a standing agreement with fixed prices (often called a blanket or framework agreement) lets the system raise orders against it without fresh approval, up to a monthly ceiling. And for branch staff who work mostly from their phones, make sure the request form works well on a basic mobile browser. A form that only works on a desktop will quietly push people back to WhatsApp.
Measure it once it runs
Pick three or four measures before go-live so you can see whether the change worked: average time from request to sent order, share of orders approved automatically, number of escalations and number of emergency orders. Review them monthly for the first quarter. If escalations are high, an approver is overloaded or a threshold is wrong. If emergency orders do not fall, the problem may be upstream in reorder planning rather than in approvals.
Faster buying with control intact
Purchase order automation works best when it removes waiting and retyping and leaves a clear record of who approved what. The rules come first, the system second. That order of work reflects the KEMLAT Method, which saves the Automate stage for processes that have been understood and simplified.
Our Intelligent Automation service designs and builds approval workflows, purchase request automation and the reporting that shows whether buying is getting faster, so your team spends its time on suppliers and stock, not on chasing signatures.



