How to Set Ecommerce Product Image Standards for Catalogues and Merchant Feeds

A product image can look acceptable in a catalogue and still create problems elsewhere. It may be too small for a merchant feed, inconsistent with the rest of the range, cropped badly on mobile or linked to the wrong variant. Those issues affect more than presentation. They can make products harder to compare, reduce confidence and create avoidable feed exceptions.

That is why ecommerce product image standards should be agreed before a catalogue grows large enough for manual correction to become expensive. A useful standard gives catalogue managers, merchandisers, suppliers, developers and marketing teams the same reference for what a product image must contain, how it should be named, where it should be stored and when it is ready for publication.

This guide explains how to create a practical image standard for UK ecommerce catalogues and merchant feeds, while leaving room for different products, variants and channel requirements.

Why product image standards need to be documented

Without a defined standard, image quality becomes a matter of personal judgement. One supplier may provide square white-background images, another may send lifestyle photography and a third may supply inconsistent files for each colour variant. All three may technically be usable, but the catalogue becomes difficult to browse and maintain.

Common problems include:

• Different aspect ratios across products in the same category.
• Images that show a product too small within the canvas.
• Variant images attached to the wrong size, colour or pack.
• Low-resolution files being used for large product displays.
• File names that make asset matching difficult.
• Missing images causing blank cards or feed exclusions.
• Supplier images overwriting approved catalogue photography.

A written standard creates a shared acceptance test. It also makes exceptions visible rather than allowing them to become permanent inconsistencies.

Start with the jobs each image must perform

Do not begin by choosing one pixel dimension for every image. Start by listing where the image will be used and what the customer needs to understand from it.

Typical uses include:

• Product listing cards and category pages.
• Product detail pages and image galleries.
• Mobile layouts and zoom views.
• Google Merchant Centre and other shopping feeds.
• Marketplaces with their own image rules.
• Email campaigns, social posts or internal catalogue tools.

The main image may need to identify the product clearly at a small size, while gallery images may explain dimensions, features or use. A lifestyle image can support buying confidence, but it may not be suitable as the primary feed image if the product is difficult to identify.

Write the standard around these jobs. That prevents a channel-specific requirement from damaging the wider catalogue experience.

Define a core technical standard

Your core standard should specify the minimum technical properties expected for every approved image. The exact values will depend on the ecommerce platform and channels you use, so VERIFY them against current platform documentation before implementation.

Recommended fields to define

• Minimum and preferred pixel dimensions.
• Accepted file formats, such as JPEG, PNG or WebP where supported.
• Maximum file size for practical page performance.
• Aspect ratio and canvas treatment.
• Colour profile and background expectations.
• Maximum number of gallery images.
• Image quality or compression settings.
• Whether transparent backgrounds are permitted.

A useful standard normally has a preferred target and a hard minimum. For example, you may prefer a consistent square canvas for catalogue and feed use, while allowing a defined alternative for products that genuinely need a different shape. The important point is that exceptions are deliberate and recorded.

Do not optimise only for the largest screen. A large source file can be useful for zoom and high-density displays, but it should be delivered efficiently to smaller devices. This is where image standards connect with responsive website implementation and ecommerce performance.

Set a consistent composition rule

Technical dimensions do not guarantee visual consistency. Two square files can still look completely different if one product fills 90% of the canvas and another occupies only 35%.

Define how products should appear within the frame:

• Product centred or aligned according to a clear category rule.
• Consistent spacing around the product.
• Similar scale across comparable products.
• Minimal distracting shadows, borders or overlays.
• Background treatment that supports product recognition.
• Products shown from a consistent angle where comparison matters.

Some categories need a white or neutral background for clear comparison. Others benefit from lifestyle images because context is important. The standard can allow both, but state which image is primary and which is supplementary.

For technical products, include guidance on showing connectors, controls, dimensions or included accessories. For clothing, define whether the main image should show the full garment, the model, or both. A category-level rule is often more useful than one universal rule.

Connect images to variants correctly

Variant accuracy is a central part of product image data quality. If a customer selects blue but sees the red image, the catalogue is not merely untidy; it is communicating the wrong product state.

Every image should have a clear relationship with the catalogue product or sellable variant. Decide:

• Whether the image belongs to the parent product or a specific variant.
• Which colour, size, pack or configuration the image represents.
• Whether one image can be reused across several variants.
• Which image appears first when a variant is selected.
• What happens when a variant has no dedicated image.

Use stable product and variant identifiers in the asset record. Do not rely only on a descriptive file name such as blue-shirt-final-new.jpg. That name may become ambiguous after supplier updates or a platform migration.

HOFK's related guide on modelling product variants explains why parent products, sellable variants and stock records should remain distinct. The same principle applies to images: the asset relationship should be explicit rather than inferred from appearance.

Define naming, storage and ownership rules

Good catalogue image governance depends on more than the file itself. Teams need to know where the approved asset lives, which version is current and who can replace it.

Document a naming pattern that supports searching and matching. A useful structure might include:

• Brand or supplier reference.
• Product or variant identifier.
• Image role, such as main, detail or lifestyle.
• View or sequence number.
• Optional revision or date information.

Avoid using spaces, vague words or names that depend on internal memory. The exact naming format matters less than consistent use.

Also assign ownership at field or asset level. The supplier may own technical product photography, while the ecommerce team owns the approved primary image. A marketing team may request campaign imagery, but that does not automatically make it suitable for the main catalogue or merchant feed.

Translate channel requirements without weakening the catalogue

Merchant feed image requirements should be treated as a controlled output from the catalogue, not as a reason to distort the core product model. Different channels may require different image sizes, backgrounds, URLs or variant relationships.

For each channel, record:

• Required or recommended image fields.
• Primary and additional image rules.
• Prohibited overlays, text or watermarks where applicable.
• Accepted formats and size limits.
• How unavailable or incomplete images are handled.
• Which catalogue field supplies the exported image.

Keep the channel transformation separate from the approved source asset where possible. This lets the same product image be resized, compressed or mapped for a channel without losing the original governance record.

Platform rules change, so VERIFY current Merchant Centre, marketplace and ecommerce-platform requirements before publishing a standard. HOFK's guide to building a Merchant Centre feed launch sign-off process covers the wider ownership and approval controls needed before paid Shopping campaigns go live.

Build validation before images reach production

Manual inspection is useful for priority products, but it will not scale across a large catalogue. Add automated or semi-automated checks wherever your platform and workflow allow.

Useful validation rules include:

• Image URL exists and returns successfully.
• File type is accepted and the file is not corrupt.
• Dimensions meet the agreed minimum.
• Aspect ratio is within the permitted range.
• Image is linked to a valid product or variant.
• Primary image is present before publication.
• Duplicate or suspiciously reused assets are flagged.
• Unexpectedly large batches of changed images are held for review.

Do not treat a successful import as proof that the catalogue is correct. A feed can process successfully while linking the wrong image to a variant or replacing approved assets with low-quality supplier files.

Use a review state for material changes. Show the current approved asset beside the incoming asset, record the source and give the catalogue owner a clear approve, reject or query decision.

Measure image quality as an operational process

Once standards are in place, review the results regularly. Useful measures include:

• Products missing a primary image.
• Variants missing an image where one is expected.
• Images below the agreed technical minimum.
• Rejected or held supplier assets.
• Image-related merchant-feed warnings.
• Products with frequent image replacements.

Use these measures to improve the workflow, not to create a dashboard for its own sake. A high rejection rate from one supplier may indicate unclear requirements. Frequent wrong-variant matches may indicate weak identifiers. Missing images on new products may show that photography is being left too late in the launch process.

Ecommerce product image standards checklist

Before approving your standard, confirm that:

• Primary and gallery image roles are defined.
• Minimum dimensions, formats and file sizes are documented.
• Composition and background rules fit each major category.
• Images are linked to products and variants using stable identifiers.
• File naming and storage ownership are clear.
• Supplier images cannot overwrite approved assets without rules.
• Merchant feed image requirements are mapped separately by channel.
• Automated validation catches missing, invalid or undersized files.
• Material changes can be reviewed before publication.
• Image quality and feed exceptions are reviewed periodically.

Where HOFK can help

Image standards often sit across ecommerce platforms, supplier imports, PIM or ERP data, responsive templates, Merchant Centre feeds and catalogue operations. HOFK can help review the data flow, improve image handling, add validation or support the ecommerce and full stack development behind a more maintainable catalogue workflow.

The useful work may involve defining asset ownership, connecting image records to variants, creating an exception queue, monitoring feed outputs or improving how images are delivered across responsive product pages. The goal is not to make every product identical. It is to make quality, exceptions and responsibility visible.

Conclusion

Effective ecommerce product image standards give catalogue teams a shared way to judge whether an image is technically usable, visually consistent, correctly linked and ready for downstream channels. Start with the jobs each image must perform, define core technical and composition rules, connect assets to stable product identifiers and separate catalogue governance from channel transformations.

Then add validation and review before images reach production. That improves product image data quality, makes merchant feed image requirements easier to manage and gives the business a clearer form of catalogue image governance as the range grows.

Frequently asked questions

What are ecommerce product image standards?

They are agreed rules for image dimensions, formats, composition, naming, variant relationships, ownership and publication quality across an ecommerce catalogue.

What should a product image standard include?

Include preferred and minimum dimensions, accepted formats, file-size guidance, aspect ratio, background and composition rules, naming conventions, ownership and validation checks.

Why does product image data quality matter for merchant feeds?

Accurate, consistent images help channels represent the right product and variant. Poor or missing assets can create feed warnings, weak listings or customer confusion.

Should every product use the same image background?

Not necessarily. A consistent background can help comparison, but some categories benefit from lifestyle or contextual imagery. Define the rule by category and identify which image is primary.

How can catalogue teams prevent the wrong variant image being published?

Link images to stable product and variant identifiers, validate those relationships during import and review material changes before they reach the live catalogue or merchant feeds.