Product variants
One product in several colours and sizes, instead of a separate product for every combination. This is a Bang! Cart Pro feature, and it needs free 3.6.0 or newer.
Everything here happens on the Products page, inside the product card you already know. Nothing moves, and there is no new shortcode to add: the buy button you have already pasted grows the pickers by itself.
Turning variants on
Open a product and switch on Variants in its Product type and extras bar. The card grows an options panel beneath the usual fields.
Variants are for products you added here, in the plugin. They are not mapped onto Stripe's own price objects, so a product synced from Stripe cannot carry them - Stripe would have no idea which combination was sold.
Variants and customer-set prices are mutually exclusive. One product cannot both name its combinations' prices and let the buyer type an amount. Ticking either hides the other, by design rather than by accident.
Naming your options
You get up to two options, and you name them yourself. Colour and Size for a jumper; Scent and Weight for a candle; Flavour on its own for a jam that only comes in one jar. Both start empty, with a placeholder suggesting Colour, Size or Flavour - the plugin does not assume your product varies the way clothing does.
Under each option name, add its values one at a time: Navy, Sage, Oat; Small, Medium, Large. Type the first in the + add a value box and press Add (it appears as soon as you start typing) or press Enter. It becomes a tag, and the cursor stays in the box for the next one. A value you type and then click away from is kept too, so nothing you typed is lost if you go straight to Save.
Customers see the values in the order you keep them here. To change it, drag a tag into place - a value shown as a photo or colour is dragged by the grip at the left of its row - or focus one and use the arrow keys. Moving a value is only a move: every variant keeps its price, stock and picture, the table below re-sorts to match, and the dropdown on the product page follows.
Each value you add gets its own row in the combination table below, which is where the prices go. The values themselves are names, not prices: a voucher sold at £25 and £50 is one option called Value with two values, 25 and 50, each then given its price in the table.
Two options is the limit, and it is deliberate. A third was considered and rejected: three options with three values each is twenty-seven rows to price and count, inside a card inside a page. Two keeps the grid something you can fill in and still read.
The combination table
The table builds itself as you type. Three colours and four sizes make twelve rows, each with a price and a stock count, and each appearing the moment its value does.
Twelve rows is not twelve pieces of typing. Each column has a Set all box at its head: type one price, press it, and every row takes it. Then change the two rows that differ. Most shops price a size run flat and only the large one costs more.
Combinations you do not make
Each row ends with Switch off. It takes that combination off sale rather than deleting it, so the Navy in Extra Large you have never made simply stops being offered. Press Switch on later and its price and stock come back exactly as they were - the row was never thrown away, only set aside.
A switched-off combination does not appear in the customer's pickers at all, and cannot be bought.
Pictures
One option can carry the pictures. Tick show each [option] as a photo or colour against whichever one it is - usually the colour, because that is the thing a customer wants to see.
The picture belongs to the value, not to the combination, and that is what makes this quick. Two colours in three sizes needs two pictures, not six: Navy looks like Navy whether it is a small one or a large one.
Each value gets a photo well, and each well takes one of two things:
- A photograph, uploaded from your media library like any other product photo.
- A flat colour swatch, picked from a colour box. Navy reads better as a square of navy than as a photograph of a navy shirt in bad light - and a shop that has not photographed its range yet can still get its variants live today.
You can mix the two freely across one option's values. There is no requirement to picture every value, either; a value with nothing set simply shows its name.
The product's own price box goes grey
This is the single most confusing moment in the editor, so it is worth understanding before it happens.
Switch on Variants and the product's own Price field greys out. It is not broken and nothing was lost. The variants carry the prices now, and a product-level price would only be a fourth answer to a question the combination table has already answered three ways.
A product with options listed but nothing priced yet saves normally and keeps everything. It just stays off sale, with a note on the card saying exactly why. Nothing you typed is discarded to punish you for stopping halfway through, and nothing goes on sale at a price nobody set.
Variants without a price are drafts
The same goes for a single row. A variant that is switched on but has no price yet is a draft: it saves with everything else, but customers do not see it until you give it a price and save. The rest of the product stays on sale as normal.
In the table a draft row is shaded amber and marked Draft - needs a price, and the count above reads like 4 on sale, 1 draft, 1 off. Type a price and the mark goes straight away. After you save, a line at the top of the page names each product with drafts and which variants they are. And so one is never forgotten, a product with a draft among its priced variants carries a small amber 1 variant draft pill on its card even when the card is closed, and Start here lists it as a grey worth-doing row - counted in the sidebar number - with a button that lands on that card. Nothing is ever priced for you - a variant goes on sale only at a price you typed.
What the customer sees
The pickers sit above the Add to basket button that is already on your page. You do not place them, and you do not re-copy a shortcode.
- They filter each other, in both directions. Choose Navy and the sizes narrow to the ones you make in Navy; choose Large first and the colours narrow instead. Whichever order the customer works in, they cannot land on a combination you do not sell.
- A price range shows until a choice is made - £18–£24 rather than a single figure that would be wrong for half the range. It settles to the exact price as soon as the combination is known.
- Sold-out combinations grey out, the same way a sold-out product's button does. Stock is counted per combination, so running out of Small in Navy takes nothing away from Large in Sage.
- Nothing reaches the basket without saying which one it is. The line reads the product name and its chosen values, and two colours of one product sit in the basket as two visibly different lines - as they do on the order, the emails and the receipt.
If Pro is not active
A product with variants pauses. It shows the NOT ON SALE pill in your admin and stops rendering on the storefront, rather than picking one combination and selling it at a guess.
Every option name, value, price, stock count and picture is kept exactly as you left it. Reactivate Pro and the product returns to sale with nothing to set up again. This is the same promise every Pro feature makes: a paused feature is better than a wrong charge, and nothing is ever deleted. See What Bang! Cart Pro adds.
What variants are not
They are two choices on one product, with a price and a stock count each. They are not a general product-options system: there is no per-option surcharge on top of a base price, and no third axis. If your product genuinely needs three, it is two products.
A variant is also a thing you stock rather than a thing the customer writes. If what you need is a box for the buyer to type in - a name to engrave, an allergy, a note about delivery - that is order and product notes, which is also in Pro. The two work together: a product can sell in three sizes and still ask what to embroider on it.
Still stuck?
Write to me and it is me who answers, not a ticket queue. Tell me what you expected and what happened instead.


