Product Variants
Variants let you offer a single product in multiple configurations — different sizes, weights, flavours, cuts, or any other attribute — while keeping them linked in the catalog. Socialone groups variants under a ProductTemplate that holds the shared display settings and inventory configuration.
The ProductTemplate
Every variant group has one ProductTemplate — the parent object that holds the name, option axis labels, inventory scope, and base price for the group. Individual variants (each a full Product record with its own SKU, price, and stock) are children of that template.
On the web store and in WhatsApp catalog messages, customers see the template as the product listing and pick their variant from a dropdown or option buttons. In OMS, each variant is its own product with its own inventory counter, SKU, and price.
The template's retailer_id (also called item_group_id in the CSV) is the identifier that groups variants together. It is what Meta uses to link variants in the catalog.
Single product vs. variant group
A product with no item_group_id (no siblings) has no template — it stands alone. Only when you assign an item_group_id to two or more products does Socialone create a ProductTemplate to group them.
Option Axes
A variant group has up to three option axes — the dimensions by which variants differ. These are defined on the template as option1_name, option2_name, and option3_name. Each variant then has a value for each axis in option1, option2, option3.
Option axis names are not locked to a standard vocabulary. You can name them anything that fits your product:
| Product type | option1_name | option2_name | Example option1 values |
|---|---|---|---|
| T-shirt | Size | Colour | XS, S, M, L, XL, XXL |
| Coffee beans | Roast level | Pack size | Light, Medium, Dark |
| Wheat flour | Pack size | (none) | 500g, 1kg, 2kg, 5kg, 25kg |
| Tailored kurta | Cut | Fabric | Slim, Regular, Relaxed |
| Paint | Shade | Finish | Ivory White, Warm Beige, Sage |
| Protein powder | Flavour | Size | Chocolate, Vanilla, Unflavored |
If you do not set option axis names, Socialone defaults to "Size", "Color", and "Material".
Classic Attribute Fields
In addition to the flexible option1/2/3 axes, each variant has six structured attribute fields. These are used by Meta for catalog compliance and ad targeting, and are synced to the WhatsApp catalog regardless of what option axes are named:
| Field | Valid values | Used for |
|---|---|---|
| color | Any text | Meta catalog color facet, ad targeting |
| size | Any text (XS, S, M, 10, 12, etc.) | Meta catalog size facet |
| material | cotton, linen, polyester, wool, etc. | Meta catalog material facet |
| pattern | solid, stripes, floral, check, etc. | Meta catalog pattern facet |
| gender | male, female, unisex | Meta catalog gender targeting |
| age_group | adult, teen, kids, toddler, infant, newborn | Meta catalog age targeting |
Socialone automatically syncs the color and size classic fields from the matching option axis when the axis name is "Color" or "Size" — so you do not need to set them twice if your axes already use those names.
Inventory Scope
The inventory_scope setting on the template controls how stock is tracked across the group. Two modes are available:
Per Variant (default)
Each variant has its own independent stock counter. Selling a large shirt does not reduce stock of a small shirt. Use this for discrete products where sizes or styles have separate physical inventory:
- Clothing (each size is a separate SKU with its own count)
- Pre-packaged items (500g pack stock is separate from 1kg pack stock)
- Accessories (black and white versions stocked separately)
Pricing: each variant has its own explicit price.
Shared Pool (Commodity)
All variants draw from a single shared pool of inventory, measured in a physical unit (kg, g, litre, ml, etc.). Use this for bulk commodities where variants differ only in the amount dispensed:
- Loose grain sold in 500g, 1kg, and 2kg packs — all from the same sack
- Cooking oil in 500ml, 1L, and 5L containers — all from the same drum
- Spices sold by weight — 50g, 100g, 250g packs from the same batch
The pool is tracked in the inventory_unit you set on the template (kg, g, litre, ml, each, or dozen). Each variant has a uom_factor (unit-of-measure factor) that says how many units from the pool one sale of that variant consumes.
Shared pool example — wheat flour
| Variant | uom_factor | Price | Pool deducted per sale |
|---|---|---|---|
| 500g pack | 0.5 | ₹30 (base ₹60/kg × 0.5) | 0.5 kg |
| 1 kg pack | 1.0 | ₹60 (base ₹60/kg × 1.0) | 1.0 kg |
| 2 kg pack | 2.0 | ₹110 (base ₹60/kg × 2.0 − discount) | 2.0 kg |
| 5 kg pack | 5.0 | ₹270 (base ₹60/kg × 5.0 − discount) | 5.0 kg |
Template: inventory_unit = kg, base_price = ₹60. Pool starts at 100 kg. After selling one of each pack: 100 − 0.5 − 1.0 − 2.0 − 5.0 = 91.5 kg remaining.
Commodity Pricing
For shared-pool groups, the effective price of a variant is calculated as:
effective price = base_price × uom_factor- Set
base_priceon the template (via CSV or the product form) — this is the price per inventory unit (e.g. per kg). - Set
uom_factoron each variant — the number of inventory units in this pack. - Leave the variant's
priceblank — it is computed from base_price × uom_factor. - If you want a custom price on a specific pack (e.g. a bulk discount), set an explicit
priceon that variant — it overrides the computed price.
Creating a Standard Variant Group (Per-Variant Inventory)
Via the Product Form (UI)
- Open Catalog → Products → New Product, fill in the name, description, and primary image, then save.
- Go to the Variants tab and click Add Variants.
- Enter the option axis labels (up to three) — e.g. "Size", "Colour".
- Enter the option values for each axis as comma-separated values — e.g. "S, M, L, XL" for Size and "Black, White" for Colour.
- Socialone generates all combinations (a 4 × 2 matrix = 8 variants) and shows a preview table.
- Set the price, SKU, and stock quantity for each generated variant in the table.
- Save. Each combination becomes a separate product record linked under a shared template with
inventory_scope = per_variant.
The UI generator produces all combinations. If you only carry a subset (e.g. not every size in every colour), generate all then delete or deactivate the ones you do not stock.
Creating a Shared-Pool (Commodity) Group
A shared-pool group requires you to set three template-level fields before creating variants: inventory_scope = shared, inventory_unit (the physical unit of the pool), and base_price (price per unit). CSV import is the most reliable way to do this in one pass.
Via CSV Import (recommended)
CSV import is the fastest way to create a shared-pool group — you set inventory_scope, base_price, inventory_unit, and uom_factor in one pass with a full annotated example. See Importing Variant Groups → Shared-pool group in the Bulk Import guide.
Via the Product Form (UI)
- Create a new product, fill in the name and image. On the Inventory tab, set Inventory Scope to Shared Pool, choose the Inventory Unit (e.g. kg), and enter the Base Price (price per unit, e.g. ₹120/kg).
- Save the product. This creates the template with shared scope.
- Go to the Variants tab → Add Variants. Enter your option axis label (e.g. "Pack Size") and values (e.g. "500g, 1kg, 2kg, 5kg").
- In the generated variant table, set the UoM Factor for each variant (0.5 for 500g, 1.0 for 1kg, 2.0 for 2kg, 5.0 for 5kg). Leave the Price column blank — it is calculated.
- Set the pool stock quantity at the template level (the total kg on hand). This one counter is shared across all variants.
- Save. Each variant's effective price and stock deduction are computed from base_price and uom_factor automatically.
Changing scope after orders exist
Switching inventory_scope after the group already has inventory transactions resets all stock counters. Only change scope before the first sale or during a full stocktake reset.
Creating Variants via CSV
CSV import lets you create an entire variant group — both standard and shared-pool — in one pass. The Bulk Import guide has step-by-step walkthroughs with annotated examples for both types under Importing Variant Groups. Use it as the definitive how-to: it covers column placement, which fields go on the first row only, the full column reference, and the most common mistakes to avoid.
After creating your group
- Advanced Inventory — set minimum order quantities, slab pricing, and UoM rules for the group or individual variants.
- Inventory Management — monitor on-hand stock, ATS, and reorder points across all variants and locations.
- Updating Prices — change
base_pricefor a shared-pool group or per-variant prices in bulk via CSV.
Web Store Policy for Variant Groups
The three web policy fields — web_visibility, commercial_mode, and price_display — are set at the variant level, not the template level. For a consistent storefront experience, all variants in a group should share the same policy.
- Inheritance at creation: when a new variant is added to an existing group (via import or UI), it inherits the group's settled policy from the existing siblings automatically.
- Overriding for one variant: you can set a different policy on a specific variant (e.g. hide a size that is out of stock permanently). Include the three web policy columns for just that row in the import CSV.
- Bulk apply via import: use the Import Options web policy batch mode to apply a policy to all rows in an import at once — useful for first-time setup of a large variant catalog.
- Price display — from: set
price_display=fromon the template group when variants have different prices. The web store shows the lowest variant price as "From ₹X".
Editing Variants After Creation
- Price — per-variant group: edit each variant's
pricein the product form or via the Price Update Template in bulk import (one row per SKU). - Price — shared-pool group: update
base_priceon the template — all variant prices recalculate automatically viabase_price × uom_factor. Use a group command row in a CSV or edit the template in the product form. Updatingpriceon individual variant rows has no effect for shared-pool groups. - Stock: edit directly in the product form per variant, or via import (stock_quantity column). For shared-pool groups, entering stock on any variant updates the shared pool total.
- Option axis labels (option1_name, option2_name, option3_name): editable on the template via the product form or via import. This is a display-only change and does not affect stored values.
- Option values (option1, option2, option3): editable per variant in the product form. For example, rename "Slim Fit" to "Tailored" for a specific variant.
- Adding more variants: use the product form's Add Variant button, or add rows with the same
item_group_idto a new import CSV. - Removing a variant: set
is_active=falseto deactivate it without deleting historical order data, or delete via the product form. Deletion is permanent and cannot be undone. - Changing inventory scope: you can change
inventory_scopebetween per_variant and shared after creation, but this resets all existing inventory counts for the group. Only change scope when setting up for the first time or during a full stocktake.
WhatsApp Catalog Behavior
Meta's WhatsApp catalog groups products by item_group_id (the template's retailer_id) and shows them as a single listing with variant swatches. How variants appear in the catalog:
- The template name and primary image are used as the catalog item title and thumbnail.
- The classic attribute fields (
color,size,gender,age_group) drive the swatch and filter chips shown to customers. - Only active, in-stock variants are eligible for catalog sync. Setting
availability=out_of_stockon a variant hides it in the catalog until restocked. - Meta requires at least one of
google_product_categoryorfb_product_categoryfor catalog approval. Set them on individual variants or via a group command row. - For Indian compliance, set
origin_countryandwa_compliance_category(orCOUNTRY_ORIGIN_EXEMPTfor digital/service variants).
Related Docs
Related product
Commerce & Orders for WhatsApp selling
Manage WhatsApp catalogs, products, variants, bulk imports, product messages, carts, payments, and order follow-up from one Socialone workspace.
View product →