Klaviyo vs Apple Wallet Push for Shopify Retention (2026)

Klaviyo is the default retention stack for most Shopify stores. There are good reasons for that. The platform is well-built, the data model is sane, the deliverability infrastructure is mature, and the agency ecosystem is enormous.

There is also a structural problem with using Klaviyo for the kind of messaging Shopify stores send most often: transactional updates (order shipped, order delivered), earned-event notifications (points earned, referral redeemed), and lifecycle nudges (cart abandoned, replenishment due). For all of those, Apple Wallet push is a better channel by every measure that matters except one. This post lays out the comparison honestly.

If you take only one thing away: keep Klaviyo for promotional campaigns and acquisition emails. Move the transactional and earned-event traffic to wallet push. Most stores are using Klaviyo for everything because wallet was harder to set up, and that has changed.

The numbers

A direct comparison of the three retention channels:

| Channel | Open rate | Click rate | Unsubscribe friction | Cost per message | |---|---|---|---|---| | Email (Klaviyo) | ~21% (DTC avg) | ~2.6% | 1 click, easy | $0.001 to $0.005 | | SMS (Klaviyo) | ~98% delivered | ~9-19% (varies) | "STOP" reply | $0.01 to $0.03 | | Apple Wallet push | ~90%+ visible | 15-40% | 1 tap (remove pass) | ~$0 |

The open-rate column is the most important. Email at 21% means 79% of your sends never get seen. Wallet push at 90%+ means 9 out of 10 sends actually surface on the customer's lock screen. For a transactional message like "your order shipped" or "points earned," that delivery rate is the difference between the customer knowing what happened and the customer not knowing.

The cost column is the second most important. Klaviyo charges per-message based on contact list size. SMS is meaningfully more expensive per send. Wallet push goes through APNs (for iOS) and FCM (for Android), both of which are essentially free at any volume a Shopify store would hit.

The unsubscribe-friction column is where wallet push has its biggest weakness. Removing a wallet pass is a single tap from the lock screen. There is no "you might want to come back" interstitial, no unsubscribe survey, no winback flow. If you abuse the wallet push channel, customers remove the pass and the channel goes with it. This makes wallet push closer to SMS than to email in the "use sparingly" continuum.

Where wallet push wins

Transactional messaging. Order paid, order shipped, order delivered. These are the messages customers actually want, sent at the moment they are most relevant. Email gets buried in promotions tabs. SMS works but you are paying per send and you are competing with bank fraud alerts and 2FA codes. Wallet push appears directly on the lock screen, opens 90%+ of the time, and updates the pass itself so the customer can re-check the status by opening their wallet later.

Earned-event notifications. Points earned, reward unlocked, referral attributed. These are messages the customer earned by doing something. The reciprocity makes them feel like updates, not marketing. Wallet push is the most appropriate channel for the same reason transactional messages work: the message is clearly relevant.

Loyalty balance and status. The wallet pass itself shows the current points balance, the next reward threshold, and the customer's referral code. Email cannot do this. SMS cannot do this. The customer opens their wallet to pay for coffee and sees their current loyalty status. That ambient presence is the actual retention mechanism. The pushes are secondary.

Order tracking from confirmation to delivery. A wallet pass with order status updates the back of the card in real time: processing, shipped, out for delivery, delivered. The customer never opens a tracking email. They tap the pass in their wallet when they want to know.

Where Klaviyo wins

Promotional campaigns. Sale announcements, new product launches, content marketing, brand storytelling. The wallet pass is the wrong channel for these because the customer did not opt into them and the unsubscribe is one tap. Email is the right channel because the customer expects promotional content in their inbox and the cost of unsubscribing is asymmetric (clicking unsubscribe costs more effort than archiving).

Acquisition. Welcome series for new email signups, lead nurturing, content upgrades. Klaviyo's strength is the email-list-as-asset model. The wallet pass requires the customer to have already bought something to install. Klaviyo can reach prospects; wallet push cannot.

Long-form content. Educational emails, customer success stories, product deep-dives. Wallet push is a 30-character notification. Anything that needs more than a sentence goes through email.

Browser abandonment flows that need links. A "you left this in your cart" email with product images and a CTA button is exactly what email is for. A wallet push for the same use case is awkward (the customer has to open the wallet, find a link on the pass, tap it) versus the natural email-with-button experience.

Segmentation and triggered flows. Klaviyo's flow editor and segmentation engine are mature and well-designed. Wallet push platforms have less sophisticated segmentation. For complex lifecycle flows (welcome → onboarding → upsell → reactivation), Klaviyo is still the right tool.

The mistake most stores make

The default Klaviyo setup at most Shopify stores looks like this:

• Email flow for order confirmation
• Email flow for shipping notification
• SMS flow for delivery notification (because the customer specifically wanted SMS for that)
• Email flow for points earned
• Email flow for referral credit
• Email and SMS flows for cart abandonment
• Email flow for replenishment
• Plus the promotional email campaigns the merchant actually wants to send

The first five items in that list are doing the work of wallet push and doing it through the wrong channel. The shipping notification email gets 21% open rate. The points-earned email gets 18% open rate (slightly worse than average because customers do not feel urgency to open them). The same messages through wallet push would hit 90%+ open rate with zero per-message cost.

The cart abandonment flow is a hybrid case. If the customer has the wallet pass, the abandonment can fire as a wallet push. If they do not, it falls back to email or SMS. Most platforms support this kind of channel fallback today.

The promotional campaigns at the bottom of the list are exactly where Klaviyo belongs. The mistake is using Klaviyo for everything because it is the only channel set up.

What the stack should look like

The retention stack that actually optimizes per channel:

• Wallet pass for: order confirmation push, shipping status, delivery confirmation, points earned, reward unlocked, referral attributed, replenishment nudge (for customers with the pass installed).
• SMS for: time-sensitive transactional events for customers without the wallet pass installed (delivery confirmation, urgent fraud alerts), and any messaging where the customer explicitly opted into SMS.
• Email for: promotional campaigns, welcome series, content marketing, long-form lifecycle flows, browse abandonment (with images), winback campaigns, and anything that does not fit a 30-character notification.

The key word in the email column is "promotional." Email is good at promotion. It is bad at transactional, because transactional sends do not need 79% inbox waste.

What about Klaviyo's own SMS product?

Klaviyo Mobile (formerly the standalone SMS product) is solid for what it does. The deliverability is good, the unified Klaviyo segmentation is convenient, and the per-message cost is in line with the industry.

The structural problem is the same: SMS is a transactional channel that costs $0.01 to $0.03 per message. For a Shopify store sending 50,000 transactional messages per month (shipping notifications, points-earned alerts, etc.), that is $500 to $1,500/month in SMS bills. Wallet push handles the same volume at zero per-message cost. The cost-per-message math alone justifies the switch for stores at scale.

For stores below ~5,000 orders/month, the absolute Klaviyo SMS bill is small enough that the switch is more about the customer experience than the cost. The lock-screen channel is genuinely better for transactional messages; the cost savings are a secondary benefit.

The acquisition cost of the wallet pass

The honest weakness in this whole argument is that the wallet pass is not free to acquire. The customer has to add it to their wallet. The most common acquisition channel (a button in the post-purchase email) converts at 30-50% on first-time buyers. Some customers never install the pass.

For those customers, the retention messaging still has to go through Klaviyo. The wallet-push channel is not universal the way email is. Stores that want full transactional coverage will run both channels, with wallet push as the preferred channel when the pass is installed and Klaviyo as the fallback when it is not.

In practice, after 6 months of an active wallet-pass program, most stores see 40-65% of their loyalty-program customers carrying the pass. That covers the majority of high-engagement customers (who are also the ones most worth talking to via lock-screen push). The long tail of low-engagement customers continues to get email-only treatment, which is the appropriate channel for them anyway.

How OfferGuard fits

OfferGuard's Enterprise tier ($900/mo) ships an Apple Wallet pass plus the push notification stack as part of a broader fraud-and-rewards engine. The pass surfaces points balance, share-and-earn code, and live order status. Push notifications fire on the events that matter most: order paid, shipped, delivered, points earned, referral attributed.

The angle that differentiates from a pure wallet-pass app (JeriCommerce, Toki) is that OfferGuard's wallet pass is tied to the same identity engine that runs fraud detection. The points minting on the wallet, the referral attribution that triggers a push, the loyalty balance updates - all of them are gated by the five-signal identity check that catches sharer-equals-redeemer fraud and welcome-discount cycling. The retention messaging only fires for verified buyers, not for the disguised repeat buyer who is gaming your offers.

For stores that want the wallet-push channel without rebuilding the entire fraud stack, JeriCommerce and Toki are simpler. For stores that want fraud + rewards + retention in one engine, the OfferGuard Enterprise tier consolidates the stack.

Frequently asked questions

Should I cancel my Klaviyo subscription?

No. Klaviyo is still the right tool for promotional email, acquisition, lifecycle flows, and any messaging that does not fit a wallet push. The recommendation in this post is to move transactional and earned-event messaging off Klaviyo onto wallet push, not to replace Klaviyo entirely.

What about customers without smartphones?

A small fraction of Shopify customers (typically <2% for DTC) do not have a smartphone capable of running a wallet pass. For those customers, all messaging falls back to email and SMS. The fallback is automatic in most wallet-pass platforms.

Does this work for Android customers?

Yes. Google Wallet passes work essentially the same way on Android, with FCM push notifications taking the role of APNs. Most wallet-pass apps ship both Apple and Google Wallet support.

What about customers who do not install the wallet pass at all?

They continue to get retention messaging through email and SMS, the same way they would without a wallet program. The wallet push channel adds reach for the customers who do install; it does not subtract reach for the customers who do not.

Is there a privacy concern with wallet push?

The customer explicitly added the pass to their wallet, and notifications are gated by the wallet permission. The privacy posture is similar to SMS: opt-in, identifiable, controllable by the user. Different from email (where the customer may have signed up years ago and forgotten).

How do I measure ROI on the channel switch?

Track open rate, click-through rate, and per-message cost for the messages you move from email/SMS to wallet push. The open rate should jump from ~21% (email) or ~98% delivered but ~30% read (SMS) to 90%+ visible. The per-message cost should drop to near zero for the moved messages. If those numbers do not improve, the channel switch is not working and worth re-evaluating.

What to do next

For stores already running Klaviyo: identify the transactional and earned-event flows currently running through Klaviyo email or SMS. Set up a wallet-pass platform (JeriCommerce, Toki, or OfferGuard Enterprise). Route the identified flows through wallet push with a Klaviyo fallback. Measure for 60 days.

For stores not yet running any retention stack: start with Klaviyo for the promotional and lifecycle flows that need email. Add a wallet pass within the first 3 months of operation. The longer you wait, the more retention messaging gets locked into the wrong channel as institutional habit.

For the broader rewards-and-retention picture, see the Shopify Apple Wallet loyalty card guide and the best Smile.io alternatives writeup.

Try OfferGuard's free Watchdog plan for the fraud-prevention side. The Enterprise tier adds the wallet pass and push stack.