Supply Chain & InventoryFree worksheetPDF, Excel, Word export

Blanket Purchase Order Release Schedule Worksheet

Blanket orders and scheduling agreements lock in price and capacity, but the release schedule is easy to lose track of. This worksheet shows what is left on each blanket and what the next release will cost.

Download:
Blanket POPart numberSupplierBlanket qtyReleased to dateRemainingConsumedNext release qtyUnit priceNext release valueNext release dateBlanket expiry
4,800
60%
$2,220
1,500
92.5%
$930
4,500
25%
$2,050
21,000
30%
$840
Total remaining units
31,800
Total value of next releases
$6,040
Highest consumed
92.5%
Average percent consumed
51.9%

Compare each row's remaining quantity against demand until the expiry date. A blanket that will run out before expiry needs an amendment; one that will not be used needs a review.

Blanket order monitoring from ERP data

Optional: a short review of alerting on near-expiry and near-exhaustion blankets.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

Enter one row per blanket order line. Put the total committed quantity and the quantity released so far; the sheet works out the remaining balance and the percent consumed. Enter the next planned release and its date, and the worksheet computes the release value so you can see the cash impact. Review the list weekly with your planners, not only when a supplier calls.

What to look for

A blanket that is nearly consumed well before its expiry date will run dry and force a spot buy at a worse price. A blanket with a low consumed percent near expiry means you committed to more than you used, which may carry a take-or-pay obligation depending on the terms. Read the contract: some blankets let the supplier invoice unused quantity, others simply lapse.

  • Over 80 percent consumed: plan the amendment now
  • Low consumption near expiry: discuss extension or cancellation terms
  • Check price breaks: releases often carry the blanket price only inside the term

ERP equivalents

In SAP the equivalent is a scheduling agreement or contract with releases against it. In Oracle EBS it is a blanket purchase agreement with releases, in NetSuite a blanket purchase order, and in Dynamics 365 a purchase agreement. Each system tracks released quantity, so use the ERP as the source and this worksheet as the planner's review view.

Common mistakes

Releasing against the wrong blanket when two exist for the same part, forgetting the expiry date, and letting releases run above the committed quantity without an amendment are the usual failures. Another is releasing in lumps that do not match the supplier's ship pattern, which inflates inventory and the supplier's cost.

Frequently Asked Questions

What is the difference between a blanket order and a scheduling agreement?

A blanket order commits to a total quantity or value over a period with releases called as needed. A scheduling agreement, common in SAP, also carries a delivery schedule the supplier follows. Both fix price and terms for repeated purchases.

Can releases exceed the blanket quantity?

Only with an amendment or a new agreement. Most ERPs warn or block over-release, but some do not, so check the remaining balance before releasing and confirm tolerance with the supplier.

How often should releases be reviewed?

Weekly for fast-moving parts and monthly for slow ones. Review against the MRP forecast so the release quantity matches expected need, not just the supplier's preferred batch.

Do blankets reduce lead time?

They can, because the supplier plans capacity against a known commitment. The benefit depends on terms, so record the agreed release lead time in your item master after negotiation.

If you manage hundreds of blankets and releases, we can build alerts from your ERP data for near-expiry and near-exhaustion blankets.