Types of Purchase Orders — Standard, Planned, Blanket, and Contract POs Explained

Most people learn one type of purchase order — the standard one — and try to make it fit every situation. That's fine until you start buying the same thing repeatedly, or scheduling deliveries months out, or running a complex contract.

There are four standard PO types. Each fits a different procurement pattern. Picking the right one is the difference between sensible paperwork and either over-documentation or hidden risk.

Here's the breakdown.

Quick reference table

| Type | Quantity | Delivery | Pricing | Best for | |---|---|---|---|---| | Standard PO | Specific | Specific | Specific | One-off purchases with all details known | | Planned PO | Specific | Tentative | Specific | Known quantity, uncertain timing | | Blanket PO | Maximum | Multiple over time | Fixed for period | Recurring purchases, same vendor | | Contract PO | Unspecified | Unspecified | Specified terms | Ongoing relationship, no commitment to quantity |

If you only remember one thing: the more uncertain the details, the further down this table you go.

1. Standard purchase order

The default. The one you've used (or seen) before.

A standard PO specifies everything: which items, how many, what price, when delivered, where shipped. Nothing is left open. The vendor accepts it and fulfills exactly what's on the document.

When to use it:

• You know exactly what you need
• You know exactly when you need it
• You know exactly what it costs
• This isn't part of a recurring pattern

Example: Your office needs a new conference room TV. You spec the model (Sony XBR-65X90L), quantity (1), price ($1,499), delivery date (next Friday), shipping address (HQ). Standard PO covers this perfectly.

For most one-off purchases under ~$5,000, a standard PO is the right call. Templates and generators (like our free PO generator) handle this case in 90 seconds.

If you want the full primer on what a standard PO contains and how it works, see what is a purchase order.

2. Planned purchase order (PPO)

Use a planned PO when you know what and how much, but not exactly when.

A PPO commits to the items and quantities but leaves the delivery schedule tentative. The vendor knows the order is real; the buyer retains flexibility on timing.

When to use it:

• You're certain you'll need the items, but the timing depends on something else (project schedule, internal demand, seasonal patterns)
• You want to lock in pricing now to avoid future increases
• The vendor is willing to commit production capacity in exchange for the order

Example: A construction firm knows they'll need 200 windows for a development project breaking ground in Q3. Exact delivery dates depend on the construction schedule, which slips constantly. A planned PO commits to 200 windows at today's price; specific delivery releases get scheduled as construction phases lock in.

Planned POs are common in manufacturing and construction, where lead times matter and prices fluctuate. They're rare in service businesses where timing isn't separable from the order itself.

The key feature of a PPO is the scheduling release. The PPO sets the umbrella commitment; each release schedules a specific shipment date. This is similar to how blanket PO releases work — but with a fixed total quantity rather than a fixed maximum.

3. Blanket purchase order (BPO)

Use a blanket PO when you'll order the same items from the same vendor repeatedly over time.

A blanket PO sets pricing and terms for a defined period (usually 6–12 months), with a maximum total quantity or value. Individual shipments under the blanket are issued as releases.

When to use it:

• You buy the same items from the same vendor regularly
• Pricing is stable enough to lock in
• The admin overhead of issuing fresh POs each time is meaningful

Example: A restaurant orders produce from the same wholesaler twice a week. Instead of 100+ POs a year, they negotiate a blanket PO covering all standard produce items, with locked pricing, for 12 months. Each delivery is a release against the blanket.

Blanket POs trade upfront negotiation effort for ongoing administrative savings. They're standard in industries with predictable recurring purchases — restaurants, manufacturers, healthcare, facilities management.

For a deeper dive, see what is a blanket purchase order.

4. Contract purchase order

Use a contract PO when you want to formalize a vendor relationship without committing to specific quantities or delivery schedules.

A contract PO documents agreed terms — pricing structure, payment terms, quality standards, dispute resolution — but doesn't commit either party to specific transactions. Individual orders are issued as separate POs that reference the contract PO.

When to use it:

• You're entering a long-term vendor relationship
• You want pricing and terms documented before any actual orders flow
• The volume and timing of future orders is genuinely unknown
• Multiple cost centers or business units may issue orders against the same contract

Example: A growing SaaS company signs a contract PO with a managed services provider covering hourly rates for various engineering tiers, payment terms, IP ownership, and confidentiality. As specific projects come up over the next year, individual project POs reference the contract PO for terms and only specify the project-specific scope and budget.

Contract POs are the foundation for master service agreements (MSAs) in professional services and staffing. They're the procurement equivalent of "we agreed in principle; here's the framework for whatever specifically we end up doing."

Choosing between PO types: the decision tree

Is this a one-off purchase with all details known?
├─ Yes → Standard PO
└─ No → Will you order the same items repeatedly?
        ├─ Yes → Are prices stable enough to lock in?
        │       ├─ Yes → Blanket PO
        │       └─ No → Standard POs each time, or contract PO
        └─ No → Do you know quantities but not timing?
                ├─ Yes → Planned PO
                └─ No → Contract PO (framework now, specifics later)

This isn't dogma — businesses combine PO types all the time. A common pattern is a contract PO at the master level, with blanket POs for predictable categories and standard POs for one-offs underneath.

Real-world combinations

Manufacturing company:

• Contract PO with primary steel supplier (annual master agreement)
• Blanket PO for standard fastener inventory (quarterly)
• Planned POs for project-specific custom components (per project)
• Standard POs for one-off equipment purchases

Healthcare clinic:

• Contract PO with medical supply distributor
• Blanket PO for routine consumables (gloves, gauze, sanitizer)
• Standard POs for specialty equipment

Construction contractor:

• Contract PO with each major subcontractor (electrical, plumbing, HVAC)
• Planned POs for materials with long lead times (windows, custom millwork)
• Standard POs for everything bought as the job progresses

Small B2B services firm:

• Standard POs for everything

The smaller and simpler your operation, the less you need beyond standard POs. The larger and more complex, the more value you get from layering the types.

Common confusion points

Is a blanket PO the same as a contract PO?

No. A blanket PO commits to a quantity (with a cap) and pricing. A contract PO commits to terms but not quantity. The blanket PO is "we'll buy up to $25,000 of these items at these prices." The contract PO is "if and when we buy from you, here are the terms."

Can a single vendor have multiple PO types active?

Yes, and it's common. You might have a contract PO for the master relationship, a blanket PO for routine items, and standard POs for one-offs that fall outside the blanket scope. As long as each PO type is used for its intended purpose, this works fine.

What about "open POs"?

"Open PO" is informal usage. It usually refers to either a blanket PO or a standard PO that hasn't been fully consumed yet. The accounting team uses "open" to mean "still has remaining commitment"; it isn't a fifth distinct PO type.

What about "spot POs" or "emergency POs"?

These are also informal. They're standard POs with expedited approval workflows for urgent purchases. The PO type itself is still "standard" — what's different is the internal handling, not the document.

When you don't need POs at all

For tiny operations with simple purchases, all of this is overkill. A solo consultant buying $40 of supplies doesn't need a PO type framework — they just need an invoice from the vendor and a credit card.

POs become valuable when:

• Multiple people approve or initiate purchases
• Order sizes get large enough that mistakes get expensive
• You need an audit trail (compliance, taxes, internal controls)
• Vendor relationships are formal enough that you want documentation

If you're growing into PO usage from "we just send invoices and pay them," start with standard POs. Add blanket POs when you notice repeated orders to the same vendor. Add planned POs when you start working on projects with long lead times. Add contract POs when you formalize major vendor relationships.

Tools and templates

• Free PO generator — for standard POs
• PO template hub — Word, Excel, PDF formats
• Blanket PO deep dive — when and how to use BPOs
• Purchase order vs invoice vs sales order — how POs fit alongside other docs

The bottom line

Four PO types, four different procurement patterns:

• Standard — one-off purchases, everything known
• Planned — known quantity, uncertain timing
• Blanket — recurring purchases, fixed period
• Contract — terms framework, no specific commitment

Most small businesses live in standard PO land and that's fine. As volume and complexity grow, the other types start paying for themselves in saved time and cleaner vendor relationships.

The mistake isn't using too few PO types — it's using a standard PO for every situation, including ones where a blanket or planned PO would save real overhead.