Plan Product Variants Before Uploading Your Store Catalogue

Illustrative example. The fictional range has three sellable combinations; wide sand is absent.

Illustrative example. Keep photographs and internal references matched to the actual variant.

Plan product variants by listing the combinations you actually sell, giving each one a consistent identifier and confirming its images, availability and distinguishing details before upload. Do not assume that every colour exists in every size. A clean variant matrix makes those differences visible while corrections are still easy.

The objective is a catalogue that staff and shoppers can interpret the same way. A customer chooses a recognisable option; the order handler sees the exact item to prepare. Product names, option labels and internal references should support that connection.

Separate the product from the sellable combination

A product groups related versions. An option describes a choice, such as size or colour. An option value is one selection within that choice. A variant represents a particular combination that is available as a distinct version of the product. Shopify's variant documentation uses this combination-based model; verify the rules of your chosen platform before building an import.

Keep customer language separate from internal shorthand. “Medium” may be a useful option label, while a stock reference helps staff identify the corresponding item. Customers should not have to decode an internal reference to understand their selection.

A fictional variant matrix

Imagine a fictional desk-mat range called Plain Desk. The proposed choices are compact or wide, in charcoal or sand. The following identifiers are illustrative internal references, not real stock or supplier codes.

• PD-C-CH: compact, charcoal. Confirm measurements, assign charcoal photographs and record availability from the approved stock source.
• PD-C-SA: compact, sand. Confirm whether the same care instructions apply; do not copy them without checking.
• PD-W-CH: wide, charcoal. Assign its own measurements and an image that accurately shows this version.
• Wide, sand: not sold in this fictional range. Do not create a selectable variant merely to complete the grid.

The missing fourth combination is a useful finding. If the website permits customers to choose it, the interface promises something the business does not supply. Decide how unavailable combinations should be represented during implementation, then test that behaviour on the actual store.

Add the fields that make the matrix usable

Each row should contain the product family, customer-facing option values, internal reference, approved price source, availability source and assigned images. Add measurements or other facts that change between variants. Shared information can live at product level, but the team should know which fields can override it.

Include a review owner and status. “Photo missing” is a different problem from “supplier has not confirmed this variant exists.” The first requires an asset; the second may block the variant entirely. A single vague “incomplete” label makes it harder to assign the next action.

Keep option names consistent

Choose a controlled vocabulary for each product family. Do not mix “charcoal,” “dark grey” and “graphite” for the same approved colour unless there is a genuine distinction. Preserve the supplier's information in a reference field when useful, while presenting a clear customer label.

Keep identifiers stable

Select an identifier convention the team can maintain. Avoid reusing an old reference for a different physical item. Record any mapping between your reference and a supplier's reference separately. This is a catalogue administration recommendation, not a requirement to rebuild your inventory systems.

Run a missing-data review before import

1. Check that every listed combination is genuinely offered.
2. Look for duplicate identifiers and almost-identical option labels.
3. Confirm which values change by variant, including measurements and images.
4. Ask the product owner to resolve blank price or availability sources.
5. Review one completed product in the target platform before preparing the full import.

Use that first product as a practical test. Select each available combination, inspect the displayed information and examine the resulting order details in an appropriate test environment. If the customer and staff views disagree, fix the data mapping before multiplying the problem across the catalogue.

Resolve ambiguous combinations before they become orders

Extend the fictional Plain Desk example with a supplier sheet that calls one colour “graphite” while the photograph folder calls it “charcoal.” Do not create two colour options immediately. Ask the product owner whether the labels refer to the same item, different batches or genuinely different finishes. Preserve the answer in the mapping record.

Now suppose a wide version has a different edge treatment. That difference may need a variant-level note and its own detail photograph. Copying the compact version's text into every row would hide information relevant to the choice. The matrix should make meaningful differences explicit while allowing genuinely shared facts to stay together.

Model a missing combination correctly

A combination that has never been offered is different from a normally offered item that is temporarily unavailable. Record the business meaning before discussing the interface. Otherwise, “out of stock” can become a misleading label for something the supplier does not manufacture or the business does not sell.

During ecommerce catalogue implementation, use these cases to agree the selection behaviour. Ask what the customer sees before and after selecting an option, and whether the resulting order description identifies the correct physical item.

A row-by-row quality check

1. Identity: can two rows be mistaken for the same item? Compare the full combination, not just the visible product name.
2. Reference: does each sellable row have the intended internal identifier, with any supplier mapping kept separately?
3. Evidence: can the reviewer trace dimensions, material and other distinguishing facts to an approved source?
4. Assets: do image filenames point to the correct version, and are shared pictures genuinely applicable?
5. Operations: can staff interpret the order line without opening an unrelated spreadsheet to guess the customer's choice?

Check the matrix with the person who handles the physical stock. They may recognise that two similar codes refer to different packaging or that an old supplier label is still used internally. Resolve those differences in the record rather than relying on a staff member's memory to correct orders later.

Plan changes without losing the catalogue's history

Give catalogue changes an effective date and a reviewer. When a colour is renamed for clarity, record the old and new labels and confirm whether the physical item has changed. When the item itself changes, ask whether keeping the old reference would confuse stock handling or customer communication.

Keep retired combinations out of routine upload files while preserving whatever operational history the business needs. This recommendation concerns the working catalogue; it is not an instruction to delete order records or alter an inventory system. Changes to connected systems need their own agreed process.

Keep visual labels aligned with the data

Colour swatches and promotional graphics should use the same approved names as the product selection. A campaign calling an item “sand” while the store calls it “beige edition” can create unnecessary uncertainty. Where presentation conventions need attention, coordinate them with the brand identity guidance used by the team.

Before a larger import, ask someone unfamiliar with the matrix to find a named variant in the preview store. Have them read back the product, size, colour and any version-specific detail. Compare that selection with the test order line and the physical stock reference. This small rehearsal tests the whole mapping, rather than only whether an upload completed.

Frequently asked questions

Should every colour have a separate product page?

There is no universal answer. Decide whether shoppers see the items as versions of one product or meaningfully different products, then confirm the platform's supported structure.

Does every variant need a different photograph?

It needs imagery that accurately represents it. A shared detail image can be useful, but a colour or shape change may require a specific photograph.

Can the website team create missing product references?

They can propose a convention, but the business should approve it and coordinate with the staff who use those references elsewhere.

Plan your next project with Tralionex

Share one complete variant matrix and the combinations that need clarification. Use them to define the catalogue structure before preparing a larger upload.

Discuss your project with Tralionex