How to Set Different Sales Prices in Product Template for Each Company in Odoo?

[vihanrichard]

Hello everyone,

I’ve been working with Odoo’s multi-company environment and faced an issue I think others may have run into. I want to maintain different sales prices in the same product template across multiple companies. For example, Company A should sell Product X at ₹100, while Company B should sell the same product at ₹120, without having to duplicate the product itself.

From what I’ve tested, pricelists allow some flexibility, but when dealing with hundreds or thousands of products across multiple companies, managing separate pricelists feels complex and error-prone. It becomes especially tricky when you want updates to sync properly while still maintaining company-specific pricing logic.
So here are my main questions for the community:

• What’s the most effective way to configure product pricing per company?
  
• Do you rely solely on pricelists, or is there a better method using Odoo’s native features?
  
• Is a customization required, or can this be solved with proper configuration?
  
  

If anyone has already tackled this scenario, I’d appreciate real-world examples of what worked. Also, I’d be interested in recommendations for Odoo Implementation partners or guidance from the best Odoo implementor in India who may have experience in solving such multi-company pricing structures.
Looking forward to hearing your suggestions and best practices.

Thanks in advance!

[bloomagency]

Managing Different Sales Prices for the Same Product Across Multiple Companies in Odoo
This is a common challenge in multi-company Odoo implementations, especially when businesses operate in different regions, currencies, or markets while sharing the same product catalog.

Based on our experience implementing and optimizing Odoo for businesses across multiple industries, here are the best approaches:

1. Understanding Odoo's Native Behavior
By default, Odoo stores the Sales Price (list_price) at the product template level. This means that when a product is shared across companies, the sales price is also shared. Odoo does not natively provide a company-dependent sales price field on the product template.
As a result, changing the sales price in one company will typically affect the same product in other companies if the product is shared.

2. Recommended Approach: Company-Specific Pricelists
The standard Odoo approach is to create separate pricelists for each company and assign them accordingly. Odoo allows pricelists to be linked to specific companies, making them the officially supported method for handling company-specific selling prices.
Benefits include:

• No need to duplicate products
  
• Centralized product management
  
• Support for multiple currencies
  
• Advanced pricing formulas and discounts
  
• Easy scaling across multiple companies
  

For organizations managing thousands of products, manual maintenance can be avoided through imports, automated pricing rules, or custom synchronization scripts.

3. When Pricelists Become Difficult to Manage
Many growing businesses find that managing hundreds or thousands of product-specific pricelist entries becomes cumbersome.
In such cases, we generally recommend:

• Rule-based pricing formulas
  
• Category-level pricing rules
  
• Margin-based automated pricing
  
• Scheduled price update automations
  

This significantly reduces maintenance effort while preserving company-specific pricing structures.

4. Customization Option for Company-Specific Product Prices
If your business users need to see a different sales price directly on the product form or Kanban view depending on the selected company, a customization is usually required.
A common implementation is:

• Create a company-dependent sales price field
  
• Store pricing in a separate model linked to Product + Company
  
• Automatically display the correct price based on active company
  
• Keep a shared product catalog across all companies
  

This approach provides a cleaner user experience than relying entirely on pricelists.

5. Avoid Product Duplication Unless Necessary
Some organizations duplicate products per company to maintain separate pricing.
While this works, it often creates challenges such as:

• Duplicate product records
  
• Increased maintenance effort
  
• Inventory synchronization issues
  
• Reporting complexity
  
• Data inconsistency across companies
  

For most implementations, pricelists or company-specific customization are better long-term solutions. Community discussions around multi-company pricing also frequently recommend pricelists over product duplication.
Bloom Agency Recommendation
For small to mid-sized multi-company setups:

• Use company-specific pricelists.
  

For large enterprises managing thousands of SKUs across multiple companies:

• Implement automated pricelist management or custom company-dependent pricing fields.
  

For organizations operating in multiple countries and currencies:

• Combine company-specific pricelists with automated exchange-rate and margin-based pricing rules.
  
  

This provides scalability, easier maintenance, and better control over pricing across the entire organization.
We have seen this approach work effectively for businesses managing large product catalogs while maintaining a single source of product data across multiple companies.