{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-catalog-store-variant-identity","id":"email-catalog-store-variant-identity","slug":"email-catalog-store-variant-identity","title":"Bind Email Product Cards to Store and Variant Identity","description":"Prevent a valid product card from pointing to the wrong store or variant. A composite catalog key and destination assertion sheet.","dek":"Prevent a valid product card from pointing to the wrong store or variant. A composite catalog key and destination assertion sheet.","category":"Ecommerce Email","topics":["Migma","email marketing","ecommerce email"],"publishedAt":"2026-09-18","updatedAt":"2026-09-18","lastVerifiedAt":"2026-09-18","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma: Shopify integration","url":"https://docs.migma.ai/integrations/shopify?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-catalog-store-variant-identity"},{"title":"Shopify: Find a variant ID","url":"https://help.shopify.com/en/manual/products/variants/find-variant-id?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-catalog-store-variant-identity"},{"title":"Migma: Fashion email platform guide, September 17","url":"https://migma.ai/blog/best-fashion-email-marketing-platforms?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-catalog-store-variant-identity"}],"wordCount":764,"body":"Bind each Migma product card to a store, product and variant before approving its image and destination. A familiar product name or shared SKU is not enough evidence that a link leads to the exact item the campaign intends to sell.\n\n> **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 18, 2026.\n\n> **Affiliation disclosure:** Marketing Wiki’s commissioning maintainer also maintains Migma. This guide is published directly by automation without independent review.\n\nMigma's [Shopify integration](https://docs.migma.ai/integrations/shopify?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-catalog-store-variant-identity) uses connected product, inventory, customer and order context for email preparation, with review before action. We recommend providing an explicit catalog identity for every featured item. The documentation does not establish an automatic cross-store reconciliation service.\n\nMigma's [September 17 fashion-platform guide](https://migma.ai/blog/best-fashion-email-marketing-platforms?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-catalog-store-variant-identity) prompted this narrower operational question. Its broad ranking, pricing and real-time synchronization claims are not used as evidence here. [Shopify's variant-ID documentation](https://help.shopify.com/en/manual/products/variants/find-variant-id?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-catalog-store-variant-identity) provides the useful technical fact: variant identifiers support reconciliation, including for products without visible option choices.\n\n## Make ambiguity visible before generation\n\nA fictional accessories business has two regional stores. Both sell an item called “Studio Tote.” One storefront offers a zip closure and the other a snap closure. The product photography is similar, and a spreadsheet uses the same merchandising nickname for both.\n\nA writer can produce accurate copy about one item while a copied link opens the other. A working URL and a recognizable image would not catch the mismatch. The required check is identity, not merely link availability.\n\nRecord the following composite key in the production sheet:\n\n```text\nbrand: Studio Goods\nsource store: regional storefront A\nproduct reference: catalog product identifier\nvariant reference: exact selected variant identifier\noption tuple: black / zip closure\ndestination market: region A\ndestination: approved customer-facing product link\ncreative slot: second product card\nverified by: catalog owner\nverified at: timestamp\n```\n\nThese labels are an editorial record, not an API payload. Do not expose administrative identifiers in customer-facing copy. Keep the stable references where producers can inspect them while readers see a clear product name and useful description.\n\n## Test two rows that look interchangeable\n\nCreate a small fixture containing the two regional totes. Give both the same display title but different store references, variant references and closure descriptions. A matching rule based only on title should fail the fixture. A rule that resolves the intended store and variant should select exactly one row.\n\nIf your source uses SKUs, document their scope and ownership. Do not assume that a SKU is globally unique across every supplier, store and historical catalog your organization has used. That is a property to verify in your own data, not something the campaign can infer from a tidy-looking code.\n\nThe fixture is also useful for agency handoffs. A designer should be able to point from a canvas card to one production-sheet row without guessing which client or regional catalog supplied it.\n\n## Give Migma a constrained product brief\n\nAsk Migma to prepare the card using the approved product facts, image and customer-facing destination from that row. Specify which option is pictured and whether the CTA should open a particular variant or the general product page. Do not let a requirement for a variant-specific destination disappear into “Shop now.”\n\nReview the generated card against the row: displayed item, option wording, image, link and region. If the connector cannot provide a required fact, supply it from the catalog owner's approved record or leave the claim out. A missing fact should not be filled from another store because the title matches.\n\nOpen the final destination in the relevant market context and confirm the selected option. Redirects, language selectors and remembered storefront state can affect what a reviewer sees. Record the conditions used instead of claiming a single desktop visit proves every customer's route.\n\n## Keep identity distinct from availability\n\nAn identity match does not prove current stock, offer eligibility or a reserved item. Use the [product-image eligibility audit](/articles/promotional-email-product-image-eligibility-audit) for promotion scope and the [restock promise guide](/articles/email-restock-notification-promise) for availability wording.\n\nIf a catalog item is replaced, do not silently reuse the old row because the picture is unchanged. Ask whether the product, variant, destination or promise changed, then review the affected card. The acceptance condition is one unambiguous source item and one intended customer destination per card.\n\nNo Shopify account, catalog or Migma draft was accessed or changed during this research. The two-store example is synthetic. Begin with the product name that appears most often across your stores and prove which exact item each current email card represents."}