Build or Buy Web Push Notifications on Shopify?
Web push notifications are a rent-first channel on Shopify: buy the app unless a PWA program is funded, where push becomes an estimated $8,000–$20,000 in added scope (Deploi estimate, illustrative). The buy lane covers cart recovery, back-in-stock, and price-drop automations for a low monthly line, live in a day. The build lane rides the PWA's service worker, keeps subscriptions on your keys, and adds the Home Screen install iOS requires for push.
Your profile — see how the verdict shifts
- Confidence
- Medium — Stable web standards and low lock-in, but the verdict pivots on a strategic input (a funded PWA program) and app pricing is unverified
- Reference scenario
- $20M–$100M GMV · agency dev bench · single storefront
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under $2M revenue | BUY | A free push-app tier is a fine channel experiment; custom scope for a secondary channel is not where your first dev dollars go. |
| $2M – $15M | BUY | Check your email suite first: bundled push beside email and SMS (Omnisend's model) beats paying a standalone line, and a build case doesn't exist yet at this size. |
| $15M – $75M | DEPENDS | No PWA program means keep renting. A funded one flips it: push becomes bounded added scope on a service worker you're building anyway, and the channel data lands in your stack. |
| $75M+ | DEPENDS | Subscriber- and impression-priced fees grow with traffic while the build increment stays flat, and app-like mobile UX is more often the strategy here. The PWA question still decides it. |
What Web push notifications Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — indirect | Medium | Cart, browse, and restock nudges reach shoppers who never surrendered an email address: recovery pressure on the anonymous majority of traffic. |
| Retention & LTV | Medium | A one-tap opt-in builds a reachable audience from visitors who skip every signup form; restock and price-drop alerts then hand lapsing browsers a reason to return. |
| Revenue — direct | Low | Flash-sale broadcasts drive same-day clicks, but modest click-through and browser-level fatigue keep push a nudge channel rather than a primary revenue engine. |
| Customer experience | Low | Timing decides the experience: an intent-triggered soft prompt reads as service, while a cold permission demand on first pageview reads as spam and burns the ask. |
Spend ceiling: Web push is a secondary channel beside email and SMS, so size spend that way: rent it for a small monthly line, and own it only when a PWA program makes push marginal added scope.
What buying enables (top apps)
- + Live this week: soft-prompt templates plus cart-recovery, back-in-stock, and price-drop automations out of the box
- + Vendor-maintained tracking of permission-UX changes across Chrome, Safari, and Firefox
- + Suite bundling through Omnisend puts push beside email and SMS under one subscription and one segmentation model
- + Send scheduling, segmentation, and engagement reporting nobody budgets to rebuild
What building additionally unlocks
- + One service worker carrying push, offline caching, and the Home Screen install that iOS requires for push delivery at all
- + Subscriptions on your VAPID keys, keyed to customer records: push engagement joins email and SMS in one owned profile
- + Prompt UX that is fully yours: intent-triggered, styled as storefront, tested like any other section
- + Event-driven sends from your own webhooks and Flow triggers, with no per-impression meter running
Find Your Verdict in 3 Questions
Is an app-like mobile storefront — a PWA — funded or already live?
Yes: Go to question 2.
No: Your verdict: BUY — rent the channel; standalone custom push never pays back the scope.
Do you want push subscriptions and engagement data in your own stack, beside email and SMS?
Yes: Your verdict: BUILD — push rides the PWA's service worker as bounded added scope, on your keys.
No: Go to question 3.
Does a suite you already pay for bundle web push on your plan?
Yes: Your verdict: BUY — switch on the bundled channel; a second push subscription is suite overlap.
No: Your verdict: BUY — a dedicated push app covers the automations today; revisit at your next mobile-strategy review.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | An app prompts visitors the same day; the build is a service worker, a sending backend, and subscription storage across an estimated 2–4 weeks inside a PWA program (Deploi estimate, illustrative). | ||
| Recurring fees | Push apps price by subscribers or impressions, so the fee grows with the list; delivery through the browsers' own push services costs the build nothing, leaving upkeep as the only line. | ||
| Maintenance & upgrades | Vendors absorb browser permission-UX churn across Chrome, Safari, and Firefox; a build owns that tracking itself at the standard ~15–20% of build cost per year (Deploi estimate). | ||
| Switching & exit | Lock-in is genuinely low: subscriptions tied to a vendor's keys don't migrate, but a one-tap opt-in list rebuilds in weeks, unlike an email list. | ||
| Risk | |||
| Vendor risk | Standalone push apps sit in suite-consolidation territory, the pattern that keeps folding single-channel tools into platforms; a build answers to browser standards, not a vendor roadmap. | ||
| Security & compliance surface | Modest either way: push tokens carry no payment data, though the build makes you custodian of VAPID keys and endpoint records. | ||
| Platform-deprecation exposure | The Push API and service workers are stable web standards far from checkout's churn; the moving part is browser permission UX, and both lanes ride those changes. | ||
| Value | |||
| Fit to requirement | Apps ship the jobs merchants actually run (cart recovery, back-in-stock, price drop) with segmentation attached; a build matches your prompt UX but must rebuild that tooling. | ||
| Time to market | Prompting visitors this week versus weeks of scope that only makes sense inside a larger PWA timeline. | ||
| Performance & scale | One more vendor script and modal on every page load versus a service worker that ships with the storefront and earns extra keep as offline caching. | ||
| Data ownership & AI-readiness | Owned subscriptions key push engagement to customer records beside email and SMS; rented, the channel's behavior data sits in a vendor dashboard behind export limits. | ||
| Focus & opportunity cost | Web push is a secondary channel; standalone custom scope here is a poor trade, which is exactly why the verdict hinges on a PWA program already carrying the build. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Omnisend | Live — Email + SMS bundled; a leaner-budget alternative to the anchor | Contact-tiered | Stores that want push beside email and SMS without a standalone line |
| Dedicated push apps | Category — Push-only specialists priced by subscribers or impressions; a churn-prone single-channel category — shortlist names and verify | Free–$100/mo bands at mid-market subscriber counts (illustrative) | Fast standalone launch with cart-recovery and back-in-stock automations built in |
| PWA service worker + Push API | Build lane — This page's conditional verdict: push as added scope inside a PWA program, on your own VAPID keys | $8,000–$20,000 added to a PWA build (Deploi estimate, illustrative); no subscription | Stores funding an app-like storefront that want the channel owned |
The Build Path
- Push scope inside a PWA program: The PWA's service worker registers subscriptions on your VAPID keys; a small backend stores endpoints keyed to customer records and sends through the browsers' push services. Opt-in uses an intent-triggered soft prompt styled as part of the storefront.
- Serving the worker: Liquid vs. headless: A standard Liquid storefront serves the service worker through an app-proxy path from a lightweight custom app; a Hydrogen or headless build owns the origin and serves it directly.
- Automation triggers, not a campaign suite: Wire push into events you already emit (abandoned checkout, back in stock, price drop) via webhooks and Flow, and skip rebuilding broadcast tooling until the channel earns it.
- Effort band
- $8,000–$20,000 for the push scope inside a PWA program (Deploi estimate, illustrative); the increment lands in the $10–25K contact-form band, while the PWA program carrying it typically sits in the $25–75K band
- Typical timeline
- 2–4 weeks for the push scope riding a PWA build already underway (Deploi estimate, illustrative); standalone, the calendar belongs to the PWA program, not the push feature
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): browser permission-UX changes, service-worker upkeep, and API version bumps, roughly $1,200–$4,000/yr on this increment (Deploi estimate, illustrative). There is no subscription line.
- What you own — and what you take on
- You own: the VAPID keys, the subscription records, the prompt UX, and push engagement joined to customer profiles. You take on: browser-quirk tracking, and the discipline not to rebuild a campaign suite nobody asked for.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$500 | $8,000–$20,000 |
| Years 1–3 (recurring) | $1,100–$5,400 | $3,600–$12,000 (maintenance) |
| 3-year total | ≈$1,100–$5,900 | ≈$11,600–$32,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: one mid-band push subscription held flat; impression-priced tiers grow with sends, so flat is conservative.
- † Build path: the push increment only — the PWA program around it is budgeted as its own decision; upkeep at ~15–20%/yr; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Impression- and subscriber-priced tiers grow with every opt-in and every campaign: cheap at install, then the bill tracks list size
- — A hard permission prompt on landing burns the ask: browsers suppress re-prompting after a denial, so a vendor SDK's default timing can spend the channel before it starts
- — Suite overlap: paying for a standalone push app while your email platform already bundles the channel on your plan (check before install)
- — Dashboard subscriber counts include expired endpoints, so deliverable reach runs smaller than the number you're billed against
On the build path
- — Campaign tooling is the hidden 80%: segmentation, scheduling, and reporting are what apps actually sell, so rebuild only the automations you'll run
- — Serving the service worker on a Liquid storefront needs an app-proxy path from a custom app: unglamorous plumbing that surprises first-time scopes
- — Building doesn't lift the iOS cap by itself: Home Screen install is Apple's requirement either way, and only the PWA program changes reach
- — Upkeep isn't zero: ~15–20% of build cost per year (Deploi estimate), mostly tracking browser permission-UX changes
What Merchants Say
Permission-prompt regret is the recurring shape: stores that let an SDK fire the browser ask on first pageview report burned opt-ins they can't win back.
The 1–2★ theme for push apps pairs pricing creep with reach doubt: bills that climb with impressions while merchants question how many subscribers still receive anything.
If You Change Your Mind Later
If you bought and outgrow it
Uninstall is clean and the stranded asset is small; web push is the rare marketing channel with genuinely low lock-in. Subscriptions ride the vendor's keys, so a provider switch resets the list, but one-tap opt-ins rebuild a working list in weeks rather than the years an email list takes. Check export terms for subscriber and engagement data anyway.
If you built and want out
You hold the VAPID keys and the endpoint records, so the subscriber list survives any tooling change around it. Retreating to an app later means re-prompting subscribers under the vendor's keys: a few weeks of rebuild, not a migration project. The service worker keeps earning its keep either way, since offline caching and install prompts don't uninstall with the channel.
When This Answer Changes
We're watching for:
- ▸ Shopify shipping native web-push campaigns or extending Shop app notifications into storefront marketing (none as of July 2026 research)
- ▸ Apple relaxing the Home Screen install requirement for iOS web push — the reach cap inside this verdict
- ▸ Your email/SMS suite adding bundled web push to a plan you already pay for
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Does web push work on iPhone for Shopify stores?
Web push reaches iPhones only after the shopper installs your storefront to the Home Screen as a web app; Apple added that support in iOS 16.4 and kept the install requirement. Android Chrome and desktop browsers subscribe straight from the page. Mobile-heavy Shopify stores should treat iOS reach as a PWA decision, not a push-app setting: no app can prompt Safari visitors without that install.
How much do web push apps cost on Shopify?
Web push apps run in a free-to-$100/mo illustrative band at mid-market subscriber counts, priced by subscribers or by impressions. Suites change the math: Omnisend bundles push beside email and SMS on paid plans, so check what a subscription you already pay for includes before adding a standalone install. Impression pricing is the line to model, because the bill tracks every campaign send.
When does building web push beat buying an app?
Building wins only when a PWA program is funded or live: the same service worker then carries push for an estimated $8,000–$20,000 in added scope (Deploi estimate, illustrative). Subscriptions and engagement data stay in your stack, keyed to customer records. A standalone push build fails the math, because campaign tooling, segmentation, and browser upkeep rebuild what apps rent for a low monthly fee. No PWA program, no build case.
Your Next Steps
If you're going with BUY
- Check whether your email/SMS suite already bundles web push before adding any standalone install
- Shortlist on pricing model first: subscriber-priced beats impression-priced at broadcast volumes
- Replace any default first-pageview permission ask with an intent-triggered soft prompt
- Start with cart-recovery and back-in-stock automations; hold broadcasts until the list earns them
- Track deliverable reach against billed subscribers, since expired endpoints inflate the dashboard number
If you're going with BUILD
- Confirm the PWA program first; scope push as its rider, never as a standalone project
- Store subscriptions on your own VAPID keys, keyed to customer records from day one
- Serve the service worker via an app-proxy path on Liquid, or from the origin on headless
- Wire sends to events you already emit: abandoned checkout, back in stock, price drop
- Measure opt-in rate and push-attributed sessions from week one; cut the channel if it stays noise
Official Docs & Sources
- Shopify Flow — Shopify Help Center
- Managing customer privacy settings — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Abandoned Checkout Recovery on Shopify?
Abandoned checkout recovery belongs in the email/SMS platform you already pay for, with an audited tracking layer underneath.
Should You Build or Buy Email Marketing & Flows on Shopify?
Buying email marketing and flows is the clear call for mid-market Shopify stores at every band.
Should You Build or Buy Back-in-Stock Alerts on Shopify?
Building back-in-stock alerts wins when an email platform is in place: a webhook plus a flow retires the app fee.
Should You Build or Buy SMS Marketing on Shopify?
Buying SMS marketing wins outright: the real decision is your email platform's SMS module versus a standalone platform, never an in-house build.
Should You Build or Buy a Points Program on Shopify?
Buying a points program wins for Shopify brands under roughly $50M in revenue; the liability math and vendor ecosystems beat building.
Ready to pick your push lane?
We'll check what your suite already bundles, shortlist the right push app, or scope push into a PWA program if app-like UX is where you're headed. Honest math first: the channel is only worth owning when the service worker is already yours.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing is illustrative band pricing, re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.