--- title: "LPO, PO or LPR? Purchasing documents explained" description: "LPO meaning explained: how a local purchase order differs from a PO, LPR, RFQ and requisition, with a document flow, comparison table and worked example." url: https://1flux.ai/blog/lpo-vs-purchase-order-vs-lpr last_updated: 2026-10-11 --- Purchasing basics # LPO, PO or LPR? Purchasing documents explained The LPO meaning, how it differs from a PO, an LPR, an RFQ and a requisition, and where each document sits in the buying flow. Purchasing and inventory 8 min read Updated 10 October 2026 1. Requisition or LPR (Inside your company). 2. RFQ (To several suppliers). 3. Supplier quotation (The supplier's offer). 4. LPO (Commits you to buy). 5. Delivery note (From the supplier). 6. GRN (What you counted). 7. Supplier invoice (Matched to LPO and GRN). Seven documents, one flow. Only the LPO and the supplier's invoice commit you to pay. ## In short The LPO meaning is simple: a [local purchase order](https://1flux.ai/glossary/local-purchase-order) is a purchase order. It is the buyer's numbered, approved commitment to buy specific goods from one supplier at agreed prices and terms. The documents around it do different jobs. A requisition or local purchase request (LPR) asks to buy, a request for quotation (RFQ) asks suppliers for prices and the LPO places the order. 1flux prints an issued, priced purchase order as a "Local purchase order". ## Why do purchasing documents cause so much confusion? Purchasing documents cause confusion because they look alike and their abbreviations vary from company to company. A requisition, an RFQ and an LPO can all list the same items, quantities and delivery date. Only one of them commits your company to pay. The confusion costs money. A supplier delivers against an RFQ because it “looked like an order”. A storekeeper accepts goods with no LPO behind them. Accounts receive an invoice and can’t tell which order it belongs to. The fix starts with the vocabulary. Below, each document is defined, compared and traced through one purchase. ## LPO meaning: what is a local purchase order? An LPO is a purchase order, under the name used across the Gulf. It is a formal document from a buyer to a supplier that says: we will buy these items, in these quantities, at these prices, delivered here, by this date, on these payment terms. The word “local” is historical. It separated orders placed with suppliers in the same country from import orders, which usually carried different paperwork such as letters of credit and shipping documents. Many companies now call every purchase order an LPO, whether the supplier is in Dubai, Dammam or overseas. A complete LPO usually carries: - your legal name, address, VAT [tax registration number](https://1flux.ai/glossary/tax-registration-number) (TRN) and [commercial registration](https://1flux.ai/glossary/commercial-registration) or trade licence; - a unique LPO number and the order date; - the supplier’s legal name, address and VAT number; - the delivery address or warehouse and the expected delivery date; - each line’s item code, description, quantity and unit; - the unit price, any discount, the VAT rate and VAT amount per line; - the subtotal, VAT, total and currency; - payment terms, such as 60 credit days from the invoice date; - a reference to the supplier’s quotation; - your standard terms and an authorised signature, often with the company stamp. One more point trips people up. For the seller, your LPO is the [customer purchase order](https://1flux.ai/glossary/customer-purchase-order) that confirms their quotation. When a customer says “send the quotation and we’ll issue the LPO”, they mean this same document, seen from the other side. ## Is an LPO the same as a purchase order? Yes. An LPO and a [purchase order](https://1flux.ai/glossary/purchase-order) (PO) are the same document. You will hear both names across the UAE and Saudi Arabia, sometimes inside one company. What matters is what the document does: it is the approved, numbered order the supplier delivers and invoices against. If your team uses both terms, pick one for printed documents and treat the other as a synonym. Suppliers and auditors care that delivery notes and invoices quote an approved order number, not which name is printed at the top. ## What is an LPR, and how is it different from an LPO? An LPR is an internal request to buy, not an order. It usually stands for [local purchase request](https://1flux.ai/glossary/local-purchase-request); some companies say “local purchase requisition”. Either way, it is the fast lane for small, urgent or routine local purchases, such as consumables for a site or a part needed tomorrow. The difference from an LPO is commitment: - **An LPR** stays inside your company. It says “we need this”. It may name a preferred supplier and may be sent to suppliers as a request for prices, but it never obliges anyone to pay. - **An LPO** goes to one supplier. It says “we are buying this”. Once the supplier accepts it, it is the basis for delivery, invoicing and payment. An LPR is usually lighter than a full [purchase requisition](https://1flux.ai/glossary/purchase-requisition), often skipping formal approval and quote comparison. That speed is the point, so set a clear limit on what may go through it. ## Requisition, RFQ and supplier quotation: what comes before the LPO? Three documents usually come before an LPO on a sourced purchase. Each answers a different question. 1. **Purchase requisition (PR):** “May we buy this?” Someone inside the company asks for goods, with a purpose, quantities and a needed-by date. A manager approves it before anyone talks to suppliers. 2. **[Request for quotation](https://1flux.ai/glossary/request-for-quotation) (RFQ):** “What would you charge?” The buyer sends the approved needs to several suppliers. A good RFQ says in plain words that it is not a purchase order and leaves the price columns blank. 3. **Supplier quotation:** “Here is our offer.” Each supplier replies with prices, validity, lead time and payment terms. The buyer lines the offers up in a [quote comparison](https://1flux.ai/glossary/quote-comparison), picks a winner per line and records why. Only then does the buyer raise the LPO, one per winning supplier. ## How do the purchasing documents compare? Print this table for new buyers and storekeepers. The key column is the fourth: only two documents commit you to pay. | Document | Raised by | Goes to | Commits you to pay? | Typical contents | | -------------------------------------------------------------------------- | ------------------------------- | ---------------------------------------------- | ------------------------------------------------------ | --------------------------------------------------------- | | Purchase requisition (PR) | Requester (site, stores, sales) | Approver, then buyer | No | Items, quantities, purpose, needed-by date | | Local purchase request (LPR) | Requester or buyer | Buyer; sometimes suppliers, as a price request | No | Items, quantities, preferred supplier, needed-by date | | Request for quotation (RFQ) | Buyer | Several suppliers | No | Items, quantities, delivery point, blank prices | | Supplier quotation | Supplier | Buyer | No (it is the supplier’s offer, open until it expires) | Prices, validity, lead time, payment terms | | Quote comparison | Buyer | Approver or file | No | Offers side by side, the award and the reason | | LPO / purchase order | Buyer, after approval | One supplier | Yes, once accepted | Agreed prices, VAT, delivery, payment terms, signature | | Delivery note | Supplier | Your stores | No (it records what was sent) | LPO number, items and quantities delivered | | [Goods received note](https://1flux.ai/glossary/goods-received-note) (GRN) | Your stores | Buying and accounts | No (it records what arrived) | Quantities received, short, damaged; delivery note number | | Supplier invoice | Supplier | Accounts | Yes, for what was ordered and received | LPO number, quantities, prices, VAT, due date | ## What does the purchasing document flow look like? The flow runs from an internal request to a supplier invoice that matches what was ordered and received. There are usually two routes into the LPO and one common path after it. **Route A, sourced purchase:** requisition → approval → RFQ → supplier quotations → comparison and award → LPO. **Route B, quick local purchase:** LPR → (optional price check with a supplier) → LPO. **After the LPO, both routes meet:** LPO issued → supplier delivers with a delivery note → stores record a GRN → accounts receive the supplier invoice and match it to the order and the receipt → the supplier is paid. Some companies add a step between the GRN and the invoice, a [goods receipt report](https://1flux.ai/glossary/goods-receipt-report) (GRR). The GRN records what physically arrived; the GRR is the back-office document that accepts the goods into stock and books them. Splitting the two keeps the person counting boxes separate from the person posting value. ### Worked example: one purchase, start to finish Here is a fictional purchase traced through every document, in AED with UAE VAT at 5%. | Step | Document | What happens | Amount | | ---- | ------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------- | | 1 | Requisition REQ-2026-0118 | A project engineer asks for 60 rolls of 2.5 mm² cable, needed by 14 October. The operations manager approves. | — | | 2 | RFQ | The buyer sends the approved lines to three suppliers, with blank price columns. | — | | 3 | Supplier quotations | Supplier A quotes AED 182 a roll, Supplier B AED 176, Supplier C AED 179. All are valid for 7 days. | — | | 4 | Quote comparison | The buyer awards the line to Supplier B. Reason: lowest valid price and a 2-day lead time. | — | | 5 | LPO PO-2026-0337 | Issued to Supplier B: 60 rolls × AED 176 = AED 10,560, plus VAT of AED 528. | AED 11,088 | | 6 | Delivery note and GRN | The delivery note shows 56 rolls. Stores count 56 and record 4 short; the LPO stays open for 4. | — | | 7 | Supplier invoice | 56 rolls × AED 176 = AED 9,856, plus VAT of AED 492.80, matching the order price and the received quantity. | AED 10,348.80 | Fictional example. Amounts in AED; VAT at the UAE standard rate of 5%. The trail shows why Supplier B won, what was ordered, what arrived and why the invoice is lower than the LPO. ## What are the most common mix-ups, and how do you avoid them? Most purchasing disputes trace back to a few habits, each with a simple fix. - **An RFQ is treated as an order.** Print “This is not a purchase order” on every RFQ and leave prices blank. - **The LPO is raised after delivery.** A retrospective LPO hides an unapproved purchase. Track each one as an exception. - **Changes are agreed by phone.** If quantities or prices change, issue a revised LPO with a revision number and a reason, so the supplier’s invoice has something to match. - **The LPR lane is used to dodge approval.** Set a value limit and a list of what may be bought through an LPR. - **Delivery notes and invoices don’t quote the LPO number.** Make the LPO number a condition of acceptance at the gate and in accounts. - **One delivery covers several LPOs.** Record every LPO number on the GRN, so each order is received against correctly. For the full process from request to payment, read the [procure-to-pay guide](https://1flux.ai/guides/procure-to-pay). ## How 1flux handles this 1flux uses the vocabulary your buyers and storekeepers already use, and connects each document to the next in 1flux Inventory, which includes purchasing and receiving. In 1flux 1. Requisition: Approved . Nothing posts. 2. RFQ and quotes . Nothing posts. 3. Compare and award . Nothing posts. 4. Purchase order (PO-2026-0012) . Nothing posts. 5. GRN check-in: Checked & approved . Nothing posts. 6. Goods receipt report (GRR-2026-0074) . Posts Dr Inventory , Cr GRNI. 7. Purchase invoice (PI-2026-0033) . Posts Dr GRNI, VAT , Cr AP. Procure to pay in 1flux, from requisition to purchase invoice. The GRN check-in posts nothing; the goods receipt report posts stock and the journal. - **Requisitions with a purpose.** Each requisition is for **Replenish stock**, **Customer demand (sales order)** or **Internal use**. A customer-demand requisition requires the sales order it serves and can copy its open lines. Requisitions have one approval step. - **RFQs as PDFs.** An approved requisition downloads as a request for quotation, general or addressed to one supplier, and 1flux marks that supplier “RFQ sent”. - **Quotes, comparison and award.** Buyers record each supplier quotation with the supplier’s file attached, compare offers side by side with a “Best” badge and award each line with a reason. Awards become draft purchase orders, one per supplier. - **The LPR lane.** A local purchase request needs no approval. It downloads as an RFQ PDF, keeps revision-numbered files when edited and converts into a priced or unpriced purchase order. - **Purchase orders that print as LPOs.** An issued, priced order prints as a “Local purchase order” with your letterhead and tax registrations. Statuses run Draft → Issued → Receiving → Closed, or Cancelled. Quantity and price revisions need a reason, and orders can be short-closed. If prices aren’t agreed yet, a “PO without price” lets you order now and price later. - **Separate lanes.** Raising, approving, awarding, issuing, receiving and invoicing are separate permissions, so you decide who can commit the company. - **After the LPO.** A GRN check-in posts nothing; a goods receipt report posts the stock and the journal; the purchase invoice is built from what was received. You then pay suppliers and allocate each payment to purchase invoices, and payments post to the ledger. On the selling side, when your customer’s LPO arrives, attaching it to the accepted quotation sends it to operations as an order request. [1flux purchase orders](https://1flux.ai/products/purchasing/purchase-orders) [Requisitions and quote comparison](https://1flux.ai/products/purchasing/requisitions) Related product ### [1flux Purchasing](https://1flux.ai/products/purchasing) From requisition and quote comparison to receiving, purchase invoices and supplier payments, on one record. FAQ ## Questions, answered Still deciding? [Talk to sales](https://1flux.ai/contact) ### What does LPO stand for? LPO stands for local purchase order. It is the name used across the UAE, Saudi Arabia and the wider Gulf for a purchase order: the buyer's formal, numbered order to a supplier, with agreed items, quantities, prices, VAT, delivery and payment terms. "Local" originally meant a supplier in the same country, as opposed to an import order, but many companies now use LPO for every purchase order. ### Is an LPO legally binding? An LPO is the buyer's formal offer to buy, and it usually becomes binding once the supplier accepts it, for example by signing it or delivering against it. The exact effect depends on your terms and conditions, the supplier's quotation and local law. Make sure your LPO states its own terms, references the supplier's quotation and is signed by someone authorised. If a contract matters, ask your lawyer to review your standard purchase terms. ### What is the difference between an LPO and an LPR? An LPR (local purchase request) is an internal request to buy; an LPO (local purchase order) is the order placed with a supplier. The LPR says "we need this" and commits nobody to pay. The LPO says "we are buying this at these prices" and, once accepted, is what the supplier delivers and invoices against. An LPR is usually the fast lane for small local purchases and converts into an LPO. ### Do you need an RFQ before every LPO? No. An RFQ is worth sending when the value, risk or price uncertainty justifies comparing suppliers. Small, routine or urgent local purchases often go straight from an LPR to an LPO with a known supplier. Write the rule down: for example, an RFQ to at least three suppliers above a set value, and a recorded reason whenever you buy without one. ### Can you issue an LPO before the price is agreed? Yes, but it needs care. Some trading companies must order before a supplier confirms the final price, for example on volatile materials. If you do, mark the order clearly as unpriced, agree the price before the invoice arrives and value the received stock provisionally until then. In 1flux, a "PO without price" does exactly this: receipts carry a provisional cost until the buyer agrees prices on the order. ### How does 1flux print an LPO? 1flux prints an issued, priced purchase order as a "Local purchase order" with your letterhead, tax registrations, the supplier's tax number and totals, ready to save as a PDF and send to the supplier. Requisition RFQs and local purchase requests download as PDFs in one click, and every change to an issued order is kept as a numbered revision with a reason. Related ## Keep exploring ### [Purchase orders (LPO)](https://1flux.ai/products/purchasing/purchase-orders) Priced or unpriced orders, VAT per line, revisions with reasons and a report of what's due. ### [Requisitions and quote comparison](https://1flux.ai/products/purchasing/requisitions) Requisitions with a purpose, RFQ PDFs, recorded quotes and awards with a reason. ### [Procure-to-pay guide](https://1flux.ai/guides/procure-to-pay) Eleven steps from requisition to supplier payment, with the documents, controls, accounting, KPIs and a checklist. ### [Goods received not invoiced (GRNI), explained](https://1flux.ai/blog/goods-received-not-invoiced-explained) The journals from goods receipt to supplier invoice, why the balance creeps up and a month-end routine that keeps it clean. Last updated 11 October 2026