Never Run Out of Stock Again with n8n-Driven Reorders
Monitor Shopify/WMS levels, auto-create procurement POs and notify suppliers via email/Slack with resilient n8n workflows.
Why continuous inventory monitoring matters
Missed sales, rush shipping and emergency buys are symptoms of inventory blind spots. For retailers and distributed warehouses, relying on manual checks, daily spreadsheets or ad-hoc emails creates delays and errors that multiply across SKUs and suppliers.
Implementing a continuous, rule-driven monitor that reads Shopify and WMS data in real time eliminates those blind spots. The rest of this post shows a practical n8n-based implementation that turns inventory signals into purchase orders and supplier notifications — reducing stockouts and lowering carrying costs.
Technical n8n workflow: components and flow
At a high level the workflow has three phases: detect low stock, generate a purchase order, and notify & track supplier acknowledgements. Use a Cron or Webhook trigger in n8n: if your Shopify/WMS supports webhooks, subscribe to inventory updates and use n8n Webhook nodes; otherwise schedule frequent polling with the Cron node and Shopify/WMS HTTP Request (or the built-in Shopify node) to fetch inventory levels.
After ingesting inventory, use an If node (or Function node with business logic) to compare on-hand quantities to reorder points. Calculate reorder quantities with a simple formula: reorderQty = max(minOrderQty, ceil((avgDailySales * leadTimeDays) + safetyStock - onHand)). Build the PO payload with Set nodes, save a unique PO reference in a DB (Postgres or Google Sheets) for idempotency, and send the PO to your procurement system using the HTTP Request node (or a native connector if available).
Supplier notifications, acknowledgements and error handling
Once a PO is created, the same workflow pushes notifications to suppliers via the Slack node or Email node (SMTP/SendGrid). Send a human-readable PO and include a machine-readable attachment (JSON or CSV) and a unique PO ID to enable automatic matching on the supplier side. Optionally include an estimated delivery date computed from lead time and cut-off times.
For robustness implement confirmation and retry patterns: after sending, pause and wait for supplier acknowledgement (a webhook endpoint or a parsed incoming email). If no acknowledgement within X hours, escalate to a human via Slack in a procurement channel. Also add a dedicated Error workflow in n8n to log failures, notify ops, and optionally retry idempotently based on error type and API rate-limit headers.
Before and after: concrete scenarios
Before automation: a procurement coordinator runs a daily export from Shopify, manually reviews 1,200 SKUs, emails three suppliers, creates POs in a procurement tool and tracks replies in spreadsheets. Stockouts occur for high-turn SKUs between checks and emergency air shipments cost 2–5x normal freight. This process consumes 20+ labor hours per week and ties up working capital in excess buffer stock.
After automation: n8n polls or listens to Shopify/WMS changes and creates POs automatically when a SKU falls below its reorder point. Suppliers receive instant Slack alerts or emails and can confirm via webhook. The company reduces manual work to exception handling (≈2–4 hours/week), stockouts drop by an estimated 60–90% for automated SKUs, and freight spend for emergency orders falls dramatically.
Business benefits, ROI and practical next steps
The measurable benefits include fewer stockouts (increased revenue), lower expedited shipping costs, reduced manual labor and improved supplier responsiveness. Example ROI: if automation saves 15 labor hours/week at $30/hr ($1,800/month) and avoids $5,000/month in lost sales and emergency freight, a modest n8n implementation that costs $500–$1,500/month pays back in weeks and yields ongoing monthly savings.
Practical next steps: run a 30–90 day pilot on 50 high-turn SKUs: set up Shopify and WMS credentials in n8n, implement the detection-to-PO workflow, log every action to a Postgres or Google Sheet for audit, and configure supplier notifications. Monitor hits, API rate limits, and exceptions, then iterate on reorder formulas, safety stock and lead time values to tune service levels and working capital.