Scheduling Agreement vs Blanket Order

Buyers use three long-term instruments to commit volume without cutting a new purchase order every week, and people mix them up constantly: the blanket order, the standing order, and the scheduling agreement. They look similar on a screen. The difference is where the delivery schedule lives and how it gets updated. Get that wrong during EDI setup and you either over-ship, under-ship, or consume available-to-promise inventory you were not supposed to touch yet.

If you supply automotive, aerospace, or any high-volume manufacturing account, you will meet all three. Here is what each one actually does.

What Is a Blanket Order?

A blanket order is a single agreement that commits a total quantity and price over a period, which the buyer then draws against through separate release documents called call-offs. The blanket itself is a ceiling, not a shipping instruction. You do not ship anything against a blanket until a release arrives.

The important accounting point: the committed blanket quantity does not consume available-to-promise (ATP) inventory until a release is issued. A blanket for 100,000 units over a year is a commitment, but only the released 5,000 units for next week actually reserve stock. Treat the whole blanket as demand and you will show phantom shortages.

In X12 terms, the blanket usually starts as an EDI 850 purchase order flagged as a blanket, and each release comes as a subsequent 850 or an 862 shipping schedule referencing the original number. Changes to the blanket flow through an EDI 860 purchase order change. For release mechanics in detail, see our blanket purchase order guide.

What Is a Standing Order?

A standing order is a recurring order for a fixed quantity delivered on a fixed cadence, set up once and repeated until someone cancels it. Think of a distributor that takes 40 cases of the same SKU every Tuesday. There is no forecast and no per-release negotiation. The template repeats.

Standing orders are common in food service, DSD beverage, and consumables. They are simple to automate because nothing changes between cycles. The risk is the opposite of a blanket: because the quantity is fixed, a standing order does not flex when the buyer's real demand moves, so it tends to build either backlog or excess unless someone reviews it. Picture that standing 40-cases-every-Tuesday order still arriving months after the buyer's actual sell-through fell to 25 cases a week: nobody cancels it, nobody flags it, and the surplus quietly piles up in the buyer's back room until someone finally audits the recurring orders.

Most ERPs model a standing order as a recurring sales order template rather than a distinct document type. It is the least EDI-driven of the three.

What Is a Scheduling Agreement?

A scheduling agreement is a blanket order with the delivery schedule built directly into the agreement, updated continuously by EDI rather than by discrete release orders. The term comes from SAP, where it is a formal document type, but the concept exists in every major ERP under different names.

Instead of the buyer cutting a fresh release each week, the buyer transmits a rolling schedule. Firm dates for the near term, forecast dates further out, all against the same agreement number. The supplier reads the schedule lines and ships to them. This is the model automotive OEMs run on, because it lets them adjust a supplier's daily ship plan without renegotiating the contract.

The two EDI transactions that feed a scheduling agreement are the EDI 830 planning schedule (forecast and material authorization) and the EDI 862 shipping schedule (firm, near-term ship instructions). We break the difference apart in EDI 830 vs 862.

How SAP Models It

In SAP SD (the sell side), scheduling agreements use document types LZ (with delivery schedules) and LP or LPA (forecast and JIT variants), as covered in SAP's own documentation. On the MM buy side, you create a scheduling agreement with transaction ME31L, maintain schedule lines with ME38, generate releases with ME84, and the system stores the transmitted releases in table EKEK.

The reason the schedule lives inside the agreement is control. The OEM authorizes you to fabricate up to one cumulative point and buy raw material to a further-out point, capping their liability if the program is cancelled. That cumulative-quantity mechanism is its own topic, covered in cumulative quantity accounting in automotive EDI.

Rule of thumb: if the buyer sends you a rolling forecast that firms up as dates approach, you are on a scheduling agreement, not a blanket. If the buyer cuts a discrete release each time, it is a blanket.

The Cross-ERP Rosetta Table

Every ERP implements the same idea with a different label, which is why teams argue about definitions when they actually mean the same thing. Use this table to translate.

ERP	Instrument name	Create / release mechanism	EDI feed
SAP	Scheduling agreement (LZ / LP / LPA)	ME31L create, ME38 schedule lines, ME84 release, table EKEK	830, 862
SAP	Blanket / outline agreement (contract)	Contract plus release orders	850 releases
Oracle JD Edwards	Blanket order plus release	Blanket order entry, release with P420111	830, 862, 850
Microsoft Dynamics 365 F&O	Purchase / sales agreement plus release order	Agreement, then release order	830, 862, 850
Infor M3	Delivery schedule	RSS100 delivery schedule maintenance	830, 862
SYSPRO	Blanket sales order with releases	Blanket sales order, release lines	850 releases

Microsoft documents the agreement-and-release-order pattern in its supply chain guidance (learn.microsoft.com, Purchase and sales agreements). The ASC X12 standard defines the underlying transaction sets that carry the schedule (x12.org transaction sets).

Which One Should You Expect?

Match the instrument to the buyer's demand pattern. Stable, unchanging demand suits a standing order. A committed annual volume with lumpy, buyer-initiated pulls suits a blanket. Continuous production demand that flexes weekly suits a scheduling agreement.

The operational mistake that costs money is treating a scheduling agreement like a blanket. If you wait for a discrete release that never comes, because the schedule was already sitting in the 830, you miss ship dates and take a scorecard hit. Read the inbound EDI, confirm which model the account uses, and configure your order pipeline to match.

You can inspect any inbound 830 or 862 to see how the schedule lines and quantities are structured with our free EDI Inspector before you wire it into your ERP. For the broader connection between these documents and your back office, see ERP integration and order processing automation.

Frequently Asked Questions

Is a scheduling agreement the same as a blanket purchase order?

Not quite. A scheduling agreement is a type of blanket where the delivery schedule is embedded in the agreement and updated by EDI. A plain blanket purchase order commits quantity and price but relies on separate release documents to authorize each shipment. The scheduling agreement automates that release step through 830 and 862 transactions.

Does a blanket order reserve inventory?

The committed blanket quantity does not consume available-to-promise inventory on its own. Only the released quantity against the blanket reserves stock. Treating the full blanket as active demand is a common configuration error that creates phantom shortages in your ERP.

What EDI documents feed a scheduling agreement?

Two transactions. The EDI 830 planning schedule carries the forecast and, in automotive, the authorization to commit labor and material. The EDI 862 shipping schedule carries firm, near-term ship or delivery instructions. They are designed to work together, with the 862 supplementing the 830.

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

A standing order ships a fixed quantity on a fixed cadence with no forecast. A scheduling agreement carries a rolling schedule that changes as the buyer's demand changes, with firm near-term dates and forecast dates further out. Standing orders are simplest; scheduling agreements handle variable production demand.

How do I tell from the EDI whether an account uses a blanket or a scheduling agreement?

Look at what arrives. Discrete releases arriving as separate 850s that reference a contract number mean a blanket. Rolling 830 or 862 schedules that firm up as dates approach mean a scheduling agreement.