Many businesses start with only a small number of products.
As the business grows, however, a single product may come in multiple sizes, colors, flavors, packaging formats, materials, or configurations.
For example, one snack product may have:
- 30g and 120g sizes
- Original, Salted, and Spicy flavors
- Single pack, 6-pack, and 24-pack carton options
A fashion product may have:
- Product model
- Color
- Size S, M, L, and XL
- Material
- Collection
The challenge is no longer simply creating product codes.
The real challenge is making sure Sales, Inventory, Purchasing, eCommerce, and Accounting all work with the same product information.
This is where an ERP system designed to manage product variants becomes increasingly important.
What Is a Product Variant?
A product variant is a specific version of a main product.
For example:
Product: Classic Polo Shirt
Attributes:
- Color: Black / White / Blue
- Size: S / M / L / XL
The item:
Classic Polo / Black / Medium
is one product variant.
A product variant should not be treated simply as an option displayed on an eCommerce website.
Each variant may need its own:
- SKU
- Barcode
- Sales price
- Purchase price
- Inventory quantity
- Reordering rule
- Supplier
- Product image
- Sales history
- Inventory movement history
In Odoo, product variants can be managed separately while remaining connected to the same main product.
Common Problems for Businesses with Product Variants
1. The Same Product Has Different Inventory Levels
Consider Product A:
- 30g Original: 200 units available
- 120g Original: 8 units available
- 30g Salted: 80 units available
- 120g Salted: Out of stock
If the system treats Product A as one inventory item, the sales team may believe stock is available even when the exact variant requested by the customer is sold out.
This can result in:
- Overselling
- Incorrect deliveries
- Manual warehouse checks
- Order changes
- Delayed shipments
A proper ERP system should therefore track inventory at the variant level, not only at the main product level.
2. SKU Numbers Grow Very Quickly
Imagine a company has 10 product models.
Each product has:
- 5 colors
- 4 sizes
That already creates:
10 × 5 × 4 = 200 SKUs
If there are three packaging configurations as well, the number may increase to:
600 combinations
This explains why many businesses say:
“We do not have that many products, so why is inventory management becoming so difficult?”
The important number is often not the number of main products.
It is the number of product variants and SKUs generated from them.
3. Different Variants Have Different Prices
For example:
| Variant | Price |
|---|---|
| 30g | THB 30 |
| 120g | THB 89 |
| Pack of 6 | THB 169 |
| Carton | THB 620 |
Fashion businesses may have additional pricing such as:
- XL: +THB 20
- XXL: +THB 40
- Premium Material: +THB 150
Without a properly designed product structure, pricing can become increasingly complicated.
Eventually, businesses may find that prices shown on their website, quotations, sales orders, and invoices do not match.
A modern ERP should allow pricing rules to work together with individual products and variants.
4. Sales, Warehouse, and eCommerce Use Different Product Data
This is another common problem.
Sales may use one Excel file.
The warehouse may use another spreadsheet.
The website has a separate product catalog.
Accounting may use different product codes.
When a new variant is introduced, such as:
120g / Salted / Pack of 6
employees may need to create it manually in several different systems.
If someone forgets one system, the data becomes inconsistent.
ERP should therefore do more than manage inventory.
It should become the single source of truth for product information.
5. Management Cannot See Which Variants Actually Perform Well
Management may know that:
“Product A is selling well.”
But much more useful questions are:
- Which size sells best?
- Which color performs best?
- Which flavor has the highest turnover?
- Which pack size generates the highest margin?
- Which variants are becoming slow-moving inventory?
- Which variants may run out soon?
- Which variants should be discontinued?
When product data is structured properly, reporting can go down to the individual variant level.
This is where ERP starts evolving from a simple transaction system into a business decision platform.
Which Businesses Need Product Variant Management?
Product variants are not limited to fashion businesses.
Many industries can benefit from a structured variant model.
Food and FMCG
Typical attributes include:
- Size
- Flavor
- Pack size
- Packaging
- Weight
For example, coffee could have:
- 250g / 500g / 1kg
- Medium Roast / Dark Roast
- Whole Bean / Ground
Fashion and Apparel
Typical attributes include:
- Size
- Color
- Material
- Collection
- Style
Cosmetics
Typical attributes include:
- Shade
- Size
- Formula
- Packaging
Equipment and Spare Parts
Typical attributes may include:
- Model
- Dimensions
- Voltage
- Capacity
- Material
Furniture
Typical attributes include:
- Size
- Color
- Material
- Fabric
- Finish
Wholesale and Distribution Businesses
Products may be sold as:
- Piece
- Pack
- Box
- Carton
Pricing may also vary by customer group, such as:
- Retail
- Dealer
- Wholesaler
- Distributor
- Key Account
Product Variant vs Unit of Measure: What Is the Difference?
This is one of the areas where businesses commonly design their ERP incorrectly.
Consider one product sold as:
- 1 piece
- 1 box = 12 pieces
- 1 carton = 48 pieces
It may not be necessary to create three different product variants.
The correct design may involve Units of Measure or Packaging instead.
By contrast:
- Black Shirt / Medium
- White Shirt / XL
should usually be separate product variants because they represent physically different inventory items.
Before implementing ERP, the first question therefore should not be:
“How do we create products in Odoo?”
A better question is:
“How should our product structure be designed?”
This decision affects:
Sales
↓
Purchasing
↓
Inventory
↓
Manufacturing
↓
eCommerce
↓
Accounting
↓
Business Intelligence
Example of a Product Variant Structure
Consider a snack company.
Main Product:
Potato Chips
Attribute 1: Flavor
- Original
- BBQ
- Cheese
Attribute 2: Size
- 30g
- 120g
Attribute 3: Pack
- Single
- Pack of 6
- Carton of 24
The theoretical number of combinations is:
3 × 2 × 3 = 18 variants
However, a business does not necessarily need to create every possible combination.
For example:
- The 120g size may not be available as a 6-pack.
- Cheese flavor may not be available in a carton of 24.
The ERP structure should represent the combinations that the business actually purchases, stocks, manufactures, and sells.
This is why product architecture should be designed around real business operations rather than simply generating every possible combination.
What If the Business Also Has an eCommerce Website?
Product variant design becomes even more important for businesses that sell online.
When a customer changes a product from:
30g
to:
120g
the website should correctly update:
- Price
- Product image
- Availability
- Product options
After the customer completes an order, that order should connect directly with real inventory.
A growing business should not need to export website orders and manually adjust stock in another system.
With an integrated ERP and eCommerce environment, product information can remain consistent throughout the entire order lifecycle.
How Can AI Help Businesses with Product Variants?
This is where ERP becomes much more powerful.
Once Product, Sales, Inventory, and Purchasing data are structured properly, AI can help management answer questions that previously required several reports and spreadsheets.
For example:
Which product variants sold best during the last 90 days?
Which products may run out of stock within the next two weeks?
Which sizes are selling below average?
Which flavors should we purchase more of next month?
Which product variants have high inventory but no sales during the last 90 days?
Traditionally, management may need to:
Open ERP
↓
Find the correct report
↓
Set filters
↓
Export to Excel
↓
Create a Pivot Table
↓
Analyze the results
A new approach can become:
Ask → Analyze → Recommend
AI-Powered ERP Search for Management
Imagine a CEO asking:
Which products are selling unusually well this month?
The AI could respond:
Sales of the 120g Original variant increased approximately 37% compared with the previous three-month average, particularly in the wholesale channel.
The CEO then asks:
Do we have enough inventory until the end of the month?
The system could analyze recent sales velocity together with current inventory and provide an estimated stock coverage period.
This is the concept behind an ERP Management Search experience.
Instead of forcing executives to learn every ERP report, business information becomes accessible through natural-language questions.
Is Odoo Suitable for Businesses with Product Variants?
Odoo can be a good fit for businesses that need product variants to connect across multiple operations.
For example:
Sales
Quotation → Sales Order
↓
Inventory
Warehouse → Stock → Barcode
↓
Purchasing
Supplier → Purchase Order
↓
Manufacturing
Bill of Materials → Manufacturing Order
↓
eCommerce
Product → Variant → Online Order
↓
Accounting
Invoice → Payment → Cost
The important question, therefore, is not simply:
“Does Odoo support product variants?”
The more important question is:
How should product architecture be designed to match your real business?
What Should You Analyze Before Implementing ERP?
Before importing thousands of products and SKUs into an ERP system, a business should answer at least seven important questions:
- What should be the Product Template?
- What should become a Product Variant?
- Which characteristics should be Attributes?
- Which differences should be handled by Unit of Measure?
- Which differences should be Packaging?
- Does every variant require a separate SKU or Barcode?
- At what level should inventory and pricing be separated?
If the product structure is designed incorrectly, changing it after thousands of transactions have already been recorded can become significantly more difficult.
IMOTIF Product Variant ERP Solution
At IMOTIF, we do not treat Product Variant as simply another ERP feature.
We look at the entire product information architecture:
Product Architecture
↓
Sales Process
↓
Inventory
↓
Purchasing / Manufacturing
↓
Website / eCommerce
↓
Accounting
↓
Data & AI
The goal is to make product information flow through one consistent structure.
This approach is suitable for businesses experiencing problems such as:
- Rapidly increasing SKU counts
- Inventory discrepancies between different channels
- Different product data between website and ERP
- Multiple pricing structures
- Large numbers of sizes, colors, flavors, or pack configurations
- Sales teams constantly asking the warehouse to confirm stock
- Difficulty identifying which variants generate the most profit
- The need to apply AI to sales and inventory analysis
Not Sure How Your Product Variants Should Be Designed?
If your business manages products with multiple:
- Sizes
- Colors
- Flavors
- Materials
- Pack sizes
- Configurations
- SKUs
the first step may not necessarily be purchasing an ERP system.
The first step should be designing the right Product and Inventory Architecture.
IMOTIF helps businesses analyze Product Templates, Variants, SKUs, Barcodes, Pricing, Inventory, and Sales workflows before implementing Odoo ERP.
This creates a foundation that can support future business growth, eCommerce integration, automation, analytics, and AI.
Frequently Asked Questions
What is a product variant in ERP?
A product variant is a specific version of a main product, such as a particular size, color, flavor, or configuration. Each variant may have its own SKU, barcode, price, and inventory quantity.
Can Odoo track inventory separately by size and color?
Yes. When size and color are configured as product attributes that generate variants, Odoo can track inventory for each variant separately.
What is the difference between a product variant and packaging?
A product variant usually represents a physically different version of a product, such as a different size or color. Packaging represents how the same product is packed or sold, such as one piece, a pack of six, or a carton.
What ERP is suitable for businesses with many SKUs?
Businesses with many SKUs should look for an ERP that supports product variants, inventory by SKU, purchasing, sales, barcode management, pricing rules, and ideally eCommerce integration. Odoo is one option for businesses that require these functions within an integrated platform.
Can ERP manage product variants on an eCommerce website?
Yes. An integrated ERP and eCommerce setup can allow customers to select attributes such as size, color, or material while keeping prices, inventory, orders, delivery, and invoicing connected.
How can AI help with product variant management?
AI can analyze ERP data to identify best-selling variants, slow-moving inventory, potential stock shortages, unusual sales patterns, demand trends, and other insights. Natural-language ERP search can also allow managers to ask business questions without manually building reports.
