Types of Purchase Orders: Standard, Planned, and Blanket

There are four types of purchase orders in common use. A standard PO covers a one-off order where you know the item, quantity, price, and delivery date. A planned PO fixes those details but schedules deliveries over time. A blanket PO commits to spend or quantity without fixed delivery dates. A contract PO commits to terms only, with no items named yet.

The distinction matters more than it looks. Each type creates a different level of legal and financial commitment, each shows up differently on your open PO report, and each is handled by a different document in whichever system you run. Pick the wrong one and you either lock yourself into quantities you do not need, or you lose the price protection you negotiated. Here is what each type actually does, followed by how SAP and Oracle name them, because that is where most of the confusion starts.

The four types of purchase orders compared

Standard purchase order

A standard purchase order is the default. You know what you are buying, how many, at what price, and when you want it delivered, so all of that goes on one document and the order is complete the moment the supplier accepts it. Most of the POs any business issues are standard POs.

Use it when the purchase is discrete: a replacement pump, a batch of laptops, a print run, a contractor's fixed-scope job. There is nothing to release later and nothing left open. Once the goods arrive and the invoice is matched and paid, the order is closed and it drops off the open PO report.

The commitment is full and immediate. From the moment the supplier accepts, both sides are bound to the quantities and prices on the document, which is why a standard PO is the type most often treated as a contract in its own right. If the details are still moving, one of the other three types is the safer choice.

Planned purchase order

A planned purchase order names the items, quantities, and prices up front, exactly like a standard PO, but the delivery schedule on it is tentative. You commit to buying 12,000 units across the year at an agreed price; you do not commit to receiving 1,000 of them on the first of every month. Actual deliveries come from releases issued against the planned PO as you need them.

This is the type for a known, forecastable annual requirement where you want price certainty and supplier capacity reserved, but you do not want the warehouse filling up. Manufacturers use it heavily for raw materials and components. The buyer gets volume pricing, the supplier gets a production forecast, and inventory stays sane.

The trade-off is administrative. A planned PO plus its releases is two layers of paperwork instead of one, and the open commitment on your books is the undelivered balance rather than a simple order total. If your accrual process is not set up to read releases separately from the parent order, month end gets awkward.

Blanket purchase order

A blanket purchase order, sometimes called a standing order or a blanket purchase agreement, fixes prices and terms for a period of time without fixing quantities or delivery dates. You agree that for the next twelve months you will pay a set rate for whatever you order, usually up to a spending ceiling or a maximum quantity. Individual purchases are then made as releases against the blanket.

Blankets are the right answer for consumables and recurring services: office supplies, safety equipment, maintenance parts, janitorial work, staffing hours. Anything you will buy repeatedly but cannot forecast precisely. Issuing a fresh PO for every small order would cost more in processing than the goods are worth, and the published estimates for fully processing a single purchase order by hand run from roughly $15 to $40, which is exactly why blankets exist.

Two things to watch. First, the ceiling is real, and orders that would breach it get rejected or require an amendment, so somebody has to track consumption against the limit. Second, blanket POs are where maverick spend hides: a broad blanket with a loose description becomes a convenient place to charge purchases that should have gone through a proper approval. Review what is actually being released against each blanket at least quarterly.

Contract purchase order

A contract purchase order commits to the commercial terms of a relationship without naming a single item. Payment terms, lead times, liability, warranty, discount structure, and the duration of the agreement are all settled; what you will actually buy is not. Later, standard POs reference the contract PO and inherit its terms.

This is the type used when you want a supplier under agreed terms before you know your requirements, which is common with professional services, IT vendors, and long-term suppliers whose product mix changes. It reduces every subsequent order to a quantity and a delivery date, because the arguing about terms already happened.

Because no items or quantities are named, a contract PO usually creates no financial commitment on its own and does not appear as an open order awaiting receipt. It sits in the background as the terms container that other orders point at.

Purchase order types in SAP

SAP does not use the words standard, planned, blanket, and contract. It uses purchasing document types, identified by two-character codes that are configured per client. Three standard ones cover most of what US buyers meet:

• NB is the standard purchase order, used for ordinary external purchases from a vendor. It is the everyday type and the closest match to a standard PO.
• FO is the framework order, the document type used for blanket and limit purchase orders where you are buying against a value limit over a validity period rather than against fixed quantities.
• UB is the stock transport order, used to move stock between plants inside your own company. It looks like a PO but there is no external vendor and no external spend.

Because document types are configurable, plenty of SAP shops add their own codes on top of these, so the list in your system may be longer. The underlying idea is the same: the type decides the number range, the field layout, and which follow-on documents are allowed. Orders arriving from SAP-based customers as PDFs are covered in purchase order to SAP, and the machine-readable equivalent is explained in the IDoc purchase order guide.

Purchase order types in Oracle

Oracle maps almost exactly onto the four-type model, which is why Oracle terminology has become the common vocabulary for this topic. Oracle Purchasing distinguishes standard purchase orders, planned purchase orders, blanket purchase agreements, and contract purchase agreements, and treats the two agreements as separate document classes rather than as orders.

The practical difference in Oracle is what each document does to your commitments. Standard and planned POs encumber funds and show as open orders; blanket and contract purchase agreements are agreements that releases and standard POs are written against. If you are loading historical orders into Oracle, the document type has to be right in the interface data, because it drives validation. The load paths themselves are covered in Oracle purchase order import, which walks through the FBDI template for Oracle Fusion Cloud and the Purchasing Documents Open Interface for E-Business Suite.

What is the difference between a planned purchase order and a blanket purchase order?

A planned purchase order commits you to specific items and quantities with tentative delivery dates. A blanket purchase order commits you to prices and terms but not to quantities. Put simply, a planned PO says what you will buy but not exactly when, and a blanket PO says what it will cost but not how much you will take.

That difference decides your financial exposure. On a planned PO the quantity is a genuine obligation, so it lands on your commitment reporting and feeds accruals. On a blanket PO nothing is owed until a release is issued, so only the released portion carries weight. Buyers who confuse the two end up either accruing for orders that were never binding, or missing commitments that were.

Which type of purchase order should I use?

Work through it in this order. If you are buying something once and you know all the details, issue a standard PO and stop there. If you know your total annual requirement and want price and capacity locked but deliveries spread out, use a planned PO. If you will buy the same things repeatedly but cannot say how much or when, use a blanket PO with a sensible ceiling. If you want a supplier on agreed terms before you know your requirements at all, use a contract PO and write standard POs against it.

The most common mistake is defaulting to standard POs for everything. It feels safe and it produces a mountain of low-value transactions, each carrying the same processing cost as a large one. The second most common mistake is the opposite: writing a broad blanket to avoid paperwork and then losing visibility of what is being spent under it.

Do the different types change how a PO is closed?

Yes. A standard PO closes when its quantities have been received and invoiced, and that usually happens automatically. Planned and blanket POs stay open until every release against them is settled and the agreement itself is expired or closed, which is why they are the ones that linger on the open PO report for months after anyone stopped ordering. Contract POs simply expire on their end date.

This is the practical reason to keep the types straight: a clean open PO report depends on knowing which documents are supposed to be sitting there and which are stale. The mechanics of closing each one are covered in the guide to closing a purchase order, and the report itself in the open purchase order report.

How the type affects accruals and the month-end close

Open POs are the raw material for goods-received-not-invoiced accruals, and the type determines what belongs in that calculation. Received-but-unbilled quantities on standard and planned POs accrue. An unreleased blanket does not, because nothing has been ordered yet. A contract PO never does. Getting this wrong overstates liabilities on the balance sheet, and the error compounds quietly because nobody reconciles agreements the way they reconcile orders.

Finance teams who have cleaned up this data usually find the harder problem is not the accounting rule but the data quality feeding it, since the commitment balance is only as good as the order records behind it. Once the numbers are trustworthy, turning them into board-ready P&L and balance sheet output is straightforward. The accrual mechanics are covered in purchase order accrual and goods received not invoiced.

Getting the type right when orders arrive as PDFs

If you are on the selling side, the type your customer used is stated on the document, usually in the header near the PO number, and it tells you what you are actually committed to. A blanket reference means the order you just received is a release, not a fresh order, and it should be booked against the agreement rather than as a standalone. That detail gets lost constantly when orders are re-keyed from PDFs under time pressure.

PurchaseOrders is the data-capture layer for exactly that step. Upload a PO PDF, scan, or photo and it returns the header fields and the full line-item table as Excel, CSV, JSON, or an API response, so the reference, terms, and lines land in your system as typed by a machine rather than a person at four in the afternoon. To be clear about the boundary: it reads purchase orders and returns structured data. It does not create them, approve them, or post them to your ERP.

In practice that means you can convert purchase order PDFs to Excel as they arrive, use line item extraction when the detail lines carry the commitment, and clear an accumulated week through bulk purchase order upload. If you are evaluating software for the blanket case specifically, blanket purchase order software covers that ground, and the field-by-field breakdown of a PO header is in purchase order fields.

What to do with this

Audit your last quarter of POs and count how many were standard. If the number is close to 100 percent, you are almost certainly processing transactions you could have consolidated onto a blanket or a planned order, and paying full processing cost for each one. Pick the two or three suppliers you order from most often and move them onto blankets with a real ceiling and a named owner who reviews releases. Then check the other direction: any blanket that has been open more than a year without a review is a spend-control gap, not a convenience.