How Do I Avoid Running Out of Stock on Black Friday?
The fastest way to avoid running out of stock on Black Friday is to raise your WooCommerce low stock threshold before the sale and route alerts to the right people the moment inventory drops. Krom Automation handles both steps, and the free plugin covers team alerts by email. Pro adds Slack, Telegram and SMS through the messaging integrations for Slack, Discord, Twilio and Telegram.
Black Friday 2026 falls on November 27. You have time to build this now.
Most stores get caught out the same way every year. The WooCommerce default alert fires once per product, goes to a single admin email address, and uses a threshold set for a normal Tuesday in March. A sale day that moves 10 times the usual volume needs a different number and a different routing setup.
This guide covers the threshold calculation most stores skip, the alert workflows that get inventory in front of the right people within minutes, and the back-in-stock sequence that recovers revenue after a sellout. Every workflow described here can be built and tested before November 27.
See how Krom Automation handles WooCommerce triggers and actions
Why the Default WooCommerce Alert Fails on Sale Days
WooCommerce sends one low stock email, to one address, when stock crosses the threshold once. After that, nothing.
If you sell 40 more units in the next two hours, you get no further alert. That is the design, not a bug.
On a normal day, one alert is fine. On Black Friday, one alert is a gap large enough to drive a truck through. Your warehouse team may not see the email for an hour.
Your purchasing manager may not be on the same inbox. The product page keeps selling until stock hits zero.
- Single recipient: one admin address, not a team channel or multiple roles
- Fires once: no repeat alert if stock continues to fall after the first trigger
- No routing logic: the same alert goes to the same person regardless of product category or supplier
- No channel options: email only, no Slack, no SMS, no Telegram
- Static threshold: the number you set in Settings is the number used every day of the year
The complete guide to WooCommerce low stock notification emails covers the default system in detail. The short version: it gets you started, but it is not built for volume days.
What Low Stock Threshold Should You Actually Set for Black Friday?
This is the question no other resource answers directly. Every guide tells you to set a threshold. None of them tell you what number to use on a day when you might sell 10 times your normal volume.
The calculation is straightforward. Take your sales velocity on last year’s Black Friday, or if you do not have that data, take your best single day ever and multiply by 1.5. Divide by your typical restock lead time in days.
That is your minimum threshold for sale days. Round up, not down.
A concrete example: if you sold 200 units of a product last Black Friday across a 24-hour window, that is roughly 8 units per hour. If your supplier takes 3 days to restock, you need to be alerted when you have at least 576 units remaining (8 units per hour, 72 hours, with zero buffer).
In practice, add 20 percent. Your Black Friday threshold for that product is around 690 units, not the 50 you have set for normal months.
Every competitor article treats the low stock threshold as a set-and-forget field. It is not. On Black Friday, your threshold is a live calculation, not a preference.
Per-Product Thresholds vs. Global Thresholds
WooCommerce lets you override the global low stock threshold at the product level under the Inventory tab. Use this for your top 10 to 20 sellers. Set a Black Friday specific number on each before November 20, then revert it after Cyber Monday on November 30.
- High velocity products: multiply normal threshold by 5 to 10
- Medium velocity products: multiply normal threshold by 3 to 5
- Low velocity or long tail: the global threshold is probably fine
- Products with long restock lead times: add an extra buffer equal to one full day of projected sales
This per-product work takes 30 to 60 minutes for most stores. The cost of skipping it is a missed sale day for your best products.
How to Build a Low Stock Alert Workflow in Krom Automation
Krom Automation sits on top of the WooCommerce Order Created and Order Completed triggers in the free version. For stock-specific triggers, you need Krom Automation Pro, which adds 80 or more additional triggers including WooCommerce inventory events. The free plugin is the right place to start if you want to test the canvas and build your first workflows before committing to Pro.
The basic alert workflow has three nodes on the canvas: the low stock trigger, a condition that checks which product or category fired it, and an action that routes the alert. That is it. You build it once and it runs on its own from that point forward.
Alert Routing: Who Gets Notified and How
The real advantage of building this in Krom Automation rather than relying on the WooCommerce default is routing. You can send different alerts to different people based on the product, the category, or the supplier.
A furniture product running low goes to the warehouse team. A digital product running low goes to nobody, because you likely have unlimited stock.
The Slack, Discord, Twilio and Telegram messaging integration in Pro handles all the multi-channel options. The alert can land in a dedicated Slack channel, trigger an SMS to a warehouse phone via Twilio, or send a Telegram message to a purchasing manager who is not watching email on a busy sale day.
- Slack: post to a #black-friday-stock channel so the whole ops team sees it without email
- Twilio SMS: send a text to a warehouse or purchasing contact who is not at a desk
- Telegram: useful for remote teams or suppliers who prefer it over email
- Email: available free, best used as a backup channel rather than the primary one on busy sale days
For teams already using Slack for operations, this is the most reliable setup. An alert in a shared channel is visible to whoever is on duty without any email routing or forwarding rules.
An email alert to one inbox is a single point of failure. A Slack message in a shared ops channel is a team alert. The difference on a day moving 10 times normal volume is significant.
If you are also running high-value order alerts during the sale, the WooCommerce high value order notification setup covers how to combine order triggers with the same messaging channels without building separate workflows for each case.
Using Merge Tags to Make Alerts Actionable
A low stock alert that says “product is low” is not useful. An alert that says “Running Shoes (Size 10) has 18 units remaining, threshold is 50, SKU: RS-10-BLK” is something a warehouse team can act on immediately. Merge tags in Krom Automation inject live data into any action field, including message text, email subject lines and HTTP request payloads.
Build your alert message to include at minimum: product name, current stock count, the SKU, and a direct link to the product’s inventory page in WooCommerce. That is four fields and about two minutes of setup. The person receiving the alert has everything they need to act without logging in and searching.
Adding Conditional Logic: Not Every Alert Is Equal
Conditional branching lets you split a single workflow into different paths based on what fired the trigger. On Black Friday, that matters because a product with 50 units remaining and a 24-hour restock time is a very different situation from a product with 50 units remaining and a 3-week restock time.
The conditions and branching documentation walks through the Yes and No path structure. For stock alerts, the most useful branches are by product category (so you can route to the right supplier contact), by stock count relative to threshold (so you can send a warning alert at 2x the threshold and a critical alert at 1x), and by time of day (so a 2am alert goes to a Slack channel rather than waking someone’s phone).
- Warning path: stock drops below 2x threshold, post to Slack with normal priority
- Critical path: stock drops below threshold, send SMS and Slack with urgent tag
- Supplier routing: use product category to determine which supplier email or contact to include
- Off-hours path: suppress SMS between midnight and 7am, keep Slack active
Back-in-Stock Notifications: Recovering Revenue After a Sellout
Running out of stock during a sale is bad. Running out and having no way to recover that customer is worse. A back-in-stock workflow captures demand from customers who hit the out-of-stock page and notifies them the moment inventory is restored.
The workflow shape is: a customer submits a back-in-stock request form, Krom Automation logs their details against the product, and a second workflow fires when stock is updated to trigger a notification email to every customer on the list for that product. This requires a form plugin on the front end to capture the request. Any of the supported form integrations work: Gravity Forms, WPForms, or Fluent Forms all connect directly to Krom Automation as triggers.
The notification email itself benefits from the visual email builder in Pro. A back-in-stock email that looks like a proper transactional email with product image, name, price and a direct add-to-cart link converts significantly better than a plain text notification. This is worth the 20 minutes it takes to build the template before the sale.
A back-in-stock list is not a consolation prize. It is a pre-qualified buyer list that already tried to purchase. That email list converts at a higher rate than cold traffic on the day stock is restored.
Testing Everything Before Black Friday: The Simulator
Krom Automation includes a workflow simulator for dry-run testing that executes the full workflow logic with zero real side effects. No emails send. No Slack messages post.
No SMS fires. You see exactly what would happen, including which branch the conditions resolve to and what data the merge tags would inject.
Run the simulator on every stock alert workflow at least once before November 20. The specific things to verify:
- Merge tag output: confirm the product name, SKU and stock count are pulling correctly
- Branch resolution: confirm the warning and critical paths resolve as expected at different stock counts
- Recipient routing: confirm the Slack channel, SMS number and email address are correct for each product category
- Delay nodes: if you have any delays, confirm the units are set to minutes or hours, not days
Five minutes with the simulator before the sale is worth several hours of incident response during it. The full WooCommerce Black Friday automation guide covers the wider set of workflows worth testing in the same session.
A Note on WP-Cron and Low-Traffic Windows
Krom Automation runs workflow execution via Action Scheduler, which relies on WP-Cron by default. On a high-traffic store during Black Friday, this is not a concern. WP-Cron fires with every page load, and you will have plenty of those.
The risk is the window before the sale opens, or after it closes, when traffic drops sharply. If no one visits the site for 45 minutes, a delayed workflow action may not fire until the next page load. For time-sensitive stock alerts, configure a real server cron job to call wp-cron.php on a 1-minute interval.
Your host’s control panel or a simple cPanel cron entry handles this in about 5 minutes. It is worth doing before any major sale event.
Set It Up By: A Timeline Counting Back from November 27
| Date | Task | Who |
|---|---|---|
| November 7 | Install Krom Automation free and Pro, run the first test workflow | Developer or site admin |
| November 10 | Calculate Black Friday thresholds for top 20 products | Ops or inventory manager |
| November 13 | Update per-product stock thresholds in WooCommerce | Site admin |
| November 14 | Build alert workflows: warning path, critical path, supplier routing | Developer |
| November 17 | Configure Slack, Twilio or Telegram channels and credentials | Developer |
| November 19 | Build back-in-stock capture form and notification workflow | Developer |
| November 20 | Run simulator on every workflow, fix any merge tag or branch issues | Developer |
| November 21 | Configure real server cron if not already in place | Developer or host support |
| November 24 | Final review: check execution logs from test runs, confirm recipients | Ops lead |
| November 27 | Black Friday. Workflows run on their own. | Nobody manually |
What Does This Cost, and Is the Free Version Enough?
The free version of Krom Automation covers email alerts to multiple addresses and the full workflow builder. If email is enough for your team, the free version is genuinely sufficient and has no run caps or feature locks. Download the free plugin from the WordPress.org plugin directory to start.
Pro is worth it if you need Slack, Twilio SMS or Telegram, if you want the visual email builder for back-in-stock notifications, or if you need the schedule trigger to automatically revert thresholds after Cyber Monday. Pro starts at $69 a year for one site, or $199 as a one-time lifetime payment.
See the full pricing breakdown and plan comparison. Every plan carries a 14-day money-back guarantee.
| Requirement | Free Version | Pro Version |
|---|---|---|
| Email alerts to multiple addresses | Yes | Yes |
| Slack alerts to a team channel | No | Yes |
| Twilio SMS to a warehouse phone | No | Yes |
| Telegram alerts | No | Yes |
| Conditional routing by product category | Yes (basic) | Yes (full Pro trigger data) |
| Visual email builder for back-in-stock emails | No | Yes |
| Schedule trigger to revert thresholds post-sale | No | Yes |
| Workflow simulator for dry-run testing | Yes | Yes |
| Merge tags in alert messages | Yes | Yes |
| Execution logs with per-step audit trail | Yes | Yes |
What the Marketing Pages Leave Out
A few things worth knowing before you build:
- WooCommerce stock triggers are Pro-only: the free triggers cover Order Created and Order Completed. Inventory-specific events need Pro.
- WP-Cron timing matters on low-traffic sites: covered above, but worth repeating because it is the most common support question after a missed alert.
- The default WooCommerce alert and Krom run in parallel: you do not have to disable the WooCommerce default. You can let it continue as a fallback while Krom handles the primary routing. There is no conflict.
- AI actions need your own API key: if you plan to use AI Content Moderation or AI Auto-Tag alongside stock workflows, you supply the API key and pay your provider directly. Krom does not mark up token costs.
- Back-in-stock capture requires a compatible form plugin: Krom Automation does not add a front-end form widget on its own. You connect it to a form plugin you already use.
If a workflow does fail during the sale, Krom Automation sends a failure notification by email and retries automatically with configurable backoff. The guide to silent automation failures on WordPress covers what to check first and how to read the execution log.
Also from wpRigel
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search orders, products and customers by name, email or order number, and run WooCommerce actions without clicking through menus.
During a busy sale day when your team needs to update order status or check stock fast, it removes a lot of unnecessary navigation. It is the only WordPress command palette with real WooCommerce order, product and customer commands built in.
Pollify is a Gutenberg native poll, survey and quiz plugin. If you want to run a post-sale customer survey or a product preference poll before Black Friday to inform your stock decisions, it builds directly inside the block editor as a native block, with no shortcodes required.
Our Verdict: Who Should Do This and Who Should Not
If your store does any meaningful volume on Black Friday and you are still relying on the WooCommerce default alert, you should fix that before November 20. The threshold calculation and the routing setup together take less than a day. The cost of a stockout on a sale day is larger than the cost of the Pro licence across most product categories.
If you run a very small store with five or fewer active products and a supplier who can restock in 24 hours or less, the default WooCommerce alert plus a higher threshold is probably sufficient. Start with the free plugin, build one test workflow, and upgrade only if you find you need the messaging channels.
What we would do: install Pro before November 14, set up the Slack alert workflow first because it takes 20 minutes and has the highest value on sale day, then build the back-in-stock sequence the following day. Run the simulator on both before November 20, set a calendar reminder to revert the per-product thresholds on December 1, and leave the workflows active for the rest of the year. Most of them are worth keeping.
Compare Krom Automation Pro plans and start the free trial
Frequently Asked Questions
Does Krom Automation replace the default WooCommerce low stock email?
No, it runs alongside it. The WooCommerce default alert continues to fire as normal.
Krom Automation adds additional workflows on top, so you can keep the default as a fallback while routing more specific alerts to Slack, SMS or Telegram. You do not need to disable anything in WooCommerce settings.
Do I need Pro to get Slack or SMS alerts for low stock?
Yes. The Slack, Twilio and Telegram integrations are Pro features.
The free version handles email alerts to multiple addresses with full merge tag support. Pro starts at $69 a year with a 14-day money-back guarantee.
Why did my WooCommerce low stock alert only fire once and never again?
That is the intended WooCommerce behaviour. The default system fires one alert when stock first crosses the threshold and does not repeat.
If you sell another 40 units after the first alert, you get no further notification. Krom Automation workflows do not have this limitation because each stock event fires the trigger independently.
Can I set different thresholds for different products in WooCommerce?
Yes. Go to the product edit screen, open the Inventory tab, and enter a per-product low stock threshold.
This overrides the global setting in WooCommerce settings for that specific product. Do this for your top 20 sellers before Black Friday using the velocity calculation described above.
What happens if a Krom Automation workflow fails during Black Friday?
Krom Automation sends an email failure notification and retries the workflow automatically with configurable backoff. Every execution step is logged in the audit trail, so you can see exactly where a failure occurred and what data was passed. The workflow settings documentation covers retry configuration in detail.
Is the workflow simulator safe to run on a live store?
Yes. The simulator is a dry run with zero side effects. It does not send emails, post to Slack, fire SMS messages or modify any data.
It shows you what the workflow would do, including which branch conditions resolve to and what merge tags would output, without executing any real actions. Run it freely on production before the sale.