This module extends the functionality of Sale Order to support Blanket
+Order and Call of Order.
+
Blanket Order
+
A Blanket Order is a standard sales order with the following specific
+features:
+
+- Type: Classified as “Blanket Order”.
+- Defined Duration: Includes a validity period (end date).
+- Payment Terms: Allows selection of preferred terms (e.g., 90 days end
+of month, upon delivery, etc.).
+- Invoicing Policy: Can be based on product settings or the order
+itself.
+- Stock Reservation: Allows advance reservation of sold quantities.
+- Handling Unfulfilled Quantities: Provides options for dealing with
+undelivered quantities upon order expiration.
+- Prices are calculated based on existing rules since it is a standard
+sales order type.
+
+
The blanket order serves as the central element triggering stock
+management and invoicing mechanisms.
+
+
Stock Management
+
Delivered quantities are tracked on the sales order lines as with
+regular sales orders. By default, the stock is not reserved upon
+confirmation of the blanket order. This is achieved by using the OCA
+module
+sale_manual_delivery.
+As a result, the stock will be reserved only when a call-off order is
+created for the quantity to be delivered.
+
In some cases, you may want to reserve stock upon confirmation of the
+blanket order. This can be achieved by using the OCA module
+sale_order_blanket_order_stock_prebook.
+This module extends the functionality of Sale Blanket Order to support
+the reservation of stock for future consumption by call-off orders. The
+reservation is done at the time of the blanket order confirmation for a
+consumption starting at the validity start date of the blanket order.
+This behavior can be configured on the blanket order.
+
+
+
Invoicing
+
Standard invoicing policies apply (e.g., invoice on order or on
+delivery). Payment terms are configurable per order. Prepayment can be
+enforced by configuring the invoicing policy at the order level using
+the OCA module
+sale_invoice_policy.
+
+
+
Consumption Management
+
A wizard will be available on the blanket order to initiate a delivery.
+It allows users to select products and quantities for delivery. This
+action creates a Call-off Order linked to the blanket order.
+
+
+
Standard Sales Orders
+
To support existing workflows (e.g., e-commerce), call-off orders can be
+generated transparently from standard sales orders based on product and
+availability:
+
Entire orders may be converted into call-off orders if all products are
+linked to a blanket order. Mixed orders split call-off items into a new
+call-off order, with both confirmed within the available quantities of
+the blanket order.
+
Table of contents
+
+
Use Cases / Context
+
When a company sells the same products to the same customers on a
+regular basis, it’s a common business practice to create a sale
+framework that defines the terms and conditions of the sales.
+
If you need a way to define:
+
+- the terms and conditions of the sales,
+- the payment terms,
+- the delivery terms,
+
+
and also secure the quantities of the products to be delivered, the sale
+framework module is the right choice.
+
This module introduces 2 new kinkds of sale orders:
+
+- Sale Blanket Order: This is a sale order that defines the terms and
+conditions of the sales, the payment terms, the delivery terms, and
+secures the quantities of the products to be delivered. It is used to
+create sale orders that will be delivered in the future.
+- Call of order: This is a sale order that is created to consume the
+quantities of the products secured in the sale blanket order.
+
+
Others modules can be used to provide the same kind of features. For
+example, the module
+(sale_blanket_order)[https://pypi.org/project/odoo-addon-sale-blanket-order]
+also defines the concept of sale blanket order. The main difference
+between the two modules is that the sale framework module extends the
+sale order model to add the sale blanket order and the call of order.
+This allows to keep the benefits of all the extensions made on the sale
+order model by other modules without having to adapt them to the sale
+blanket order model (discount, invoicing; inventory process, …).
+
+
Bug Tracker
+
Bugs are tracked on GitHub Issues.
+In case of trouble, please check there if your issue has already been reported.
+If you spotted it first, help us to smash it by providing a detailed and welcomed
+feedback.
+
Do not contact contributors directly about support or help with technical issues.
+
+
Credits
+
+
+
+
Other credits
+
The development of this module has been financially supported by:
+
+
+
+
Maintainers
+
This module is maintained by the OCA.
+
+
+
+
OCA, or the Odoo Community Association, is a nonprofit organization whose
+mission is to support the collaborative development of Odoo features and
+promote its widespread use.
+
This module is part of the OCA/sale-workflow project on GitHub.
+
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
+
+