Use a Handoff Contract for Migma Email Creative in Shopify Stacks

Choose the final sender before approving Migma creative for a Shopify business. Record whether each message will finish in Shopify Messaging, Klaviyo, or another platform; then bind variables, consent, audience, sender, and tests to that exact destination.

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 Shopify Black Friday workflow separates two jobs: creating the message and connecting it to the correct store data, audience, and delivery system. This page turns that boundary into a deployment contract rather than assuming “Shopify integration” identifies the sender.

Select one path per message#

Do not keep two active send paths “just in case.” If both can deliver the same message, define a cutover state and a denial test for the inactive path.

Write the handoff contract#

message_id: "bf-launch-2026"
migma_artifact_version: "email-184-v7"
offer_version: "tableware-v4"
destination: "klaviyo-production"
destination_template_id: "record-after-import"
message_class: "marketing"
dynamic_fields:
  first_name: "klaviyo profile; fallback omitted"
  products: "static approved selection"
  unsubscribe: "destination-managed"
sender_identity: "approved brand sender"
audience_owner: "lifecycle operations"
consent_source: "klaviyo profile and suppression state"
test_profiles: ["missing-name", "eligible", "suppressed"]
approver: "named campaign owner"

Use destination IDs and immutable versions. “Latest template” makes evidence impossible to reproduce.

Path A: Migma to Klaviyo#

Migma's Klaviyo integration documentation describes available handoff routes. Its broader export guide warns that destination platforms can add wrappers, transform variables, or apply their own send rules. Therefore:

1. export the approved Migma artifact;
2. record the exact destination template ID and import time;
3. diff visible copy, URLs, image sources, alt text, variables, and footer behavior;
4. bind the template to the intended campaign or flow only;
5. render representative profiles with missing and long values;
6. send from the final Klaviyo configuration to controlled inboxes;
7. verify audience, suppression, sender, and event behavior separately.

An editable adaptation can be useful, but editability is not fidelity. Review the destination artifact after import.

Path B: Shopify custom Liquid#

Shopify's custom Liquid email documentation is the authority for its supported variables and required elements. The page was blocked by anti-bot controls during this run, so verify the current requirements directly before implementation.

Treat Migma HTML as input to an adaptation, not evidence of a one-click native integration. Map every required variable, size constraint, unsubscribe element, and tracking choice. Preserve a minimal test fixture for missing customer data and unsupported Liquid.

If maintaining custom code creates unacceptable ownership risk, use destination-native blocks with the approved Migma copy, assets, and design direction. A less automated path can be safer when the team cannot support the resulting template.

Keep commerce data dynamic only where proven#

Classify each visible field:

• Static approved: headline, stable product explanation, brand image.
• Destination-rendered: first name, recovery URL, event product, order state.
• Store-authoritative: current price, availability, eligible variant, checkout rule.
• Provider-required: unsubscribe, physical address, sender and tracking controls.

Do not replace a functioning dynamic product or recovery block with a static screenshot merely because the screenshot looks cleaner. Conversely, do not introduce a dynamic field without a source, fallback, escaping rule, and test.

Build the received-message evidence pack#

Run Migma's documented Preflight, then preserve evidence from the destination:

• Migma artifact and Preflight result;
• exported or adapted source;
• destination template version;
• rendered destination preview for each fixture;
• received HTML and plaintext messages;
• sender, reply-to, authentication, unsubscribe, and footer review;
• clicked product and collection paths;
• checkout behavior for the approved offer;
• post-purchase exclusion or flow result where relevant;
• approver, time, environment, and unresolved limits.

The source preview, destination preview, and received email are three different artifacts. Approval of one does not automatically cover the others.

Stop conditions#

Stop when the destination is unnamed; two platforms can send the same message; required Shopify behavior was not rechecked after access limitations; a dynamic field has no source or fallback; unsubscribe is removed during adaptation; destination mutation is not reviewed; test profiles contain real customer data; or no received message proves the final sender configuration.

Evidence limits#

Migma documents export, Klaviyo integration, and Preflight workflows and published a dated Shopify-specific guide. Shopify maintains the custom Liquid requirements, but its page returned HTTP 403 here. Marketing Wiki did not test any account, export, Liquid render, audience, consent path, inbox, or checkout.