Zapier has no verified Black Friday sale on record and no confirmed discount is available for November 2026. During a busy sale week, the real cost question is not whether you can find a coupon code. It is how many tasks your WooCommerce store fires per order and whether your current plan covers the load.

Krom Automation, a self-hosted WordPress plugin, removes that maths entirely with flat-rate pricing from $69 a year and no task limits at any tier. The free version handles 16 triggers and 21 actions with no run caps.

The coupon-aggregator pages that dominate search results for this query show codes ranging from 40 to 70 percent off. None of those codes are verified.

Zapier rarely runs public promotional discounts, and no documented Black Friday deal has appeared in any year we can confirm. That matters before you spend time hunting a code that does not exist.

This article gives you the per-task maths for a real Black Friday week, a timeline for getting automations live before November 27, and an honest comparison of what each pricing model actually costs when order volume spikes.

Browse the full Krom Automation feature list if you want to see what 16 triggers and 21 free actions actually cover before reading further.

Has Zapier Ever Had a Black Friday Sale?

Based on publicly available information, Zapier has not run a documented Black Friday promotion. The deal-tracker sites that appear for this query fall into two camps: those that show fabricated or expired codes with no verification, and those that honestly say no confirmed deal exists and pivot to the standing annual-billing discount instead.

The closest Zapier comes to a seasonal saving is switching from monthly to annual billing, which reduces the effective monthly rate. That offer is available year-round and has nothing to do with Black Friday. Waiting until late November to act on it does not save you anything extra.

There is no documented Zapier Black Friday sale. The codes circulating on deal sites are unverified. Annual billing is available today at the same rate it will be on November 28.

If a deal does appear, it would likely show up on Zapier’s own pricing page. Checking there directly is more reliable than any third-party coupon site. For now, assume full price and do the maths on that basis.

What Does Zapier Actually Cost During a Busy Sale Week?

Zapier’s Professional plan costs around $240 per year billed annually, which covers 750 tasks per month, as of September 2026. The key word is tasks, not workflows. Every step in a multi-step Zap counts as a separate task.

Consider a typical WooCommerce Black Friday workflow:

• Order Created fires the Zap
• Add contact to Mailchimp: 1 task
• Apply a tag in FluentCRM: 1 task
• Send a confirmation email via Zapier Email: 1 task
• Log the order to Google Sheets: 1 task

That is 4 tasks per order. At 200 Black Friday orders, you consume 800 tasks in a single day.

The Professional plan’s monthly allowance is 750. You have already exceeded it before Cyber Monday arrives.

Zapier charges overage beyond plan limits, and the next tier jumps significantly in price. That overage bill arrives when you are least expecting it, during or just after your highest-revenue days of the year.

The Per-Task Maths: Three Store Sizes

Store Size (BF Orders)	Steps per Workflow	Tasks Consumed	Zapier Pro Monthly Limit	Overage Risk
50 orders	4	200 tasks	750 tasks	Low
200 orders	4	800 tasks	750 tasks	Exceeds limit on day 1
500 orders	4	2,000 tasks	750 tasks	Well into overage territory

The Professional plan at $240 per year assumes you spread 750 tasks across a full month. Black Friday concentrates a month’s worth of orders into 48 to 96 hours. A workflow that runs fine in February will breach its limit before you finish dinner on November 27.

Adding Cyber Monday on November 30, 2026 extends that spike. Our guide to automating Cyber Monday follow-up emails shows how a second wave of orders inside the same billing cycle compounds the task count further.

Is There a Cheaper Way to Handle Black Friday Automation on WordPress?

Krom Automation is a self-hosted WordPress plugin that runs automations inside your own server. There is no per-task billing, no monthly run cap and no overage charge. A store that processes 5,000 Black Friday orders pays the same as one that processes 50.

The free version, available on the WordPress.org plugin directory, includes the WooCommerce Order Created and Order Completed triggers, plus actions for sending email, adding post meta, making HTTP requests, and running AI tasks. That covers most of what a small store needs for Black Friday without spending anything.

Pro adds 80 or more additional triggers and 60 or more additional actions, including deeper WooCommerce Subscriptions support, form integrations and messaging channels. The full free vs Pro comparison breaks down exactly which features sit behind each tier.

On a task-billing model, your most profitable day of the year is also your most expensive automation day. Flat-rate self-hosted pricing breaks that link entirely.

Flat Rate vs Per-Task: Year-One Cost at Different Order Volumes

Scenario	Zapier Professional (as of Sept 2026)	Krom Automation Pro (1 site)	Krom Automation Free
Under 200 BF orders, simple 2-step workflow	~$240/year, within plan limits	$69/year	$0
200 to 500 BF orders, 4-step workflow	$240/year plus overage charges	$69/year, no overage	$0, no overage
500+ BF orders, 4-step workflow	Higher tier or significant overage	$69/year, no overage	$0, no overage
Multiple client sites (5)	$240/year per connected account	$149/year, 5 sites	$0 per site

Krom Automation Pro pricing starts at $69 per year for one site during current launch pricing. Lifetime plans start at $199 for one site. Every plan includes all Pro features and all 25 integrations.

The only variable is the number of sites. See the full pricing breakdown before your Black Friday prep window closes.

What Krom Automation Covers for Black Friday, Specifically

The free plugin handles the core WooCommerce loop without any configuration beyond installing and connecting. For stores that need more, the Pro integrations cover the services most commonly used during a sale period:

• Email marketing: Mailchimp, ConvertKit, MailerLite, ActiveCampaign
• CRM tagging: FluentCRM for segmenting Black Friday buyers automatically
• Messaging: Slack, Discord, Twilio and Telegram for order alerts to your team
• Data logging: Google Sheets for order tracking without a separate dashboard
• Subscriptions: WooCommerce Subscriptions triggers for renewal and cancellation events

Our guide on tagging Black Friday customers in Mailchimp or FluentCRM shows a complete workflow setup using these integrations. You can also automate early VIP access to your sale using the early access workflow pattern documented there.

Set It Up Before Black Friday: A Working Timeline

Black Friday 2026 is November 27. Cyber Monday is November 30. That gives you a specific window for setup, testing and stress-testing before the first order fires.

1. By November 7: Install the free plugin and connect your WooCommerce store. Run through the step-by-step workflow builder guide to confirm your first automation works end to end.
2. By November 14: Build your Black Friday workflows. Order confirmation, customer tagging, team notifications. If you need email marketing or CRM integrations, activate Pro and link your accounts.
3. By November 20: Run every workflow through the workflow simulator for a dry run with zero side effects. The simulator fires the full execution chain and logs every step without sending real emails or updating live data.
4. By November 25: Check execution logs from your test runs. Confirm failure notifications are configured. On low-traffic sites, configure a real server cron job so WP-Cron fires on schedule rather than waiting for a visitor. This is the single most common cause of delayed automations on quiet staging environments.
5. November 27: Workflows live. Monitor the analytics dashboard during the first hour of your sale for failed executions.

Our broader guide to WordPress automations to set up before Black Friday covers the full preparation checklist, including stock alerts and recovery sequences.

Honest Limits to Know Before You Commit

Krom Automation runs inside WordPress, which means a few constraints are worth naming before you rely on it for your busiest trading week.

• WP-Cron dependency for delays: Delayed actions, such as a follow-up email 24 hours after purchase, depend on WP-Cron firing. On sites with very low traffic between sale events, delays can fire late unless you set up a real server cron. This is not a Krom-specific problem but it is worth configuring before November 27.
• WordPress native scope: Krom Automation is built for automations that involve your WordPress site. If you need to connect two external SaaS tools with no WordPress involvement, a platform like Zapier is the right choice for that specific use case.
• AI actions need an API key: The free AI actions require your own OpenAI, Gemini or Groq key. wpRigel does not charge per AI call and does not mark up tokens, but you do need to supply the key and pay the provider at their standard rates.
• Traffic spike and server capacity: Krom Automation runs via Action Scheduler in the background, so nothing executes during page loads. However, if your hosting plan cannot handle the order volume at the server level, that is a hosting constraint, not an automation one. Our post on whether Black Friday traffic breaks WordPress automations covers this in more detail.

Should You Wait for a Zapier Black Friday Deal or Act Now?

Given that no verified Zapier Black Friday discount exists on record, waiting for one carries a real cost. If you need automation running before November 27, building on Zapier now at full price means paying $240 per year before any overage, then paying again when your task count spikes during the sale.

The alternative is installing the free Krom Automation plugin today, running the simulator against your Black Friday workflows before the sale starts, and having a tested setup live well before November 27. If your workflows stay within the free tier, the cost is $0. If you need Pro, the current launch pricing puts it at $69 for the year on a single site.

For agency owners managing multiple client stores, the Standard plan covers 5 sites at $149 per year during launch pricing. That is the full Pro feature set across five client sites for less than the cost of one Zapier Professional subscription. Our guide to WordPress automation across multiple client sites shows how to manage that at scale.

Waiting for a discount that has never been confirmed means your Black Friday automations go live untested. That is a worse outcome than paying full price for something that works.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate admin interface to learn. Useful for post-purchase surveys and Black Friday feedback forms directly inside your content.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl and K to jump anywhere in the dashboard, search orders and customers, and run admin actions without clicking through menus. It is the only command palette with real WooCommerce order, product and customer commands built in, which makes it genuinely useful during high-volume sale periods when speed inside the admin matters.

Frequently Asked Questions

Has Zapier ever offered a Black Friday discount?

No verified Zapier Black Friday promotion appears on record. Deal-aggregator sites publish codes each year, but none have been independently confirmed. Zapier’s annual billing discount is available year-round and is not a Black Friday promotion.

What happens if I exceed my Zapier task limit during Black Friday?

Zapier pauses your Zaps or charges overage fees depending on your plan. Either outcome is damaging during a sale. Paused automations mean missed confirmations, untagged customers and silent failures that are hard to diagnose after the fact.

Does Krom Automation work with WooCommerce out of the box?

Yes. The free plugin includes WooCommerce Order Created and Order Completed triggers, plus a Create Coupon action and an Update Order Status action.

No additional setup is required beyond having WooCommerce active on the same site. You can download the free plugin from the WordPress.org plugin directory and have a test workflow running in under 30 minutes.

Can I test my Black Friday workflows without triggering real emails or data changes?

Yes. Krom Automation includes a workflow simulator that runs a full dry-run execution with zero side effects. Every step is logged so you can confirm the workflow behaves correctly before the sale goes live.

Is the Krom Automation free version actually free, or does it expire?

It is free forever with no trial period, no run caps and no feature locked behind a paywall after a set number of executions. The 16 triggers, 21 actions and 20 workflow templates are all available without a licence key or a credit card.

What is the deadline for setting up automations before Black Friday 2026?

Black Friday 2026 is November 27. We recommend having workflows built and simulator-tested by November 20, leaving a week to fix any issues before real orders arrive. Leaving setup until the week of the sale means you will not have tested the failure scenarios in time to correct them.

No, Black Friday traffic should not break your WordPress automations, but it can slow them, delay them, or silently fail them if you have not set things up correctly. Krom Automation, available free from the WordPress.org plugin directory, runs all workflow execution through Action Scheduler rather than a synchronous page request, which means a traffic spike does not queue your automations behind site visitors.

The bigger risks are WP-Cron timing on low-traffic sites, email deliverability at high send volumes, and workflows that fail without alerting anyone. This guide covers all three, with a setup timeline counting back from Black Friday, November 27, 2026.

The free version of Krom Automation covers every risk described here: background execution, execution logging, failure alerts, and the workflow simulator for dry-run testing. Pro is only needed if you want scheduled triggers, the visual email builder, or integrations with external platforms like Mailchimp or FluentCRM.

Work through this article in order. The sections on WP-Cron and Action Scheduler come first because every other fix depends on reliable execution timing. Email deliverability and failure alerting come after, because they only matter once execution is stable.

Browse the full feature list to see everything included in the free plugin before reading further.

Quick Summary

Risk	Cause	Fix	Free or Pro?
Delayed workflow execution	WP-Cron only fires on page visits	Set up a real server cron calling wp-cron.php every minute	Free
Duplicate coupon sends	Workflow fires more than once per order	Enable “Run once per entity” in workflow settings	Free
Silent failures	No one monitors execution logs	Enable failure notifications with email alert and auto-retry	Free
Emails landing in spam	High send volume from a shared host	Route through a transactional mail provider with SPF, DKIM, DMARC set	Free
Untested workflows going live	No dry-run before the sale	Use the workflow simulator before November 27	Free
Scheduled deal launch	Manual publish is error-prone	Use the Schedule Trigger to fire at exact times	Pro

Why Does Black Friday Specifically Break Automations?

Most automation failures on high-traffic days are not caused by the traffic itself. They are caused by deferred execution systems behaving differently under load than they did during quiet testing. WordPress relies on WP-Cron, a pseudo-cron that fires when a site visitor loads a page.

On most days that gap is acceptable. On Black Friday, two things happen at once: more events fire in a shorter window, and WP-Cron can fire multiple times in quick succession as traffic spikes.

The result is either over-execution, where the same workflow fires twice for one order, or under-execution on low-traffic gaps between bursts. Neither is obvious from the front end. You only see it in the execution logs, and only if you know to look.

A workflow failing 20 percent of the time looks identical to a working one until you check the logs. Most sites check the logs after the sale ends, which is exactly the wrong moment.

How Action Scheduler Protects You (and Where It Does Not)

Krom Automation queues every workflow execution through Action Scheduler, the same background processing library that powers WooCommerce. This means a workflow triggered by an order completion does not run inline with the page request. It is queued, and a background process picks it up and runs it separately.

That separation is what keeps your checkout page fast during a traffic spike. The automation runs in the background, typically within 30 to 60 seconds on a healthy site, while the customer sees their thank-you page immediately. Action Scheduler is not WP-Cron. It has its own queue, its own retry logic, and its own failure tracking, all of which Krom Automation surfaces in the execution log and the analytics dashboard.

Where it does not protect you: Action Scheduler still needs PHP to run its queue. On a severely overloaded shared hosting environment where PHP workers are fully saturated, queue processing can fall behind. The fix is not a different plugin.

The fix is adequate hosting for the traffic volume you expect. If your host cannot handle 200 simultaneous visitors, no automation plugin will compensate for that.

The Real Server Cron Fix Every Site Needs Before November 27

WP-Cron’s default behavior is to piggyback on page visits. On a low-traffic site, a gap of 2 to 4 hours between visitors is common, which means a delay-based workflow set to fire “15 minutes after order completion” can actually fire 2 hours later if the site goes quiet. On Black Friday, the risk flips: too many page loads can trigger multiple simultaneous cron runs, creating race conditions.

The fix is standard and takes about 5 minutes:

1. Disable WP-Cron page-visit triggering by adding define( ‘DISABLE_WP_CRON’, true ); to wp-config.php.
2. Add a real server cron job that calls wp-cron.php directly, on a one-minute interval.
3. Confirm the cron is running by checking the Action Scheduler queue in Tools, Scheduled Actions inside wp-admin. The “Last run” timestamp should update every minute.

This is the single highest-impact configuration change you can make before Black Friday. It costs nothing, requires no plugin, and eliminates the entire class of timing-related automation failures. Do it first, before testing anything else.

What to Test Before the Sale: The Simulator First

Krom Automation includes a workflow simulator for dry-run testing with zero side effects. You give it a sample trigger payload, it walks the workflow step by step, evaluates every condition, and shows you what each action would have sent, without actually sending anything. No test emails, no test orders created, no coupons generated.

Run the simulator on every workflow that will be active during the sale. The three most common failures it catches before they happen:

• Merge tags that resolve to empty strings, usually because the trigger payload does not contain the field you referenced. An order confirmation email with a blank customer name looks unprofessional at any volume and catastrophic at 500 sends.
• Conditional branches that never reach a Yes path, meaning the workflow silently does nothing for every qualifying order.
• Actions pointing to deleted posts or obsolete coupon codes, common when workflows were built months ago and the content has changed since.

After the simulator passes, run a live test with a real but low-value order or a test user account. Check the execution log to confirm every step completed and the timestamps are within the expected window. See the step-by-step workflow building guide if any step looks unfamiliar.

The simulator catches the failures that only show up at volume. A merge tag resolving to empty on 3 orders is a minor annoyance. The same bug on 600 orders is a customer service crisis.

Keeping Emails Out of Spam on High-Volume Days

Transactional emails sent through WordPress’s default wp_mail() function go out through whatever mail system your host provides. On shared hosting, that usually means a server IP shared with hundreds of other sites. On Black Friday, deliverability from shared IPs collapses because spam filters treat sudden volume increases from unfamiliar IPs as suspicious, regardless of the content.

The fix is routing all automated email through a dedicated transactional mail provider. Common choices include SendGrid, Postmark, Mailgun, Amazon SES, and Brevo.

Any of these will work with a WordPress SMTP plugin. Set it up before the sale, not during it, because warming a new sending IP takes days and you want the reputation established before the volume hits.

Three DNS records are non-negotiable:

• SPF: tells receiving servers your transactional provider is authorized to send on your domain’s behalf.
• DKIM: cryptographically signs each message so the content cannot be tampered with in transit.
• DMARC: tells receiving servers what to do when SPF or DKIM fails, and sends you reports when they do.

For a deeper look at why automated WordPress emails end up in spam and how to fix each cause, this guide on WordPress email deliverability covers every scenario. If you are sending order confirmation or post-purchase sequences through Mailchimp or FluentCRM, check the Mailchimp integration documentation or the FluentCRM integration documentation to confirm your API credentials and list mappings are current before the sale.

Failure Alerts: The Feature That Saves Your Black Friday

Krom Automation sends failure notifications by email and automatically retries failed executions with configurable backoff. This sounds like a minor feature until you consider what the alternative is: a workflow fails at 11 PM on Black Friday, no one knows, and by the time you check the logs Saturday morning, 300 customers have received nothing. Silent automation failures are a real and common problem on high-volume days.

Configure failure alerts to go to an address someone actually monitors on sale day. The default retry behavior handles transient failures, such as a momentary timeout on an HTTP request or a brief database lock, without manual intervention. For persistent failures, the execution log records the exact step that failed, the error message, and the trigger payload, giving you everything needed to diagnose and fix it.

The analytics dashboard shows total executions, active workflows, success rate, failed execution count, and an execution trend chart. Check it the morning of Black Friday, and again mid-afternoon. A rising failure count that does not trigger an immediate investigation is a risk with a known cost.

The Run-Once Setting: Stopping Duplicate Sends

Under high load, WP-Cron can fire multiple times for the same event in quick succession before Action Scheduler has finished processing the first run. Without a safeguard, a single order completion could trigger the same workflow twice, sending two coupon codes, two confirmation emails, or two Slack alerts.

Krom Automation’s “Run once per entity” setting prevents this. Enable it in the workflow settings panel for every workflow that should fire only once per user, order, or post. With it active, even if the trigger fires three times for the same entity, the workflow executes exactly once.

This is not a workaround for bad hosting. It is a deliberate design feature for exactly this scenario.

Setup Timeline: What to Do by When

Black Friday is November 27, 2026. Cyber Monday is November 30.

Work backwards from the sale date and complete each step before moving to the next. Skipping ahead to email testing before cron is configured wastes time because timing failures will corrupt your test results.

Date	Task	Time required
By November 10	Configure real server cron. Disable WP-Cron page-visit triggering. Verify Action Scheduler queue is processing every minute.	30 to 60 minutes
By November 13	Set up transactional mail provider. Configure SPF, DKIM, DMARC. Send 50 to 100 test emails and check deliverability scores.	2 to 3 hours
By November 17	Audit every active workflow. Enable “Run once per entity” on all order and user workflows. Enable failure notifications on all workflows.	1 to 2 hours
By November 21	Run the workflow simulator on every workflow that will be active during the sale. Resolve all merge tag and branching issues found.	2 to 4 hours
By November 24	Run one live end-to-end test per critical workflow. Check execution logs for timing and completeness. Fix anything that does not match expected behavior.	2 to 3 hours
November 27 morning	Check the analytics dashboard. Confirm failure alert email is reaching the right inbox. Watch execution trend chart in the first 2 hours of the sale.	30 minutes

Workflows Worth Having Active on Sale Day

These are the automations that earn their place on a high-traffic day. Each one is buildable in the free version of Krom Automation, with the triggers and actions referenced here available without a Pro licence.

• Order Created alert to Slack or SMS: fires within 60 seconds of each order. High-value order monitoring is covered in the WooCommerce order alerts guide, and Slack, Discord, Twilio, and Telegram are all supported in the messaging integrations documentation.
• Low stock alert: triggers when product stock drops below a threshold you set, and notifies the team before the item oversells. See how to set this up for Black Friday specifically.
• Post-purchase coupon send: Order Completed trigger, Send Email action with a dynamic coupon merge tag. Enable “Run once per entity” to prevent duplicates. The guide on sending coupon codes automatically walks through the exact setup.
• Customer tagging in Mailchimp or FluentCRM: tags every buyer with a “black-friday-2026” tag for segmentation later. See how to tag Black Friday customers for the step-by-step.
• Cyber Monday follow-up sequence: starts after Order Completed, uses a delay of 3 days, then sends a follow-up with retention content. Automating the Cyber Monday follow-up is a separate workflow worth building now.

What Krom Automation Does Not Handle

This is the section competitors rarely write, so read it carefully. Krom Automation is a WordPress-native automation plugin.

The trigger or the action needs to touch your WordPress site. It is not designed for automations between two external services that have no WordPress involvement.

Delays depend on WordPress Cron and Action Scheduler. With a real server cron configured and adequate hosting, timing is reliable to within a minute or two.

Without a real server cron, on a site that gets one visitor every few hours, a “15 minute delay” can mean 3 hours. That is an infrastructure issue, not a plugin issue, but it is a real constraint.

AI actions require your own API key from OpenAI, Google Gemini, or Groq. wpRigel does not charge per AI call and does not mark up tokens. You pay your provider directly at their standard rates.

On a high-volume Black Friday, if you are running AI content moderation or auto-tagging on every order, that API cost can add up. Budget for it.

Shared hosting and a Black Friday traffic spike is not a combination. It is a slow-motion disaster that starts looking like an automation problem but is really a resource problem.

Free vs Pro: What You Actually Need for Black Friday

Every reliability feature described in this article, including the workflow simulator, execution logging, failure alerts, retry logic, and “Run once per entity”, is in the free version. Pro is worth it if you need the Schedule Trigger to launch deals at exact times without manual publishing, the visual email builder for branded order emails, or integrations with external platforms. The complete free vs Pro comparison lists everything side by side.

Pro plans start at $69 a year or $199 as a one-time lifetime payment, covering 1 site. Every Pro plan includes all 25 integrations and all 101 Pro workflow templates.

All Pro plans carry a 14-day money-back guarantee. See the full pricing breakdown for per-site costs across all three tiers.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built directly inside the block editor as real blocks, so there are no shortcodes to paste and no separate interface to learn. It is worth using during a Black Friday campaign to collect buyer feedback or run a post-purchase satisfaction poll.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search everything, and run admin actions without clicking through menus.

On a high-pressure sale day when you need to check an order, update stock, or resend a receipt without navigating five menus, it pays for itself in seconds. It is the only WordPress command palette with real WooCommerce order, product and customer commands built in.

Verdict: Who Should Act, Who Should Wait

Act now if you are running any WooCommerce automation, post-purchase email, or delay-based workflow on a site that gets Black Friday traffic. The setup timeline above takes 8 to 12 hours spread over three weeks. That is a reasonable investment against a sale that may do more revenue in 48 hours than a typical month.

You can wait if your site runs on managed WordPress hosting with a real server cron already configured, your automations have been stable for months, and you have monitored execution logs recently. In that case, run the simulator against your active workflows, confirm failure alerts are pointing to an inbox someone watches, and you are done.

What we would do: configure the real server cron first, run every active workflow through the simulator on November 21, and check the analytics dashboard twice on November 27. The three steps that cause the most Black Friday automation failures are timing, silent failures, and email deliverability. Each one has a known fix and none of them require paid software to resolve.

The free plugin is available now from the WordPress.org plugin directory. Install it, build your first workflow using the welcome email automation guide, and have every critical workflow simulator-tested before November 24.

See the full pricing breakdown if you need the Schedule Trigger or Pro integrations for this sale season.

Frequently Asked Questions

Does Krom Automation slow down my site during high traffic?

No. Every workflow execution is queued through Action Scheduler and runs in the background, separate from page requests.

A visitor completing an order does not wait for the automation to finish. The checkout response goes out immediately and the workflow fires within 30 to 60 seconds on a healthy server.

What happens if a workflow fails during the Black Friday rush?

Krom Automation sends a failure notification email and automatically retries the failed execution with configurable backoff. The execution log records the exact step that failed and the error message. You can review and manually retry any failed execution from the wp-admin dashboard.

Can I schedule deal launches to go live automatically at midnight?

Yes, with the Pro Schedule Trigger. You can set a workflow to fire at an exact date and time, on a one-time basis, without needing to be online.

The free version does not include the Schedule Trigger. See the Schedule Trigger documentation for configuration details.

How do I test my workflows without sending real emails to real customers?

Use the built-in workflow simulator. It performs a complete dry run through every step of the workflow, evaluating conditions and resolving merge tags, without executing any action.

No emails are sent, no posts are created, and no API calls are made. See the simulator documentation for how to supply a test payload.

Will Krom Automation work with my WooCommerce subscriptions or abandoned cart setup?

WooCommerce Subscriptions triggers and actions are covered in the WooCommerce Subscriptions integration documentation. Abandoned cart recovery without a SaaS tool is covered separately in this guide on recovering abandoned carts in WooCommerce.

Is there a limit on how many workflows or executions I can run on the free plan?

No. The free version has no execution caps, no run limits, and no features locked behind a paywall. Every reliability feature described in this article, including failure alerts, execution logging, and the workflow simulator, is available in the free plugin with no trial period.

You can tag Black Friday customers in FluentCRM or Mailchimp automatically using Krom Automation. The free plugin handles WooCommerce order triggers and FluentCRM tag actions with no code.

For the Mailchimp integration, you need Krom Automation Pro. Set up one workflow per tag, run it through the simulator before November 27, and every buyer gets tagged the moment their order completes.

Most guides stop at “use tags to segment your list.” None of them show you which tags to create, what workflow logic fires them, or how to structure things so your January re-engagement campaign actually reaches the right group. That is what this article covers. Black Friday 2026 is November 27.

Cyber Monday is November 30. The setup takes under an hour if you start this week.

The gap most stores fall into is collecting a lot of buyers in November and then mailing the same message to all of them in January. A first-time buyer who spent $30 on a clearance item needs a different message than a returning customer who spent $200 on your flagship product. Tags are how you tell them apart, and automation is how you apply those tags without thinking about it during the sale rush.

Browse the full feature list to see what triggers and actions are included at each tier.

Which Tags Should You Actually Create?

The tags you create now determine the segments you can use in January. Create too few and everyone ends up in one bucket.

Create too many and the list becomes unmanageable. The following structure works for most WooCommerce stores running Black Friday campaigns.

• BF2026-Buyer: applied to every completed order during the sale window, regardless of what they bought or how much they spent. This is your broadest segment.
• BF2026-FirstTime: applied only when the buyer has no prior completed orders. Identifies people who discovered you through the sale and need nurturing toward a second purchase.
• BF2026-Returning: applied when the buyer already has at least one prior completed order. These are your most valuable contacts, and they should never receive a “welcome new customer” sequence.
• BF2026-HighValue: applied when the order total clears a threshold you set, typically $100 or $150. These buyers respond well to loyalty offers and early access to future sales.
• BF2026-[ProductCategory]: one tag per product category, for example BF2026-Apparel or BF2026-Gear. Use these to send category-specific follow-up content in December and January.

Five tag types covers almost every post-sale scenario without drowning your CRM in noise. You can always add more, but start here and expand based on what the data shows after the sale.

How to Set Up the Workflow in Krom Automation (Free Version)

The free version of Krom Automation includes two WooCommerce triggers, Order Created and Order Completed, and four user actions including Update User Meta and Change User Role. For FluentCRM tagging, the FluentCRM integration is a Pro feature. For the free version, the closest native option is Update User Meta, which stores the tag value in WordPress user meta and can be read by FluentCRM’s dynamic segment rules.

If you are running Pro, skip ahead to the FluentCRM and Mailchimp sections below. If you are on the free version and want to test the workflow structure before upgrading, use Update User Meta as a placeholder action and swap it for the FluentCRM tag action once Pro is active.

Start with the broadest tag. Go to Krom Automation, create a new workflow, and set the trigger to Order Completed. No conditions yet.

Add a single action: the FluentCRM action to apply the tag BF2026-Buyer. Save, activate, and test with the workflow simulator before any real orders come in.

How to Tag First-Time Versus Returning Buyers

This is where conditional branching does its real work. Create a second workflow with Order Completed as the trigger. Add a condition node that checks whether the customer’s total order count equals 1.

If Yes, apply the tag BF2026-FirstTime. If No, apply BF2026-Returning. One workflow handles both paths.

The condition uses the order count value available in the Order Completed trigger data. You do not need to query the database separately. Krom Automation passes the order context through every downstream node, so the condition has access to customer history at the moment it runs.

A first-time Black Friday buyer is not a loyal customer yet. Treating them like one before they have made a second purchase is the fastest way to waste a re-engagement sequence on someone who was only ever hunting a discount.

The full explanation of triggers, actions, and workflow logic covers how condition nodes evaluate data from the trigger context, which is worth reading before you build the branching workflow.

How to Tag by Order Value

High-value tagging follows the same pattern. Create another workflow, trigger on Order Completed, and add a condition that checks whether the order total is greater than or equal to your threshold.

Set that threshold at a number that represents genuinely strong spend for your store, not just above average. For most stores, $100 to $150 is a reasonable starting point for a “high value” tag.

If the condition passes, apply BF2026-HighValue in FluentCRM. If it does not, the No path can be left empty or used to apply a different tag.

You do not need to run a separate workflow for every order value band. One condition per workflow keeps things readable.

The analytics dashboard in Krom Automation shows how many times each workflow executed and its success rate. After the sale, check that number against your order count in WooCommerce. If they do not match, check the execution logs for failures before you send any January campaign.

How to Tag by Product Category

Category tagging is the most granular layer and the most useful for product-specific follow-up emails in December. Create one workflow per category.

Each workflow uses Order Completed as the trigger and adds a condition checking whether the order contains a product from that category. Apply the matching tag on the Yes path.

If you sell across five categories, you have five workflows. They all run in parallel when an order completes.

A buyer who purchases from two categories gets both tags. That is the correct behaviour, and it means a single buyer can appear in multiple segments without any extra logic on your part.

For stores with a large product catalogue, the merge tags documentation explains how to pull product and order data dynamically into action fields, which is useful if you want to include product names in the tag value itself rather than hardcoding a category name.

Tagging in FluentCRM: The Exact Workflow

With Krom Automation Pro active, the FluentCRM integration adds a set of dedicated actions for contacts, tags, and lists. The full reference is in the FluentCRM integration docs. For Black Friday tagging, the action you want is “Apply Tag to Contact.” It takes the contact email from the order trigger, finds or creates the FluentCRM contact, and applies the tag you specify.

The workflow shape for the master BF2026-Buyer tag looks like this:

1. Trigger: Order Completed (WooCommerce, during the sale window)
2. Action: Apply Tag “BF2026-Buyer” to FluentCRM Contact (matched by email)
3. Enable “Run Once Per Entity” to prevent duplicate tag applications on the same order

Duplicate the workflow for each additional tag, adjusting the condition and tag name. Keep each workflow focused on one tag.

Five tags, five workflows. That way, if one workflow fails, the others keep running and you only lose one segment, not all of them.

The workflow settings documentation covers the Run Once Per Entity toggle and the import and export options, which matter if you are deploying the same tag logic across multiple client sites.

Tagging in Mailchimp: What the Pro Integration Handles

The Mailchimp integration in Krom Automation Pro works through the same trigger-and-action pattern. The full setup is documented in the Mailchimp integration guide.

The action applies a Mailchimp tag to a subscriber matched by email address. If the subscriber does not exist yet, the action can optionally create them.

The tag names you use in Mailchimp should match what you use in FluentCRM wherever possible. BF2026-Buyer in both tools means your January reporting uses consistent labels, and if you ever migrate between platforms you do not need to remap everything.

For stores running both platforms in parallel, run two action nodes in each workflow: one for FluentCRM and one for Mailchimp. Both get the same tag applied from the same order event.

Running FluentCRM and Mailchimp in parallel during a sale is more common than most guides admit. The workflow that tags both platforms from a single Order Completed trigger is the one you want to build once and never think about again.

If you need to connect other email tools in the same stack, the ActiveCampaign integration and MailerLite integration follow the same pattern and are documented separately.

What the Summary Table Looks Like Before You Build

Tag	Trigger	Condition	Plugin Tier	Applies To
BF2026-Buyer	Order Completed	None	Pro (FluentCRM/Mailchimp action)	All buyers
BF2026-FirstTime	Order Completed	Order count = 1	Pro	New customers only
BF2026-Returning	Order Completed	Order count 1	Pro	Repeat customers only
BF2026-HighValue	Order Completed	Order total >= $100	Pro	High-spend buyers
BF2026-[Category]	Order Completed	Order contains category	Pro	Category-specific buyers

Set It Up By: A Timeline Counting Back From November 27

Leaving this until the week of Black Friday means you will be troubleshooting workflows during the sale itself. Work backwards from November 27 and give each step a fixed deadline.

• By November 10: Create tags in FluentCRM and Mailchimp. Empty tags ready to receive contacts are better than tags you create during the sale under pressure.
• By November 14: Build all five workflows in Krom Automation. Use the visual canvas to lay them out and review the logic top to bottom before saving.
• By November 17: Run each workflow through the workflow simulator. The simulator runs a dry pass with no side effects, so no real tags are applied and no real emails are sent. Confirm each Yes and No path resolves correctly.
• By November 20: Place a real test order in WooCommerce staging or use a $0.01 test product on production. Confirm the tags appear in FluentCRM and Mailchimp within 60 seconds of order completion.
• By November 24: Activate all workflows. Check that execution logging is on. Set up failure notification emails so you know immediately if a workflow stops running during the sale.

If you want to give your best customers early access before November 27, the VIP early access guide covers how to identify and notify them automatically. And once the sale is over, automating your Cyber Monday follow-up emails is the next workflow to build.

What Does Not Transfer Automatically and What You Must Do By Hand

Automation handles every order that completes during the sale window. It does not handle anything that happened before the workflows were active, any order that was refunded before completion, or any buyer who checked out as a guest if their email does not already exist as a FluentCRM contact.

Scenario	Automated	What You Need to Do
Orders completed while workflows are active	Yes	Nothing
Orders placed before workflows were activated	No	Bulk import via FluentCRM CSV with tags pre-filled
Guest checkouts with no existing CRM contact	Partial	Enable “create contact if not found” in the action settings
Orders that are refunded or cancelled	No	Build a separate workflow using Order Status Changed trigger to remove tags
Existing Mailchimp subscribers not yet in FluentCRM	No	Run a one-time CSV migration before the sale window opens

Refunded orders are the most common mistake. If a buyer gets the BF2026-HighValue tag and then requests a refund two days later, they will still appear in that segment unless you build a cleanup workflow. The Order Status Changed trigger handles this.

Add it as a sixth workflow that checks for a status change to Refunded and removes the BF2026 tags from that contact. It takes ten minutes to build and prevents embarrassing “valued high-spend customer” emails going to people who returned everything.

The workflows you do not build are the ones that cost you in January. A refunded buyer who receives a loyalty reward email is not a rounding error. It is a support ticket and a lost re-engagement opportunity in the same message.

A Note on WP-Cron Timing

Krom Automation runs workflows via Action Scheduler, which uses WordPress Cron. On a high-traffic WooCommerce store during Black Friday, cron fires constantly and delays are negligible.

On a lower-traffic site where page visits drop off overnight, cron can run late by 30 to 90 minutes. For Black Friday tagging this rarely matters, because the tag only needs to be in place before you send the first post-sale email, which is usually at least 24 hours after the order.

If precise timing is critical, configure a real server-side cron job to replace WP-Cron. Your host’s control panel or a simple crontab entry set to run every minute is all it takes. The delays and scheduling documentation covers timing behaviour in detail.

Krom Automation Pricing for This Use Case

The FluentCRM and Mailchimp tag actions require Pro. Pro starts at $69 a year for a single site, and lifetime plans start at $199 as a one-time payment. Every Pro plan includes all 25 integrations and all Pro features.

The only difference between plans is the number of sites. See full pricing details, and note that all Pro plans carry a 14-day money-back guarantee.

If you manage automation across multiple client stores, the Standard plan covers 5 site activations and the Enterprise plan covers unlimited sites. For agencies running Black Friday campaigns across 10 or more clients, the multi-site automation guide explains how to deploy and manage workflows at scale. The free version is available on the WordPress.org plugin directory with no trial period and no run limits, so you can install it, build the workflow structure, and test with the simulator before committing to Pro.

If you want to see how Krom Automation compares to Uncanny Automator or Zapier on price, Uncanny Automator’s automation plans started at $199 per year for one site at the time of writing (September 2026), with AI features starting at $300 per year. Zapier’s Professional plan ran around $240 per year billed annually for 750 tasks per month, with overage charges on top.

Neither offers a lifetime plan. Krom Automation has no per-task billing at any tier.

For more context on those numbers, the Uncanny Automator pricing breakdown and the Zapier pricing analysis go into more detail.

Once the sale is over, the BF2026 tags in FluentCRM and Mailchimp are the foundation for everything that comes next. Turning Black Friday buyers into repeat customers covers the January campaign logic, including which segment to prioritise first and what message works for each tag group.

Also from wpRigel

Pollify is a Gutenberg native poll, survey, and quiz plugin. Polls are built as real blocks inside the WordPress editor, so there are no shortcodes to paste and no separate interface to configure. It is useful for post-sale surveys and NPS collection from the same buyers you just tagged.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump to any order, search customers, change order status, and run admin actions without clicking through menus. It is the only WordPress command palette with genuine WooCommerce order, product, and customer commands built in.

Our Verdict

If you run a WooCommerce store and use FluentCRM or Mailchimp for email marketing, this setup is worth the hour it takes to build. The tags you apply during Black Friday 2026 are the segmentation you use for the next six months. A store that does not tag is sending the same January email to a first-time $25 buyer and a returning $300 customer, and wondering why re-engagement rates are poor.

The free version of Krom Automation is enough to learn the workflow structure and test it in the simulator. Pro is what connects the Order Completed trigger to FluentCRM and Mailchimp directly.

Start with the free plugin, build the five workflows described here, and run the simulator before November 24. That is the minimum viable setup, and it is enough.

Download the free plugin from the WordPress.org plugin directory and build the workflow structure today. When you are ready to activate the FluentCRM and Mailchimp tag actions, upgrade to Pro before the sale window opens.

Frequently Asked Questions

Does tagging Black Friday customers in FluentCRM require Krom Automation Pro?

Yes. The FluentCRM tag action is a Pro feature. The free version of Krom Automation includes WooCommerce order triggers and can store data in WordPress user meta, but applying tags directly inside FluentCRM requires a Pro plan, which starts at $69 per year for a single site.

What happens if a buyer places an order before I activate the workflows?

Krom Automation only processes orders that complete after the workflow is active. Any orders placed before activation need to be tagged manually. The fastest way is a CSV export from WooCommerce filtered to the sale date range, with your BF2026 tag column pre-filled, imported directly into FluentCRM.

Can I apply multiple tags to the same buyer from a single order?

Yes. Run one workflow per tag and all of them listen to the same Order Completed trigger. A buyer who qualifies for BF2026-Buyer, BF2026-FirstTime, and BF2026-HighValue will have all three applied within seconds, because each workflow runs independently and in parallel.

What if a buyer checks out as a guest and has no FluentCRM contact yet?

The FluentCRM action in Krom Automation can create a new contact if one does not already exist for that email address. Enable the “create contact if not found” option in the action settings. The contact will be created with the buyer’s email and name from the order, and the tag will be applied immediately.

Can I remove Black Friday tags automatically if an order is refunded?

Yes. Build a sixth workflow using the Order Status Changed trigger, set the condition to check for a status of Refunded, and add a FluentCRM action to remove the BF2026 tags from that contact. Without this workflow, refunded buyers remain in your high-value and buyer segments and will receive incorrect follow-up emails.

Does the workflow simulator confirm that FluentCRM tags will be applied correctly?

The simulator runs a complete dry pass through every node in the workflow with zero side effects. No tags are applied, no emails are sent, and no FluentCRM contacts are created or modified.

It confirms that the trigger fires, conditions resolve to the correct Yes or No path, and every action node is reachable. Use it to validate all five workflows before November 24.

You can give VIP customers early access to your Black Friday deals using Krom Automation, and the free plugin covers most of what you need. The core workflow: set a condition that identifies high-value customers by WooCommerce order history or user role, fire a personalised coupon code email before the public sale opens, and trigger a Slack or email alert to your team when a VIP order lands.

Black Friday 2026 is November 27. If you start setup by November 10, you have two weeks to build, test and stress-test before anything goes live.

Most guides on VIP early access assume you already have a clean segment ready to go. They skip the harder question: how do you define “VIP” in the first place, and how do you automate the entire chain from identification to notification without stitching together three separate tools? This article answers both.

For the email design side of the early access message itself, the visual email builder in Krom Automation Pro gives you a block-based editor powered by Gutenberg, so you can build a properly branded early access email without touching HTML. If you are staying on the free plan, the Send Email action handles plain and simple HTML just fine for getting started.

Browse the full feature list to see exactly what the free version includes before deciding whether Pro is worth adding for this campaign.

What Does “VIP” Actually Mean, and How Do You Identify Those Customers?

This is the step every competitor guide skips. They tell you to email your VIP segment.

They never tell you how to build it. The honest answer is that “VIP” should be a definition you set deliberately, not a gut feeling applied at send time.

Here are the most common definitions that work well with WooCommerce data:

• Cumulative spend threshold: customers who have spent more than a set amount across all orders, for example $500 lifetime.
• Order frequency: customers with three or more completed orders in the last 12 months.
• Recency plus value: customers who placed a high-value order in the last 90 days, combining both signals.
• Explicit membership or subscription: customers on a MemberPress or WooCommerce Subscriptions plan that includes VIP perks.
• Custom user role: a WordPress role you assign manually or via automation to your top tier, for example a role named “VIP Customer”.

Krom Automation’s conditional branching lets you check these attributes at the moment a trigger fires. You are not running a batch query across your whole customer list. You are evaluating each user against your VIP criteria when something happens, such as when an Order Completed event lands or when a scheduled workflow runs the morning before early access opens.

Defining VIP as a role you assign automatically, rather than a list you compile manually, means your segment stays accurate all year without any maintenance effort.

The cleanest setup for most stores is a two-stage approach. First, a year-round workflow that promotes customers to a “VIP Customer” role once they hit your spend or frequency threshold. Second, the Black Friday workflow that triggers only for users holding that role.

The first workflow runs quietly in the background and keeps your segment fresh. The second fires once, on schedule, and sends the early access email to whoever qualifies at that moment.

How to Build the VIP Early Access Workflow in Krom Automation

The full setup uses two separate workflows. Work through them in this order: the role-promotion workflow first, because it needs time to classify your existing customers before the early access email fires.

Workflow 1: Promote Customers to the VIP Role Automatically

This workflow runs whenever an order completes, checks whether the customer meets your VIP threshold, and updates their role if they do. It uses three nodes on the canvas:

1. Trigger: Order Completed. This fires every time WooCommerce marks an order as complete.
2. Condition: Check cumulative spend or order count. Use the Yes/No branch to evaluate whether the customer meets your threshold. Orders below the threshold exit on the No path and nothing happens.
3. Action: Change User Role. On the Yes path, set the customer’s role to your VIP role. Enable “Run Once Per Entity” in workflow settings so returning customers who already hold the VIP role are not processed again.

Run this workflow now, not in November. Customers who qualify today should be tagged today, so your early access list is as accurate as possible by the time you send. The “Run Once Per Entity” setting is the key detail here: without it, the role change action fires on every order, which wastes execution cycles and can cause unexpected behaviour if a customer’s role is shared across your site’s permission logic.

Workflow 2: Send the VIP Early Access Email and Coupon

This workflow fires on a schedule you set in advance. It uses the schedule trigger, which is a Pro feature, to run at a precise date and time, for example 6 AM on November 24, giving VIPs 72 hours before the public sale opens on November 27.

The workflow nodes:

1. Trigger: Schedule. Set it to run once on November 24 at 6 AM. One-time execution, not recurring.
2. Condition: User Role equals VIP Customer. This filters each user the workflow processes against the VIP role you set in Workflow 1.
3. Action: Create Coupon (WooCommerce). Generate a unique percentage or fixed discount coupon for this customer. Set expiry to midnight on November 27 so the exclusive window is genuinely exclusive.
4. Action: Send Email. Use merge tags to inject the customer’s first name, the coupon code, and the expiry date into the email body. Every email is personalised with zero manual effort.

If you are using an email marketing platform rather than WordPress transactional email, the Mailchimp integration, ActiveCampaign integration, and FluentCRM integration all let you push the customer and their coupon data into your email platform instead, where your existing templates and deliverability setup take over.

Workflow 3: Alert the Team When a VIP Orders

This is the step most Black Friday automation guides omit entirely. Knowing when a VIP converts during the early access window lets your team respond fast: a personal thank-you message, a priority fulfilment flag, or a hand-off to your account manager if you run a B2B store.

Build a third workflow triggered by Order Created or Order Completed, with a condition checking whether the customer holds the VIP role. On the Yes path, add a Slack message or email alert via the messaging integration with the order total, customer name and order link pulled in via merge tags. This workflow runs all year and costs you nothing extra to leave active.

For a broader look at automating your WooCommerce store ahead of the sale, the guide on automating your WooCommerce store for Black Friday covers the full stack beyond just the VIP flow.

An alert when a VIP converts is not a nice-to-have. It is the difference between a customer who feels recognised and one who wonders whether anyone noticed they showed up early.

What Does Each Part Require: Free or Pro?

Workflow component	Free or Pro?	Why it matters
Order Completed trigger	Free	Fires every time WooCommerce marks an order complete
Conditional branching (Yes/No paths)	Free	Filters customers against your VIP criteria
Change User Role action	Free	Promotes qualifying customers to your VIP role automatically
Create Coupon action (WooCommerce)	Free	Generates a unique code per customer at send time
Send Email action with merge tags	Free	Personalises each email with name, code and expiry date
Slack or messaging alert	Pro	Notifies your team the moment a VIP order lands
Schedule trigger (one-time, precise date/time)	Pro	Fires the early access email at exactly 6 AM on your chosen date
Visual email builder	Pro	Branded block-based email without writing HTML
Workflow simulator (dry-run testing)	Free	Test the full chain with zero side effects before going live

The free plugin handles the core of this campaign: identifying VIPs, generating coupons, and sending personalised emails. Pro adds the precision timing of the schedule trigger and the team notification.

If your store runs less than $10,000 a month in revenue, the free plugin alone may be enough. If you are managing a meaningful Black Friday campaign with a team, Pro starts at $69 a year for a single site, and the schedule trigger alone is worth that for a campaign of this size.

What Is the Setup Timeline Before Black Friday 2026?

Black Friday is November 27, 2026. Work backwards from that date and you have a clear build window. Compress this and you risk going live with an untested workflow on your biggest sales day of the year.

Date	Task	Why this date matters
By November 3	Define your VIP criteria and create the VIP Customer role in WordPress	Gives Workflow 1 three weeks to classify your existing customers before you send anything
By November 7	Build and activate Workflow 1 (role promotion)	Every order that completes from this date forward starts tagging VIPs automatically
By November 14	Build Workflow 2 (early access email and coupon) and Workflow 3 (team alert)	Leaves 10 days for testing before the scheduled send date
By November 17	Run the workflow simulator on all three workflows	Simulator runs a full dry run with zero side effects, so no real coupons are created and no emails are sent
By November 21	Send a real test to a small internal group (your own team accounts)	Confirms deliverability, merge tag rendering, and coupon creation under live conditions
November 24 at 6 AM	VIP early access email fires automatically	72 hours before the public sale opens on November 27
November 27	Black Friday public sale opens	VIP coupon codes expire at midnight. Team alert workflow continues through Cyber Monday (November 30)

On low-traffic sites, there is one honest caveat worth naming. Krom Automation uses Action Scheduler for background execution, which keeps everything off the page load. But Action Scheduler depends on WP-Cron to fire.

If your site goes hours without a visitor, WP-Cron can fire late. For a time-sensitive campaign like this, configure a real server cron job to call wp-cron.php on a regular interval.

Your host’s control panel usually provides this. It takes five minutes and removes the timing uncertainty entirely.

Testing with the Simulator Before the Sale Starts

The workflow simulator is the most important tool to use before Black Friday, and it is included free. It runs your entire workflow, including conditions, branching logic, merge tag resolution and action sequencing, without executing any real actions. No coupons are created.

No emails are sent. No roles are changed.

What to check in the simulator:

• Does the VIP condition branch correctly? Confirm a non-VIP user exits on the No path and a VIP user reaches the coupon and email actions.
• Do merge tags resolve to real values? First name, coupon code, and expiry date should all render, not appear as raw tag placeholders.
• Does the coupon action fire in the correct order before the email action that references the coupon code?
• Does the team alert fire only for VIP customers, not for every order?

After the simulator passes, send a real test using your own account as the recipient. This confirms your email reaches the inbox rather than spam. For more on that specific problem, the guide on why automated WordPress emails go to spam covers the most common causes and the fastest fixes.

Running the simulator is not optional on a sale this size. A workflow that creates coupons incorrectly at scale will give every VIP customer the wrong code, or the same code, and you will find out when the support tickets arrive at 7 AM on Black Friday.

The Part No One Talks About: What Happens When the Public Sale Goes Live?

Here is the gap none of the competitor guides address. You have given your VIPs early access to the same deals the public will see in 72 hours.

Some of those customers will notice. A small number will feel manipulated rather than rewarded, especially if they expected genuinely better pricing rather than just earlier access.

There are two honest ways to handle this:

• Make the VIP discount genuinely deeper. If the public sale is 20% off, VIPs get 25% or 30%, and their coupon reflects that. Early access plus a better rate is a real reward. Early access to the same rate is mostly convenience.
• Be transparent about what VIP means. State clearly in the early access email that the deals open to everyone on November 27, and that the exclusivity is the early window and the personal code, not a secret price. Customers who understand the structure do not feel deceived when the public sale starts.

This also affects stock. If your VIP segment is large and the early access window is 72 hours, popular products may sell out before the public sale opens. That is either a great outcome (the campaign worked) or a support problem (public customers are frustrated).

Inventory limits on WooCommerce coupons and product stock thresholds let you control how much of each SKU the early access window can consume. The guide on avoiding stock-outs on Black Friday covers how to set up low-stock alerts so you are not surprised mid-campaign.

How Much Does Krom Automation Cost Across Multiple Sites?

Plan	Sites	Annual cost	Lifetime cost	Cost per site (annual, 3-year view)
Basic	1	$69/year	$199	$69/year
Standard	5	$149/year	$399	$30/year per site
Enterprise	Unlimited	$299/year	$699	Under $10/year per site at 30+ sites

These are launch prices as of 2026. All plans include every Pro feature, all 25 integrations, and a 14-day money-back guarantee. The only difference between plans is the number of site activations.

For agencies running this campaign across 10 or more client stores, the Standard or Enterprise plan makes the per-site cost negligible. The full pricing breakdown has the current figures.

The free plugin is available now with no trial period and no feature paywalls. Download Krom Automation from the WordPress.org plugin directory to start building your VIP identification workflow today.

If you are looking at the broader picture of what automation costs across a client portfolio, the breakdown of what client automation costs per site puts those numbers in context alongside alternatives.

After Black Friday: Keeping the VIP Relationship Going

The VIP role you have built does not have to be a one-campaign asset. Leave Workflow 1 running and your segment self-updates throughout the year.

Customers who cross your spend threshold in January get the VIP role in January. By next November, your list is a year more accurate with zero maintenance.

The guide on turning Black Friday buyers into repeat customers covers what to do in the 30 days after the sale, including follow-up sequences and re-engagement triggers. The Cyber Monday follow-up email automation guide is the natural next step if you want to extend the campaign through November 30.

Also from wpRigel

Pollify is wpRigel’s Gutenberg native poll, survey and quiz plugin. It builds polls as real blocks inside the editor, so there are no shortcodes to paste and no separate interface to learn. If you want to ask customers how they heard about your VIP program or what they want to see on sale, Pollify is the tool that fits naturally into a post or page without any friction.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search orders by customer name or email, and run admin actions without clicking through menus.

During a high-volume Black Friday window, the ability to pull up any order in under two keystrokes is not a minor convenience. It is the only command palette with real WooCommerce order, product and customer commands built in.

Our Verdict: Who Should Set This Up and Who Should Wait?

Set this up now if: you have a WooCommerce store with at least 12 months of order history, a recognisable top tier of repeat buyers, and the capacity to run a slightly earlier sale for a defined group. The free plugin gets you 80% of the way there. Pro adds the schedule trigger and team notifications, which are worth it for any store where Black Friday is a meaningful revenue event.

Skip or simplify if: your customer base is too small to segment meaningfully, you have fewer than 50 completed orders in the last 12 months, or you have not decided what your VIP criteria actually are. Sending an “exclusive” early access email to your entire mailing list because you could not define the segment is worse than sending nothing. It trains customers to ignore your exclusivity framing permanently.

We would run Workflow 1 starting today, regardless of Black Friday plans. A live, self-maintaining VIP segment has value all year. The Black Friday campaign is just the first time you use it.

See what each plan costs and what it includes before the campaign window closes.

Frequently Asked Questions

How far in advance should VIP customers get early access before Black Friday?

48 to 72 hours is the most common window and the one we recommend. It is long enough to feel exclusive and for VIPs to actually shop, but short enough that you are not managing two separate sale periods simultaneously. 72 hours means your schedule trigger fires on November 24 for a November 27 public opening.

Does the free version of Krom Automation support automatic coupon creation?

Yes. The Create Coupon action for WooCommerce is included in the free plugin.

You can generate a unique coupon per customer, set the discount type, amount and expiry date, all without Pro. The schedule trigger that fires the workflow at a precise date and time requires Pro.

What if my site is low traffic and I am worried about WP-Cron timing?

Set up a real server cron job to call wp-cron.php every 5 minutes. Your host’s control panel usually provides a cron manager. This takes the timing control away from visitor-triggered WP-Cron and makes scheduled workflows fire at the time you set, not whenever the next visitor happens to arrive.

Can I use this workflow with a membership plugin like MemberPress or WooCommerce Subscriptions?

Yes. If your VIP definition is tied to an active membership or subscription, the MemberPress integration and WooCommerce Subscriptions integration both provide triggers you can use to assign the VIP role when someone joins or renews, rather than deriving VIP status from order spend.

Are the early access deals the same as the public Black Friday deals?

That is entirely your choice. Early access can mean the same discount applied earlier, or it can mean a deeper discount exclusive to VIPs.

The second option creates a more defensible VIP program because the reward is not just timing. If you go with the same discount, be transparent in the early access email that the deals open publicly on November 27, so customers feel informed rather than surprised.

Does Krom Automation log which VIP customers received the early access email and coupon?

Yes. Krom Automation writes a full per-step execution log for every workflow run, including which user triggered each execution, which actions completed, and any failures with retry status. You can review this in the execution history and export it from the reports page with date range filtering and CSV export.

You can automate Cyber Monday follow-up emails directly inside WordPress using Krom Automation. The free plugin handles the core sequence: tag buyers when an order completes on Black Friday (November 27, 2026), branch non-buyers into a Cyber Monday (November 30, 2026) sequence, and suppress anyone who already purchased. The Schedule trigger and visual email builder require Pro, which starts at $69 a year.

Most WordPress stores send a single Cyber Monday blast to their entire list. That means buyers get a discount email for something they already paid for, and browsers get a generic pitch with no acknowledgment of what they looked at.

Both are avoidable with a workflow that runs three decision checks before it sends anything. This guide walks through exactly that setup, with timing, a pre-sale checklist, and an honest note on where WordPress Cron can let you down.

If you are also thinking about what comes after the sale, the companion post on turning Black Friday buyers into repeat customers covers the longer retention sequence. And if abandoned carts are part of your BFCM concern, recovering abandoned carts in WooCommerce without a SaaS tool explains how to handle that without a separate platform.

Browse the full feature list to see everything the free and Pro versions include before you build.

Quick Summary

Goal	Trigger or feature needed	Free or Pro?
Tag buyer when BF order completes	Order Completed trigger	Free
Send immediate post-purchase email	Send Email action	Free
Delay Cyber Monday email 72 hours	Delay scheduling	Free
Branch buyers vs. non-buyers	Conditional branching	Free
Schedule a CM teaser the morning of Nov 30	Schedule trigger	Pro
Design branded email without code	Visual email builder	Pro
Suppress buyers from CM sequence	Run once per entity + conditions	Free
Dry-run test before sale starts	Workflow simulator	Free

What Does the Full Sequence Actually Look Like?

The goal is three separate workflows running in coordination, not a single automation trying to do everything. Keeping them separate means you can pause, edit, or test one without touching the others.

• Workflow 1: Black Friday buyer tagging. Trigger: Order Completed. Action: Update User Meta to write a “bf_buyer_2026” tag and send a thank-you email. This workflow does exactly one thing and runs once per customer.
• Workflow 2: Cyber Monday sequence for non-buyers. Trigger: a Pro Schedule trigger firing at 7 a.m. on November 30. Condition check: does the user have the “bf_buyer_2026” meta tag? Yes path exits immediately. No path sends the CM offer, waits 4 hours, checks for a completed order again, then sends a last-chance email to those still without a purchase.
• Workflow 3: Post-purchase retention (days 3 to 14). Trigger: Order Completed. Delay 72 hours. Send a product tips or cross-sell email. Delay another 7 days. Send a loyalty or review request email. This is the sequence competitors almost never document, and it is where one-time CM buyers become repeat customers.

The conditions and branching documentation explains how to set up the Yes and No paths that keep buyers off the non-buyer sequence. The delays and scheduling documentation covers the exact units available, including hours, days, and custom seconds.

Sending a Cyber Monday discount to someone who bought yesterday is not just wasted email. It is the fastest way to train your best customers to wait for a sale every time.

How Do I Suppress Buyers from the Cyber Monday Sequence?

This is the step most guides skip, and it is the one that matters most. There are two layers of protection in Krom Automation.

Layer one: the “run once per entity” setting. Enable this in workflow settings on your buyer-tagging workflow. It guarantees that a customer who places two Black Friday orders does not get tagged, emailed, or processed twice. One order, one pass through the workflow.

Layer two: conditional branching on the CM workflow. Before Workflow 2 sends anything, it checks whether the user has the “bf_buyer_2026” meta value. If the check returns true, the workflow exits the Yes path with no action.

If it returns false, the CM offer goes out. This two-layer approach means that even if a buyer somehow missed the tagging workflow, the condition check on the CM side catches them.

If you are sending to a Mailchimp or FluentCRM list rather than native WordPress users, the same logic applies through the relevant integration. The Mailchimp integration documentation and the FluentCRM integration documentation show how to add and check tags in each platform from within a Krom workflow.

How Many Follow-Up Emails Should I Send, and When?

Three to four emails across the Black Friday to Cyber Monday window is the upper limit before deliverability starts to suffer. More than that and unsubscribes accelerate, which costs more than the extra send is worth. Here is a sequence that fits within that ceiling.

• November 27, immediately after order: buyer thank-you email with order confirmation and a hint that Cyber Monday has something new. This goes only to confirmed purchasers.
• November 30, 7 a.m.: Cyber Monday launch email to non-buyers. One offer, one link, no padding.
• November 30, 6 p.m.: last-chance email to non-buyers who have still not converted. Subject line should state the deadline, not tease it.
• December 3: post-purchase follow-up to everyone who bought across both days. Product tips, a cross-sell, or a loyalty invite. No discount language.

The December 3 email is where almost all competitor content stops. A customer who bought on CM and never hears from you again until the next sale has no reason to pay full price in January. That four-email structure costs nothing to automate and takes less than an hour to build in Krom Automation.

The most valuable email in a Cyber Monday sequence is the one sent on December 3. Nobody else is sending it, which means it lands in an inbox that is finally quiet.

What Should I Send Non-Buyers After the Sale Ends?

This is the gap that every strategy guide ignores. The sale is over, the discount is gone, and you have a list of people who clicked but never bought.

A re-engagement email with no offer looks desperate. A new discount undercuts the urgency you just spent a week building.

The answer is to shift the frame. These people are interested but unconvinced. The follow-up should address the objection, not repeat the pitch.

• Day 1 after sale closes: a “what you missed” email that recaps the product, names real use cases, and links to reviews or testimonials. No discount.
• Day 5: a content email that solves a problem related to what they looked at. If they browsed a productivity plugin, send a guide on saving time in WordPress. Position the product as a tool, not a transaction.
• Day 10: a soft offer, either a smaller discount than the CM price or an invitation to join a free tier. This is the only email in the post-sale sequence that mentions price.

This three-email post-sale sequence runs as a separate Krom workflow with a trigger on a custom user meta flag set when someone clicks a CM email link without completing an order. That requires the HTTP Request action to check click data from your email platform, or an incoming webhook from a platform that fires on link clicks. The incoming webhook receiver documentation explains the setup, including HMAC-SHA256 signature verification.

Set It Up Timeline: Counting Back from Black Friday

Rushing automation setup the week of a sale is how workflows go live untested. The simulator exists so you do not have to. Work backward from November 27 using this timeline.

Date	Task	Why it matters
November 10	Install Krom Automation and connect WooCommerce	Gives 17 days to find any compatibility issues before traffic spikes
November 13	Build Workflow 1 (buyer tagging) and run the simulator	The simulator fires a dry run with zero side effects, so no test orders pollute your data
November 17	Build Workflow 2 (CM non-buyer sequence) and test branching	Conditional branching errors are the most common failure point; catch them in staging
November 20	Build Workflow 3 (post-purchase retention) and review merge tags	Merge tags pulling wrong field names cause broken personalisation in live emails
November 24	Full end-to-end simulator run on all three workflows	Three days before the sale is the last safe window to fix anything structural
November 26	Set all workflows to active, confirm email sending is live	Workflows set to paused the night before the sale do not run

The workflow simulator documentation walks through exactly how to run a dry test, including how to inject fake trigger data to test specific paths without placing a real order. Run it on every workflow individually, then run a sequence test where Workflow 1 outputs feed into Workflow 2.

What Are the Real Limits of This Setup?

Krom Automation runs background execution through Action Scheduler, which means no workflow logic fires during page loads. That is the right architecture for a sale day when your server is handling real traffic. But there is one constraint worth naming before you depend on it.

WP-Cron timing on low-traffic sites. WordPress Cron fires when someone visits the site. On a high-traffic sale day, this is not a problem. On a low-traffic staging environment, or on a site that sees very little overnight traffic, a delay set to fire at 6 p.m.

may not fire until someone visits at 7 p.m. or later.

If precise send timing matters, configure a real server cron to trigger wp-cron.php every 5 minutes. Your hosting panel or a plugin like WP Crontrol can set this up in under 10 minutes.

AI actions need your own API key. Krom Automation includes AI Generate Text and AI Content Moderation in the free version, with no markup on tokens. But you supply the API key and pay your provider directly at standard rates. There is no per-execution fee from wpRigel at any plan level.

Email deliverability is separate from automation. Krom Automation builds and schedules the emails. Whether they reach the inbox depends on your sending infrastructure: SPF, DKIM, DMARC, and your choice of SMTP provider.

A busy inbox on November 30 amplifies any existing deliverability weakness. The post on why automated WordPress emails go to spam covers the specific fixes.

Using Merge Tags for Personalisation Without the Risk

Every email in this sequence can pull live event data through merge tags. A merge tag like {{order.total}} or {{customer.first_name}} resolves at send time from the triggering event. That means a post-purchase email can name the exact product the customer bought without any manual segmentation.

The risk with merge tags in a high-volume sequence is a missing fallback. If the field is empty, the tag renders blank.

Always define a fallback value for every merge tag in a CM sequence: “there” instead of a blank first name, “your recent order” instead of a blank product name. The merge tags documentation shows where to set fallbacks in the field editor.

How Does Krom Automation Compare on Price for This Use Case?

The core buyer-suppression and delay sequence described in this article runs entirely on the free version of Krom Automation. There is no trial period, no run cap, and no paywall on the WooCommerce triggers or the conditional branching. The free plugin is available in the WordPress.org plugin directory.

The Schedule trigger, which fires the CM launch email at 7 a.m. on a specific date, and the visual email builder are Pro features. Pro plans start at $69 a year for a single site, or $199 as a lifetime payment.

Every Pro plan includes all 25 integrations, 101 additional workflow templates, and 80 or more additional triggers. There are no per-execution fees at any tier.

For context, Uncanny Automator’s automation plans start at $199 per year for one site as of September 2026. Zapier’s Professional plan runs around $240 per year for 750 tasks per month with overage charges on top.

Both use task-based or per-execution billing models that grow in cost as your sequence runs more frequently. Krom Automation does not.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey, and quiz plugin. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate interface to configure. It works well alongside a post-CM sequence for collecting buyer feedback or running a product preference survey.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search orders, switch order statuses, update product prices, or jump to any admin screen without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product, and customer commands, which makes it a practical tool during a high-volume sale day when speed in the admin matters.

FAQ

Does the free version of Krom Automation handle buyer suppression on its own?

Yes. The Order Completed trigger, Update User Meta action, and conditional branching are all free.

You can tag buyers and branch non-buyers into a separate path without a Pro licence. The Schedule trigger for sending the CM email at a specific time on November 30 requires Pro.

What happens if a customer buys during the Cyber Monday sequence, mid-sequence?

The condition check inside Workflow 2 runs before each email sends, not just at the start. If a customer converts after the first CM email, the next delay resolves, the condition re-checks the user meta, finds the buyer tag, and exits the Yes path. They do not receive the last-chance email.

Can I connect Krom Automation to an external email platform like Mailchimp or ActiveCampaign instead of sending emails directly?

Yes. The Pro plan includes Mailchimp and ActiveCampaign integrations as actions.

Instead of the Send Email action, you add the subscriber to a Mailchimp audience or trigger an ActiveCampaign automation via the ActiveCampaign integration. The tagging and branching logic stays in Krom, and the email delivery moves to your external platform.

How do I handle Cyber Monday follow-ups for a store that sells digital products through Easy Digital Downloads?

Krom Automation supports Easy Digital Downloads through a dedicated integration. The Easy Digital Downloads integration documentation covers the available triggers and actions. The buyer-tagging and suppression logic described in this article applies directly, with the EDD purchase trigger replacing the WooCommerce Order Completed trigger.

Does running three workflows simultaneously on Black Friday slow down the site?

No. Krom Automation executes every workflow through Action Scheduler in the background.

Nothing runs in the request cycle, so a spike in orders on Black Friday does not translate into a spike in page load time. The execution queue processes independently of front-end traffic.

What is the minimum setup I need to run before the sale to be safe?

Build each workflow, run the workflow simulator on each one individually, then run a connected test where a simulated Black Friday order feeds through Workflow 1 and the suppression check in Workflow 2. Confirm your SMTP sender is authenticated and that a test email lands in the inbox, not spam. That full process takes 2 to 3 hours and should finish by November 24 at the latest.

If you want a broader view of what else to automate before the sale, the guide on WordPress automations to set up before Black Friday covers stock alerts, order notifications, and coupon delivery in one place.

The free version of Krom Automation covers most of this sequence with no time limit and no run cap. Download it from the WordPress.org plugin directory, build the buyer-tagging and suppression workflows before November 10, and use the simulator to confirm every branch before traffic arrives. If you need the Schedule trigger or the visual email builder, see the Pro plan pricing to decide whether upgrading makes sense for your sale volume.

You can turn Black Friday customers into repeat customers by running five timed workflows: a first-purchase welcome, a 48-hour thank-you, a day-10 review request, a review reward coupon, and a January win-back. Krom Automation’s free plan covers the core email actions and WooCommerce Order Completed trigger, so the first three workflows cost nothing beyond the plugin. The review reward coupon and win-back sequence benefit from Pro’s visual email builder and schedule trigger, but the free version gives you a working retention stack on day one.

The bigger problem most guides ignore: a significant portion of Black Friday buyers bought a gift for someone else. That buyer may never need your product again.

The real repeat-purchase opportunity is the gift recipient, and they are sitting completely outside your list right now. We will cover that too.

Black Friday this year is November 27, 2026, with Cyber Monday on November 30. Build and test these workflows before November 20 so you are not debugging automations while orders are flowing. See what Krom Automation can do before we walk through each workflow.

Are Black Friday Buyers Even Worth the Effort?

The honest answer is: most of them are deal-hunters, and a minority will buy again at full price. That minority is large enough to be worth targeting systematically, and the cost of running automated workflows is low enough that a 10 to 15 percent second-purchase conversion rate is profitable even on a thin margin product.

The mistake is treating every Black Friday buyer the same. A customer who bought one discounted item and never opened a single post-purchase email is a different prospect from one who clicked your thank-you, left a review, and visited your site again in December. Segment by behaviour, not just by purchase date, and your retention rate will look very different by February.

The question is not whether Black Friday buyers will ever pay full price. The question is whether you did anything worth paying for after they checked out.

For the operational side of preparing your store before the sale starts, the guide on preparing your WooCommerce store for Black Friday covers inventory, pricing rules, and the automations to have in place before traffic spikes.

The Five Workflows, in Order of Impact

Work through these in order. The welcome email fires first and sets the tone for everything that follows. Skipping to the win-back without a working welcome sequence wastes time, because customers who never felt acknowledged after purchase are the hardest to re-engage in January.

1. First-purchase welcome, fires immediately on Order Completed
2. Timed thank-you, fires 48 hours after order
3. Review request, fires 10 days after order (delivery window)
4. Review reward coupon, fires when a review is submitted
5. January win-back, fires on a fixed schedule in early January

Each of these is a separate workflow in Krom Automation, not a single multi-step sequence. Keeping them separate means a failure in one does not block the others, and you can pause or edit any step without touching the rest.

Workflow 1: First-Purchase Welcome (Fires Immediately)

Trigger: WooCommerce Order Completed. Action: Send Email, using merge tags to pull in the customer’s first name and order total. This fires the moment WooCommerce marks an order complete, with no delay.

The welcome email is not the place for another offer. It is the place to confirm the customer made a good decision, remind them who you are beyond a transaction, and tell them what happens next. Keep it to three short paragraphs and one clear link, ideally to something useful like a getting-started guide or a care page for the product they bought.

The first workflow documentation walks through the exact steps for building a welcome email in Krom Automation, including how to use merge tags for personalisation. The merge tags reference covers every dynamic variable available from WooCommerce order data.

Free or Pro: Free. The Order Completed trigger and Send Email action are both in the free plugin.

Workflow 2: The 48-Hour Thank-You (With a Soft Offer)

Trigger: WooCommerce Order Completed. Delay: 48 hours. Action: Send Email with a single related product recommendation or a loyalty programme invitation.

Forty-eight hours is long enough that the package is probably still in transit, which means the customer is in a positive anticipation state. It is short enough that your brand is still top of mind. This is the right window for a soft second offer: not a discount, but a reason to look around the site again.

If you send another percentage-off code here, you are training the customer to expect discounts every time. Instead, offer something with perceived value that does not cut margin: free shipping on their next order over a threshold, early access to a new product, or an invitation to a private customer group. Delay scheduling in Krom Automation supports minutes, hours, days, and weeks, so a 48-hour delay is a single field change.

Free or Pro: Free. Delay scheduling is included in the free plugin.

Send another discount at 48 hours and you are not retaining a customer. You are renting one until your next sale.

Workflow 3: Review Request at Day 10 (Match Your Delivery Window)

Trigger: WooCommerce Order Completed. Delay: 10 days. Action: Send Email with a direct link to leave a review.

Ten days covers most domestic shipping windows and gives the customer time to actually use what they bought before you ask them to judge it. Adjust this to 14 days if you ship internationally, or 7 days for digital products. The delay is a single field in the workflow settings.

Review requests sent before the product arrives get ignored or, worse, get a frustrated one-star response about delivery speed. Reviews submitted after 10 days of use are more detailed and more credible to future buyers. A single authentic review from a Black Friday buyer is worth more for long-term conversion than the discount you gave them.

If your site runs WooCommerce Subscriptions, subscription customers have different post-purchase behaviour and timing. The WooCommerce Subscriptions integration documentation covers the triggers specific to subscription lifecycle events.

Free or Pro: Free.

Workflow 4: Review Reward Coupon (Closes the Loop)

This workflow is the one most stores skip, and it is the one that generates the second purchase. The mechanic is straightforward: a customer leaves a review, they immediately receive a thank-you email containing a single-use coupon for their next order.

In Krom Automation, the trigger is a Comment Submitted or Comment Approved event on your product pages, with a conditional branch checking that the comment is a WooCommerce product review. The action is Create Coupon followed by Send Email. Conditional branching documentation explains how to add Yes/No logic so the coupon only fires on genuine reviews, not on every comment.

The coupon amount matters. A 10 percent discount on a full-price item restores some of the Black Friday margin gap.

A free shipping coupon costs less and converts almost as well for physical goods. Do not make the coupon time-limited to less than 30 days. A customer who leaves a review in December and gets a coupon that expires January 5 will feel manipulated when they try to use it in January and it is gone.

Free or Pro: Free for the core workflow. Pro’s visual email builder lets you design a coupon delivery email that matches your brand, with the coupon code styled as a proper block rather than plain text.

Workflow 5: The January Win-Back (For Everyone Who Did Not Come Back)

Trigger: Schedule trigger, set to January 8, 2027. Audience filter: customers who placed an order in November but have not placed another order since. Action: Send Email with a January-specific offer.

January is the right time for a win-back because it carries its own natural urgency: new year, fresh intentions, and a cultural moment where people are open to spending again after the post-Christmas quiet. A “New Year” framing on the email does not feel like a desperate re-engagement; it feels timely.

The schedule trigger is a Pro feature. The schedule trigger documentation covers how to set a one-time date, a recurring interval, or a monthly cadence. For the win-back, a one-time date pointing to January 8 is the right choice: early enough to catch January spending intent, late enough that the Christmas returns window has closed.

For stores already using an email marketing platform, connecting Krom Automation to your list is documented for Mailchimp, ActiveCampaign, and FluentCRM, so you can tag Black Friday buyers and trigger platform-side sequences from WordPress events without duplicating your email setup.

Free or Pro: Pro for the schedule trigger. The Send Email action in the free plugin can cover a manual batch if you are not ready to upgrade yet, but the automated January send requires Pro.

The Gift-Buyer Problem (No One Else Talks About This)

Every retention guide assumes the buyer is also the user. A large portion of Black Friday volume is gift purchases. The person who bought a product in November may have zero personal need for it, because they bought it for their partner, parent, or colleague.

That buyer is not a bad retention prospect because they are disloyal. They are a bad prospect because the product was never for them.

The repeat-purchase opportunity is sitting with the gift recipient, who is entirely outside your database. Here is a practical approach to capturing them:

• Include a gift registration card or URL in the packaging, inviting the recipient to register their product, get a warranty extension, or access setup resources. This is the lowest-friction way to get recipient data.
• Add a post-purchase option at checkout for the buyer to enter the recipient’s email so they can receive setup instructions directly. Frame it as a service, not a marketing opt-in.
• Build a Krom Automation workflow triggered by a custom form submission on your gift registration page, using an HTTP Request action or a form integration to capture the recipient as a new contact in your CRM or email platform.

The third option connects directly to Krom Automation’s form integrations. If your gift registration form runs on Gravity Forms, the Gravity Forms integration fires a trigger the moment a recipient submits their details. If you use WPForms, the same is available through the WPForms integration.

None of your Black Friday competitors are building this workflow. That is exactly why it is worth building.

Set It Up By: A Pre-Sale Timeline

Date	Task	Why it matters
November 10	Build all five workflows in draft	Leaves two weeks for testing, not one day
November 13	Run the simulator on every workflow	Catches logic errors with zero side effects
November 15	Send test emails to your own inbox	Confirms merge tags resolve and emails land, not spam
November 17	Activate workflows in production	WooCommerce test orders fire real triggers
November 20	Check execution logs after test orders	Confirms background processing is working on your host
November 27	Black Friday: monitor analytics dashboard	Failed execution count visible in real time
November 30	Cyber Monday: workflows already running	Nothing to configure, only orders to process

The simulator in Krom Automation is a dry run with zero side effects: no emails sent, no coupons created, no database writes. It shows exactly which branch a workflow would take given the test data you supply.

Workflow simulator documentation explains how to configure a test scenario and read the output. Run it on every workflow before November 17, not on November 26.

What This Stack Costs, Compared to the Alternatives

Approach	Year 1 cost	Year 2 cost	Run limits	Data location
Krom Automation free	$0	$0	None	Your server
Krom Automation Pro (1 site)	$69/year	$69/year	None	Your server
Krom Automation Pro (lifetime)	$199 once	$0	None	Your server
Uncanny Automator (1 site, as of September 2026)	$199/year	$199/year	None listed	Your server
Zapier Professional (as of September 2026)	~$240/year	~$240/year	750 tasks/month	Zapier’s servers

Zapier’s task-based billing is the hidden cost that most comparisons understate. Five workflows firing across 500 orders on Black Friday is 2,500 task executions in a single weekend. At 750 tasks a month on the Professional plan, you would hit your limit before Cyber Monday.

Krom Automation has no per-task billing at any tier. Our full Zapier pricing breakdown covers what WordPress sites actually pay across a year.

Per-task billing and a Black Friday spike are a combination that turns a $20 monthly plan into a $200 invoice with no warning.

One Honest Limitation: WP-Cron on Low-Traffic Sites

Krom Automation runs delayed actions through Action Scheduler, which depends on WP-Cron. On a site that receives consistent traffic, WP-Cron fires reliably and delays execute within a few minutes of their scheduled time. On a site that goes hours between visits, the 48-hour thank-you email might fire at 49 or 51 hours instead.

For Black Friday, when traffic is high, this is not a practical concern. For the January win-back on a site that quiets down after December, configure a real server cron job to call wp-cron.php on a fixed interval.

Most managed WordPress hosts let you do this in the control panel. It takes about five minutes and removes the dependency entirely.

If you are running into silent failure issues more broadly, the guide on when an automation fails silently on WordPress covers the diagnostic steps for execution log errors, cron issues, and action scheduler backlogs.

Also from wpRigel

Pollify is our Gutenberg-native poll and survey plugin. If you want to understand why Black Friday buyers did or did not return, a short post-purchase survey built directly inside the block editor is the fastest way to get real answers, without shortcodes or a separate interface to manage.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search orders, manage products, update customers, and run admin actions without navigating menus. It is the only command palette with genuine WooCommerce order, product and customer commands built in, which makes it genuinely useful during the Black Friday rush when speed inside the admin matters.

Our Verdict

If your store ran Black Friday without a post-purchase automation in place, you left a measurable number of second purchases on the table. The five workflows above are not sophisticated: they are consistent, timed, and automatic. That is what makes them work when your team is stretched and you are not thinking about a customer who bought 10 days ago.

Start with the free plugin and build the welcome, thank-you, and review request. Those three workflows require nothing beyond the free download.

Add the schedule trigger for the January win-back when you upgrade to Pro. Build the gift-buyer capture workflow if even 20 percent of your Black Friday volume is gift purchases, because that segment has no other path back to your store.

Download Krom Automation free from the WordPress.org plugin directory, or see full pricing for the Pro plans if the schedule trigger and visual email builder are what you need to complete the stack.

Frequently Asked Questions

Does the free version of Krom Automation work for Black Friday retention workflows?

Yes. The WooCommerce Order Completed trigger, Send Email action, delay scheduling, and conditional branching are all in the free plugin. The first three workflows in this article, the welcome, thank-you, and review request, run entirely on the free version.

The review reward coupon also works free using Create Coupon and Send Email. The January win-back requires the Pro schedule trigger.

Should I offer a discount in my post-purchase emails to bring buyers back?

Not immediately. A discount in the 48-hour thank-you trains customers to expect one every time.

Use the 48-hour window for a value-add: free shipping on a future order, early access, or a useful resource. Save the percentage-off coupon for customers who leave a review, where it functions as a reward rather than a bribe.

How do I handle customers who bought as a gift and will never buy again?

Build a gift registration workflow. Add a gift registration URL to your packaging or your order confirmation email.

When the recipient submits their details via a form, a Krom Automation workflow captures them as a new contact in your CRM or email platform. That recipient is a fresh prospect with no prior discount expectations.

What happens if a workflow fails during Black Friday?

Krom Automation logs every execution step. If an action fails, it retries automatically with configurable backoff and sends a failure notification to your admin email. The analytics dashboard shows failed execution count in real time, so you can see a problem as it develops rather than discovering it a week later.

How many sites does one Krom Automation Pro licence cover?

The Basic plan covers 1 site. Standard covers 5 sites.

Enterprise covers unlimited sites. If you manage client WooCommerce stores, the Standard plan at $149 per year covers five stores, which works out to under $30 per site annually with no per-task billing on any of them.

Is the January win-back email worth the effort if Black Friday buyers are mostly deal-hunters?

Yes, because it costs almost nothing to run. A single scheduled workflow firing once in January, targeting customers who have not reordered, requires no ongoing maintenance. Even a 5 percent re-engagement rate on a list of 500 Black Friday buyers is 25 orders from people who already know your brand and trusted you enough to check out once before.

Yes, you can recover abandoned carts in WooCommerce without a SaaS tool. Krom Automation is one concrete way to do it: the free plugin gives you two WooCommerce triggers (Order Created and Order Completed), 21 built-in actions including Send Email, and timed delay scheduling, so you can build a pending-order follow-up sequence that runs entirely on your own server. No monthly SaaS fee, no customer data sent to a third-party platform.

The free version handles this workflow. Pro adds a visual email builder and a Schedule trigger for more complex sequences.

There is an important honesty note before we go further. Krom Automation’s free WooCommerce triggers fire on Order Created and Order Completed. That covers pending and failed orders well.

True “abandoned cart” recovery (catching visitors who add items but never reach the order stage) requires capturing a guest email before checkout completes, which WooCommerce does not do natively. We will cover what is genuinely possible, what requires additional tooling, and how to build the most useful recovery sequence with what Krom provides today.

If you are setting this up for Black Friday on November 27, 2026, you have a firm deadline. Keep reading for a setup timeline that works backward from the sale.

Browse the full Krom Automation feature list to see every trigger and action available before you build.

What WooCommerce Tracks Out of the Box (and What It Does Not)

WooCommerce does not track abandoned carts natively. It has no built-in mechanism to detect that a logged-in user added items to a cart and left without checking out. Cart contents for logged-in users are saved to the session, but there is no scheduler, no email hook, and no recovery flow attached to that data.

What WooCommerce does create is an order record the moment a customer submits the checkout form. That order starts in a Pending Payment status, then moves to Processing or Completed once payment clears.

Orders that stay in Pending for 24 hours almost always mean a real intent that broke down: a failed card, a payment gateway timeout, or a customer who got distracted at the payment step. These are recoverable, and they are what Krom Automation can act on today.

The distinction matters for honest expectation-setting:

• Pending/failed orders (checkout started, payment not completed): Krom Automation handles this free.
• True cart abandonment (items added, checkout never started, no email captured): requires a dedicated cart-capture plugin to store the email before checkout. Krom can then act on that data, but the capture step is outside its current scope.
• Guest recovery: impossible without an email address. WooCommerce does not capture guest emails until the checkout form is submitted.

A pending order that sits for 24 hours is not a lost sale. It is a recoverable one, and you do not need a SaaS subscription to act on it.

How to Build a Pending Order Recovery Sequence in Krom Automation

The core workflow uses the Order Created trigger, a conditional branch checking order status, and a timed delay before sending a follow-up email. Here is the sequence in plain language:

1. Trigger: Order Created fires when any new WooCommerce order is recorded.
2. Condition: Check whether order status equals “Pending Payment”. If No, exit the workflow. If Yes, continue.
3. Delay: Wait 1 hour (or 24 hours, depending on your preference).
4. Condition: Check order status again. If it has moved to Processing or Completed, the customer paid and no email is needed. If it is still Pending, send the recovery email.
5. Action: Send Email using the customer’s email address, pulled in via merge tags.

Merge tags let you inject the customer name, order number, and order total directly into the email body. The merge tags documentation covers every available variable.

The delay step uses Krom’s built-in delay scheduling, which supports minutes, hours, days, and weeks. For a recovery workflow, 1 to 24 hours is the practical range.

You can also add a second follow-up at 48 hours. Use Krom’s run-once-per-entity setting to make sure a customer who pays between the two emails does not receive the second one. That setting enforces a single execution per order ID, which prevents duplicate sends.

What About the Email Itself?

This is the section every other guide omits. Sending recovery emails through wp_mail() without a configured SMTP relay means your emails route through your hosting server’s default mail setup. On shared hosting, that almost always means the email lands in spam or gets silently dropped before it reaches the inbox.

The full breakdown of why this happens and how to fix it is in our guide on why automated WordPress emails go to spam. The short version: you need SPF and DKIM records pointing to a sending domain, and you need an SMTP plugin routing wp_mail() through a service that has a sender reputation. Options include Postmark, SendGrid, Mailgun, or Amazon SES.

None of these are SaaS cart tools. They are transactional mail relays, and the cheapest tiers cost less than $1 per month at typical recovery email volumes.

If you want to keep email entirely self-hosted, that is a valid choice. It requires more infrastructure work: a dedicated mail server, proper PTR records, and regular bounce management. For most agency-built WooCommerce stores, a transactional SMTP relay is the right balance between control and deliverability.

Krom Automation Pro includes a visual email builder that lets you design recovery emails using a block-based interface powered by the Gutenberg editor. That replaces the plain-text Send Email action with a properly structured HTML email, which improves both readability and deliverability.

Self-Hosted vs SaaS Cart Tools: What You Actually Pay

The honest comparison is not just sticker price. SaaS cart recovery tools charge per month regardless of whether you recover a single order. Self-hosted tools have a one-time or annual cost, but they carry infrastructure and setup time that SaaS tools absorb for you.

Factor	Krom Automation (self-hosted)	Typical SaaS cart tool
Year 1 cost	$0 (free) or from $69/year Pro	$300 to $600+/year
Year 2+ cost	Same annual fee, no increase	Same or higher as usage scales
Per-email or per-recovery fee	None	Often yes, at scale
Customer data location	Your own database	Vendor’s cloud
SMTP setup required	Yes, for deliverability	No, vendor handles it
Email design	Free: plain text. Pro: visual builder	Usually included
Setup time (first workflow)	30 to 60 minutes	15 to 30 minutes
Works across N client sites	Yes, with the right licence	Usually per-store pricing

For a single store, the break-even point is roughly 2 to 3 months of a mid-tier SaaS subscription. For an agency running 10 or more client stores, the Krom Automation Enterprise plan at $449/year (regular price, or currently $299/year at launch pricing) covers unlimited sites.

The equivalent SaaS cost across 10 stores could easily reach $3,000 to $6,000/year. The full pricing breakdown shows all plan options including lifetime purchases.

An agency paying per-store SaaS fees across 10 client sites is often spending more on cart recovery software than on hosting.

Conditions and Delays: The Logic That Makes Recovery Work

A recovery email sent to someone who already paid is worse than no email. It erodes trust and generates support tickets. The conditional branching in Krom Automation solves this: you check the order status a second time before sending, and only fire the email if the order is still pending.

The conditions and branching documentation covers how to build Yes/No logic into any workflow. For recovery specifically, the relevant condition is order status at the time the delay expires, not at the time the trigger fired. Those can be different if the customer pays in the interim.

Delays in Krom Automation run through Action Scheduler, the same background processing library WooCommerce itself uses. That means delays are decoupled from page loads and will fire reliably on any site with reasonable traffic. On very low-traffic sites where nothing visits for several hours, WordPress Cron fires late unless you configure a real server cron job.

If your recovery workflow needs to fire within 1 hour of order creation, confirm that your cron is running on a real schedule. The delays and scheduling documentation explains how to verify this.

Can I Connect a Third-Party Email Marketing Tool Instead?

Yes. If you already use Mailchimp, ActiveCampaign, FluentCRM, or MailerLite, Krom Automation can add the customer to a specific list or tag them when an order is created in pending status. Your email platform then handles the recovery sequence using its own automation tools.

The relevant integrations are documented here:

• Mailchimp integration: subscribe, tag, and sync WordPress users automatically
• ActiveCampaign integration: contacts, tags, and lists
• FluentCRM integration: contacts, tags, and lists (self-hosted CRM, no SaaS required)
• MailerLite integration: subscribe, unsubscribe, and manage groups

FluentCRM is worth calling out specifically if you want to stay fully self-hosted. It is a WordPress-native CRM that stores all contact data in your own database. Combining Krom Automation as the trigger layer with FluentCRM as the email sequence layer gives you a complete self-hosted stack with no SaaS dependency at either end.

Setting Up Before Black Friday: A Realistic Timeline

Black Friday 2026 falls on November 27. Cyber Monday is November 30.

These are not dates to be experimenting with a new workflow for the first time. Here is a working backward schedule:

Date	Task	Why it matters
By November 7	Install Krom Automation and configure SMTP	3 weeks to catch deliverability issues before the sale
By November 10	Build the pending order recovery workflow	Leaves 2 weeks for testing, not 2 hours
By November 14	Run the workflow simulator	Dry run with zero side effects confirms logic before a live order fires it
By November 17	Place a real test order and let it stay pending	Confirms the delay fires, the email arrives, and the status check works
By November 21	Review execution logs and fix any failures	6 days before the sale, enough time to iterate
November 27	Black Friday goes live	Workflow runs without intervention

The workflow simulator is the step most people skip. It runs a complete dry-run of the workflow with real trigger data but no actual emails sent and no orders touched. Use it to confirm that your conditional branches behave correctly before the sale traffic arrives.

For more on what to prepare before the sale, see our full guide on preparing your WooCommerce store for Black Friday and the broader list of WordPress automations to set up before Black Friday.

What Else Can Go Wrong (And How to Catch It Early)

Recovery workflows have three real failure modes. Knowing them before you go live saves a panicked support session during the sale.

• Email lands in spam. The fix is an SMTP relay with proper SPF and DKIM. This is not optional if recovery matters to you. See the full guide linked earlier.
• The second status check fires too early. If your delay is set to 1 hour but the payment gateway takes 90 minutes to process a bank transfer, the order will still be pending when the check runs. Adjust the delay to 4 to 6 hours for payment methods with slow confirmation.
• The workflow fires on every order, not just pending ones. The first condition branch is what prevents this. If that branch is missing or misconfigured, customers who completed payment receive a recovery email. Use the simulator to verify the No path exits cleanly.

Krom Automation logs every execution with a per-step audit trail. If something goes wrong during the sale, the execution history shows exactly which step failed and why.

That is the difference between debugging in 5 minutes and debugging blind. Our post on when an automation fails silently on WordPress covers the broader pattern of silent failures and how to catch them.

For failed payments specifically, the companion guide on recovering failed payments during Black Friday covers the Order Status Changed trigger, which fires when an order moves from Pending to Failed. That is a different workflow from the pending order sequence, and both are worth running simultaneously during a high-volume sale.

Running the simulator is not optional before a sale. It is the only way to know whether your conditional logic is correct without sending a recovery email to someone who already paid.

Free vs Pro: Which Do You Actually Need?

The free plugin handles the core pending order recovery workflow without restriction. No trial period, no run cap, no feature locked behind a paywall. Here is what each tier gives you for this specific use case:

• Free: Order Created and Order Completed triggers, Send Email action, conditional branching, delay scheduling, merge tags, execution logs, workflow simulator, run-once enforcement.
• Pro: Visual email builder for HTML recovery emails, Schedule trigger for time-based re-engagement, 25 integrations including Mailchimp and ActiveCampaign for routing pending orders into external sequences, incoming webhook receiver if your payment gateway sends status events via webhook.

If you are sending a plain-text follow-up from a single store, start with the free plugin. If you are building a multi-step HTML sequence across multiple client stores, Pro pays for itself quickly.

The free vs Pro comparison lists every feature difference in a single table. Pro plans start at $69/year for one site and $199 for a lifetime licence on one site, with multi-site options available.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built directly inside the block editor as real blocks, with no shortcodes to paste and no separate interface to learn. It is useful for collecting feedback during or after a sale.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search orders, products and customers, and run admin actions without clicking through menus. It is the only command palette with real WooCommerce order, product and customer commands, which makes it genuinely useful during a high-volume sale day when you need to find an order in 3 seconds instead of 30.

Our Verdict

If your question is “can I recover abandoned carts in WooCommerce without a SaaS tool,” the honest answer is: partially yes, and fully yes for pending order recovery. Krom Automation’s free plugin gives you everything needed to catch orders that stall at payment, run the sequence on a delay, check status before sending, and log every execution. That covers the majority of recoverable revenue for most WooCommerce stores.

True cart abandonment recovery (visitors who never submit the checkout form) requires a dedicated cart-capture plugin to grab the email address first. Krom can then act on that data, but it cannot capture what WooCommerce never records. Be skeptical of any self-hosted tool that claims otherwise without explaining how guest email capture works.

Set up the SMTP relay before you build the workflow. Everything else is configuration.

Download the free plugin from the WordPress.org plugin directory and build the pending order workflow today. If you need Pro for the visual email builder or multi-site coverage, see the current pricing and plans before Black Friday.

Frequently Asked Questions

Does Krom Automation capture guest emails before checkout is submitted?

No. Krom Automation’s WooCommerce triggers fire on order events, which means an order record must exist before the trigger activates.

If a guest adds items to the cart and leaves without submitting the checkout form, there is no email address to act on. A separate cart-capture plugin is needed for that step.

Will the recovery email send if the customer pays between the delay and the check?

Not if your workflow includes a second status check after the delay. That condition checks the current order status at the moment the delay expires.

If the order has moved to Processing or Completed, the No branch exits without sending. This is why the second status check is essential, not optional.

Does WP-Cron affect when the recovery email fires?

Yes, on very low-traffic sites. WordPress Cron is triggered by page visits, so on a site with hours between visits, a 1-hour delay might fire 2 or 3 hours late.

The fix is to disable WP-Cron in wp-config.php and set up a real server cron that runs every minute. Action Scheduler then runs on schedule regardless of traffic.

Can I use Krom Automation to recover abandoned carts across multiple client sites without paying per site?

Yes. The Krom Automation Pro Enterprise plan covers unlimited sites.

You can export a workflow as JSON from one site and import it on another, adapting merge tags and email copy as needed. The workflow import and export documentation covers the exact steps.

What is the difference between a pending order recovery workflow and a failed order recovery workflow?

Pending order recovery targets orders where payment was never attempted or is awaiting confirmation. Failed order recovery targets orders where payment was attempted and declined.

The triggers are different: Order Created (with a Pending status check) for the first case, and the Order Status Changed trigger (from any status to Failed) for the second. Running both simultaneously during a high-volume sale catches more recoverable revenue than either alone.

Is there a risk of sending duplicate recovery emails to the same customer?

Krom Automation’s run-once-per-entity setting prevents a workflow from firing more than once for the same order ID. Enable this in the workflow settings to ensure a customer with one pending order receives at most one recovery sequence, even if the trigger fires multiple times.

To recover failed payments in WooCommerce, set up an automated recovery sequence triggered by a failed order status. Krom Automation handles this with its free Order Created trigger and Send Email action, no Pro plan required for a basic email sequence.

Add a delay, a conditional branch checking order status, and a direct payment link, and customers can complete their purchase without contacting support. For SMS recovery or advanced branching on subscription failures, you need Krom Automation Pro.

Black Friday 2026 falls on November 27, Cyber Monday on November 30. Card networks process roughly 3 to 5 times their normal transaction volume across those four days. That volume spike is the reason your gateway’s soft decline rate climbs, not a problem with your store.

The customer’s card is often fine. The network is simply overwhelmed, or the bank flags an unusual spend pattern and declines as a precaution.

The sites that recover the most revenue are not the ones with the lowest failure rate. They are the ones with a workflow running the moment a payment fails. This guide builds that workflow, stress-tests it before the sale starts, and tells you what not to do.

See what Krom Automation can automate on your WooCommerce store

Why Payment Failures Spike on Black Friday

Card declines come in two types and the distinction changes your recovery strategy. A hard decline means the card is genuinely blocked: stolen, expired, over limit, or fraud-flagged. Retrying immediately does nothing.

A soft decline means the bank rejected the transaction temporarily, usually because of velocity checks, network congestion, or a mismatched billing address. Soft declines resolve on their own 35 to 60 percent of the time when the customer simply tries again within a few hours.

On Black Friday, soft declines dominate. Banks run aggressive fraud scoring on large or unusual purchases, and a customer buying five items in a single cart hits thresholds that would not fire on a quiet Tuesday. The correct response is a calm email with a payment link sent within 30 to 60 minutes, not a blunt “your payment failed” notification with no next step.

There is also a category most recovery content ignores: one-time order failures. Nearly every plugin and guide covering WooCommerce payment recovery focuses on subscription renewals. But on Black Friday, the majority of your failed payments are single-checkout orders from first-time customers who hit a soft decline and closed the tab.

That customer is still warm. They had their card out. A well-timed email with a link back to checkout recovers a meaningful slice of that revenue, and no dedicated tooling exists in the market to automate exactly that flow.

The customer whose card soft-declined on Black Friday is not a lost sale. They are a warm lead who still has their wallet open. The only question is whether you reach them before they forget.

What Triggers a Recovery Workflow in WooCommerce

Krom Automation ships two WooCommerce triggers in the free version: Order Created and Order Completed. When an order fails at checkout, WooCommerce creates it with a status of failed. That creation event fires the Order Created trigger, giving you the hook you need.

The recovery workflow logic is:

• Trigger: Order Created (WooCommerce)
• Condition branch: check that order status equals “failed”
• Delay: 45 minutes (long enough for the customer to retry manually, short enough to catch them while the purchase is still on their mind)
• Action: Send Email to the customer’s billing address with a direct payment retry link
• Stop condition: if order status has changed to “processing” or “completed” before the email fires, do not send

The stop condition is the part most guides omit. Without it, customers who retried and paid successfully still receive a “your payment failed” email an hour later.

That email damages trust and generates support tickets. Conditional branching in Krom Automation handles this with a Yes/No path before the Send Email action, checking live order status at the moment the delay expires.

How to Build the Recovery Sequence, Step by Step

The steps below use the free version of Krom Automation. Install the plugin from the WordPress.org plugin directory and activate it before working through these steps.

Step 1: Create a new workflow

Go to Krom Automation Workflows Add New in your WordPress admin. Name it “Black Friday Failed Payment Recovery” and give it a note in the workflow notes field so anyone else on the team knows what it does and when to pause it. Open the visual workflow builder and set your first node.

Step 2: Set the trigger

Select Order Created from the WooCommerce trigger group. This fires every time WooCommerce creates an order, regardless of status. The next step filters it down to failures only.

Step 3: Add a condition branch

Add a condition node and set: Order Status equals Failed. The Yes path continues to the delay and email.

The No path exits immediately with no action. This keeps the workflow clean and prevents it from sending emails on successful orders.

Step 4: Add a delay

Insert a delay node set to 45 minutes. Krom Automation runs delays via Action Scheduler, which means the delay executes in the background without blocking page loads. Read the delays and scheduling documentation if you want to test different timing windows or adjust the cadence after Black Friday data comes in.

Step 5: Add a second condition check

Before the email fires, add another condition node: Order Status equals Failed. If the customer paid in the last 45 minutes, this check returns false and the email does not send.

This is the stop condition. It is not optional.

Step 6: Write the recovery email

Use the Send Email action. The subject line matters more than the body. “Your order is waiting” outperforms “Payment failed” in both open rate and recovery rate because it frames the situation as an incomplete task rather than a rejection.

Use merge tags to pull in the customer’s first name, the order total, and the order number. Include a direct link to the WooCommerce order pay page, which you can construct with the order ID merge tag appended to your checkout URL.

Step 7: Add a second email at 24 hours (optional)

A second touchpoint at 24 hours recovers customers who saw the first email, intended to retry, and forgot. Apply the same stop condition check before this action fires.

Do not send a third email. Three emails about a single failed payment is the threshold where customers unsubscribe or mark as spam.

Two recovery emails with a stop condition beats four emails with no stop condition. The difference is not open rate. It is whether customers trust your store enough to buy again next year.

Should You Add SMS Recovery?

SMS recovery adds a meaningful lift for high-value orders because open rates on SMS run around 90 percent versus 20 to 40 percent for email. The Twilio integration in Krom Automation Pro lets you send an SMS action in the same workflow, after the first email delay but before the 24-hour email.

The message should be short: the customer’s name, the order total, and the payment link. Nothing more.

SMS recovery requires Krom Automation Pro and a Twilio account. Twilio charges per message sent, so factor that into your cost calculation for orders below a certain threshold.

For orders above $100, the ROI is straightforward. For orders below $30, the SMS cost may exceed the margin recovered.

One important constraint: collect explicit SMS marketing consent before sending transactional-style recovery messages. TCPA in the US and similar regulations elsewhere require it. Do not assume a billing phone number is a consent to receive marketing texts.

What Not to Do

These are the mistakes that turn a recovery sequence into a customer complaint:

• No stop condition. Every successfully paying customer receives a “your payment failed” email. This happens more often than you would expect, because the delay window overlaps with manual retries.
• Emailing too quickly. Sending within 5 minutes of failure catches customers still on your site and adds confusion. The 45-minute window lets them self-resolve first.
• More than 2 recovery emails. A third email has a high probability of triggering a spam report, which affects deliverability for every email your store sends, including order confirmations.
• Generic subject lines. “Payment failed” has a lower open rate than a subject that leads with the customer’s name or the item they tried to buy.
• Sending recovery emails for hard declines without differentiation. If your gateway returns a decline code you can read via a webhook, use it. Sending a retry link for a card that is genuinely blocked wastes the touchpoint.

Testing Before Black Friday: The Simulator Timeline

Krom Automation includes a workflow simulator that runs your workflow as a dry run with zero side effects. No emails send.

No delays execute against real orders. Use it to confirm the condition branches route correctly and the merge tags resolve to real values.

Here is the setup timeline counting back from Black Friday, November 27, 2026:

Date	Task	Why it matters
November 10	Build the workflow and simulate it with a test order	Leaves two weeks to fix logic errors before traffic spikes
November 14	Send a real test email to yourself via a staging order	Confirms merge tags resolve, links work, and email lands in inbox not spam
November 17	Check WP-Cron or server cron configuration	Delay nodes depend on cron firing reliably. Low-traffic sites need a real server cron or delays run late
November 21	Review email deliverability: SPF, DKIM, DMARC	Black Friday email volume from your domain spikes. ISPs notice. Misconfigured auth gets flagged
November 24	Confirm workflow is active and analytics baseline is set	You need a pre-sale baseline to measure recovery rate during the sale
November 27	Monitor execution logs during peak hours	The analytics dashboard shows failed execution count in real time. Catch problems in the first hour, not the next day
December 1	Export CSV report, review recovery rate by order value	Tells you whether to add SMS for the next campaign and what delay timing worked best

The WP-Cron point on November 17 is worth emphasising. Krom Automation runs delays via Action Scheduler, which is reliable, but Action Scheduler itself depends on WP-Cron to dispatch jobs. On a site that receives steady traffic all day, this is not an issue.

On a low-traffic staging environment, or a store with unusual quiet periods, delays can fire 1 to 2 hours late. Set up a real server cron job before Black Friday if you have not already. Your host’s control panel has the option, and the Krom Automation documentation covers the configuration.

Recovery for WooCommerce Subscriptions

Subscription renewal failures are a different problem. The customer is not at a checkout page.

They are not watching their email. The failure happens quietly, in the background, and the customer may not notice until their access stops working.

WooCommerce Subscriptions has a built-in retry system, but it retries at fixed intervals without any customer-facing communication until the subscription cancels. Krom Automation Pro adds triggers from the WooCommerce Subscriptions integration that fire on payment failure, renewal failure, and subscription status changes. That lets you send a warning email before the subscription cancels, rather than after, which is where recovery is still possible.

The sequence for subscription recovery follows the same logic as one-time orders: trigger on failure, wait a reasonable interval, check whether payment succeeded before sending, and limit touchpoints to two before pausing the sequence entirely.

Subscription recovery email sent before cancellation recovers the customer. The same email sent after cancellation is a win-back campaign, and win-back campaigns cost more and convert less.

What This Costs Compared to Other Tools

The recovery sequence described in this article runs entirely on the free version of Krom Automation for one-time order email recovery. SMS and subscription triggers require Pro. Here is how the cost compares across options at the time of writing:

Option	Year 1 cost (1 site)	Run limits	SMS included	Subscription triggers
Krom Automation free	$0	None	No	No
Krom Automation Pro (Basic)	Starts at $69/year	None	Via Twilio integration	Yes
Uncanny Automator (as of September 2026)	From $199/year for one site; AI plans from $300/year	None stated	Via third-party add-on	Via integration
Zapier Professional (as of September 2026)	Around $240/year for 750 tasks/month	750 tasks/month, overage charges apply	Via Zap steps (each step counts as a task)	Via Zap trigger

The Zapier column is worth examining on Black Friday specifically. A recovery sequence that sends 2 emails and checks 1 condition uses roughly 3 task credits per failed order.

At 750 tasks per month on the Professional plan, a store with 250 failed orders across Black Friday weekend burns through its monthly allowance in a single weekend. Krom Automation has no per-task billing at any tier.

For agencies managing multiple stores, the Krom Automation Standard plan covers 5 sites at $149 per year during the current launch pricing, and the Enterprise plan covers unlimited sites at $299 per year. Running this workflow across 10 client stores on Zapier would cost $2,400 per year at Professional pricing, assuming you stay within task limits. See all Krom Automation plan options to compare the site counts.

If you are also running other Black Friday automations like low stock alerts and coupon delivery, the no-task-limit model matters even more. We covered the full picture in how to automate your WooCommerce store for Black Friday.

What the Analytics Tell You After the Sale

Krom Automation’s analytics dashboard shows total executions, active workflows, failed execution count, and an execution trend chart. The reports page adds date range filtering, success rate per workflow, and CSV export. After Black Friday, filter the recovery workflow to the November 27 to 30 window and look at three numbers:

• Total executions: how many failed orders triggered the workflow
• Stopped by condition: how many self-resolved before the email fired (this is your soft decline recovery rate without any intervention)
• Completed executions: how many emails sent, which tells you your actual recovery email volume

Cross-reference against WooCommerce order data to see how many of those emailed customers completed payment. That ratio is your recovery rate.

If it is below 15 percent, the issue is usually the email itself, specifically the subject line or the friction in the payment link. If it is below 5 percent, check whether delays are firing on time, which points back to the WP-Cron configuration.

Also from wpRigel

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search orders, edit products, change order status, and run admin actions without clicking through menus.

It is the only command palette with real WooCommerce order, product and customer management built in, which makes it genuinely useful on the busiest days of the year when you need to find and update orders fast. Learn more about Commandify.

Pollify is a Gutenberg-native polls, surveys and quiz plugin. Polls are built as real blocks inside the editor, no shortcodes, no separate interface.

If you want to survey customers after Black Friday about their experience or run a post-sale NPS, it is the tool that fits inside the editor you already use. Learn more about Pollify.

Our Verdict

Build the recovery workflow before November 10, not the night before Black Friday. The simulator costs nothing to run, the free version costs nothing to install, and a single recovered order on a $150 average cart pays for the Pro plan several times over. The window to act is the six weeks between now and the sale, not the weekend itself.

Who should not bother: stores with fewer than 20 orders per day will see so few failures that a manual check on the orders screen is faster than building a workflow. Also skip this if your gateway already sends its own retry emails with payment links, since adding a second sequence creates confusion about which link the customer should use.

For everyone else: the workflow described here takes under an hour to build, runs automatically across every failed order regardless of volume, and stops itself when it is no longer needed. That is the correct trade-off for a four-day peak event.

Download the free Krom Automation plugin from the WordPress.org plugin directory and start with the free version. You can see what the full Pro feature set adds without committing to a purchase.

Compare Krom Automation plans and pricing

Frequently Asked Questions

Does the recovery workflow work for guest checkouts, or only registered users?

It works for guest checkouts. The Order Created trigger fires on every WooCommerce order regardless of whether the buyer has an account.

The Send Email action pulls from the billing email address attached to the order, which WooCommerce captures even for guests. You do not need the customer to be a registered user.

What happens if my delay runs late because WP-Cron is unreliable on my host?

The email sends late rather than not at all, which means a customer might receive it 2 to 3 hours after the failure instead of 45 minutes. On Black Friday that window matters because the customer’s intent to purchase cools quickly.

Configure a real server cron job before the sale to ensure Action Scheduler fires on time. Most shared and managed hosts expose this in their control panel as a cron jobs section.

Can I recover failed subscription payments with the free version?

No. Subscription-specific triggers, including payment failure and renewal failure, are available through the WooCommerce Subscriptions integration in Krom Automation Pro. The free version covers one-time order failures via the Order Created trigger and a status condition check.

How do I find out whether a payment failed because of a hard decline or a soft decline?

Your payment gateway logs the decline code. In WooCommerce, go to WooCommerce Status Logs and filter by your gateway’s log file.

Stripe, for example, logs the decline code (card_declined, insufficient_funds, do_not_honor) alongside each failed charge. Reading those codes tells you whether to retry or to ask the customer to use a different card.

Will sending recovery emails hurt my email deliverability during Black Friday?

It can, if you send too many or if your authentication is misconfigured. Keep the sequence to 2 emails maximum, ensure SPF, DKIM and DMARC are configured correctly before the sale, and use a transactional email service rather than PHP mail. We cover the full deliverability picture in why your automated WordPress emails go to spam.

Can I use the same Krom Automation workflow for Black Friday and other sales events during the year?

Yes. The workflow is not date-specific. Once it is live and tested, it runs on every failed order throughout the year.

Black Friday is the highest-stakes moment to have it running, but the workflow recovers revenue in January, April and August too. There is no reason to pause it between sales events unless your gateway changes or you restructure your checkout flow.

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.