Walkthrough
Checklist
Success check
Walkthrough: Procurement Request to PO
Move a purchase need from request, review, approval, sourcing, and supplier selection into a purchase order.
The request-to-PO workflow helps teams buy with context and control. It starts with a business need and ends with a supplier-facing purchase order that can be received, matched, and reported.
Before You Start
- You can create procurement requests or manage procurement records.
- You know the item or service, quantity, required date, delivery location, reason, and budget context.
- The requester, department, branch, warehouse, or cost center is clear.
- Supplier selection and approval rules are understood.
- Required attachments, specifications, or previous supplier references are ready.
Steps
- Open Procurement and create a request.
- Add item or service details, quantity, unit, required date, branch, warehouse, and justification.
- Attach specifications, photos, previous invoices, budget notes, or supporting documents if needed.
- Submit the request for approval where required.
- After approval, prepare sourcing or RFQ activity according to your procurement process.
- Compare quotations or supplier options and record the selection reason.
- Create the purchase order using approved quantities, prices, taxes, delivery terms, and supplier details.
- Review PO status and notify the supplier if your process sends or shares POs from AWRA.
Success Check
- The request shows the correct status and approval history.
- The PO has the selected supplier, item, quantity, price, tax, delivery terms, and delivery location.
- The warehouse or receiving team can identify what is expected.
- Finance or management can see why the supplier was selected.
Common Mistakes
- Submitting vague requests without item details, dates, or justification.
- Skipping approvals before creating the PO.
- Changing requested quantity or supplier without recording the reason.
- Creating a PO from an outdated quotation.
- Forgetting to tell receiving teams what delivery to expect.
Support tip: Include request number, PO number, supplier, requester, approval status, and the step where the workflow is blocked.
Support escalation
Open support guide
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.