Product Variant Spec Sheet: One Page or Six?

A product variant spec sheet is not a layout decision. It is a routing decision: does the buyer get one page per size, or one page for the whole range, and where does the number that actually differs live?

Get the routing wrong and the failure is quiet. A shopper in a Nielsen Norman Group usability study was looking at a stool range sold across six separate pages — three frame colours and two heights. She settled on a black version she liked, added it, and only later noticed it was the bar-height model, not the counter-height one she had started with. The page had told her the frame colour. It had not told her the height, because the two heights looked the same in the product photos.

That is the whole problem in one scene. Buyers do not compare your model codes. They compare pictures. If the picture does not carry the difference, the number is somewhere in a paragraph they did not read.

Here is how to build a spec sheet for a variant range that survives that comparison: which fields split per variant, which stay locked, what goes on the photo, and when a variant should stop being a variant at all.

What a product variant spec sheet actually has to do

A product variant spec sheet is one page that proves what changes between two sizes, colours or configurations of the same product — and, just as important, what stays identical.

It has three jobs:

• Let a buyer pick the right variant without measuring for you.
• Let a buyer prove, later, which variant they picked.
• Let anyone in your own team reissue the page for a new variant without redesigning it.

Most suppliers do the first job and skip the other two: then a spec change reaches the website and not the PDF, or a purchase order cites a model code on no page you sent.

The stool case: separate pages did not prevent the wrong size

Worth looking at what actually failed there, because the instinct after any variant mistake is "split them into separate products."

The range was already split. Three frame colours times two heights sat on six different product pages, and the shopper still had to keep the height in her head while browsing. The description of the failure is the useful part: "The different-height stools looked the same in the product photos."

Splitting pages does not fix a picture problem. It moves the comparison work to the buyer's side of the table, and buyers do that work badly at browsing speed.

Nielsen Norman Group's guideline is narrower than "split everything": variations that differ in one simple attribute — size, colour, pattern — belong to a single listing with selectable attributes, while genuinely different products with different descriptions get separate listings. A stool height is a simple attribute. A stool and a bench are not.

Decision 1: one spec sheet for multiple sizes, or one per size?

Three arrangements work, and they are not equally good.

The middle row is where most export suppliers should sit. One page per variant is not a marketing decision — it follows from the fact that each size is its own item in every downstream system, which is Decision 2 below. The index page is what makes it work; without one, per-variant cards look like a filing cabinet with no labels.

Decision 2: each variant is its own item, and the identifiers disagree if you skip this

There is a hard rule here, and it is not a style preference. Under the GS1 GTIN Management Standard, each style, colour and size variation is treated as a unique product and is assigned a unique GTIN. A change to a physical dimension on any axis — or a gross weight change over 20% — requires a new GTIN, and stacking up small sub-20% changes to dodge that rule is explicitly called unacceptable practice.

In plain terms: two seat heights are two items, with two codes, forever. Not "the same stool, one is taller."

So the model code and the GTIN belong to the variant layer, not the range layer, and must sit on the variant's page, not only in the price list.

Decision 3: which fields split, which stay locked

Every field on a variant page falls into one of three layers. Split the layers once and every future variant is a fill-in job.

The failure mode to watch for is inheritance. A 75 cm stool is not a 65 cm stool plus 10 cm: footrest height, centre of gravity, carton height and packed weight all move, and the load rating may not move at all. Copying the base model's fields and editing one number produces a page that is wrong in four places.

A worked example, clearly labelled

Say your range has two seat heights, 65 cm and 75 cm (examples, not a standard):

Two rows are doing most of the work: the seat height and the carton height. One is what the buyer is choosing. The other is what the freight forwarder will charge for.

Decision 4: how the difference gets onto the photo

This is where the stool case was lost, so it gets its own rule.

Measure each variant. Never scale a photo, and never multiply one dimension to infer another. Two heights of the same silhouette are not photographs of the same object at two zoom levels. Arm proportions, footrest placement and the apparent seat depth all shift, and a resized image asserts a set of dimensions you never took.

What to put on the image itself:

• The one dimension that differs between variants, labelled on the photo, not only in the table.
• The unit, next to the number. A bare "65" invites a buyer to read it in inches when your sheet is in centimetres.
• The variant code in the same frame, so a forwarded screenshot still says which one it is.

A dimension label template is a reasonable starting layout: the annotations stay in place, you swap the photo and the values per variant. The labels are only as good as the numbers you type into them, which is why the measurement rule above is not optional.

Variant size labels: what a good one contains

A label is the smallest unit of proof your buyer can forward to a colleague.

• The differing dimension, with unit
• The variant/model code
• The measurement method if the number could be read two ways (seat height: floor to seat top, or floor to cushion compressed)
• The date the measurement was confirmed
• Nothing else — every extra label competes with the one that matters

That fourth item sounds bureaucratic until a spec changes. A label with a date lets you prove which version a buyer was looking at when they ordered.

The index page: how a buyer picks a variant in twenty seconds

The index is the page that makes a product variant spec sheet usable at scale: one page, one row per variant, so nobody opens six files to compare two numbers.

Keep the index to the columns that decide the choice. A sixth comparison column usually means the variants are different products.

The size in the product title matters as much as the sheet: it is what the buyer searches and what a marketplace may match against.

When a variant should stop being a variant

The two authorities agree, which is rare enough to be worth stating plainly.

• Nielsen Norman Group: if the product descriptions differ, the items are different products — give them separate listings.
• GS1: if the attributes change in a way that makes it a new addition to your portfolio rather than a change to an existing item, treat it as a new product with its own identifier.

In practice, a variant is the same product when only attributes move: size, colour, finish, configuration within the same function. It stops being a variant when the function, mechanism or material class changes. A swivel stool is a different product from a fixed stool, even if the photo looks similar — and that difference belongs in the sheet, not discovered at inspection.

FAQ

Should each size variant have its own product page?

For a B2B quote, yes — each variant needs its own page plus an index page linking to all of them. Each size is a distinct item with its own code and GTIN, and a buyer's purchase order cites one of them. A single page carrying all sizes works for a short range, but fails the moment two buyers quote two different sizes from it.

How do I show the size difference between two variants in a photo?

Label the differing dimension directly on each photo and shoot or compose both variants at the same scale, side by side if possible. Do not resize one photo to imply the other. In the Arhaus study, the two stool heights "looked the same in the product photos," and that is exactly the failure a single labelled number prevents.

Do size variants need different GTINs?

Yes. GS1 treats each size variation as a unique product with its own GTIN, and a physical dimension change on any axis requires a new GTIN. Distributors and marketplaces key their records on that code, so sharing one GTIN across two heights creates a mismatch the buyer will discover at goods-in.

What should an index page for a product range contain?

One row per variant with the model code, the single number that defines the choice, the price and its basis, lead time, and a link to that variant's page. Everything else belongs on the variant page. The index is for choosing; the variant page is for confirming.

Can I reuse one photo for all size variants?

Only if the variants genuinely look identical and the difference is an internal attribute. Where the visible proportion changes — height, width, depth, capacity — reusing the photo asserts the wrong shape. Reuse the layout, not the photo.

Next steps

Three routes, depending on what is actually broken.

If buyers keep choosing the wrong size, the difference is invisible, not under-documented. Label the one differing dimension on each variant photo, then add the index page. That pair fixes more wrong-size orders than any redesign of the catalogue.

If the bottleneck is production time per variant, the fix is the three-layer field split. Lock the shared fields once, then each variant is a fill-in job rather than a design job. A workspace that keeps the measured labels locked to the photo while you swap the values per variant is one option among several; so is a fixed template in a design tool, or a drawing from your factory that you annotate yourself.

If the bottleneck is that a whole range has never been indexed, build that page first — model code, the differing number, price basis, lead time, link. It is the cheapest page you will ever make and it removes the most common reply in a stalled enquiry: "which one do you mean?"

Either way, keep the destination in view: a product variant spec sheet per SKU is not a paperwork habit. It is a way of making the product card vs PDF catalog argument unnecessary, because the buyer never has to read a range document to find one SKU.

Sources & References

• GS1 — GTIN Management Standard, rule 4: dimensional or gross weight change (new GTIN required for any axis change, or gross weight over 20%)
• GS1 — GTIN Management decision support: new product or product change (each style, colour and size variation is a unique product)
• Nielsen Norman Group — Design guidelines for selling products with multiple variants (Kim Flaherty, 2022): the Arhaus stool case and the single-listing guideline