Product variations are different versions of the same product, such as a shirt in charcoal and medium, or a candle in cedar and a small jar. The option is the choice category, such as Color. The option value is one choice, such as Charcoal. A variant is the specific combination a customer can buy. These product variations examples show how to turn choices into a list of real, orderable items.
The distinction matters before you build a color picker. Two colors and three sizes can produce six combinations, but that does not prove your supplier makes all six. Start with what you can sell and fulfill, then decide how customers choose it.
Five product variations examples
The examples below are illustrative catalog plans, not claims about a particular supplier’s range. Each assumes that every listed combination is available.
- T-shirt. Color values Charcoal and Cream combine with sizes S, M, and L. That gives six variants, including Charcoal / M.
- Candle. Scents Cedar and Citrus combine with Small and Large jars. That gives four variants, including Cedar / Large.
- Ceramic mug. Glazes Blue and White combine with capacities 250 ml and 350 ml. That gives four variants, including Blue / 350 ml.
- Tote bag. Colors Natural and Black give two variants. No second option is needed if both bags have the same dimensions.
- Dining table. Finishes Oak and Walnut combine with lengths 140 cm and 180 cm. That gives four variants, including Walnut / 180 cm.
Each variant needs more than a name. The large candle may cost more to make. The longer table may need a different shipping service. The black tote needs an image that actually shows black fabric.
Propel’s product-variant reference describes the same parent-product, option, and value relationship. Use that structure to keep related choices together without losing the identity of each sellable combination.
Count combinations before adding another option
For independent options with every combination allowed, multiply the number of values in each option group. Two colors, three sizes, and two materials produce 12 potential variants, not seven. Seven is the number of individual option values; 12 is the number of combinations.
Write the combinations out when the catalog is small:
- Charcoal / S has example SKU
TEE-CHA-S. - Charcoal / M has example SKU
TEE-CHA-M. - Charcoal / L has example SKU
TEE-CHA-L. - Cream / S has example SKU
TEE-CRE-S. - Cream / M has example SKU
TEE-CRE-M. - Cream / L has example SKU
TEE-CRE-L.
These SKUs are examples of merchant-defined stock codes, not supplier identifiers. Keep the supplier’s mapping separately when fulfillment depends on it.
If Cream / L does not exist, you have five valid combinations. Do not fill the missing row with a made-up SKU or treat it as temporarily out of stock. A combination that was never manufactured is different from a real variant whose available quantity is zero.
Check whether your platform supports an incomplete grid. If it generates every combination automatically, revise the option structure or use a supported restriction mechanism. Do not publish the missing combination merely to complete the grid.
Decide whether a choice needs a variant
Use a variant when the choice identifies a distinct item you must price, stock, or map to a supplier. Color and size usually qualify for a shirt because the warehouse or printer needs the exact combination.
An open-ended engraving message is different. A thousand possible names should not automatically become a thousand variants. The text can be customization data attached to the chosen item, provided the store supports that workflow and preserves it in the order. A gift message may be an order note rather than a product choice at all.
This is a modeling decision, not a promise that every platform supports personalization. Confirm how your system stores and forwards the value before offering it to customers.
Separate products can also be the clearer choice. A cotton tote and a leather backpack differ in purpose, construction, and care. Calling them two values of a Material option can conceal information a shopper needs. Keep them separate when choosing between them is really choosing a different product.
Check price, stock, images, and fulfillment together
For each valid combination, answer four questions:
- What does it cost the customer? Check the selling price and currency for the intended market. Do not assume every size has the same cost or margin.
- Can it be bought now? Check tracked quantity for stocked items or the provider’s availability rules for supplier-made items.
- What will the customer see? Match images, labels, and dimensions to the selected version. A mockup is not proof of physical availability.
- What reaches fulfillment? Verify that the cart and order identify the same variant the customer selected, with the correct quantity and any supported customization.
For example, 12 small cedar candles and eight large cedar candles are 20 units in total. Entering 20 into both variant rows would advertise 40 units. The right stock figure belongs to each item, not to the parent product’s total.
For print-on-demand, a blank product’s color and size choices come from the provider catalog. Runner’s POD implementation selects provider variants and checks whether the artwork’s print geometry remains compatible when the selection changes. It also distinguishes prepared mockups by color. That is why a mockup and a purchasable variant should not be treated as the same record.
Use the Printful workflow guide for the supported Runner process. Do not copy manual stock quantities into a provider-managed availability workflow.
Turn the examples into a Runner AI product plan
Runner’s manual product form generates combinations from option values and keeps variant prices and inventory separately. Before editing a live product, prepare a short list of the valid choices, their prices, their stock, and the images that represent them.
The inventory and variants guide owns the setup steps and includes an annotated product-form example. Use it when you are ready to enter the data. This article helps decide what the data should represent.
If the storefront needs a more involved selection flow, review Runner’s ecommerce product configurator capability. Give the builder your actual option groups, valid combinations, identifiers, prices, and unavailable states. Do not ask it to infer supplier availability from a photograph.
Before sharing the product page, select each combination and inspect the cart summary. Test an unavailable choice and an incomplete selection too. The acceptance condition is that a shopper can buy the intended item, not merely that the swatches change color.
Common questions
Are product variations and variants the same?
They often describe the same customer-facing concept. In this guide, a variation is a version of the product and a variant is its specific sellable record. Use your platform’s terminology, but keep the option, value, and combination distinct.
Does every color need its own product page?
Not necessarily. Colors can be variants under one product. Separate pages may make sense when the products need substantially different explanations or merchandising. Page structure does not remove the need for accurate variant data.
Does adding more variations increase sales?
Not by itself. More choices can meet a customer need, but they also add prices, images, availability states, and fulfillment mappings to maintain. Add a choice when you can support it and have a reason customers need it. Measure the result rather than promising a conversion lift.
What should I do when the variant count is wrong?
Check blank or duplicate values, count each option group, and list the expected combinations. Then compare that list with what the product form generated before saving. For the broader data contract, read our ecommerce product data guide.