How to Build Make com Low Stock Alerts for Your Shop
The Inventory Tracking Mistake That Cost Me Sales
Last winter, I lost nearly a week of sales on one of my niche merchandise stores because my top-selling item dropped to zero inventory without me noticing. Running multiple automated content sites and e-commerce stores solo from Seoul means I do not spend my morning opening up ten different platform dashboards to manually check stock levels. I rely entirely on automated notifications.
Standard e-commerce platform notifications are surprisingly weak. WooCommerce emails usually get lost in a cluttered administrative inbox, and Shopify’s native notification settings often notify you only when an item is completely out of stock—not when it drops down to a critical buffer limit where you still have time to reorder from suppliers.
Setting up make com low stock alerts gives you complete control over when, where, and how you get notified. In this practical guide, I will walk you through setting up a reliable, automated inventory monitoring system using Make (formerly Integromat) so you never get caught off guard by unexpected stockouts.
Why Native Store Notifications Fall Short
Before jumping into the step-by-step setup, it helps to understand why a custom Make scenario is superior to relying strictly on built-in store settings.
- Lack of custom thresholds: Many platforms treat low stock and out-of-stock as the same thing. You want an alert when you have 5 items left, not 0.
- Wrong delivery channel: Native store apps send generic emails. Email is where notifications go to die. Getting a instant message in Slack or Telegram lets you act immediately.
- No custom routing: If you work with different suppliers or virtual assistants, native settings cannot easily route specific product alerts to specific people.
What You Need Before Starting
To follow along with this build, you will need a few basic tools in your stack:
- An active online store running on WooCommerce, Shopify, or a similar platform with API access.
- An account on Make. Make offers a functional free tier with a monthly quota of operations. Paid tiers generally start around the $9 to $10/month range depending on your region and volume. Be sure to check the official Make pricing page for current plan boundaries.
- A destination app for your alert (Slack, Telegram, Microsoft Teams, or a dedicated Gmail account).
Step-by-Step: Building the Low Stock Scenario in Make
Step 1: Choosing Your Trigger Strategy
There are two primary ways to set up inventory monitoring in Make: Webhook Triggers and Scheduled Search Modules.
When I first built this, my mistake was using instant webhooks on every inventory update event. Every time a customer bought an item or an inventory level changed by 1 unit, the scenario ran. That burned through my monthly Make operations balance in less than a week.
A much smarter approach for small to medium operations is using a scheduled search module that runs once or twice a day (e.g., every morning at 8:00 AM).
- Create a new scenario in Make.
- Add your store app (for example, Shopify or WooCommerce).
- Select the action module Search Product Variants (Shopify) or List All Products (WooCommerce).
- Set the module limit high enough to retrieve all active items across your inventory catalog.
Step 2: Filtering for Low Inventory
Once Make pulls your list of products, you need to filter out items that have healthy stock levels so you do not send spam notifications for items that are totally fine.
- Click on the connecting line between your store module and your notification destination module to create a Filter.
- Label the filter something clear like
Inventory Less Than or Equal to Threshold. - In the condition field, select the
Inventory Quantitytag output from your store module. - Set the text/numeric operator to Less than or equal to (<=).
- Enter your chosen numeric threshold (for instance,
5).
Step 3: Setting Up Your Notification Module
Now that the filter isolates items with 5 units or fewer, connect your preferred communication tool. For this example, we will use Slack, but Telegram or Email works identically.
- Add the Slack app to your scenario and select the Create a Message module.
- Connect your Slack workspace and select your dedicated alert channel (e.g.,
#inventory-alerts). - In the message content box, map the data fields dynamically from your store module.
Here is an example message structure that works well for immediate clarity:
- Product Name: [Mapped Product Title]
- SKU: [Mapped SKU]
- Current Stock: [Mapped Inventory Quantity] units remaining
- Direct Link: [Mapped Store Admin Link]
Comparing Notification Destination Options
| Destination | Setup Difficulty | Best Used For |
|---|---|---|
| Slack / Teams | Easy | Team visibility and structured channels |
| Telegram | Moderate | Instant personal mobile push alerts |
| Email / Gmail | Very Easy | Non-urgent daily digest summaries |
Advanced Tweaks: Preventing Notification Storms
If you set your Make scenario to run every 12 hours and an item stays at 3 units in stock for four days straight, you will receive eight identical alerts for that single product. This creates notification fatigue, causing you to ignore your alerts altogether.
To fix this, you have two practical choices:
Option A: Store the Alerted State in Make Data Stores
Make includes a feature called Data Stores. When an alert triggers, you write the product’s SKU or ID to a local Data Store table with a timestamp. The next time the scenario runs, you add a lookup filter that checks if an alert was already sent for that SKU within the last 48 hours. If it was, the scenario drops the message.
Option B: Use Store Tags
Alternatively, after sending the Slack alert, add another module that adds a temporary tag like low-stock-notified directly to the product in Shopify or WooCommerce. Then update your initial filter to ignore products that already carry that tag.
My Take
Building custom low stock alerts with Make is one of the highest-return 30-minute automation setups you can do as a solo operator. It frees up your mental energy from constantly checking inventory dashboards, allowing you to focus on marketing and content production.
However, Make is not without its drawbacks here. If your store has tens of thousands of individual SKUs, running full catalog searches inside Make can quickly consume your monthly operation limits. In those massive scale scenarios, custom code extensions or dedicated, standalone inventory management tools might make more sense. But for catalog sizes under 1,000 SKUs, Make strikes the ideal balance between build speed, flexibility, and operational costs.
FAQ
Is Make better than Zapier for low stock alerts?
Make offers significantly lower costs per operation and superior visual data mapping for complex filtering compared to Zapier. While Zapier has a slightly gentler learning curve for complete beginners, Make’s custom scenario branching makes handling multi-variant product structures far easier.
How many operations does a low stock scenario use in Make?
If you schedule a product search scenario to run once per day across a store with 50 products, it will generally use around 2 to 5 operations per run depending on your bundle settings. That equates to under 150 operations per month, fitting comfortably within standard free or entry-level tiers.
Can I configure Make to alert my supplier automatically?
Yes. Instead of or in addition to sending a Slack message, you can add an Email module configured to automatically draft or send a purchase order template directly to your supplier’s email address whenever an item hits your reorder threshold.
