Purchasing

Purchase request vs purchase order: what's the difference?

By the Slateo teamPublished 6 min read

On this page

Every factory buys the same way in principle: someone needs something, someone agrees to it, someone orders it, and someone checks it in. The purchase request and the purchase order are the two documents that sit at the start of that chain, and mixing them up is how orders go out that nobody approved, or approvals happen that nobody turns into an order.

The short answer

A purchase request says “we need this”. It’s raised inside your company by the person or team who needs the goods, such as a production supervisor who needs mild steel sheet for next week’s run. It goes to someone who can say yes. No vendor sees it, and nothing has been bought.

A purchase order says “we will buy this from you”. It’s raised by whoever deals with vendors, usually the purchase team, and sent to a vendor. It names the items, quantities, prices, delivery date and terms. Once the vendor accepts it, you’re committed.

Side by side

Purchase request Purchase order
Purpose Ask to buy something Commit to buying it from a vendor
Raised by The person or team who needs it The purchase team
Goes to An approver inside your company The vendor
Holds What’s needed, how much, by when, why Items, quantities, prices, delivery date, terms
Binding? No Usually yes, once the vendor accepts
Ends when Everything asked for has arrived Everything ordered has been delivered

Why keep them separate

You could skip the request and let people raise orders directly. Small teams often do, and that’s fine while one or two people do all the buying. The request starts to earn its keep when more people buy:

  • Approval happens before money is committed. A plant head can say no to a request. Saying no to an order the vendor has already accepted is harder and more expensive.
  • The person who needs it isn’t the person who buys it. Supervisors know what the line needs; the purchase team knows vendors and prices. The request hands the need over without either doing the other’s job.
  • One need can become several orders. A request for a month’s materials might be split across two vendors, or ordered in two lots. The request shows whether the whole need has been met, not just one order.
  • You can trace spend back to a reason. When a bill arrives months later, you can follow it to the order, and the order to the request and the person who asked for it.

When you don’t need purchase requests

If one person both decides what to buy and orders it, a request adds a step without adding a check. The same goes for routine re-orders of the same consumables from the same vendor. In those cases, start from the purchase order and put the approval on the order itself.

A good rule: add requests when someone other than the buyer needs to agree before money is committed, or when the people who need things outnumber the people who buy them.

What each one should contain

A useful purchase request has the item, the quantity and unit, when it’s needed, where it should arrive (which plant or warehouse), and a line on why. It doesn’t need a vendor or a price, though a rough cost helps the approver.

A useful purchase order has the vendor, each item with quantity, unit and price, the delivery location and date, a reference to the request it came from, and your payment and delivery terms. That reference is what lets you trace a bill back to the original need.

How they connect to the rest of the chain

The request and order are only the start. Goods arrive against the order, someone checks what came in, stock goes up, and the vendor’s bill is checked against the order and the delivery before it’s paid. Each step should point back to the one before. When they do, any question (“why did we buy this?”, “did all of it arrive?”, “is this bill right?”) is answered by following the links rather than by asking around.

Questions

Is a purchase requisition the same as a purchase request?

Yes. Requisition is the older, more formal word; many teams just say request or indent. All of them mean an internal ask to buy something, approved before anything is ordered.

Is a purchase order legally binding?

Once your vendor accepts it, a purchase order usually forms a contract on the terms it sets out. A purchase request never binds you to anyone: it stays inside your company. Check the rules where you trade if the terms matter.

Can one purchase request become several purchase orders?

Yes, and it often does: one request for a month's materials might be split across two vendors. The request is only complete when everything on it has arrived.

Who should raise a purchase order?

Usually the purchase team or whoever deals with vendors, not the person who needs the goods. That split is what makes the approval on the request mean something.

Run purchasing from request to payment.

Slateo PlantOps is free for up to 3 users.