USE CASE · SALES

Blanket orders

Agree the rate once for the year. Call off against it when you need to.

The problem

A large customer commits to 2,000 units over twelve months at a fixed rate, delivered in monthly call-offs. Without a system record, each call-off is typed fresh, the rate drifts, and nobody knows how much of the commitment remains.

The flow, step by step

1. Create the blanket order. In Sales & CRM, a blanket order records the customer, items, agreed rate, total quantity and the from and to dates. The same document type exists in Buying for supplier agreements.

2. Call off. Each time the customer needs stock, a sales order is created referencing the blanket order. The agreed rate is applied.

3. Track usage. The blanket order shows ordered quantity against the agreed quantity for each item.

4. Deliver and bill. Each call-off goes through delivery and invoicing as usual.

5. Close out. At the end date, the blanket order shows what was used and what was not, which is the starting point for the next negotiation.

What the team sees

Sales sees remaining quantity on every agreement before taking a call-off. Planning sees the committed volume for the year, which feeds the production plan or supplier orders.

Finance gets a clean audit: every invoice on an agreement used the agreed rate. Where a call-off needs a different rate, the change is visible on the order.

On the buying side the logic is the same: a supplier blanket order fixes the price of a raw material for the year, and purchase orders draw down against it.

In the Kestrel Workspace sample, a corporate customer's 2,000-chair agreement shows 1,240 ordered across eight call-offs by October.

With AI (coming to Sundial)

Coming to Sundial: ask "which annual agreements are running behind their expected call-off pace?" and get the list, with a drafted note to each account owner. Roadmap framing; not in the product today.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us