A purchasing framework sets agreed terms and scope for a period; a specific PO or release identifies what is being ordered now, for which project and when. Track the framework scope, issued orders and actual receipts separately. Do not count them as separate commitments or deliveries without checking their definitions. The approved document and terms determine obligations, not the label “blanket” alone.
1. Distinguish the framework from an order to supply
For recurring purchases of the same material, a team can agree items, terms and a period with a supplier, then document specific supply orders as needed. A framework may include a price, quantity or scope limit, but check the actual agreement: a forecast is not necessarily an issued order, and a ceiling is not delivered quantity.
A standard PO can directly specify the item, quantity, jobsite and required date. An order under a blanket arrangement also needs a reference to the applicable framework and terms. These two layers do not remove the need for authorization, a supplier response and receiving checks.
Oracle describes NetSuite blanket orders with items and terms from which linked POs are released. This illustrates another system’s implementation; it does not establish automatic blanket-order releases in Novapro. Terminology and mechanisms can vary across systems and organizations.
Further reading: Oracle NetSuite: blanket purchase orders and linked POs
2. Define what each release must identify
Keep the supplier, buying entity, items and specification, units, period, revision and approved terms with the framework record. Define whether the monitored limit concerns quantity, amount or another measure; do not subtract kilograms from a monetary limit or combine unlike items merely because they share a supplier.
For each specific order, record the framework and line reference, project and delivery destination, quantity, date, relevant terms and authorization. An internal request or planned shipment remains in that state until the authorized person approves the order and it is issued through the established process. Record the supplier’s response separately.
3. Worked example: a 1,000-unit framework is not 1,000 received
This fictional operational example contains no customer, price or assumption about a contractual commitment. For planning only, the team uses a ceiling of 1,000 units of one item in one unit of measure. Two linked orders were issued: A for 200 units and B for 300. Receiving verified 150 against A and 100 against B.
Issued orders total 500 units; receipts total 250; the remaining quantity on those orders is 250. Another 500 units of planning capacity has not been released into orders. These are different balances: ordered but not received, and planned scope not yet ordered. This does not establish that the supplier must deliver the entire framework quantity.
Do not add the 1,000-unit framework to the 500 released units and report 1,500 ordered. The 250 received units are part of the 500, not another order. Show any third-order request separately until authorized and issued. This calculation assumes no cancellations, returns or revision changes.
| Linked order | Quantity ordered | Verified receipts | Open on this order |
|---|---|---|---|
| Order A | 200 | 150 | 50 |
| Order B | 300 | 100 | 200 |
| Total issued orders | 500 | 250 | 250 |
4. Link changes and receipts to the correct layer
A framework change is not a reason to automatically rewrite every issued PO. Establish what changed, from when, which orders are affected and who approved it. A canceled order, a returned receipt and an unissued request are different events; they are not the same movement in the tracking record.
Microsoft’s Business Central documentation preserves links between blanket orders and related orders and documents, and states that its illustrated sales process also applies to purchasing. For a team worksheet, the useful principle is retaining the document reference. Its automatic updates are not a claim about existing Novapro functionality.
Link each delivery ticket to the appropriate PO and line, and each invoice to the deliveries and terms it covers. A “framework used” label alone does not prove arrival or invoice approval. Review open quantities in the order register with the framework reference, rather than adding another total that counts the same scope twice.
Further reading: Microsoft Learn: blanket orders and related documents
5. Choose a process the next reviewer can trace
A blanket arrangement can be worth evaluating for recurring purchases whose terms must remain traceable over a period. An individual PO may be clearer for a specific requirement with a defined specification and date. The choice depends on the process and approved terms; this guide promises no savings, better price or interpretation of contractual obligations.
Suggested worksheet: framework and revision ___, item and unit ___, period ___, limit definition ___, linked PO ___, issued quantity ___, receipts ___, revision or cancellation ___, balance under the stated definition ___, owner ___, review date ___. This is a proposed working record, not a description of product fields or a blanket-order module.
Novapro brings POs, suppliers and documents into the project context. A demo can examine your orders, receiving and project references; support for blanket agreements, limits or automatic releases must be verified separately. Prepare a sample without sensitive information and distinguish current capabilities from future customization.
Practical checklist
- Identify the framework, period and applicable revision
- Define whether the limit measures quantity, amount or something else
- Link every issued PO to the framework and project
- Keep planned requests separate from authorized issued orders
- Attach receipts and changes to the PO without double counting
- Give each balance a definition, owner and review date
Prepare sample POs and receipts without sensitive information. Explore project references, documents and the definitions your team needs.
Request a procurement demoFrequently asked questions
Does a blanket PO mean the whole quantity has already been ordered?
The label alone does not establish that. Check the terms and the organization’s definitions of the framework and an issued order. Track the agreed scope separately from specific supply orders.
How does unused framework capacity differ from an open PO quantity?
An open PO balance compares ordered and received quantities under the relevant definition. Unused framework capacity may describe scope not yet released into orders. State what each measures rather than adding them as if they were the same open quantity.
Does a partial delivery require a blanket purchase order?
Not necessarily. A standard PO can also arrive in multiple deliveries. A blanket arrangement concerns purchasing terms and process; a partial delivery describes what arrived against a specific order.
Keep reading
Changing a Purchase Order After Approval: Keep the Versions Clear →
How to Track Partial Deliveries and Delivery Tickets →
Open Purchase Order Report: What to Check Before Closing a PO →