OCA modules for Odoo

This module extends the functionality of purchase to allow the price and the discount of the supplier-info to be updated automatically for each product of the purchase when it is confirmed. This will allow that when a purchase order is created, the suggested price and suggested discount for those products is the last one purchased.

Adds a configurable type on the purchase orders. This type can be used in filters and groupbys.

Adds a dashboard for Purchase Orders based on Purchase Order Types.

This module adds support for UBL, the Universal Business Language (UBL) standard, on purchase orders. The UBL 2.1 standard became the ISO/IEC 19845 standard in December 2015 (cf the official announce). With this module, when you generate the purchase order or RFQ report: · on a draft/RFQ/Bid Received purchase order, the PDF file will have an embedded XML Request For Quotation file compliant with the UBL 2.1 or 2.0 standard. · on an approved purchase order, the PDF file will…

If you use the py3o reporting engine (module report_py3o_fusion_server from the reporting-engine OCA project) to generate your PDF purchase orders/RFQs and you want these PDF documents to have an embedded UBL XML file, this module is for you!

Show uninvoiced amount on purchase order tree.

Show uninvoiced amount on purchase order line tree.

This module allows to add/modify of all the variants of a product in a direct screen without the need of handling them one by one

In Purchase Order show only products available from the selected vendor. This is a duplicated of https://github.com/OCA/purchase-workflow/tree/14.0/purchase_allowed_product, and shouldn't be migrated.

Display weight and volume in Purchase Order Line. · Display total order weight and total order volume in Purchase Order, tab "Other information".

This module adds a clickable link to the "Source Document" in Purchase Orders. This module does nothing by itself, it needs some submodules to compute links to other documents.

This module adds a clickable link to Sale Orders on the Source Document of Purchase Orders. It depends on the base module: purchase_origin_link

Use packaging in supplierinfo · Use uom set in the packaging instead of purchase uom for purchase · Add minimum quantity measure unit in supplierinfo · On purchase order line compute the quantity with the quantity and unit of measure

Allows you to set a default packaging on the order line using the first packaging defined in the configuration of the respective product Default packaging quantity is then set based on purchase order line quantity divided by product packaging quantity. Packaging quantity is rounded up as we sell it by units. For example: We won't sell 0.5 Boxes or 1.5 Pallets.

Compute on a purchase order the amount of transport packing (e.g. pallets). The computation is on each line and a total is computed on the order. Each product needs a packaging definition for this transport packaging to allow the computation. The transport packaging is a packaging level you must first configure in the settings (typically the Tertiary packaging level, i.e. pallet).

This module displays packaging data (quantity and type) in: · Purchase order printed reports. · Purchase BI reports.

Require partners to be approved before thay can be used on Purchase Orders. This does not require, but was designed to be used with Partner Tier Validation (partner_tier_validation module). Using that module, rules can be configured on who must approve, before the Partner Stage can be changed to an apptoved one.

This module adds incoterms for suppliers and purchase order: · incoterm modes · incoterm address Based on Partner/Supplier It will add Incoterm address.

This module limits the partners to be selected in the purchases orders according to the "Selectable in orders" field.

This module adds a "picking status" field on Purchase Orders, displaying the general state of the pickings related to that Order.