ChatGPT answers, unedited

If you have a large catalog with frequent restocks, I’d strongly lean toward Klaviyo—especially if you want the system to scale beyond basic “item is back” emails.

My ranking

Why Klaviyo is my first choice: its back-in-stock flow is built around the specific product/variant a shopper requested. Someone subscribes to a restock, Klaviyo holds them in a dedicated Back in Stock Delay, and when that particular item becomes available, the appropriate message is sent. It also supports inventory-aware catalogs and APIs, which is useful if your catalog isn't entirely straightforward. help.klaviyo.com

Klaviyo's native back-in-stock functionality currently supports Shopify, BigCommerce, Magento 2, PrestaShop, Shopware, SFCC, custom catalog feeds, and API setups. help.klaviyo.comhelp.klaviyo.com

Klaviyo

When I'd choose Omnisend instead

If you primarily want “customer clicks Notify Me → product comes back → automatically email them” and don't need Klaviyo's deeper segmentation/CRM capabilities, Omnisend is worth serious consideration.

Its native back-in-stock automation supports Shopify, BigCommerce, and WooCommerce, and the email can dynamically display the product that was restocked. support.omnisend.com

Omnisend

For a large catalog, there's one important architectural detail

I would not build this as:

“When inventory changes → search all subscribers → send an email.”

Instead, use a waitlist-per-product/variant architecture:

Out of stock
→ shopper clicks Notify me
→ store records customer + product/variant
→ automation waits for that specific SKU/variant
→ inventory becomes available
→ send dynamic email for that product
→ remove/complete that waitlist entry

That matters when you have thousands of SKUs and frequent simultaneous restocks. Klaviyo's dedicated back-in-stock delay is designed specifically around this model. help.klaviyo.com

My recommendation:

• Klaviyo if this is a significant revenue channel and you want sophisticated lifecycle marketing.
• Omnisend if you want a more straightforward ecommerce automation stack.
• If you tell me what ecommerce platform you're on (Shopify, WooCommerce, BigCommerce, custom, etc.), approximate SKU count, and whether you need SMS too, I can recommend the exact architecture and app stack I'd use.

For a large catalog with frequent back-in-stock (BIS) alerts, the right platform depends on your ecommerce stack, catalog size, and how much personalization/automation you need. The main options fall into a few categories:

For a large catalog with frequent inventory changes, I’d usually prioritize:

1. Dedicated BIS engine + ESP
   • Inventory event triggers:
     • Product X returns in stock
     • Notify subscribers for Product X only
     • Stop sending once purchased
   • Best fit: Yotpo Back in Stock + Klaviyo

2. All-in-one lifecycle marketing
   • Use product feeds, events, and flows inside one platform.
   • Best fit: Klaviyo if you want BIS to become part of broader retention campaigns.

3. Enterprise-scale personalization
   • If you have tens of thousands of SKUs, multiple regions, or millions of customers:
   • Consider Bloomreach Engagement or Salesforce Marketing Cloud.

Key features I’d require for your use case:

• SKU/variant-level subscriptions (not just product-level)
• Inventory webhooks or real-time sync
• Batch throttling (avoid sending 100k emails when a popular item returns)
• Priority queues (VIP customers first)
• Purchase suppression
• Localization/time-zone sending
• Analytics by SKU: “this product generated $X from BIS alerts”
• Integration with your inventory system (ERP/WMS), not only your storefront

If you tell me:

1. your ecommerce platform (Shopify, Magento/Adobe Commerce, BigCommerce, custom, etc.),
2. approximate SKU count,
3. monthly BIS alert volume, and
4. whether you need SMS too,

I can narrow this to the best 2–3 choices.

For a large catalog with frequent restocks, I’d prioritize a platform that handles the product/variant association automatically rather than creating separate flows for every SKU.

My pick: Klaviyo

Klaviyo is probably the strongest choice if email is a major part of your ecommerce stack.

• Product-specific alerts automatically: A shopper subscribes to a particular out-of-stock product/variant, and Klaviyo holds them in the back-in-stock flow until that item is actually available. help.klaviyo.com
• No flow per product: You can use one back-in-stock flow across a large catalog rather than maintaining hundreds or thousands of product-specific automations.
• Dynamic product information: Klaviyo looks up the restocked product from your catalog at send time, which helps ensure the image, price, and other details are current. help.klaviyo.com
• Good ecosystem: It supports Shopify, BigCommerce, Magento 2, PrestaShop, Shopware, SFCC, and inventory-aware custom catalogs/API integrations. help.klaviyo.com
• Segmentation and follow-up: You can combine restock behavior with customer segments, VIP status, purchase history, etc.

Strong alternative: Omnisend

Omnisend is particularly attractive if you're on Shopify, BigCommerce, or WooCommerce and want something more ecommerce-focused/simple.

Its native Back in Stock automation captures the product information and automatically sends the restock notification when inventory returns. support.omnisend.com It also has product-level back-in-stock reporting, so you can see which products have the most waiting demand. support.omnisend.com

For a very large catalog, Omnisend can also be paired with a dedicated back-in-stock app such as StockIQ, which passes product/variant information into Omnisend and lets you segment based on what customers are waiting for. support.omnisend.com

What I'd choose

Important: Don't build this as "one automation per product." The scalable architecture is one back-in-stock workflow → customer subscribes to a specific SKU/variant → workflow waits for that item's inventory event → dynamically renders that product → sends the alert.

If you tell me what your store runs on (Shopify, Magento, WooCommerce, custom, etc.), roughly how many SKUs/variants you have, and whether you're already using Klaviyo/Omnisend, I can recommend the exact setup and whether you need a dedicated back-in-stock app.

If you have a large catalog with frequent restocks, I’d strongly favor a platform that understands product/variant-level inventory events, rather than trying to build generic email automations.

My top pick: klaviyo.com

For a large ecommerce catalog, Klaviyo is probably the best overall choice. Its back-in-stock flow can:

• Capture a shopper against a specific product/variant
• Wait automatically until that particular item is restocked
• Pull the latest product name, image, price, and other catalog data at send time
• Send the alert automatically without creating a separate campaign for every SKU
• Support Shopify, BigCommerce, Magento 2, PrestaShop, Shopware, SFCC, and custom catalog/API setups Klaviyo Help Center Klaviyo Help Center

That last point is particularly important for your use case: you don't want thousands of product-specific automations. You want one automation whose event carries the product/variant someone is waiting for.

If you're on Shopify

I'd compare these three:

omnisend.com also has native back-in-stock functionality for Shopify, BigCommerce and WooCommerce, including product/variant context and automated workflows. Omnisend Help Center

For very high SKU volume, I'd also look at AMP Back in Stock. It specifically markets itself toward high-volume catalogs and supports email, SMS, push, Shopify Flow and integrations with Klaviyo. Shopify App Store

The architecture I'd use

For your situation, I'd aim for:

Inventory system → ecommerce platform → back-in-stock event → Klaviyo → one dynamic email flow

Rather than:

Product A → automation A
Product B → automation B
Product C → automation C
...etc.

Klaviyo's model is essentially "customer subscribed to product X → wait until product X is available → send product X's current information." Klaviyo Help Center

That scales much better as your catalog changes.

If you tell me what ecommerce platform you're using (Shopify, BigCommerce, Magento, custom, etc.), roughly how many SKUs you have, and whether you need SMS too, I can narrow this down to the best 1–2 setups for your catalog size.

For a large catalog with frequent restocks, I’d shortlist Klaviyo and Omnisend, with Klaviyo as my default choice if back-in-stock automation is a major revenue channel.

My recommendation

Why I'd pick Klaviyo: its back-in-stock flow is designed around the specific product a shopper requested. Someone subscribes to a particular SKU/variant, and Klaviyo waits until that item is actually restocked before sending. It also pulls the latest product information from the catalog at send time, which is particularly useful when prices, images, or product details change between signup and restock. help.klaviyo.com

It also supports inventory-aware custom catalog feeds/API integrations, so you're not limited to a tiny catalog or a simple Shopify setup. developers.klaviyo.com

When I'd choose Omnisend instead

If you want something easier to operate and more ecommerce-focused, Omnisend is compelling. Its native Back in Stock automation supports Shopify, BigCommerce, and WooCommerce, and dynamically inserts the product that came back into stock. support.omnisend.com

Omnisend also has integrations with dedicated back-in-stock tools, which can be useful if your inventory/waitlist requirements are more complex. For example, its StockIQ integration can pass product/variant interest and restock events into Omnisend automatically. support.omnisend.com

For your use case specifically

I'd structure it like this:

Customer → "Notify me" on SKU/variant → waitlist tied to that SKU → inventory event → automatic email → product-specific landing page → purchase

The important thing is not to create hundreds or thousands of separate email campaigns/flows—use one back-in-stock automation with dynamic product/variant data.

If you tell me what ecommerce platform you're on (Shopify, Magento, BigCommerce, custom, etc.), roughly how many SKUs you have, and your monthly email volume, I can tell you which platform I'd choose and what the architecture should look like.

For a large catalog with frequent back-in-stock (BIS) alerts, I’d prioritize platforms that can handle:

• product-level inventory triggers (SKU/variant level, not just product level)
• high alert volume
• segmentation (VIPs, regions, customer type)
• email deliverability at scale
• analytics on recovered revenue
• integrations with your ecommerce platform (especially Shopify, Magento, BigCommerce, custom)

Here are the strongest options:

For very large catalogs, I would also look at dedicated BIS apps/services rather than building it entirely inside an email platform:

• Back in Stock — purpose-built for inventory alerts; handles customer subscriptions and automatic notifications.
• Swym — useful if you want wishlists + BIS + price alerts together.

My typical recommendations by scenario

Shopify + 10k–100k SKUs
→ Dedicated BIS app + Klaviyo
Use the BIS app for triggering and Klaviyo for branding, segmentation, and analytics.

Enterprise catalog (100k+ SKUs, multiple regions)
→ Bloomreach or Emarsys
You’ll likely need stronger product-data handling and orchestration.

If BIS is a major revenue channel
Track:

• notification signup rate per SKU
• conversion after alert
• revenue per alert sent
• time-to-purchase after restock
• inventory depth vs. number of subscribers

A common mistake with large catalogs is sending alerts immediately to everyone when inventory lands, causing a product to sell out again before high-intent customers can buy. Prioritizing subscribers (VIPs, earliest signups, high-LTV customers) can improve recovered revenue.

If you share your ecommerce platform (Shopify Plus, Magento, BigCommerce, custom), catalog size, and monthly BIS alert volume, I can narrow this to 2–3 best fits.

For a large catalog with frequent restocks, I’d generally choose Klaviyo—especially if you’re on Shopify.

My pick: Klaviyo

Klaviyo has a purpose-built Back in Stock flow rather than requiring you to build the automation yourself. A shopper subscribes to a specific out-of-stock product/variant, Klaviyo holds them in the flow, and when that particular item comes back in stock, it sends the appropriate product email. It supports Shopify, BigCommerce, Magento 2, PrestaShop, Shopware, SFCC, and inventory-aware custom catalogs/API feeds. help.klaviyo.com

For a large catalog, that's important because you want:

• Product/variant-level subscriptions, not one generic "back in stock" list
• Inventory-triggered sending
• Dynamic product name, image, price, and URL
• A queue of people waiting for each product
• The ability to handle thousands of products without creating a separate automation for every SKU
• Reporting on back-in-stock activity
• Integration with your broader email/SMS lifecycle marketing

Klaviyo can also handle custom inventory feeds, so you're not necessarily limited to a standard Shopify catalog. developers.klaviyo.comhelp.klaviyo.com

Klaviyo Back in Stock documentation

Strong alternative: Omnisend

If you want something more focused on ecommerce automation and potentially simpler to operate, Omnisend is worth considering. Its native Back in Stock automation supports Shopify, BigCommerce, and WooCommerce, and the email can dynamically display the specific product that triggered the notification. support.omnisend.com

It also supports product/variant-based segmentation when integrated with inventory systems such as StockIQ. support.omnisend.com

Omnisend Back in Stock documentation

If you're on Shopify and mainly need restock alerts

I'd consider separating the "waitlist/stock detection" piece from the email platform. For example, Shopify apps such as Back In Stock | Restock Alerts can collect product-specific subscribers and fire alerts when inventory returns, while syncing the audience to Klaviyo.

That can be a particularly good architecture if your catalog is very large or has complex variants/inventory rules.

What I'd choose

Bottom line: If you're already using—or willing to use—Klaviyo, I'd make Klaviyo the central platform. Its back-in-stock functionality is specifically designed around the problem you're describing, including product-level inventory awareness and custom catalogs. developers.klaviyo.comhelp.klaviyo.com

If you tell me what ecommerce platform you're on (Shopify, Magento, WooCommerce, custom, etc.) and roughly how many SKUs/variants you have, I can recommend the best architecture and compare Klaviyo vs. Omnisend vs. dedicated back-in-stock apps for your scale.

For a large catalog with frequent restocks, I’d shortlist Klaviyo and Omnisend, with Klaviyo as my default choice if you need sophisticated product-level automation.

My recommendation: Klaviyo

Klaviyo is particularly strong when you have lots of SKUs/variants because its back-in-stock flow can use the specific product/variant the shopper requested and dynamically pull the current product name, image, price, URL, and other catalog data at send time. It supports Shopify, BigCommerce, Magento 2, PrestaShop, Shopware, SFCC, and inventory-aware custom catalogs/API integrations. help.klaviyo.com

The basic architecture is:

Product goes out of stock → shopper clicks “Notify me” → Klaviyo records the requested product/variant → inventory returns → flow releases the shopper → email dynamically renders that exact product.

That's preferable to creating separate automations for every product.

When I'd choose Omnisend instead

Omnisend is a very good alternative, especially if you're on Shopify, BigCommerce, or WooCommerce and want something relatively straightforward to deploy. Its native back-in-stock workflow captures the product/variant request and automatically sends a dynamically populated back-in-stock email. support.omnisend.com

It also has integrations with third-party inventory/restock tools such as StockIQ, which can trigger workflows based on a specific product or variant returning to stock. support.omnisend.com

Quick decision

One important consideration: don't design this as “one automation per product.” Use one back-in-stock flow driven by the customer's requested product/variant, with dynamic catalog data. That's what makes the system manageable when you have thousands—or tens of thousands—of SKUs. Klaviyo explicitly supports inventory-aware custom catalogs/API feeds for this use case. developers.klaviyo.com

If you tell me what ecommerce platform you're on (Shopify, Magento, custom, etc.), approximate SKU count, and whether you need SMS too, I can recommend the specific architecture and compare Klaviyo vs. Omnisend vs. a dedicated back-in-stock app for your catalog.

For a large catalog with frequent back-in-stock (BIS) alerts, I’d prioritize platforms that can handle high SKU volume, product-level personalization, inventory triggers, segmentation, and deliverability. The best choice depends on your ecommerce stack, but these are the strongest options:

My recommendation by scenario

If you’re on Shopify and have thousands of SKUs:

• Start with Klaviyo + a BIS app/inventory integration. It gives you the best combination of product-level alerts and broader customer lifecycle automation.

If you have a very large catalog (50k–500k+ products) or multiple storefronts:

• Look at Bloomreach or an enterprise CDP/marketing stack. You’ll care more about event pipelines, catalog sync, and throttling than just the email template.

If BIS alerts are your main goal (not full marketing automation):

• A dedicated BIS app can be simpler:
  • Back in Stock
  • Swym
  • Notify Me!

Key features I’d require before choosing:

• Product/SKU-level inventory triggers (not generic “store back in stock”)
• Variant support (size/color)
• Queue management for popular products
• Send throttling (avoid 100k emails at once when inventory returns)
• Real-time inventory sync
• Analytics by SKU (conversion rate after alert)
• Ability to suppress customers who already purchased
• Email + SMS support if you want higher urgency

A few questions would narrow this down:

1. What ecommerce platform are you on (Shopify, Magento/Adobe Commerce, WooCommerce, custom)?
2. Rough catalog size (1k SKUs, 50k, 500k+)?
3. Are alerts mostly email, SMS, or both?
4. Do you already use an ESP like Klaviyo/Mailchimp/Braze?

For a large catalog with frequent restocks, I’d shortlist Klaviyo first, with Omnisend as the strongest simpler/usually more cost-conscious alternative.

My recommendation: Klaviyo

Klaviyo is particularly well suited if you have lots of SKUs/variants and want the back-in-stock system to operate at the product/variant level automatically.

Why I’d choose it:

• Product/variant-specific alerts: a shopper subscribes to a particular out-of-stock item, and the flow waits specifically for that item to become available. help.klaviyo.comhelp.klaviyo.com
• Dynamic product data: the email can pull the relevant product information rather than requiring you to build an email for every SKU. help.klaviyo.com
• Inventory thresholds: you can configure how much inventory needs to return before notifications go out—which is valuable if you frequently receive small replenishments. help.klaviyo.comhelp.klaviyo.com
• High-volume catalog support: Klaviyo supports Shopify, BigCommerce, Magento 2, PrestaShop, SFCC, Shopware, custom catalog feeds, and API-based setups. help.klaviyo.com
• You can also control notification strategy for high-demand products, rather than blasting everyone simultaneously when a small quantity comes back. help.klaviyo.comhelp.klaviyo.com

When I'd pick Omnisend instead

Omnisend is a very good choice if your primary requirement is straightforward back-in-stock automation rather than sophisticated lifecycle marketing.

Its native system supports product variants and automatically inserts the relevant back-in-stock product into the email. It also provides a report showing which products have the most people waiting. support.omnisend.com

Omnisend also has integrations with inventory-oriented tools such as StockIQ, which can trigger workflows when a specific product or variant becomes available and segment customers based on their product interest. support.omnisend.com

What I'd use for a large catalog

One important distinction: I wouldn't build this as thousands of separate automations—one per product. You want one back-in-stock flow that dynamically knows which product/variant each subscriber requested. Klaviyo's architecture is particularly well suited to that model. help.klaviyo.comhelp.klaviyo.com

If you tell me what ecommerce platform you're on (Shopify, Magento, WooCommerce, custom, etc.) and roughly how many SKUs/variants you have, I can recommend the best setup and compare Klaviyo vs. Omnisend vs. dedicated back-in-stock apps for your catalog size.

For a large catalog with frequent restocks, I’d pick Klaviyo—especially if you’re on Shopify, BigCommerce, Magento, or a custom storefront.

My recommendation: Klaviyo

Klaviyo has a purpose-built Back in Stock flow rather than requiring you to build a generic inventory-triggered automation. A shopper subscribes to a specific out-of-stock product/variant, enters the flow, and Klaviyo waits until that particular item is available before sending the notification. help.klaviyo.comhelp.klaviyo.com

It’s particularly strong for a large catalog because it supports:

• Product/variant-specific subscriptions
• Dynamic product information in the email
• Inventory-aware catalogs and custom catalog feeds
• Shopify, BigCommerce, Magento 2, PrestaShop, SFCC, Shopware, and API/custom integrations help.klaviyo.com
• API-based implementation if your inventory system/storefront is custom developers.klaviyo.com

Klaviyo

Runner-up: Omnisend

If you're primarily Shopify/BigCommerce/WooCommerce and want something simpler, Omnisend is worth considering. Its native Back in Stock automation dynamically includes the product that was requested, and it has reporting on which products have the most customers waiting. support.omnisend.com

Omnisend

One important distinction: don't build this as a simple “inventory changed → send email” automation. You want to maintain a waitlist keyed to the specific product/variant, then release those subscribers when that SKU comes back in stock. Klaviyo's dedicated back-in-stock architecture is designed around exactly that workflow. help.klaviyo.comhelp.klaviyo.com

If you tell me what ecommerce platform you're using (Shopify, Magento, WooCommerce, custom, etc.) and roughly how many SKUs, I can recommend the best architecture and whether you need Klaviyo/Omnisend alone or a dedicated back-in-stock app feeding into it.

For a large catalog with frequent restocks, I’d shortlist Klaviyo and Omnisend, with a dedicated back-in-stock app if your inventory logic is unusually complex.

My pick: Klaviyo

Klaviyo is probably the best fit if you want the back-in-stock system to become part of a broader lifecycle marketing stack.

• Handles product/variant-specific waitlists, so someone waiting for a particular size/color can be notified when that exact item returns. help.klaviyo.com
• Has a dedicated Back in Stock flow and delay, rather than requiring you to build the logic from scratch. help.klaviyo.com
• Supports dynamic product information in the email, so one automation can serve a very large catalog. help.klaviyo.com
• Supports Shopify, BigCommerce, Magento 2, PrestaShop, Shopware, SFCC, and custom inventory-aware catalogs/API feeds. help.klaviyo.com
• On Shopify/BigCommerce, its form can automatically appear on products that are out of stock. help.klaviyo.com

When I'd choose Omnisend instead

Omnisend is attractive if you're primarily looking for straightforward automated email/SMS commerce messaging rather than a very sophisticated customer-data platform.

Its native Back in Stock automation supports Shopify, BigCommerce and WooCommerce, and the email can dynamically display the specific restocked product. support.omnisend.com

If your catalog is really large

I'd consider a dedicated back-in-stock engine + Klaviyo. For example, Amp Back in Stock specifically markets itself for high SKU volumes and fast-moving catalogs, and can send email/SMS/push notifications while feeding customer demand data back into your marketing stack. apps.shopify.com

Architecture I'd use:

Inventory → Back-in-stock engine → Product/variant waitlist → Klaviyo → instant email

That gives you a single reusable automation rather than creating a separate campaign for every product.

Bottom line:

• Klaviyo → best overall for a large catalog + sophisticated lifecycle marketing.
• Omnisend → best if you want simpler ecommerce automation.
• Amp/other dedicated BIS app + Klaviyo → best if restock volume/SKU complexity is enormous or inventory behavior is complicated.

If you tell me your ecommerce platform (Shopify, Magento, WooCommerce, custom, etc.), approximate SKU count, and monthly back-in-stock alerts, I can narrow this to the best 2–3 options and compare their likely cost.

For a large catalog with frequent restocks, I’d shortlist Klaviyo first, with Omnisend as the main alternative.

My pick: Klaviyo

Klaviyo is particularly well suited if your requirement is “customer X is waiting for product/variant Y → when Y comes back in stock, automatically email X.”

Its back-in-stock flow:

• Tracks the specific product/variant a shopper requested.
• Waits until that item is actually restocked.
• Sends the notification automatically, using current product information.
• Supports inventory-aware catalogs and APIs, which is important for a large or custom catalog.
• Supports Shopify, BigCommerce, Magento 2, PrestaShop, Shopware, SFCC, and custom catalog/API setups. help.klaviyo.com
• Lets you customize the email with dynamic product data so an old price/image doesn't get accidentally used after a long wait. help.klaviyo.com

Klaviyo back-in-stock documentation

Omnisend is a strong alternative

Omnisend has a native back-in-stock form and automation for Shopify, BigCommerce, and WooCommerce. Its automation can dynamically insert the back-in-stock product, and its reporting shows which products/variants have the most people waiting. support.omnisend.com

That makes Omnisend attractive if you're primarily an ecommerce operation and want a somewhat more turnkey setup.

What I'd choose

One important architectural point: don't build this as a giant automation with one workflow per product. You want one back-in-stock flow driven by the product/variant inventory event, with the subscriber's requested SKU/variant carried through dynamically. That's what makes the system scale when you have thousands of products and constant inventory changes.

If you tell me what ecommerce platform you use (Shopify, Magento, custom, etc.), approximate number of SKUs, and monthly back-in-stock notifications, I can recommend the best setup and compare Klaviyo vs. Omnisend vs. a dedicated back-in-stock app for your catalog.

If you have a large catalog with frequent restocks, I’d make Klaviyo the default choice—especially if you’re on Shopify.

Why:

• Product/variant-specific alerts: A shopper subscribes to a particular out-of-stock item, and Klaviyo holds them in a back-in-stock flow until that item is available. help.klaviyo.com
• Scales beyond Shopify: It supports Shopify, BigCommerce, Magento 2, PrestaShop, Shopware, SFCC, and custom inventory catalogs/API integrations. help.klaviyo.com
• Dynamic product data: The email can automatically populate the relevant product information rather than requiring you to build a campaign for every SKU. help.klaviyo.com
• You can add SMS/WhatsApp: Its current back-in-stock form can collect email, SMS, and WhatsApp preferences. help.klaviyo.comdevelopers.klaviyo.comapps.shopify.com
• Good fit for a large catalog: With a custom catalog/API, Klaviyo can use an inventory quantity field ($inventory_quantity) to determine when products become available. developers.klaviyo.com

What I'd use

For a high-SKU business, I'd actually separate the system into two pieces:

Inventory/store → back-in-stock subscription → Klaviyo → automated email

That gives you one centralized customer/marketing system while the inventory system determines exactly when a particular SKU/variant becomes available.

If you're on Shopify, dedicated apps are also worth considering. For example, Shopify's current App Store has hundreds of back-in-stock solutions, including apps designed around high-volume catalogs and email/SMS alerts. apps.shopify.com

My pick: Klaviyo if back-in-stock is part of a broader retention/CRM strategy. If you're only trying to send restock notifications and don't need a full marketing platform, I'd choose a dedicated back-in-stock app instead.

If you tell me your ecommerce platform (Shopify, Magento, WooCommerce, custom, etc.), approximate number of SKUs, and monthly restock-alert volume, I can narrow it down to 2–3 platforms and compare the automation architecture and likely cost.

For a large catalog with frequent back-in-stock (BIS) alerts, you’ll want a platform that can handle product-level inventory events, high subscriber volume, segmentation, and reliable triggering. The best choice depends on your ecommerce stack (Shopify, Magento, custom, etc.), but these are strong options:

For a large catalog, I’d prioritize these capabilities:

• Variant-level inventory tracking (not just product-level)
• Automatic suppression after purchase (avoid alerting someone who already bought)
• Waitlist throttling (prevent 50,000 emails firing at once after a restock)
• Priority rules (VIP customers first, high-margin products first, etc.)
• Inventory-aware segmentation (different messaging by product category)
• Analytics by SKU/product (which products generate the most recovered revenue)

My typical recommendations:

• Shopify + serious growth brand: Klaviyo + a dedicated BIS app/integration is usually the strongest setup.
• 100k+ SKUs or enterprise retail: Bloomreach or a similar enterprise CDP/marketing platform.
• Need something quick and low-maintenance: Omnisend or a dedicated Shopify BIS solution.

A few questions would narrow this down:

1. What ecommerce platform are you on (Shopify, Magento/Adobe Commerce, BigCommerce, custom)?
2. Roughly how many SKUs/variants do you have?
3. Are these alerts email only, or do you also want SMS/push?
4. How many BIS notifications do you send per month?