Blog
August 9, 2026

Email vs SMS Re-Engagement on Shopify

Email versus SMS versus on-site for Shopify re-engagement. When Klaviyo is enough, when Postscript is justified, and why interrupt should match intent strength.

Aaron
Aaron
11 mins read

A shopper tries on a black linen dress, checks the size chart twice, and leaves. By lunch, she qualifies for an email flow, an SMS flow, and a personalized return visit. Three tools have found one person. That does not mean all three have earned the right to interrupt her.

The channel decision belongs after the intent decision.

Email, SMS, and on-site re-engagement are different levels of interruption. Email is best for detailed, lower-pressure follow-up. SMS fits explicit opt-in plus strong, time-sensitive product intent. On-site returning state is best when the shopper comes back unaided. The strength and freshness of intent should determine how loudly a Shopify store responds.

Shopify lifecycle marketer choosing between email, SMS, and an on-site return experience for a specific fashion shopper

A saved garment can return quietly on-site, arrive with context by email, or justify a concise text when intent and permission are strong. Editorial image in Classic Antla disposable-camera style.

Channel choice is a pressure decision

Re-engagement brings prior intent back into the next customer interaction. It does not automatically require a send. The practical definition in what ecommerce re-engagement means starts with a known signal and a useful next step, not with a campaign calendar.

A lifecycle marketer should ask four questions before choosing a channel:

  1. How strong was the action? One product view is weaker than repeated views, a saved item, a completed try-on, or checkout initiation.
  2. How fresh is it? A dress considered two hours ago can support product-specific language. After six weeks, the same event may describe old taste rather than current intent.
  3. What permission exists? Email consent and SMS consent are separate operating states. A phone number in a customer record is not evidence of promotional SMS permission.
  4. How much explanation is needed? Fit notes, alternate imagery, delivery details, and several products need room. A single urgent fact can survive a text.

The resulting comparison is less glamorous than a new automation diagram, which is useful because it can actually govern one.

ChannelInterruptCostConsentDetail
Email through KlaviyoModerate and asynchronousLow marginal send cost, with platform and creative overheadEmail marketing permission requiredHigh. Supports images, fit context, alternatives, and several links
SMS through PostscriptHigh and immediateHigher per-message cost plus platform costExplicit SMS opt-in requiredLow. Best for one product, one reason, and one action
On-site returning stateLow. Appears only when the shopper returnsProduct and implementation cost, no outbound send feeDepends on cookies, identity, privacy choices, and the experience shownHigh, because the PDP can restore product, variant, size, and visual context

Cost should influence frequency, but cheap delivery is not permission to send weak messages. Email can waste attention at scale. SMS can waste attention one vibration at a time.

Klaviyo is enough for most considered purchases

Default to email when the shopper has valid email permission, the intent is meaningful but not urgent, and the message benefits from visual or explanatory room. For fashion, that is a large share of re-engagement.

The useful email is attached to the garment and the unresolved question. A shopper who previewed a cropped jacket may need the same colorway, a clear return path, shoulder and length information, and perhaps one credible alternative. She does not need a generic “we miss you” note seven hours after leaving.

Klaviyo’s help center documents the mechanics for flows, profiles, segmentation, and message controls. The lifecycle decision comes first: trigger only on an event you can explain, preserve the Shopify product and variant IDs, suppress purchasers, and let the signal expire.

Klaviyo is usually enough when:

  • the event is a product view, size-guide open, wishlist save, or completed try-on without a deadline
  • the creative needs a product image, saved preview, fit reassurance, or alternatives
  • the shopper has email permission but no SMS opt-in
  • the store needs a measured sequence rather than an immediate interruption
  • the team is still proving whether the signal produces incremental orders

Email also gives the marketer more room to show restraint. One message can contain the exact item and the information that resolves hesitation. It can be tested against a holdout and judged on orders, unsubscribe behavior, and margin.

Litmus email benchmark guidance is useful for understanding how email programs are commonly measured, but a broad benchmark cannot tell you whether this particular re-engagement created demand. Compare product-linked recipients with an eligible holdout. Opens are delivery diagnostics, not proof that the shopper needed the message.

Postscript is justified by permission plus strong intent

SMS earns attention quickly because it sits beside conversations, delivery updates, and authentication codes. That proximity is the feature and the liability. A lifecycle team should reserve it for a reason that still makes sense when read on a locked phone screen.

Postscript provides Shopify-focused SMS tooling, but software availability is not the decision rule. The rule is explicit SMS consent combined with a recent, specific, and useful event.

Reasonable candidates include:

  • an opted-in shopper requested a back-in-stock alert for the exact size that just returned
  • a saved cart or try-on contains one garment, and a genuine shipping cutoff is approaching
  • the shopper asked for a product-specific update by text
  • repeated high-intent activity shows a current decision, and frequency rules prevent channel pileup

Weak candidates include a single collection view, an old browse event, a general sale, or the mere existence of a phone number. SMS should not become the place where low-performing email copy goes to feel louder.

Keep the message compact. Name the item, state the reason for contacting now, link to the exact destination, and suppress immediately after purchase or opt-out. If the text needs three products, a sizing essay, and a paragraph defending the offer, it wanted to be an email.

When both channels are available, choose a priority rather than launching twins. For example, reserve SMS for the restock event and suppress the same-day email, or send the richer email first and allow SMS only if a separate urgent state appears. Cross-channel orchestration mostly means preventing your own tools from forming a small crowd around the customer.

A returning PDP can do the job without a send

Some shoppers come back through a bookmark, branded search, an open tab, or their own memory. The store already has attention. Sending a reminder at the same moment can add noise to a journey that restarted itself.

On-site returning state should restore useful context without pretending to know more than the data supports. A fashion PDP might:

  • reopen the exact product and selected color
  • remember the size the shopper inspected
  • restore a saved try-on or offer a clear path to recreate it
  • show current stock and delivery information
  • remove re-engagement modules after the item is purchased

This channel is especially good for medium-confidence signals. The shopper controls the timing, and the storefront has enough room to answer questions about fabric, drape, coverage, length, and fit. No subject line has to carry the entire decision.

On-site state cannot replace every send. It does nothing if the shopper never returns, and identity or browser storage may not survive a device change or privacy choice. Treat it as the least interruptive layer, not as a magical universal profile.

Build the rule before adding another flow

A reliable Shopify re-engagement engine gives each event an identity state, eligible channels, purchase suppression, and expiry. Channel selection can then be written as a small policy.

Start with this sequence:

  1. Name the event precisely. try_on_completed and size_back_in_stock can support different decisions. engaged_user cannot.
  2. Score intent without inventing certainty. Repetition, product specificity, recency, and effort increase confidence. A page load alone stays weak.
  3. Check channel permission. No SMS branch should exist for an email-only subscriber.
  4. Choose the quietest sufficient response. Restore state on-site, use email when detail helps, and use SMS when urgency and opt-in justify the interruption.
  5. Close the loop. Purchase, return, opt-out, stock change, and event expiry must update eligibility.
  6. Measure incrementality. Hold back an eligible group and compare orders, contribution margin, opt-outs, and complaints, not only attributed clicks.

The creative should answer the likely hesitation before reaching for a coupon. The playbook for re-engaging fashion shoppers without discount fatigue goes deeper on that choice. A saved preview, accurate stock update, fit explanation, or stronger return path can be more relevant than another 15% code.

Antla’s email capture feature can connect a completed virtual try-on to an email identity at the moment the shopper has a specific reason to save the interaction. That is useful lifecycle data because the identity arrives with product context. It still does not create SMS permission.

Re-engagement channel questions

Should I re-engage Shopify customers with email or SMS?

Use email for most product-specific follow-up when you have email permission and the message needs imagery, fit detail, alternatives, or a measured sequence. Use SMS only when the shopper explicitly opted into texts and the event is strong, recent, and concise. If both channels qualify, set a priority and suppress duplicate contact.

When is SMS appropriate?

SMS is appropriate when explicit consent meets a specific reason to act now, such as a requested size returning to stock or a genuine shipping cutoff on a recently saved garment. The text should name the product, explain the timing, and link directly to the relevant page. A weak browse signal does not become strong because it can trigger a text.

Can on-site returning state replace a send?

Yes, when the shopper returns without prompting and the store can restore useful context such as product, variant, size, stock, or a saved try-on. It is the least interruptive option and often the best one. It cannot reach someone who does not return, and its identity may not persist across devices or privacy settings.

Keep dormant-list work in its own lane

Recent product intent and long-term subscriber inactivity are different jobs. A shopper who tried one dress this morning needs event-led channel selection. A subscriber who has been quiet for months needs a broader lifecycle decision. The guide to email re-engagement with virtual try-on handles that dormant-list use case without turning it into an excuse for an immediate SMS.


About the author: Aaron is the founder of Antla. He thinks SMS is a privilege you earn with an opt-in and a specific garment, not a cheaper email.

Pick one high-intent Shopify event and write its email, SMS, and on-site eligibility on one page. If a completed try-on is that event, add Antla to Shopify and preserve the garment context before choosing the interrupt.