| REPOSITORY | |
|---|---|
| REPOSITORY | OCA/sale-workflow |
| GIT | |
| GIT | https://github.com/OCA/sale-workflow.git |
| GIT FOLDER | |
| GIT FOLDER | https://github.com/OCA/sale-workflow/tree/10.0/pricelist_share_companies |
| VERSION | |
| VERSION | 1.0 |
| CATEGORY | |
| CATEGORY | Generic Modules/Projects & Services |
| LICENSE | |
| LICENSE | LGPL-3 |
| APPLICATION | |
| APPLICATION | No |
| AUTO-INSTALLABLE | |
| AUTO-INSTALLABLE | No |
| AUTHORS | |
| AUTHORS | Odoo Community Association (OCA), Camptocamp |
| MAINTAINERS | |
| MAINTAINERS | Odoo Community Association (OCA), Camptocamp |
| COMMITTERS | |
| COMMITTERS | Pedro M. Baeza, Denis Roussel |
| WEBSITE | |
| WEBSITE | https://github.com/OCA/sale-workflow |
| LAST TRACKING UPDATE | |
| LAST TRACKING UPDATE | 2026-07-06 00:19:56 |
| ODOO DEPENDENCIES | |
| ODOO DEPENDENCIES |
odoo/odoo: - product - base - decimal_precision - base_setup - web_kanban - web - bus - web_tour - report |
| PYTHON DEPENDENCIES | |
| PYTHON DEPENDENCIES | Not have |
| SYSTEM DEPENDENCIES | |
| SYSTEM DEPENDENCIES | Not have |
| DESCRIPTION | |
| DESCRIPTION | In OpenERP, product prices (cost, list) are expressed in the currency of the price_type (by default the same than your company currency). The idea here is to have the same products between compagnies (with each one their own currency through different price_type and different costs) but only one pricelist for all. For that purpose, we add a company_id on price_type object and a rule to separate them for each company. This way, the price computation of pricelist will take the right price_type currency as based price. Concretely, to have a different cost price for a second company, you have to : - Create a new standard price on product.template - Create a new 'Price Type' on this new field, with the desired currency and assigned to the new currency - Assign the existing 'Cost Price' to your main company - On the setup of each company, in the 'Configuration''s Tab, select the product field used for the cost The Price Type used is the first one found for the cost field configured on the company. To ensure the right Price Type is selected, you have to put the company on the Price Types, and according to the security rule created, you will have access only to the right Price Type. Example: I create a product A. it has 2 fields for cost prices : Cost Price and Cost Price CH Price type Sale company A : Cost Price / EUR Price type Sale company B : Cost Price CH / CHF Cost Price of Product A, company A: 60 Cost Price CH of Product A, company B: 70 Product A in company A: The cost price is 60 * currency rate Product A in company B: The cost price is 70 * currency rate |
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
company_form_price_fields |
res.company.form.inherit | res.company | data | Inherits base.view_company_form |
product_price_type_view |
product.price.type.form | product.price.type | field | Inherits product.product_price_type_view |
No new fields.
Public methods (1)search(self, cr, uid, args, offset=0, limit=None, order=None, context=None, count=False)
No new fields.
Public methods (0)No public methods.
| REPOSITORY | |
|---|---|
| REPOSITORY | OCA/sale-workflow |
| GIT | |
| GIT | https://github.com/OCA/sale-workflow.git |
| GIT FOLDER | |
| GIT FOLDER | https://github.com/OCA/sale-workflow/tree/9.0/pricelist_share_companies |
| VERSION | |
| VERSION | 1.0 |
| CATEGORY | |
| CATEGORY | Generic Modules/Projects & Services |
| LICENSE | |
| LICENSE | LGPL-3 |
| APPLICATION | |
| APPLICATION | No |
| AUTO-INSTALLABLE | |
| AUTO-INSTALLABLE | No |
| AUTHORS | |
| AUTHORS | Odoo Community Association (OCA), Camptocamp |
| MAINTAINERS | |
| MAINTAINERS | Odoo Community Association (OCA), Camptocamp |
| COMMITTERS | |
| COMMITTERS | |
| WEBSITE | |
| WEBSITE | http://camptocamp.com |
| LAST TRACKING UPDATE | |
| LAST TRACKING UPDATE | 2026-07-06 00:15:20 |
| ODOO DEPENDENCIES | |
| ODOO DEPENDENCIES |
odoo/odoo: - product - base - decimal_precision - base_setup - web_kanban - web - bus - report |
| PYTHON DEPENDENCIES | |
| PYTHON DEPENDENCIES | Not have |
| SYSTEM DEPENDENCIES | |
| SYSTEM DEPENDENCIES | Not have |
| DESCRIPTION | |
| DESCRIPTION | In OpenERP, product prices (cost, list) are expressed in the currency of the price_type (by default the same than your company currency). The idea here is to have the same products between compagnies (with each one their own currency through different price_type and different costs) but only one pricelist for all. For that purpose, we add a company_id on price_type object and a rule to separate them for each company. This way, the price computation of pricelist will take the right price_type currency as based price. Concretely, to have a different cost price for a second company, you have to : - Create a new standard price on product.template - Create a new 'Price Type' on this new field, with the desired currency and assigned to the new currency - Assign the existing 'Cost Price' to your main company - On the setup of each company, in the 'Configuration''s Tab, select the product field used for the cost The Price Type used is the first one found for the cost field configured on the company. To ensure the right Price Type is selected, you have to put the company on the Price Types, and according to the security rule created, you will have access only to the right Price Type. Example: I create a product A. it has 2 fields for cost prices : Cost Price and Cost Price CH Price type Sale company A : Cost Price / EUR Price type Sale company B : Cost Price CH / CHF Cost Price of Product A, company A: 60 Cost Price CH of Product A, company B: 70 Product A in company A: The cost price is 60 * currency rate Product A in company B: The cost price is 70 * currency rate |
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
company_form_price_fields |
res.company.form.inherit | res.company | data | Inherits base.view_company_form |
product_price_type_view |
product.price.type.form | product.price.type | field | Inherits product.product_price_type_view |
No new fields.
Public methods (1)search(self, cr, uid, args, offset=0, limit=None, order=None, context=None, count=False)
No new fields.
Public methods (0)No public methods.
| REPOSITORY | |
|---|---|
| REPOSITORY | OCA/sale-workflow |
| GIT | |
| GIT | https://github.com/OCA/sale-workflow.git |
| GIT FOLDER | |
| GIT FOLDER | https://github.com/OCA/sale-workflow/tree/8.0/pricelist_share_companies |
| VERSION | |
| VERSION | 1.0 |
| CATEGORY | |
| CATEGORY | Generic Modules/Projects & Services |
| LICENSE | |
| LICENSE | LGPL-3 |
| APPLICATION | |
| APPLICATION | No |
| AUTO-INSTALLABLE | |
| AUTO-INSTALLABLE | No |
| AUTHORS | |
| AUTHORS | Odoo Community Association (OCA), Camptocamp |
| MAINTAINERS | |
| MAINTAINERS | Odoo Community Association (OCA), Camptocamp |
| COMMITTERS | |
| COMMITTERS | Stéphane Bidoul, Pedro M. Baeza |
| WEBSITE | |
| WEBSITE | http://camptocamp.com |
| LAST TRACKING UPDATE | |
| LAST TRACKING UPDATE | 2026-07-06 00:11:21 |
| ODOO DEPENDENCIES | |
| ODOO DEPENDENCIES |
odoo/odoo: - product - base - decimal_precision - base_setup - web_kanban - web - report |
| PYTHON DEPENDENCIES | |
| PYTHON DEPENDENCIES | Not have |
| SYSTEM DEPENDENCIES | |
| SYSTEM DEPENDENCIES | Not have |
| DESCRIPTION | |
| DESCRIPTION | In OpenERP, product prices (cost, list) are expressed in the currency of the price_type (by default the same than your company currency). The idea here is to have the same products between compagnies (with each one their own currency through different price_type and different costs) but only one pricelist for all. For that purpose, we add a company_id on price_type object and a rule to separate them for each company. This way, the price computation of pricelist will take the right price_type currency as based price. Concretely, to have a different cost price for a second company, you have to : - Create a new standard price on product.template - Create a new 'Price Type' on this new field, with the desired currency and assigned to the new currency - Assign the existing 'Cost Price' to your main company - On the setup of each company, in the 'Configuration''s Tab, select the product field used for the cost The Price Type used is the first one found for the cost field configured on the company. To ensure the right Price Type is selected, you have to put the company on the Price Types, and according to the security rule created, you will have access only to the right Price Type. Example: I create a product A. it has 2 fields for cost prices : Cost Price and Cost Price CH Price type Sale company A : Cost Price / EUR Price type Sale company B : Cost Price CH / CHF Cost Price of Product A, company A: 60 Cost Price CH of Product A, company B: 70 Product A in company A: The cost price is 60 * currency rate Product A in company B: The cost price is 70 * currency rate |
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
company_form_price_fields |
res.company.form.inherit | res.company | data | Inherits base.view_company_form |
product_price_type_view |
product.price.type.form | product.price.type | field | Inherits product.product_price_type_view |
No new fields.
Public methods (1)search(self, cr, uid, args, offset=0, limit=None, order=None, context=None, count=False)
No new fields.
Public methods (0)No public methods.
| REPOSITORY | |
|---|---|
| REPOSITORY | OCA/sale-workflow |
| GIT | |
| GIT | https://github.com/OCA/sale-workflow.git |
| GIT FOLDER | |
| GIT FOLDER | https://github.com/OCA/sale-workflow/tree/7.0/pricelist_share_companies |
| VERSION | |
| VERSION | 1.0 |
| CATEGORY | |
| CATEGORY | Generic Modules/Projects & Services |
| LICENSE | |
| LICENSE | LGPL-3 |
| APPLICATION | |
| APPLICATION | No |
| AUTO-INSTALLABLE | |
| AUTO-INSTALLABLE | No |
| AUTHORS | |
| AUTHORS | Odoo Community Association (OCA), Camptocamp |
| MAINTAINERS | |
| MAINTAINERS | Odoo Community Association (OCA), Camptocamp |
| COMMITTERS | |
| COMMITTERS | Yannick Vaucher, Guewen Baconnier, Lorenzo Battistini, Alexandre Fayolle, moylop260 |
| WEBSITE | |
| WEBSITE | http://camptocamp.com |
| LAST TRACKING UPDATE | |
| LAST TRACKING UPDATE | 2026-07-06 00:07:13 |
| ODOO DEPENDENCIES | |
| ODOO DEPENDENCIES |
odoo/odoo: - product - base - process - web - decimal_precision - base_setup - web_kanban |
| PYTHON DEPENDENCIES | |
| PYTHON DEPENDENCIES | Not have |
| SYSTEM DEPENDENCIES | |
| SYSTEM DEPENDENCIES | Not have |
| DESCRIPTION | |
| DESCRIPTION | In OpenERP, product prices (cost, list) are expressed in the currency of the price_type (by default the same than your company currency). The idea here is to have the same products between compagnies (with each one their own currency through different price_type and different costs) but only one pricelist for all. For that purpose, we add a company_id on price_type object and a rule to separate them for each company. This way, the price computation of pricelist will take the right price_type currency as based price. Concretely, to have a different cost price for a second company, you have to : - Create a new standard price on product.template - Create a new 'Price Type' on this new field, with the desired currency and assigned to the new currency - Assign the existing 'Cost Price' to your main company - On the setup of each company, in the 'Configuration''s Tab, select the product field used for the cost The Price Type used is the first one found for the cost field configured on the company. To ensure the right Price Type is selected, you have to put the company on the Price Types, and according to the security rule created, you will have access only to the right Price Type. Example: I create a product A. it has 2 fields for cost prices : Cost Price and Cost Price CH Price type Sale company A : Cost Price / EUR Price type Sale company B : Cost Price CH / CHF Cost Price of Product A, company A: 60 Cost Price CH of Product A, company B: 70 Product A in company A: The cost price is 60 * currency rate Product A in company B: The cost price is 70 * currency rate |
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
company_form_price_fields |
res.company.form.inherit | res.company | data | Inherits base.view_company_form |
product_price_type_view |
product.price.type.form | product.price.type | field | Inherits product.product_price_type_view |
No new fields.
Public methods (1)search(self, cr, uid, args, offset=0, limit=None, order=None, context=None, count=False)
No new fields.
Public methods (0)No public methods.
| REPOSITORY | |
|---|---|
| REPOSITORY | OCA/sale-workflow |
| GIT | |
| GIT | https://github.com/OCA/sale-workflow.git |
| GIT FOLDER | |
| GIT FOLDER | https://github.com/OCA/sale-workflow/tree/6.1/pricelist_share_companies |
| VERSION | |
| VERSION | 1.0 |
| CATEGORY | |
| CATEGORY | Generic Modules/Projects & Services |
| LICENSE | |
| LICENSE | LGPL-3 |
| APPLICATION | |
| APPLICATION | No |
| AUTO-INSTALLABLE | |
| AUTO-INSTALLABLE | No |
| AUTHORS | |
| AUTHORS | Odoo Community Association (OCA), Camptocamp |
| MAINTAINERS | |
| MAINTAINERS | Odoo Community Association (OCA), Camptocamp |
| COMMITTERS | |
| COMMITTERS | Alexandre Fayolle, Joël Grand-Guillaume |
| WEBSITE | |
| WEBSITE | http://camptocamp.com |
| LAST TRACKING UPDATE | |
| LAST TRACKING UPDATE | 2026-07-06 00:04:05 |
| ODOO DEPENDENCIES | |
| ODOO DEPENDENCIES |
odoo/odoo: - product - base - process - decimal_precision |
| PYTHON DEPENDENCIES | |
| PYTHON DEPENDENCIES | Not have |
| SYSTEM DEPENDENCIES | |
| SYSTEM DEPENDENCIES | Not have |
| DESCRIPTION | |
| DESCRIPTION | In OpenERP, product prices (cost, list) are expressed in the currency of the price_type (by default the same than your company currency). The idea here is to have the same products between compagnies (with each one their own currency through different price_type and different costs) but only one pricelist for all. For that purpose, we add a company_id on price_type object and a rule to separate them for each company. This way, the price computation of pricelist will take the right price_type currency as based price. Concretely, to have a different cost price for a second company, you have to : - Create a new standard price on product.template - Create a new "Price Type" on this new field, with the desired currency and assigned to the new currency - Assign the existing "Cost Price" to your main company - On the setup of each company, in the "Configuration"'s Tab, select the product field used for the cost The Price Type used is the first one found for the cost field configured on the company. To ensure the right Price Type is selected, you have to put the company on the Price Types, and according to the security rule created, you will have access only to the right Price Type. Example: I create a product A. it has 2 fields for cost prices : Cost Price and Cost Price CH Price type Sale company A : Cost Price / EUR Price type Sale company B : Cost Price CH / CHF Cost Price of Product A, company A: 60 Cost Price CH of Product A, company B: 70 Product A in company A: The cost price is 60 * currency rate Product A in company B: The cost price is 70 * currency rate |
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
company_form_price_fields |
res.company.form.inherit | res.company | data | Inherits base.view_company_form |
product_price_type_view |
product.price.type.form | product.price.type | field | Inherits product.product_price_type_view |
No models found for this module.