Audit Whether Every Product Image Is Eligible for the Email Offer

Approve a promotional product image only after the pictured product and variant map to the offer and destination. Use Migma to create or adapt the branded email, then verify the image against exact catalog IDs, owned assets, eligibility rules, and negative cases.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 8, 2026.

Migma's dated image-led Black Friday guide distinguishes an email screenshot used as layout direction from a product photo used as content. Its dated Shopify workflow warns that an attractive image of an excluded variant can make otherwise accurate copy misleading. Treat image identity as a factual claim.

Build the asset-to-offer table#

Scroll table →

Placement	Asset ID	Depicted catalog identity	Eligible?	Destination	Review state
Hero	`asset-hero-blue`	Product 184, blue, 500 ml	Yes	Exact blue variant	Approved
Grid 1	`asset-set-white`	Bundle 42, white	Yes	Bundle page	Approved
Grid 2	`asset-refill-gold`	Refill, gold cap	No	None	Remove
Lifestyle crop	`asset-kitchen-7`	Product 184 plus visible gift card	Mixed	Collection page	Replace or crop

Use catalog and asset identifiers, not filenames such as final-hero-2.jpg. Filenames do not prove what a photograph depicts or whether it is current.

Verify five dimensions#

1. Identity

Name the product, bundle, color, size, material, pack count, region, and any visible accessory. If the image cannot distinguish a material variant, do not attach a precise material claim to it.

2. Eligibility

Evaluate the exact depicted configuration against the offer. A selected-product promotion may exclude one color, subscription, gift card, bundle, or sale-on-sale item.

3. Destination

Click the image and nearby button. Confirm that the landing page selects or clearly presents the depicted item. A generic collection can be acceptable when the copy says “explore the collection”; it is misleading when the image implies one-click access to a specific variant.

4. Availability language

An approved image does not prove live inventory. Avoid “in stock,” “reserved,” “selling fast,” or quantity claims unless a current system supplies and enforces them. Define what the email should do when the pictured item becomes unavailable.

5. Rights and provenance

Record who created the asset, what rights permit its use, the source file, permitted markets and channels, expiration, edits, and whether recognizable people or third-party marks need additional clearance.

This rights check is narrower than a general source-asset register: it binds legal provenance to the exact product representation used in one offer.

Give the image a bounded Migma brief#

Migma's Image Clone documentation describes turning a screenshot into editable or brand-adapted email. Separate the reference from the sellable asset:

Use the reference only for its two-column product hierarchy. Build the email with our owned assets asset-hero-blue and asset-set-white. The offer covers product 184 in blue 500 ml and bundle 42 in white. Do not reuse the reference brand, product photography, logos, prices, reviews, or claims. Do not add the gold refill or gift-card imagery. Keep product links available for exact review.

After generation, search image content and extracted text for residue from the reference: old prices, dates, codes, logos, testimonials, product labels, and legal text.

Create negative fixtures#

Deliberately test:

correct product, excluded color;
correct image, destination defaults to an excluded size;
eligible product beside an excluded accessory;
old packaging that implies a different quantity;
bundle photo with one component no longer included;
image text containing a superseded price or deadline;
crop that hides the distinguishing variant feature;
mobile crop that turns a multi-product scene into one misleading product;
product becomes unavailable after approval;
reference-company mark survives adaptation.

The reviewer should reject each fixture for the correct reason. A checklist that passes obviously wrong variants is not an effective control.

Validate the final artifact and path#

Run Migma's documented Preflight for email-level issues, then continue into the destination system:

inspect desktop, mobile, dark-mode, and images-off states;
compare the final image source and crop with the approved asset;
verify alt text does not introduce an unsupported offer claim;
click image and button destinations after redirects;
confirm the landing page and cart represent the pictured variant;
repeat after destination import or template transformation;
preserve a received message from the final sender.

Preflight cannot know whether a blue product is excluded by a commerce rule. Catalog and checkout evidence remain separate gates.

Define change triggers#

Reopen the audit when the offer, product set, variant availability, catalog media, destination URL, crop, text overlay, packaging, rights scope, market, or destination template changes. Do not reuse an approval tied to another offer version.

Stop conditions#

Stop when the depicted product cannot be identified; an image includes both eligible and excluded items without clear framing; the destination defaults elsewhere; stock language is inferred from a photograph; reference assets survive without permission; the mobile crop changes the apparent offer; or no owner can replace an image after inventory changes.

Evidence limits#

Migma published dated product-image guidance and documents image-clone and Preflight workflows. Marketing Wiki did not test Migma, an asset license, image fidelity, a product catalog, inventory, destination page, cart, inbox, or outcome. Apply the audit to the exact offer and final delivered artifact.