Blanket orders and call-offs: how to run a twelve-month agreement without over-releasing it

A customer who orders the same bracket every fortnight does not want to negotiate terms repeatedly. Neither does the supplier. A blanket order solves this by agreeing a fixed quantity and price for a set period, typically 12 months. Deliveries are then triggered through call-offs against the agreement, reducing the need for repetitive negotiations. This method, long established in manufacturing and supply chain management, streamlines procurement but requires careful control to avoid oversights.

What a blanket order is

A blanket order, also known as a framework order or call-off agreement, records three key elements:

1. The product or service
2. The total quantity committed by the customer over the agreement period
3. The unit price for that quantity

Unlike a standard sales order, a blanket order does not trigger immediate delivery. Instead, it acts as a reference for future call-offs, which are individual orders drawn from the agreement. Each call-off deducts from the remaining quantity and uses the pre-agreed price.

On the procurement side, a purchase blanket serves the same purpose: a buyer commits to a supplier for a set volume at a fixed price, with individual purchase orders acting as call-offs. Microsoft Dynamics 365 Business Central models both types as “a framework for a long-term agreement between you and your customer or vendor” (Microsoft Learn), and notes that “typically, you use a blanket order when a customer buys a large quantity that you deliver in small shipments over a period of time”.

For example, a customer agrees to buy 1,000 units of a component over a year at £5 per unit. A call-off for 100 units creates a sales order priced at £500, reducing the remaining quantity to 900. This simplifies the ordering process while securing pricing stability for both parties.

Common pitfalls of manual blanket order management

When managed outside a system—such as in spreadsheets or manually tracked by account managers—blanket orders frequently fail in predictable ways:

Over-release of quantities

Without automated tracking, it is easy to exceed the agreed total. A customer might take 1,100 units under the assumption they are still within the 1,000-unit agreement, leading to disputes or unprofitable deliveries.

Incorrect pricing on call-offs

If a call-off is created as a standard order, the system’s default price list may apply instead of the contract rate. This results in either overcharging (prompting customer complaints) or undercharging (reducing margins).

Unclear remaining balances

Mid-agreement, determining how much of the commitment has been used often requires manual checks across multiple orders. A sales team might spend hours reviewing order history to answer a simple query.

Lack of visibility for planning

A blanket order represents future demand, but if it exists outside the system, planners cannot factor it into production schedules or procurement. For instance, a committed 1,000 units over a year is real demand, but without system integration, it appears as zero until call-offs arrive.

Key controls for effective blanket order management

A system-integrated blanket order addresses these issues by enforcing strict rules:

1. Automatic deduction of released quantities When a call-off is created or edited, the system updates the remaining balance in real time. For example, increasing a call-off from 300 to 350 units automatically reduces the available quantity by 50. If the order is cancelled, the balance returns to its previous level.
2. Prevention of over-release The system blocks call-offs that exceed the remaining quantity. Business Central enforces the same rule: “the sales order line quantity must not exceed the quantity of the associated blanket order line. Otherwise, you can’t post the sales order” (Microsoft Learn), and once a line is fully ordered, “no other sales order can be created for the same line”. If a customer needs to increase their commitment, the blanket order must be amended first.
3. Price consistency across call-offs The blanket order’s price overrides default pricing rules. A call-off line clearly shows the source of its pricing, ensuring transparency. For example, a £5 unit price from a blanket agreement will not be overwritten by a current list price of £5.50.
4. Automatic closure of fulfilled agreements Once the total call-off quantity matches the blanket order’s agreed amount, the system closes the agreement. No further call-offs can be created without issuing a new blanket order.

Additional safeguards include copying the customer’s reference number from the blanket to each call-off, ensuring traceability. Currency settings on the blanket order also lock in the agreed pricing currency, preventing mismatches—for instance, a sterling agreement remaining unaffected if a customer’s default currency is euros.

Integrating blanket orders with planning processes

When stored in a system like Brytebuild, blanket orders provide planners with visibility into future demand. However, how this demand is treated depends on the agreement’s nature:

• Binding agreements: If a customer is contractually obligated to take the full quantity by the end date, planners can treat this as firm demand. For example, a 1,000-unit order binding until 31 December allows precise scheduling of production runs.
• Non-binding agreements: If the quantity is an estimate with no obligation, planners use it as a forecast. This might influence bulk purchasing of raw materials but with more flexibility.

Business Central reflects this distinction by keeping blanket quantities out of availability: “quantities entered on a blanket order don’t affect item availability. You can use them as a worksheet for monitoring, forecasting, and planning” (Microsoft Learn). Either way, a planner who can see that 600 of 1,000 units remain with four months left on the agreement has something to schedule; one who sees only the call-offs to date has nothing until the next one lands.

Implementing blanket orders: practical steps

Start by identifying existing agreements with customers or suppliers that involve fixed quantities and prices over time. For each, record:

• The product or service
• Agreed quantity
• Unit price
• End date
• Quantity already called off

If retrieving the last figure takes more than a few minutes, the agreement is likely poorly controlled. Manual tracking risks over-release or pricing errors on the next call-off.

For example, a supplier with 10 active blanket agreements might find that three have exceeded their original quantities due to manual data entry errors. Moving these into a system ensures released quantities are automatically tracked, call-offs use the correct pricing, and agreements close once fulfilled.

Brytebuild’s approach to blanket orders

Brytebuild raises sales and purchase blankets with agreed quantities and prices, computes released quantity live from the call-off orders, refuses a call-off beyond what remains, applies the blanket price on every call-off, and closes the agreement when it is fully released. For implementation details, see blanket orders in the Brytebuild documentation.