N8N Inventory Management Automation: Stock Alerts, Reorder Workflows, and Supplier Notifications

Inventory problems are expensive in both directions. Run out of a fast-moving SKU and you lose the sale, irritate the customer, and hand revenue to a competitor. Overstock a slow mover and you tie up cash, pay for warehouse space, and eventually discount to clear it. Most small product businesses manage this with a spreadsheet someone checks once a day -- which means they catch the problem after it has already cost them.

N8N fixes this without an enterprise ERP. You can build workflows that pull live stock levels from Shopify, WooCommerce, Airtable, or any inventory API, compare those levels to your reorder thresholds, and fire alerts or create purchase orders automatically. The entire system runs on a schedule you set -- every hour, every four hours, or in real time via webhooks.

This guide walks through four practical inventory workflows you can build today, the exact N8N nodes involved, and the logic that prevents duplicate orders and alert fatigue.

Why Manual Inventory Checks Fail Small Businesses

The stockout problem is worse than most owners realize. Research consistently shows that out-of-stock events cause 30 to 40 percent of customers to buy from a competitor rather than wait. For e-commerce, that number is even higher because switching costs are nearly zero -- one click and they are on a competitor's page.

Manual processes fail for a predictable reason: the check happens on a schedule (end of day, Monday morning) but inventory changes continuously. A product that shows 45 units at 9 AM can be at 3 units by 2 PM during a flash sale or peak season. By the time you check and contact the supplier, you have already lost two days of lead time.

Automation solves this by monitoring continuously. N8N polls your inventory source on whatever schedule makes sense for your business and takes action the moment a threshold is crossed -- not the next time someone remembers to check.

Workflow 1: Low-Stock Alert to Slack and Email

This is the simplest workflow and the right place to start. It monitors your inventory source every hour and sends an alert when any SKU drops below its reorder threshold.

The N8N node sequence

1. Schedule Trigger: Set to run every hour (or every 30 minutes for high-velocity products). Use a Cron expression if you want to exclude overnight hours when your team is not available to act.
2. Shopify or HTTP Request node: Pull current inventory levels for all products. For Shopify, use the built-in node to query inventory items. For other platforms, the HTTP Request node hits your inventory API endpoint.
3. Code node or IF node: Filter the product list to only items where current stock is at or below the reorder threshold. The threshold can be hardcoded in the workflow or pulled from a reference table in Airtable or Google Sheets (which makes it easier to update per SKU without touching the workflow).
4. Slack node: Send a message to your #inventory or #ops channel listing each flagged SKU, current stock, and threshold. Format this as a structured message with clear SKU names and numbers -- not a wall of JSON.
5. Gmail or SMTP node: Send the same alert to the owner or ops manager email as a backup notification.

The critical detail: add a deduplication step. Without it, you will receive the same alert every hour until the stock is replenished, which trains your team to ignore the alerts. Use a Google Sheet as a simple state tracker that logs which SKUs have active alerts. The workflow only fires a new alert if the SKU is not already in the active-alert list. When stock is replenished above threshold, a second workflow pass clears the flag and sends a resolution notification.

Workflow 2: Automatic Purchase Order Creation

Alerting is useful. Creating the purchase order automatically is better. This workflow extends the low-stock detection logic to draft a PO and send it to the supplier without human intervention.

What you need before building this

For each SKU, you need a reference table that stores: supplier name, supplier email, supplier lead time (in days), reorder quantity (minimum order units), and unit cost. This typically lives in a Google Sheet or Airtable base. The N8N workflow reads this table to populate the PO details dynamically.

The N8N node sequence

1. Schedule Trigger: Same as Workflow 1, runs every hour or four hours.
2. Google Sheets node: Pull the SKU reference table with supplier contacts, reorder quantities, and thresholds.
3. HTTP Request node: Pull live stock levels from your inventory source.
4. Merge node: Join the two datasets on SKU ID so each item has both its current stock level and its supplier details.
5. IF node: Filter to SKUs where stock is at or below threshold AND no open PO exists (checked against the state tracker sheet).
6. Gmail node: Compose and send a structured email to the supplier. The email body includes SKU name, product code, quantity requested, delivery address, and a request for confirmation. Use N8N's expression syntax to pull each value from the workflow data.
7. Google Sheets node (write): Log the PO in your state tracker with status "pending," SKU, quantity, and timestamp. This prevents duplicate orders from firing on the next workflow run.
8. Slack node: Post a confirmation to your ops channel: "PO sent to [Supplier] for [SKU] -- [Qty] units."

For suppliers with an API-based order portal, you can replace the Gmail node with an HTTP Request node that submits the order directly. This is faster and eliminates the risk of the email going to spam or sitting unread in the supplier's inbox.

Setting the right reorder quantity

Reorder quantity is not just "how much I usually buy." The right number accounts for lead time demand: how many units will you sell during the supplier's delivery window? If your supplier takes 14 days and you sell 20 units per day, you need at least 280 units on order just to cover lead time, plus your safety stock buffer. Store this calculated reorder quantity in the reference table and update it quarterly as your velocity changes.

Workflow 3: Dead Stock Identification and Clearance Alerts

Overstock is the other side of the inventory problem. SKUs that have not moved in 60 or 90 days are costing you carrying costs and tying up capital. This workflow identifies them automatically and gives you an actionable report.

The N8N node sequence

1. Schedule Trigger: Run this weekly, on Monday morning, so you start each week with a clear view of dead stock.
2. HTTP Request or Shopify node: Pull inventory levels and, crucially, the last sale date or units sold in the last 30, 60, and 90 days for each SKU.
3. Code node: Flag SKUs where units sold in the last 60 days is zero and current stock is above a minimum threshold (ignore SKUs with only 1 or 2 units -- not worth the analysis).
4. Google Sheets node (write): Write the dead stock report to a sheet: SKU, current quantity, last sale date, estimated carrying cost (quantity x unit cost x monthly carrying rate, typically 20 to 30 percent annually).
5. Gmail node: Email the report to the owner or buyer with a summary line: "7 SKUs identified with no sales in 60+ days. Estimated carrying cost: $2,340/month."

The carrying cost calculation gives the report teeth. Without a dollar figure attached, dead stock reports get filed and ignored. When someone sees that three slow-moving SKUs are costing $800 a month to hold, the decision to discount and clear becomes obvious.

Workflow 4: Daily Inventory Summary Report

Beyond exception-based alerts, a daily summary gives your team a standing view of inventory health. This workflow runs each morning before the business opens and delivers a structured report.

What the report includes

• Total SKUs monitored
• SKUs below reorder threshold (with current stock and threshold)
• SKUs with open purchase orders and expected delivery dates
• Top 10 fastest-moving SKUs (last 7 days)
• Projected stockout dates for the 5 most at-risk SKUs based on current velocity

The projected stockout date calculation is the most valuable part. It takes current stock divided by average daily sales velocity and returns "X days to stockout." If a SKU shows 6 days to stockout and your supplier lead time is 10 days, you are already late -- the workflow flags this as critical.

The N8N node sequence

1. Schedule Trigger: 7:00 AM daily, Monday through Friday.
2. Multiple HTTP Request nodes (parallel): Pull inventory levels, recent sales data, and open PO status simultaneously.
3. Code node: Calculate velocity, projected stockout dates, and sort the at-risk SKU list.
4. Gmail or Slack node: Send the formatted report. For Slack, use Block Kit formatting to make the report scannable. For email, a simple HTML table is sufficient.

Connecting N8N to Your Inventory Source

The specific N8N nodes you use depend on where your inventory lives.

For Shopify users, N8N can also listen to inventory webhooks -- events that Shopify pushes when stock changes, rather than waiting for your scheduled poll. This gives you near-real-time detection. Set up a Webhook Trigger node in N8N and register the endpoint in Shopify's webhook settings under "inventory_levels/update." See our N8N webhook tutorial for step-by-step instructions on configuring webhook triggers.

Preventing Alert Fatigue and Duplicate Orders

The two failure modes for automated inventory workflows are alert fatigue (too many notifications that get ignored) and duplicate purchase orders (the same PO sent multiple times because the workflow fires before the first order is confirmed).

Both are solved with a state management table. Use a Google Sheet or Airtable base with the following columns: SKU, alert_sent (boolean), po_sent (boolean), po_date, expected_delivery. Every workflow run reads this table first. Before sending an alert, check if alert_sent is true. Before creating a PO, check if po_sent is true and expected_delivery is in the future. Only proceed if both checks pass.

When stock is replenished, a separate workflow pass or a manual update clears the flags. For teams that want full automation, N8N can watch for inbound supplier emails confirming shipment and use that trigger to update the state table automatically via the Gmail Trigger node.

What This Looks Like in Practice

A client selling specialty kitchen products ran manual daily inventory checks across 180 SKUs. The process took 45 minutes per day and still produced 3 to 5 stockouts per month during peak season because the check happened at the wrong time.

After building these N8N workflows, the business reduced stockouts by 80 percent in the first quarter. The daily 45-minute check was eliminated entirely. The reorder workflow now creates draft POs automatically for the buyer to approve with one click -- reducing the decision cycle from a day or more to under an hour.

This is the same kind of operational leverage that Le Marquier achieved with AI automation -- an 80% reduction in operational overhead and a 98% handling rate for routine processes. Inventory management is one of the clearest places where automation pays back immediately and keeps paying.

Want to assess whether your business is ready to automate inventory and other operations? Start with our AI readiness assessment to see where you are and what to tackle first.

Building This Yourself vs. Getting Help

If you have a developer or someone comfortable with APIs, these workflows are buildable in a day or two. The conceptual work -- mapping your SKUs to suppliers, defining thresholds, choosing your inventory source -- takes longer than the N8N build itself.

If you want an estimate of the time and cost savings before committing, our ROI calculator lets you model the impact of inventory automation specifically. Plug in your current stockout frequency, average order value, and manual check time to see the numbers.

For businesses that want these workflows built and integrated with existing systems, our N8N automation service handles the build, testing, and ongoing maintenance. We have connected N8N to over a dozen inventory sources and can typically have a working prototype in 3 to 5 business days.

Before jumping into inventory automation, it also helps to understand the broader workflow ecosystem. Our guide on N8N event-driven automation covers how to build workflows that react to real-time triggers rather than running on a fixed schedule -- which is the right approach for high-velocity inventory environments. And if you are thinking about the broader operational picture, our post on N8N ecommerce order management covers how inventory fits into the full order-to-fulfillment workflow.

Ready to Get Started?

Book a free 30-minute discovery call. We'll identify your biggest opportunities and show you exactly what AI automation can do for your business.

Book a Free Discovery Call

Suyash Raj Founder of rajsuyash.com, an AI automation agency helping SMBs save time and scale with AI agents, N8N workflows, and voice automation.