Procurement breaks down when the process is unclear, approvals are informal, and teams lose track of what was requested versus what was actually ordered and delivered.
This guide outlines a practical RFQ-to-PO workflow you can implement in an ERP without turning procurement into a spreadsheet project.
The RFQ-to-PO workflow (high level)
- Define what you need (scope, quantities, units, delivery constraints)
- Issue an RFQ to one or more vendors
- Collect quotes and normalize line items for comparison
- Award the RFQ (choose vendor(s) and confirm final terms)
- Generate a Purchase Order (PO) from the award
- Track delivery and receipts (GRN / goods receipt)
- Manage the payment schedule and approvals (milestones, proofs, audit trail)
What makes this workflow enterprise-grade
1) An auditable source of truth
Every key step should be represented by a record (RFQ, Quote, Award, PO, Goods Receipt, Payment Milestone), not a chat message.
2) Approval is explicit, not implied
Approvals should be:
- Role/permission gated
- Logged (who, when)
- Reversible via a new state transition (no silent overwrites)
3) Exceptions are first-class
Your workflow should handle (without chaos):
- Partial deliveries
- Substitutions
- Price changes
- Currency differences
- Split awards
Suggested checklists
Before issuing an RFQ:
- Confirm budget owner and approver
- Confirm units of measure and expected lead time
- Attach any drawings/specs needed to quote accurately
Before converting to a PO:
- Confirm awarded vendor(s) and final negotiated terms
- Confirm payment milestone expectations
- Confirm delivery locations and requested delivery dates
Next steps
If you're building this workflow in Gestio, start with consistent item naming and vendor records, then standardize how RFQs map into POs so reporting stays clean.