Raise an internal purchase request, cost it, route it for approval, then print or download the form as PDF
A purchase requisition form is the internal document someone inside your business uses to request that something be bought. It is not an order. It carries no commitment to any supplier and creates no liability. It is a request that travels up to whoever controls the budget, and only once it is approved does it become a purchase order that goes out to a vendor.
The distinction matters more than it sounds. The requisition is internal and asks permission. The purchase order is external and forms a contract. Businesses that skip the requisition step end up with staff committing company money directly to suppliers with no approval trail, which is exactly how unbudgeted spend, duplicate orders and unexplained invoices appear at month end.
These two documents are constantly confused, and the confusion is expensive. They sit at different points in the procurement chain and do genuinely different jobs:
| Purchase Requisition | Purchase Order | |
|---|---|---|
| Direction | Internal, staff to management | External, business to supplier |
| Purpose | Requests permission to buy | Instructs a supplier to supply |
| Legally binding? | No | Yes, once accepted |
| Who sees it | Requester, department head, finance | Supplier, finance, receiving |
| Supplier named? | Suggested only, purchasing may override | Confirmed and contracted |
| Prices | Estimates, for budget checking | Agreed prices, invoiced against |
| Created when | A need is identified | After the requisition is approved |
The sequence in full: a need is identified, a requisition is raised and costed, an approver checks it against budget, purchasing sources or confirms a supplier, a purchase order is issued, goods arrive against a delivery order, and the supplier invoice is matched against both before payment. That last step is the three-way match, and it only works if the paper trail starts with a requisition. The wider process is covered in our guide to purchase order management.
A requisition that gets approved quickly is one the approver can act on without asking a single follow-up question. These are the fields this generator produces:
| Field | Why It Matters |
|---|---|
| Requisition number | The unique reference the eventual purchase order and invoice are matched back to. Sequential numbering makes gaps visible |
| Date raised and required-by date | The gap between these two is what tells purchasing whether there is time to source competitively or whether they must pay for speed |
| Requester name and job title | Names the person accountable for the request, not just the department |
| Department and cost centre | Routes the spend to the right budget. Without it finance cannot tell whose numbers this hits |
| Item description, SKU and quantity | Precisely what is being asked for. Vague descriptions are the main cause of receiving the wrong goods |
| Unit of measure | Ordering 50 of something is meaningless until you say 50 pieces, 50 cartons or 50 pallets. This single field causes more over-ordering than any other |
| Estimated unit cost and total | Lets the approver check against remaining budget before approving rather than after invoicing |
| Suggested supplier | Useful information, not an instruction. Purchasing may have a contracted vendor at better terms |
| Priority | Separates genuine emergencies from routine replenishment. If everything is urgent, nothing is |
| Business justification | The single field that most decides whether a requisition is approved or bounced back |
| Delivery location | Multi-site businesses need this on the form, otherwise stock lands at the wrong warehouse |
| Approval blocks | Requested by, reviewed by and approved by, with dates. This is the audit trail |
Most businesses tier approval by value rather than sending everything to one person. There is no universal standard, but a structure that works for a growing ecommerce operation looks like this:
| Estimated Value | Typical Approver | What Is Usually Required |
|---|---|---|
| Low value, routine consumables | Department head | Single approval, no quotes needed |
| Mid value, regular replenishment | Operations or finance manager | Budget check against cost centre |
| High value, non-routine | Finance director or owner | Two or three comparative quotes |
| Capital expenditure | Owner or board | Business case, payback period, quotes |
Set the thresholds in currency terms and write them down. The most common failure is not the absence of tiers but the absence of a published limit, so nobody knows whether their request needs one signature or three. A second common failure is the requester and the approver being the same person, which removes the entire control the requisition exists to provide.
A purchase requisition form is an internal document used to request approval to buy goods or services. It records what is needed, how many, why, when it is required and the estimated cost, then routes to whoever controls the relevant budget. It is not an order and creates no obligation to any supplier. Only after approval does it become a purchase order.
A purchase requisition is internal and asks permission to spend. A purchase order is external and instructs a supplier to supply, forming a binding contract once accepted. The requisition comes first and is approved internally, then purchasing converts it into a purchase order and sends it to the chosen supplier. A requisition names a suggested supplier at best, whereas a purchase order names a confirmed one with agreed prices.
It depends on value. Routine low-value requests are usually approved by a department head, mid-value replenishment by an operations or finance manager, and high-value or capital purchases by a finance director or the business owner. The key rule is that the approver must be someone other than the requester and must hold the authority for that value band. Publish the thresholds so people know where to send requests.
No. A purchase requisition is an internal request and carries no legal weight with any supplier, which is precisely why it is safe to raise one before a supplier or price is confirmed. The legal commitment begins with the purchase order, once the supplier accepts it. This is also why a requisition should never be sent to a vendor.
A sole trader buying their own stock does not need to request permission from themselves. The moment a second person can commit company money, the control becomes worth having. In practice most ecommerce businesses adopt requisitions when a warehouse or operations hire starts raising stock orders, because that is the point at which spend can happen without the owner seeing it first. Even then, keeping the form to one page and approval to one signature for routine items is usually enough.
A blanket requisition covers repeated purchases from the same supplier over a set period, typically a quarter or a year, up to an agreed value ceiling. It is approved once rather than per order, which suits consumables such as packaging bought on a recurring basis. Individual releases against it still get recorded, but they do not each need a fresh approval cycle.
A requisition is only as good as the stock figure behind it. Selling on Shopee, Lazada, Amazon, TikTok Shop and your own store? OneCart syncs inventory across every channel in real time, so when someone raises a replenishment request they are working from what you actually have, not from a spreadsheet that was accurate yesterday.
Try OneCart Free →