Ecommerce product content: images, variants and size guides

Map the uncertainty before commissioning the assets

Start by listing what a shopper cannot know from the product name. Is the finish glossy or matte? How large is the item in a real setting? Does the selected colour change the material? What arrives in the box? What must be purchased separately? The answers define the product page's content requirements.

Group those questions into identity, fit, use, and purchase conditions. Identity covers what the product is and which variant is selected. Fit covers dimensions, sizing, compatibility, and context. Use covers assembly, care, limitations, and expected handling. Purchase conditions cover availability, delivery, returns, and the total commitment the buyer is making.

This map is a practical editorial framework, not a universal page template. A sofa and a software accessory need different evidence. The point is to identify the information that can change a buying decision before the team spends time polishing a generic description.

Review support questions and product-team knowledge together. Repeated questions may reveal missing information, but an unfamiliar new product can have important questions no customer has asked yet. Ask someone outside the team to describe what they would still need to know before buying. Record the gaps as content tasks with named owners.

Give every product image a specific job

A gallery should explain the product progressively. The main image establishes identity. Additional views show shape, construction, texture, scale, and meaningful details. A contextual image can demonstrate proportion or use. Several attractive images that all communicate the same thing may leave important uncertainty untouched.

Shopify's product page guidance recommends clear imagery from multiple angles and the ability to inspect details. For a specific catalogue, turn that broad principle into an image brief: required views, framing rules, background treatment, aspect ratio, and which details must remain visible on a small screen.

Decide which variations need distinct photography. A colour difference, surface treatment, or included accessory may materially affect the purchase. Show the actual variant accurately and identify any image that illustrates a different configuration. Do not use an attractive reference image in a way that implies an item includes something it does not.

Name and organize assets so the relationship to products survives beyond the original shoot. An internal record should identify the product, variant, view, approval state, and replacement date where relevant. The operational question is simple: could a different team member place the correct image on the correct product without relying on memory?

Keep selection, imagery, and information in agreement

A variant selector changes a promise. If the shopper chooses another size or finish, the displayed price, availability, imagery, and relevant specifications should agree with that choice. Inconsistent information forces the customer to guess which part of the page is authoritative.

Platform capabilities matter here. Shopify's variant image documentation states that a variant has one assigned image, while further images can appear in the product gallery. More elaborate image grouping requires an implementation choice rather than an assumption that every theme behaves identically. Confirm the behaviour in the actual storefront before planning the asset workflow around it.

Create a small selection matrix for quality assurance. Include available and unavailable combinations, the first selected variant, direct links to variants, and the return from cart to product. Check what happens when a size is selected before a colour and when the order is reversed. A catalogue can look correct in its default state while failing in another valid state.

Use words alongside visual choices where meaning would otherwise be ambiguous. A colour swatch should have a usable name. A disabled option should communicate that it is unavailable. Keep the chosen configuration visible near the purchase action so the customer can verify what will be added.

Make fit guidance usable at the moment of doubt

A size guide is a decision tool. It should explain what is measured, how to take the measurement, which unit is used, and how the measurement maps to the product. A chart without that context can create new uncertainty, particularly when the buyer cannot tell whether values describe the body or the garment.

Keep guidance close to the relevant choice. If products use different sizing systems, link the appropriate guide from each product rather than sending everyone to a single ambiguous table. When converting between units, establish a rounding rule and check that the displayed values remain useful. Where tolerances matter, describe them accurately.

Hypothetical example: a clothing brand sells a structured jacket in two fits. Its existing page has one generic chart. The proposed revision separates garment measurements from body guidance, explains where to measure, identifies the pictured size, and describes the fit difference in plain language. These are proposed content improvements, not a claim about return rates or sales.

The same approach applies beyond apparel. Furniture needs clearance and access dimensions; equipment needs compatibility details; containers need useful capacity information. Ask the customer to complete a fit decision with the page alone. Their hesitation can reveal whether the missing element is a measurement, an explanation, or a more informative image.

Treat the catalogue as a maintained information system

A consistent product page depends on more than a reusable layout. It needs consistent source information. Define the fields each product family requires, which fields can be inherited, and which must be verified individually. Materials, care, dimensions, included components, and compatibility often deserve structured fields rather than a single freeform description.

Create a publication gate with a small number of meaningful checks. Are mandatory facts present? Do images match the product and variant? Are delivery and return statements current? Can the selected item be identified in the cart? A gate should catch errors a customer would care about, not merely reward a page for having a certain number of paragraphs.

Google's ecommerce search documentation covers site structure and sharing product information so search systems can understand a catalogue. Treat those machine-readable details as another representation of the same approved product record. A price or availability mismatch between systems is an information problem before it is a marketing problem.

Assign responsibility for changes after launch. If a supplier revises a dimension or a product loses an included accessory, identify every place that needs updating. The value of a content system appears most clearly when an ordinary catalogue change can be made accurately without rediscovering how the entire store works.

A production example: Elites Aera

For Elites Aera, Nocturnum’s scope was product recolours and size charts: over 2,500 images creating variants for more than 100 products. This is content-production work. It should not be presented as a claim that Nocturnum designed the brand’s entire ecommerce website, or that the images produced a measured increase in sales.

The scale makes a useful planning question visible: how will the team know that each output belongs to the correct product and variant? Before commissioning a similar programme, define an acceptance record for each family. Include the product identifier, approved colour reference, required angles, dimensions, chart version and the person who signs off the set.

Check the imagery in the actual buying context, not only in an export folder. A technically correct recolour can still be confusing if the wrong image appears after selection or the size guide describes a different product. For a proposed workflow, begin with a small representative batch and correct the naming, review and upload process before scaling. Connect this work to the catalogue’s content structure so the assets remain manageable after handover.

Audit one product family before scaling the approach

Choose a representative family with meaningful variants and a manageable number of products. Review it with the people responsible for merchandising, support, fulfilment, and the website. Each sees a different source of customer uncertainty. Agree a content model, apply it, and test realistic buying tasks before extending it across the catalogue.

Use this action checklist:

• List the identity, fit, use, and purchase questions for the product family.
• Assign a purpose to each required photograph or diagram.
• Verify variant selection against images, prices, stock, and cart details.
• Make size and compatibility guidance specific enough to support a decision.
• Document required fields, approved source information, and update owners.
• Test a complete purchase path on a small screen with representative products.

After release, compare support questions and observed shopping difficulties with the gaps you intended to close. Use purchase data carefully: a new campaign, price change, or stock situation may also affect results. The immediate standard is information quality. Can a customer understand what they are buying, choose the right configuration, and find the conditions that matter? A well-maintained product page should make those answers dependable.