How to Add a New Variation to Products You Already Have
Adding a size to eighty live products is a different job from building one. The manual route, the bulk route, and the four ways it quietly goes wrong.
Your supplier has started doing XXL. You now need it on eighty existing products, each of which already has variations, stock, SKUs and a sales history.
Adding a variation to products you already have is a different job from building a new product, and considerably riskier. This covers the manual route, the bulk route, and the specific ways this goes wrong on live products — because the failure mode here isn’t a bad product you can delete, it’s eighty products that quietly stop working.
Why this is harder than creating a product
Building a new product is additive and reversible. If you get it wrong, you delete it and start again.
Editing existing products is neither. Orders reference existing variations. SKUs are on printed labels. Stock quantities correspond to things on a shelf. And a partially-applied change — forty products updated, forty not — leaves you in a state that’s harder to reason about than either end.
So the order of operations matters more than the tool you pick.
Step 1: add the value to the attribute itself
Before any product can use XXL, the attribute has to know it exists.
If you’re using global attributes — and this is one of the situations where you’ll be glad you did — go to Products → Attributes, find Size, click Configure terms, and add XXL. It’s now available to every product on the site.
If you used custom, product-level attributes, there is no central place. You’ll be retyping the value on every product, with the spelling drift that implies, and no bulk tool can help you because there’s nothing shared to extend. This is the moment the global-versus-custom decision gets expensive.
Step 2: add the variation to one product
On a single product, the flow is:
- Open the product, go to the Attributes tab, and tick XXL in the Size attribute’s value list. Save attributes.
- Go to the Variations tab and either add a variation manually and pick XXL, or press Generate variations.
- Fill in the price, SKU and stock for the new row.
- Save.
Worth knowing about step two, because a lot of people avoid it out of fear: Generate variations on an existing product creates the missing combinations and leaves the existing ones alone. It does not wipe your variations and rebuild them. Your prices, SKUs and stock survive.
That said, on a product with several axes it will generate every missing combination, which may be more than you wanted. Check the count before you save.
Step 3: doing it across many products
Eighty products is where manual stops being reasonable. The options, honestly:
| Approach | Good for | Watch out for |
|---|---|---|
| Manual, product by product | Under about ten products | Consistency drift as you get tired |
| CSV export, edit, re-import | Big changes when you already run this workflow | Re-importing columns you didn’t mean to change — this is how stock levels get overwritten |
| A bulk variation tool | Extending one attribute value across a filtered set | Whether it can preview and undo |
Whichever you use, the important capability is not speed — it’s selection and reversibility. Applying a change to the right eighty products is the hard part, and being able to undo it when the filter turns out to have caught ninety is what separates a routine job from a bad evening.
This is the operation that “bulk variations” ambiguously refers to in its third and hardest sense. In Quick Variable Products, extending an attribute across existing products is part of the Pro catalog workspace, with a dry-run preview and an undo — the free plugin covers creating new products, which is a genuinely different job.
The four ways this goes wrong
1. The new variations have no price
By far the most common. A generated variation with an empty price field is silently unpurchasable — WooCommerce won’t show an Add to Cart button for it, and nothing in the admin warns you. Multiply by eighty products and you’ve quietly created eighty broken options.
If customers start reporting that a size “doesn’t work”, this is almost always why.
2. The new variations have no stock management
New variations don’t inherit the stock settings of their siblings. If the rest of the product manages stock per variation and the new one doesn’t, XXL will show as available forever — you’ll take orders for it indefinitely regardless of what’s on the shelf.
3. SKU collisions and gaps
Either the new variations have no SKU at all — which breaks scanning and counting — or an auto-generated one collides with something that already exists. WooCommerce will refuse to save on a duplicate, which is helpful, but it means a bulk operation can fail partway through.
If you have a SKU scheme, this is the moment it pays for itself: the new codes are predictable by construction.
4. Products that shouldn’t have got it
Not everything comes in XXL. A filter that catches “all products with a Size attribute” will happily add XXL to the children’s range. This is the error that’s hardest to spot afterwards, because nothing is broken — you’re just listing things you can’t sell.
A safe order of operations
- Write down which products should get it — by category, by supplier, by brand. If you can’t express the rule, you’re not ready to run it in bulk.
- Add the term to the global attribute. One place, once.
- Do five products by hand first. Not as a test of the tool — as a test of your rule. Look at them on the front end. Can you buy the new size? Does the price show? Does it appear in the dropdown?
- Preview the bulk run. If your tool can’t tell you what it’s about to touch, do it in batches small enough to check.
- Run it, then check the front end again on three products you didn’t check before.
- Fill in the data — price, stock, SKU — before anyone can find the new variations. An unpriced variation is invisible; a priced one with no stock control oversells.
Afterwards
Two things people forget once the technical part is done:
- Count the new stock. You’ve just created eighty stock records with numbers you typed rather than counted. A partial stocktake scoped to the affected products turns guesses into figures, and it’s much cheaper now than after a month of trading on them.
- Print the labels and tell your supplier. The new SKUs exist in WooCommerce and nowhere else until you do.
The alternative worth considering
Sometimes the right answer is not to extend the attribute at all.
If the new value only applies to a handful of products, adding it to a shared global attribute makes it available everywhere, and someone will eventually tick it on a product that shouldn’t have it. And if you’re adding a fourth axis rather than a value to an existing one, stop and count the resulting combinations first — the multiplication gets away from people quickly.
Extending a catalogue is one of the few operations where doing it slowly is genuinely faster.
Adding variations FAQ
How do I add a new size to a WooCommerce product that already has variations?
Add the new value to the attribute first — for a global attribute that is Products → Attributes → Configure terms. Then on the product, tick the new value on the Attributes tab, save attributes, go to the Variations tab and generate or add the variation, and fill in its price, SKU and stock.
Will Generate variations delete my existing variations?
No. On a product that already has variations, generating creates the missing combinations and leaves the existing ones untouched, with their prices, SKUs and stock intact. On a product with several axes it will create every missing combination though, so check the resulting count before saving.
How do I add the same variation to many products at once?
You need either a CSV export and import workflow or a bulk variation tool. The capability that matters is not speed but selection and reversibility — being able to see exactly which products a change will touch, and to undo it when the filter turns out to have caught more than you meant.
Why can nobody buy the variations I just added?
Almost certainly because they have no price. A variation with an empty price field is silently unpurchasable and nothing in the admin warns you. New variations also do not inherit stock settings from their siblings, so check that too.
What if some products should not get the new value?
Write the rule down before you run anything — by category, supplier or brand. A filter that catches every product with a Size attribute will happily add XXL to the children’s range, and that error is hard to spot afterwards because nothing looks broken; you are simply listing things you cannot sell.
What should I do after adding variations across a catalogue?
Set price, stock and SKU before customers can find them, check the front end on products you did not check during the run, print any new labels, and count the new stock. You have just created stock records with numbers you typed rather than counted.
