STOQ vs. Notify!: Which Back-in-Stock App Wins?
STOQ wins this head-to-head for the dedicated back-in-stock job: restock alerts are the whole product, live in a day, with sends riding your ESP. Notify! wins when preorders and alerts should share one subscription. Both comparisons skip the owned lane: signup capture plus an inventory webhook into Klaviyo, an estimated $8,000–$20,000 build (Deploi estimate, illustrative), keeps demand-by-variant history yours forever.
Your profile — see how the verdict shifts
- Confidence
- Medium — The category structure (focused app vs. 2-in-1 vs. owned capture) is stable; both apps' tiers and integration depth stay unverified.
- Reference scenario
- $20M–$100M GMV · DTC · restock-driven catalog · Klaviyo stack
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under $2M revenue | BUY | A free or low tier from either app is fine; this isn't where your first dev dollars go. STOQ's single-job focus keeps setup to an afternoon. |
| $2M–$20M · restock-driven catalog | BUY | STOQ wins: the dedicated back-in-stock job done deep, feeding your ESP, with notification tiers still proportionate. |
| Also running preorders | BUY | Notify! wins this band: one subscription covering preorder plus back-in-stock means one widget, one vendor, one bill. |
| $75M+ · alerts as retention fuel | BUILD | Owned capture plus an inventory webhook into Klaviyo turns restock intent into a first-party asset; an estimated $8,000–$20,000 build (Deploi estimate, illustrative) replaces per-notification fees. |
What STOQ vs. Notify! Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — indirect | High | Restock alerts recover demand you already paid to acquire: shoppers who found the product, wanted it, and hit a sold-out wall. |
| Data & insight | High | Waitlist depth by variant is the cleanest restock-buying signal a store collects, and the asset at stake between these lanes. |
| Retention & LTV | Medium | A restock email is a welcome, high-intent touch that reactivates lapsed shoppers without spending a discount. |
| Customer experience | Medium | A notify-me button converts a dead end into a promise the store actually keeps. |
Spend ceiling: The widget is a form; the value is the demand data and the send moment. Size spend to signup volume and restock cadence: high-churn catalogs justify more, evergreen catalogs less.
What buying enables (top apps)
- + Live this week: widget, signup capture, throttled multi-channel sends
- + Deliverability and send-timing plumbing you don't have to own
- + ESP integrations that put alerts inside your existing flow logic
- + Preorder consolidation under one bill (Notify!'s structural pitch)
What building additionally unlocks
- + Demand-by-variant history as a first-party asset with no export ceiling
- + One signals model powering back-in-stock, price-drop, and waitlist flows together
- + A theme-rendered form with zero injected script weight on your best PDPs
- + No per-notification meter on your biggest restock days
Find Your Verdict in 3 Questions
Do you also need preorders under the same subscription?
Yes: Your verdict: BUY (Notify!) — one app covering preorder plus back-in-stock beats two bills.
No: Go to question 2.
Do you have dev capacity and treat restock intent as a data asset?
Yes: Your verdict: BUILD — owned capture plus an inventory webhook feeds your ESP and keeps the demand history yours.
No: Go to question 3.
Do you need alerts live this week?
Yes: Your verdict: BUY (STOQ) — the dedicated app is live in a day, and exports can seed a later build.
No: Your verdict: DEPENDS — trial STOQ's free tier for a quarter and measure signup volume before committing to any lane.
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 | STOQ installs in a day with widget setup in hours; the custom capture-and-webhook build runs an estimated 3–5 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Alert apps meter notifications or contacts, so restock-heavy catalogs pay more as demand grows; the build's recurring cost is minor upkeep. | ||
| Maintenance & upgrades | The vendor maintains widget and deliverability plumbing; the custom lane is a bounded webhook-plus-flow surface with theme updates as the main touchpoint. | ||
| Switching & exit | Waitlist signups live in the app's database and export completeness varies by plan; owned capture keeps every signup in your stack from day one. | ||
| Risk | |||
| Vendor risk | A crowded alert category with periodic churn and consolidation; a build has no vendor to lose. | ||
| Security & compliance surface | Alert apps hold customer emails and phone numbers; the custom lane keeps that PII inside systems you already govern. | ||
| Platform-deprecation exposure | Inventory-level webhooks and metafields are stable first-class primitives; both lanes sit on them, the build with one fewer intermediary. | ||
| Value | |||
| Fit to requirement | Apps ship proven widget UX, send throttling, and multi-channel delivery; a build matches your PDP and your ESP's flow logic exactly. | ||
| Time to market | Live this week versus about a month for the owned capture pattern. | ||
| Performance & scale | Another injected script on the PDP versus a theme-rendered form; per-notification pricing also taxes your best restock days. | ||
| Data ownership & AI-readiness | The decisive dimension: restock waitlists are declared demand by variant. Owned, they feed flows, buying, and personalization; rented, they sit behind an export queue. | ||
| Focus & opportunity cost | Small scope either way; the build is a classic first replace-an-app project, often paired with a custom wishlist on the same data model. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| STOQ | Live — Restock-alerts specialist with waitlist reporting | $10–50/mo band (illustrative) | The pure restock-alert job, done deep |
| Notify! | Live — Best-known standalone in the category; email, SMS, and push channels | Free–$40/mo band (illustrative) | Consolidating alerts and preorders under one subscription |
| Owned capture + webhook lane | Build lane — Signup capture to metafields or a small service; an inventory webhook triggers your ESP flow | One-time build plus upkeep (Deploi estimate bands) | Stores treating restock intent as a first-party data asset |
The Build Path
- Capture + inventory webhook + ESP flow: A PDP form writes variant-level signups to customer metafields or a small service; an inventory-level webhook fires your Klaviyo back-in-stock flow. One data model, no per-notification meter.
- Share the wishlist data model: The same owned-intent pattern as a custom wishlist: one signals store powering back-in-stock, price-drop, and waitlist flows together.
- Hybrid (CUSTOMIZE): Keep an app for throttling and deliverability while its ESP integration mirrors every signup into your lists, so the asset accrues to you either way.
- Effort band
- $8,000–$20,000 build, Deploi estimate (illustrative); lands in the $10–25K contact-form band
- Typical timeline
- 3–5 weeks (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): theme-update compatibility and occasional webhook or API version bumps. No per-notification line.
- What you own — and what you take on
- You own: the demand-by-variant signal, the send triggers, and the flow logic in your ESP. You take on: capture-form upkeep and webhook monitoring.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$300 | $8,000–$20,000 |
| Years 1–3 (recurring) | $1,800–$7,200 (tiers) | $3,600–$12,000 (upkeep) |
| 3-year total | ≈$1,800–$7,500 | ≈$11,600–$32,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: STOQ mid tier held flat (notification tiers step with restock demand — conservative for the build case).
- † Build path: capture + webhook + ESP flow scope; sends billed by your existing ESP; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Notification and contact meters climb exactly when restocks matter most (community-reported pattern)
- — SMS usually bills separately or per message; verify channel pricing
- — Waitlist exports vary by plan; the demand history is the asset at risk
- — Another PDP script joins the app-bloat speed tax (documented recurring pattern)
On the build path
- — Deliverability and send throttling are the deceptively hard 20%; lean on your ESP for both
- — Capture-form edge cases (variant switches, quick sellouts, duplicate signups) need real QA
- — ~15–20% of build cost per year in upkeep (Deploi estimate)
What Merchants Say
Alert-app complaints cluster on tier math: the widget is free until a hyped restock, then the send bill spikes with the traffic.
The integration-shaped complaint: signups trapped in the app instead of flowing to the ESP where the rest of retention lives.
If You Change Your Mind Later
If you bought and outgrow it
Export the waitlist and signup history your plan allows before uninstalling; completeness varies by vendor and tier. The widget rebuilds in a day, but accumulated demand history is the asset at risk, so check export terms at signup, not at exit.
If you built and want out
Nothing is stranded: signups live in customer metafields or your own store, and flows live in your ESP. Retreating to an app later means pointing its widget at the same audience; the history stays yours either way.
When This Answer Changes
We're watching for:
- ▸ Shopify shipping native back-in-stock alerts (none as of July 2026 research)
- ▸ Either app repricing notification tiers or SMS rates (re-verify quarterly)
- ▸ Your ESP shipping first-party back-in-stock triggers deep enough to skip the app
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Is STOQ or Notify! better for back-in-stock alerts on Shopify?
STOQ is the stronger pick for the dedicated back-in-stock job: restock alerts are the whole product, setup takes an afternoon, and ESP integrations carry the sends. Notify! is the pick when one subscription should also cover preorders. For pure alert depth choose focus; for consolidation choose the 2-in-1.
Can I build back-in-stock alerts without an app?
Yes: a PDP signup form writing variant-level intent to customer metafields plus an inventory webhook into your email platform covers the core loop, an estimated $8,000–$20,000 build (Deploi estimate, illustrative). You keep the demand-by-variant history that apps hold in their databases. Rent first for speed; build when the waitlist data starts steering buying and retention.
Do back-in-stock apps work with Klaviyo?
Most leading alert apps, STOQ included, push signups or events into Klaviyo so sends ride your existing flows. Two designs exist: the app sends the alert itself, or the app hands the trigger to your ESP. Prefer the ESP-triggered design; it keeps all 3 retention channels and their history in one place.
Your Next Steps
If you're going with BUY(matches your selected profile)
- Pick by job: STOQ for the dedicated alert lane, Notify! if preorders share the bill
- Wire the app's ESP integration first; app-sent email is the fallback, not the default
- Verify SMS pricing separately; per-message costs surprise at restock spikes
- Check export completeness on your tier before the list grows
- Diary a re-decision when monthly signups pass ~2,000 (Deploi estimate of the tipping zone)
If you're going with BUILD
- Define the capture model: variant-level signups on customer metafields or a small service
- Wire the inventory-level webhook to your ESP's back-in-stock flow
- Throttle sends against available stock so 500 alerts don't chase 20 units
- Ship logged-in capture first; add guest capture with double opt-in second
- Measure alert-to-purchase rate from day one; it's the ROI number
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 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 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 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 stop losing sold-out demand?
We'll size your restock cadence against the tier math, wire the winning app into your ESP, and flag the point where owning the capture beats renting it.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets 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.