THE SHORT ANSWER
Audit images at the sellable-variant level. Check that the URL resolves, the image depicts the selected product and option, and the landing page shows the same item. A present image_url field proves neither image availability nor correct variant correspondence.
Separate URL checks from visual checks
A non-empty image field is only the first layer of quality. The file might be unavailable, redirected unexpectedly or replaced with a generic placeholder. Record URL reachability separately from whether a human can recognize the actual product in the image.
For larger catalogs, automate technical checks carefully and sample the visual result. A successful HTTP response can still return a “no image” graphic. Conversely, an access restriction during an internal test may need investigation before you classify the source as broken for every destination.
Match the selected option
Compare the image with the exported color, style, size or pack configuration. Some options may share a legitimate image, while others need a distinct representation to avoid confusion. Use category judgment and the destination’s current image rules rather than assuming every variant needs an entirely different file.
Check the landing page with the variant actually selected. A feed can link to the right family page but leave the default option active, creating a mismatch between the exported item and the page a shopper sees. Save the exact URL and selected state in the audit record.
Inspect transformations and inheritance
Image URLs often pass through resizing services, templates or mapping rules. Confirm that transformations preserve the product and use a format accepted by the destination. A filename rule that works for one supplier can quietly point to the wrong image for another.
Review fallback behavior. If a variant image is missing, decide whether a family image is acceptable or whether the record needs an exception. Do not let a silent fallback turn every missing-image problem into an apparently successful release.
Prioritize corrections by impact
Start with wrong-product images, wrong variants and broken primary images. Then improve secondary coverage where it helps a shopper evaluate the item. Track the issue type and source so recurring errors can be corrected at the mapping or supplier level.
Recheck affected products after the next import. Image fixes are often overwritten when a source field refreshes. Keep evidence for approved corrections and reopen the review if the underlying product or media reference changes.
ILLUSTRATIVE WORKED EXAMPLE
Make it concrete.
Illustrative example: a green chair variant exports the family’s beige image because a fallback rule takes precedence. The audit records the mismatch, fixes the rule for that supplier and retests both variants. It also checks that the green variant is selected on the linked product page.
Your practical checklist
- Distinguish field presence, URL availability and visual correctness.
- Inspect the exact exported variant and landing page.
- Review image transformations and fallback rules.
- Prioritize wrong products and broken primary images.
- Retest corrections after a source refresh.
Common questions
Can a feed checker verify the pictured color?
A basic field checker cannot. Visual correspondence needs a separate review or a carefully evaluated image-analysis workflow.
Is a working image URL enough?
No. The image must also represent the relevant item and satisfy the destination’s applicable requirements.
Sources & scope
Official references checked 29 October 2026. Examples are illustrative, not customer results. Platform requirements can change; use current destination documentation for implementation decisions.
Our editorial method & corrections ↗