INTERNAL PO PREPARATION
An internal purchase order request ready for buyer handoff
Carry the approved requisition into PO preparation with the supplier, amount, currency, terms, ship-to detail, buyer, authorization evidence, and unresolved commercial exception in one record.
This internal request begins after requisition approval. It prepares the buyer or purchasing system to create the official supplier-facing purchase order; it is not the issued PO itself.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Do not make the buyer rediscover the approved decision
The handoff should contain the commercial facts needed to prepare the order and the evidence that internal authorization is complete.
- 01
Approved source requisition
Link the handoff to the exact requisition, approved amount, line detail, business justification, cost center, and decision history.
- 02
Supplier and delivery detail
Record the supplier, approved or review-required status, ship-to location, required date, buyer, and any special delivery term.
- 03
Commercial terms
Carry currency, price basis, payment terms, delivery terms, accepted quote, and any exception that the PO approver needs to see.
- 04
Release decision and next action
Show whether the handoff is preparing, awaiting approval, returned, PO-ready, issued, or cancelled, with the owner and due date.
Compare PO-ready work with the exceptions still blocking release
The working handoffs show approved requisitions, supplier and terms checks, returned corrections and the final PO-ready result.
Separate a missing field from a real commercial decision
Returning every irregularity to the requester creates delay without improving control.
Supplier review required
Route new, blocked, or unverified supplier status to the correct supplier process while preserving the approved business need.
Nonstandard terms
Identify which term differs, who can accept it, and whether the exception blocks PO issue.
Amount changed after approval
Do not silently overwrite the approved value. Record the change and return to the required approval stage when the policy threshold is crossed.
Delivery or coding mismatch
Give the buyer a specific correction path for ship-to, cost center, line, or tax-related context without invalidating unrelated approved details.
Keep internal approval and order issuance distinct
The separation makes missing authorization visible without turning Jodoo into an unsupported ERP promise.
| Question | Requisition answers | PO handoff answers |
|---|---|---|
| Why buy? | Business justification and need | References the approved source |
| What and how much? | Line items and approved total | Final supplier-facing amount and currency |
| Who authorized? | Budget, department, amount, and procurement decisions | Verification that required approvals are complete |
| Who supplies and delivers? | Supplier path and requirement | Supplier, terms, ship-to, buyer, and exceptions |
| What happens next? | Approved or returned | PO-ready, issued, returned, or cancelled |
Make the handoff end in an observable outcome
A PO request is not complete merely because someone opened the record.
PO-ready
All required source, supplier, commercial, delivery, and authorization checks are complete for the buyer or order system.
Returned
The record names the blocking correction, owner, due date, and approval stage that must be revisited.
PO issued
The authoritative PO number and issue date are recorded, and the requester can follow the order in the downstream tracker.
Cancelled
The team records why the approved intent will not proceed and whether budget or supplier commitments need to be released.
Adapt PO readiness to your commercial policy
Configure the exact checks that make an approved requisition safe to order.
- Add supplier-status or contract-reference checks for selected categories.
- Route nonstandard terms or amount changes to the required decision owner.
- Show ship-to or service-location questions only when relevant.
- Create buyer, returned, PO-ready, and issued-order queues without code.
Use this template for the buyer handoff, not the entire order lifecycle
The handoff should connect cleanly to the system that issues and accounts for the PO.
Strong fit: flexible pre-PO coordination
Use Jodoo when approved requisitions need supplier, commercial, delivery, and exception checks before the buyer creates the official order.
Use a PO tracker after issue
Once the order exists, shipment, delivery, receipt, supplier follow-up, and closure belong in the purchase-order tracking path.
Keep finance execution in the authoritative system
Tax determination, commitment accounting, three-way match, invoice posting, and payment should remain in ERP or AP tools unless separately implemented and proven.
Questions about purchase order request
These answers clarify where the internal PO request begins, what makes it ready, and which purchasing or ERP record remains authoritative.
What is a purchase order request?
It is an internal handoff asking a buyer or purchasing system to create an official purchase order from an approved requisition. It should carry the approved amount, supplier, commercial terms, delivery details, authorization evidence, and any exception.
Is a PO request the same as a purchase requisition?
No. The requisition is the internal authorization to buy. The PO request begins after approval and packages the information needed to prepare and authorize the official order.
What should block PO-ready status?
Missing requisition approval, supplier review, unresolved amount change, nonstandard terms without acceptance, incomplete ship-to or delivery detail, or another policy-specific control should block release.
Can the official PO still be created in ERP?
Yes. Jodoo can coordinate the approved handoff and exceptions while ERP remains authoritative for the PO number, accounting, receipt, invoice matching, and payment.
How should a returned PO request work?
Record the exact correction and owner, preserve the approved source, and route amount or policy changes back to the necessary approval. Do not make the buyer infer what changed from email.
Inspect the PO handoff before you copy the workflow
Open the populated example to compare preparing, awaiting approval, returned, PO-ready, and issued records. Then adapt supplier checks, terms, buyer ownership, and downstream system handoff.
Open the PO request handoff