Send Subscription Conversion Emails After Product Purchase

This step fires automatically every time a Shopify order is marked as paid, passing along full order data including the customer ID, line items, and product SKUs. No configuration is required — MESA listens to your store in real time. The workflow is intentionally designed to fire on every paid order and relies on later steps to filter down to only qualified customers, so casting a wide net here is by design.

MESA pulls your Shopify store details — specifically your shop domain and store name — so they can be used later when building the email. This runs automatically and requires no configuration. The shop domain is used to construct the direct link to the product page, and the store name appears in the email sign-off. This data stays in memory for the Send Email step to reference.

MESA fetches the full customer record using the customer ID from the trigger, retrieving two key fields: total order count and existing tags. If the customer's order count is greater than zero (they've bought before) or they already have your subscriber tag, the loop's filter will skip them entirely in the next step. This is the first of two customer lookups — this one checks eligibility before the 7-day delay begins.

The loop iterates through every line item in the order and applies three simultaneous filters: the line item's SKU must match your specified product SKU, the customer's order count (from Step 3) must equal zero, and the customer must not have your subscriber tag. You need to configure two values here. First, enter the SKU of the product that should qualify a customer for the subscription offer — find this in your Shopify admin under Products > [Product] > Variants. Second, enter the customer tag used to identify existing subscribers (default: subscriber). If no line items pass all three conditions, the workflow ends without proceeding to the delay or email.

This step pauses the workflow for 7 days after a qualifying line item is found before any further action is taken. The delay is pre-configured to 7 days and doesn't require changes unless you want to adjust the timing — for example, shortening it to 3 days for consumable products or extending it to 14 days for slower-use items. During testing, the delay is automatically bypassed so you can verify the full workflow runs end-to-end without waiting a week.

After the delay, MESA fetches the customer record again using the same customer ID. This is a fresh lookup that reflects any changes made in Shopify since the original order was placed. The updated tags retrieved here are passed directly to the Filter step, which decides whether the email should still go out. Relying on the data from Step 3 at this point would risk sending offers to customers who have already converted to subscribers during the delay window.

MESA re-fetches the full order using the original order ID from the trigger. The key field used in the next step is the order's current fulfillment status. If the status has changed to restocked, it indicates the order was returned or cancelled and the Filter step will halt the workflow. Like the second customer lookup, this step ensures the workflow acts on current data before committing to sending an email.

MESA fetches the full product record for the qualifying line item using the product ID stored in the loop. The key value retrieved here is the product's URL handle, which is combined with the shop domain from Step 2 to construct the product page link included in the email. No configuration is needed — MESA automatically uses the product ID from the current loop iteration.

The filter evaluates two conditions before allowing the email to proceed: the customer's current tags (from Step 6) must not include your subscriber tag, and the order's fulfillment status (from Step 7) must not be restocked. Both conditions must pass for the workflow to continue. You need to enter your subscriber tag here — it should match exactly what you entered in the Loop step (default: subscriber). If either condition fails, the workflow stops cleanly without sending an email.

MESA sends a pre-built HTML email to the customer address on the order with the subject line "Switch to subscription & save 15%." The message greets the customer by first name, references the product they purchased by title, and includes a direct link to the product page. The email is ready to use without changes, but you'll want to review the subject line and body to match your brand tone, confirm the discount percentage aligns with your actual subscription offering, and verify the product page link resolves to a page where customers can actually sign up for a subscription. To edit: open the Send Email step and update the Subject and Message fields directly.