Ecommerce · THE NO-PANIC PLAN
Configure variable products and variations in WooCommerce
A variable product groups related choices such as size and color under one product page while letting the store control price, image, SKU, and stock for each option. The hard part is deciding which differences should be selectable attributes, which combinations actually exist, and where inventory is counted. This workflow follows WooCommerce's current variable-product documentation, then checks each combination on the storefront. Nirmion's Product Attribute Mapper can help organize source attributes and destination values; it does not create WooCommerce products, validate stock, or publish catalog changes. Test configuration on a staging store or saved draft before exposing it to customers.
MISSION Set up a WooCommerce variable product with accurate attributes, purchasable variations, per-option pricing and inventory, then test the storefront selection and checkout path.
Map attributes and test a WooCommerce variable productTHE REAL-WORLD BIT
What happens outside this browser tab?
Define the real options and combinations; decide whether attributes should be reusable globally or unique to this product; create a variable product and mark the relevant attributes for variations; generate only combinations that exist; assign unique identifiers, prices, images, and inventory rules; save the product; and test selection, availability, cart, and checkout from the storefront.
YOUR CHECKLIST, WITH FEWER DRAMATIC SIGHES
One step at a time.
Follow the order below. If a step names a Nirmion tool, its link is right there with it.
- 01
Define which product differences are genuine customer choices
Start from the sellable item and list only the options a customer must choose before purchase, such as size or color. Separate those options from descriptive facts that do not create a distinct sellable choice, and write down the combinations you actually offer. This prevents the variation grid from advertising a nonexistent size-color pair or multiplying options simply because source data contains them. Decide whether each attribute will be reused across the store or applies only to this product. If you are mapping supplier or legacy labels to store terms, use Nirmion's Product Attribute Mapper to organize supplied names and values, then review every mapping yourself; the tool does not create or change WooCommerce products. (Sources 1, 2)
- 02
Choose global or product-specific attributes and add their values
For options used consistently across many products, create a global attribute under Products > Attributes and maintain its approved terms centrally. For a one-off option, add a custom attribute on this product instead. Add only the values that are currently sold, use clear customer-facing labels, and order them in the sequence shoppers expect. In the product editor, attach the chosen attributes and mark each attribute as used for variations; mark it visible on the product page when customers need to see it. Check spelling, capitalization, and units against the catalog standard before creating variations, because inconsistent values can split what should be one option into separate terms. Follow the current WooCommerce interface if labels differ by version. (Sources 1, 2)
- 03
Create only the variation combinations that exist and can be sold
Set the product type to Variable product, then create variations from the selected attribute values or add them individually. Compare the resulting combinations with the written availability matrix: remove combinations that are not manufactured, stocked, or offered, and add any valid combination omitted by the generator. Avoid blanket 'any attribute' values unless every matching combination is genuinely interchangeable; WooCommerce notes that using 'Any' attributes changes how variation matching works and can make setup more complex. For a large catalog, the built-in product CSV importer can create or update parent and child rows, but SKU, parent references, attributes, and importer-version rules matter; back up or use staging and verify the current import documentation before choosing that route. Check that every variation has a distinct combination and the parent has a purchasable option. (Sources 1, 4)
- 04
Set each variation's price, SKU, image, and product details
Open each variation and enter its actual regular price, optional sale price and dates, and any variation-specific image, weight, dimensions, or shipping class that customers or fulfillment need. Use a unique SKU for each distinct sellable variation when your store tracks stock or relies on SKU-based operations; WooCommerce's product editor documentation says SKUs must be unique across the store. Do not reuse a parent SKU as if it uniquely identifies every option. Compare sale dates and prices with the authorized price list and check tax settings through the store's established configuration. Save a small sample, reopen it, and confirm values persisted before entering the rest of a large catalog. (Sources 1, 3)
- 05
Choose where stock is managed and enter availability consistently
Decide whether all variations draw from one shared pool or each option has its own quantity. Product-level stock can suit interchangeable options that share physical inventory; variation-level stock is useful when size or color quantities differ. In WooCommerce, variation-level stock is enabled from each variation's inventory controls, while product-level management applies stock to the parent product. Set backorder permission and low-stock thresholds deliberately, and reconcile quantities against the system of record before saving. If both levels are configured, verify the documented behavior for your store version and avoid maintaining conflicting totals in a separate spreadsheet without an owner. Test a zero-stock option to ensure customers see the intended availability. (Sources 1, 3)
- 06
Review the parent page and save as a draft or controlled release
Complete the parent product's name, main description, category, product image, and any store-required shipping or tax details, while keeping variation-specific facts on the matching variation. Check that the default selection, if used, is a real available combination and does not conceal unavailable choices. Save as a draft or use the store's normal approval and staging process before publishing. WooCommerce's editor uses Update or Publish to save product changes; confirm which site and environment you are editing so a staging change is not mistaken for a live catalog update. Record the product ID, owner, source price and inventory snapshot, and the date of review for a clean handoff. (Sources 1, 3)
- 07
Test every customer selection through cart and checkout
On the storefront, select every offered attribute combination and verify the displayed price, image, SKU behavior, stock message, and add-to-cart result. Test unavailable combinations and out-of-stock options to confirm that customers cannot buy an item the store does not offer. Add representative variations to the cart and check that the selected attributes and quantities remain correct through checkout; use a test order or staging payment path approved by the store. Repeat on mobile and keyboard navigation, and verify filter behavior if the catalog uses global attribute filters. If imported from CSV, compare the parent and child rows with the saved variations and reconcile skipped or unmatched rows before release. Fix mismatches in the product data, save, and retest. A successful preview verifies this configuration at that moment, not future inventory or payment-system behavior. (Sources 1, 2, 3, 4)
THE HELPER CREW
Tools for the fiddly bits.
These are the currently published Nirmion tools matched to this guide. Open a tool page for its accepted inputs and limits.
RECEIPTS, PLEASE
Sources & review notes
Each source is linked to the steps it supports. Open it to check its scope and current guidance.
Source checked 2026-10-10