System type 03 / 11
Procurement systems
From purchase request to purchase order: supplier offers side by side, and a documented decision tied to the budget.
Closest function: Procurement
Comparison: laptops for the sales team
- Horizon NetworksBest valueSAR 168,900Score92
- Madar SolutionsSAR 162,400Score81
- Advanced LinkSAR 179,800Score86
Three signs a process has outgrown its tools.
- 01
Offers compared in separate spreadsheets
- 02
Award decisions without a record
- 03
Budget impact appears too late
The modules the system is built from.
A possible scope, not a fixed list: we choose with you what is built first and what waits.
- M01Purchase requests
- M02Approved suppliers
- M03Requests for quotation
- M04Weighted comparison
- M05Award approval
- M06Purchase orders
- M07Budget impact
- M08Decision record
A system tied to a real operating problem.
For procurement and finance teams that need a documented path from purchase request through quotation comparison, approval and purchase order.
Clear purchase request
A request tied to the requesting function, items, justification and approval state.
Supplier quotation comparison
Compare quotations side by side against clear criteria instead of scattered files and spreadsheets.
Documented award decision
Who approved, why, and the budget impact before creating the purchase order.
From process to an operational system.
The order changes by project scope; this is the structure we use to make decisions and ownership explicit before expanding.
- 01Create purchase request
- 02Request quotations and record suppliers
- 03Compare quotations
- 04Approve the award
- 05Create purchase order
- 06Track status through receipt within project scope
- Integrate with finance or ERP systems through APIs when available
- Define the budget and master-data source before integration
- Avoid re-entering the same data across systems where possible
What should remain clear after launch.
- Permissions by requester, procurement and approver roles
- Approval rules by amount, department or request type
- Decision, comment and approval history
- Separate supplier and internal-user permissions where applicable
- A reviewable purchasing decision instead of scattered messages
- Clearer visibility into where each request stands
- Connect comparison, approval and budget impact in one flow
- Procura provides a ready foundation for procurement workflow
- FlowGate can support complex approval rules
- ContractHub connects contract and renewal management where needed
- Customization starts from the organization's real process
From the same problem to the right system and product.
Clear answers before the analysis session.
Q01Is this a full ERP?
Not by default. This flow focuses on procurement and can integrate with an existing finance or ERP system where integration interfaces are available.
Q02Can approval paths change by request value?
Yes. Approval rules can vary by amount, department and request type according to the approved authority matrix.
Q03Can supplier quotations and the comparison history be retained?
Yes. Within the system scope, quotations can be retained and the comparison and decision linked to the request record.
From an approved product foundation, or from scratch.
When your process resembles no product, we build the system around it from the first workshop.
Start from the process- 01Process analysisCurrent process map
- 02Screens and rulesInteractive prototypes
- 03Phased developmentReview environment
- 04Integration with your systemsIntegration map
- 05Launch and trainingData migration
- 06Operation and supportMonitoring
Tools to clarify the decision and scope.
Discuss procurement systems with our analysis team.
An intro session with our analysis team to review your current processes and scope the first system.