Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

WooCommerce low-stock alerts with Make

A useful stock alert identifies the item, the available quantity and the person who should act. Norml builds Make workflows that check WooCommerce inventory and notify your team in Slack. Thresholds, repeat reminders and replenishment resets are defined around how your store manages stock.

Alert on a stock condition, not every update.

The workflow begins with the stock source. Parent products and variations can manage inventory differently, so each alert must refer to the record that owns the quantity.

Solution
Automations
Tools
WooCommerce, Make, Slack
Trigger
A scheduled inventory check or supported product event prompts a fresh read of the relevant WooCommerce stock record.
Outcome
Items below their agreed threshold enter an alert queue. Slack receives the item details and owner, while acknowledgement and restock state control subsequent reminders.

Products, variations and thresholds

We identify monitored products and variations, their IDs, SKU labels and stock-management settings. Thresholds can vary by item or category when that rule is documented. Missing quantities and products without quantity tracking are treated separately rather than interpreted as zero stock.

Alert state and acknowledgement

Make compares the latest stock condition with the saved alert state. A first threshold crossing creates an alert; later checks update the existing incident. The scope defines how staff acknowledge it and whether a reminder is allowed after the agreed cooldown.

Restock and escalation

A replenished quantity closes the low-stock incident only when it meets the agreed reset condition. Unacknowledged incidents can escalate to a named backup owner. The workflow distinguishes a continuing shortage, a new shortage after restock and a failed inventory read.

Choose the inventory authority and alert owner.

Stock ownership

Confirm whether WooCommerce is the operational stock source or receives updates through another inventory system. Share representative simple products, variations and backorder settings. A multi-location or warehouse-specific quantity needs its own verified source and cannot be inferred from a single store value.

Connection and channel access

We verify the WooCommerce API route, Make connection and permitted Slack destination. The implementation reads inventory and maintains its own alert records; it does not change stock or place supplier orders. Workspace app restrictions are checked before Slack delivery is promised.

Operations after launch

Choose who acknowledges shortages, handles inaccessible products and owns connection renewal. Agree where alert state is stored and how it is recovered. A failed run must remain visible to the operator instead of making the stock report appear current.

Check the alert lifecycle before release.

  1. Map stock examples

    Select products with parent-level stock, variation-level stock, backorders and missing quantities. Document what the alert should do for each supported case.

  2. Build state and notifications

    Configure inventory reads, item-specific rules and saved incident state. Link Slack notices to the product and the chosen acknowledgement method, using test items and an approved internal channel.

  3. Test repeats and replenishment

    Replay a low-stock reading, acknowledge it, restore stock and cross the threshold again. Check interrupted runs and notification failures before handing the workflow to its owner.

Low-stock alert questions.

Can thresholds vary by SKU?
Yes, the scope can define a threshold for each monitored item. We use a stable product or variation ID for identity and keep the SKU as a readable label, because SKU names can change or be missing.
How are repeat alerts suppressed after acknowledgement?
The workflow stores an incident state and acknowledgement against the stock item. Repeated readings do not create new incidents. Reminders follow the agreed cooldown and escalation policy; a genuine restock can reset the condition for a future shortage.
What if a product does not track a quantity?
It follows a separate policy. A stock-status flag can support a status alert, but it cannot justify a numeric low-stock calculation. Missing or inaccessible inventory is flagged for review rather than treated as available stock.
Will the workflow purchase replacement stock?
No. It alerts the responsible team and records the response state. Purchasing, supplier communication and inventory changes require a separately approved process with its own controls.
Share your store, inventory source and examples of shortages that need attention. We will define the thresholds, reset rules and ownership before building the scenario.

Plan stock alerts your team can act on.

Discuss your automation