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.

You can get an instant WooCommerce high value order notification using Krom Automation. Set the trigger to Order Created or Order Completed, add a conditional branch that checks order total, and point the Yes path at an email, Slack message, Telegram alert or Twilio SMS.

The free plugin covers email alerts. Slack, Telegram and Twilio SMS require Krom Automation Pro, which starts at $69 a year.

Black Friday is November 27, 2026. Cyber Monday follows three days later on November 30. During those 96 hours, a $3,000 order sitting unacknowledged for 40 minutes is a real risk.

Standard WooCommerce order emails arrive when they arrive, assuming the spam filter cooperates. A dedicated alert channel changes that. Your team knows within seconds, not minutes.

This guide covers the full setup: trigger selection, condition logic, channel options, tiered routing for different order thresholds, a setup timeline counting back from Black Friday, and how to stress test everything with the workflow simulator before the sale starts.

Browse the full feature list to see every trigger and action included in the free plugin and Pro.

Why Default WooCommerce Order Emails Are Not Enough on Peak Days

WooCommerce sends an admin order notification email for every order by default. On a slow Tuesday that is fine.

On Black Friday, when 200 orders arrive in 4 hours, the signal-to-noise ratio collapses. A $4,500 wholesale order looks identical in the inbox to a $12 single-item order.

The second problem is delivery. Shared hosting under high load throttles outbound mail.

Transactional emails on busy days are the first thing to queue and the last thing to clear. A notification that arrives 90 minutes after the order was placed is not a notification, it is a log entry.

An alert that arrives 90 minutes after a $4,000 order is not a notification. It is a log entry nobody acted on.

Third, standard order emails go to one address: the admin email. If you want a sales manager to see orders above $1,000 and an account director to see orders above $5,000, you cannot express that in native WooCommerce without custom code.

What You Need Before You Start

Before building the workflow, confirm these are in place:

• Krom Automation free plugin installed on your WooCommerce site. Follow the installation guide if you have not done this yet.
• WooCommerce active on the same site. Krom’s WooCommerce triggers only appear when WooCommerce is detected.
• Krom Automation Pro if you want Slack, Telegram or Twilio SMS. The free plugin covers email only.
• API keys ready for whichever messaging service you choose. Krom never marks up API costs. You pay your provider directly at standard rates.
• A real server cron configured on shared or budget hosting. WP-Cron fires on page load. On a low-traffic staging environment, a cron-triggered delay action could sit for hours. The delays and scheduling documentation explains how to set this up correctly before Black Friday.

How to Build the High Value Order Notification Workflow

Building a workflow in Krom Automation follows the same shape every time: pick a trigger, add conditions, then add actions on each branch. Here is the exact path for a high value order alert.

Step 1: Choose the Right Trigger

Krom Automation includes two WooCommerce triggers in the free plugin: Order Created and Order Completed. Order Created fires the moment a customer submits the order, before payment clears. Order Completed fires when fulfilment is marked done.

For a real-time alert on a big purchase, Order Created is the right choice. You want to know before you start picking and packing, not after.

Step 2: Add a Conditional Branch on Order Total

After the trigger, add a conditional branch. Set the condition to check order total. Set the threshold to whatever your “high value” floor is, for example $500, $1,000 or $2,500 depending on your typical order size.

The Yes path fires when the order meets or exceeds that amount. The No path can be left empty or used for standard handling. The conditions and branching documentation covers every operator available, including greater than, less than and between.

Step 3: Add the Alert Action on the Yes Path

On the Yes branch, add whichever action fits your team’s workflow:

• Send Email (free): fires immediately, using your SMTP or transactional mail provider. Use merge tags to pull in order total, customer name, order ID and product list so the email body carries real data, not a generic alert. The merge tags documentation lists every WooCommerce field available.
• Slack message (Pro): posts directly to a channel or a DM. A $3,200 order notification in #high-value-orders is visible to the whole fulfilment team without anyone checking email.
• Telegram alert (Pro): useful for store owners managing fulfilment from a phone. Telegram delivers in under 2 seconds on a good connection and does not end up in a spam folder.
• Twilio SMS (Pro): the right choice when someone needs to be reached regardless of whether they have a data connection. SMS delivery is more reliable than app notifications in poor signal areas like warehouses.

All four messaging channels are covered in the messaging integrations documentation for Slack, Discord, Twilio and Telegram.

Tiered Routing: Sending Different Alerts to Different People

This is the gap none of the competing guides address. A single threshold sends one alert to one place.

Tiered routing uses nested conditional branches to escalate based on order size. Here is the structure:

1. Trigger: Order Created
2. Branch 1: Order total is greater than or equal to $500. Yes path continues. No path exits.
3. Branch 2 (on the Yes path): Order total is greater than or equal to $2,000. Yes path notifies the account director. No path notifies the sales manager.
4. Branch 3 (optional, on the second Yes path): Order total is greater than or equal to $5,000. Yes path triggers a phone call via Twilio or a high-priority Slack alert in a separate escalation channel.

The result is a three-tier system. Orders between $500 and $1,999 alert the sales manager. Orders between $2,000 and $4,999 alert the account director.

Orders at $5,000 or above trigger both a Slack post and an SMS. Every recipient gets only the alerts relevant to their role. No one is buried in volume.

Tiered routing is the difference between a notification system and a genuine escalation policy. Most stores have neither.

A VIP Order Workflow: Beyond the Alert

A high value order notification is the first step. The full VIP order workflow does more than alert. It handles follow-up automatically so nothing falls through during a high-volume sale.

Here is what the extended workflow looks like after the initial alert fires:

• Alert action: Slack or SMS fires within seconds of the order.
• Tag the customer: Update User Meta or, with a CRM connected, add a tag like “VIP” or “High Value” to the customer record. This feeds future segmentation without manual work.
• Create a coupon: Krom’s Create Coupon action can generate a personalised thank-you discount code and attach it to a follow-up email. Sending Black Friday coupon codes automatically covers this exact pattern.
• Delayed follow-up: Use a delay of 2 days, then send a personalised check-in email using merge tags to reference the original order. This runs via Action Scheduler in the background, so the page load that triggers the workflow is long over by the time the follow-up fires.

The visual workflow builder makes this branching structure easy to read and audit. You can see the entire logic on one canvas rather than reading a list of rules.

Plan Comparison: Free vs Pro for High Value Alerts

What you need	Free plugin	Pro (from $69/year)
Email alert when order exceeds threshold	Yes	Yes, plus visual email builder
Conditional branch on order total	Yes	Yes, with extended operators
Slack or Discord notification	No	Yes
Telegram alert	No	Yes
Twilio SMS	No	Yes
Tiered routing to multiple recipients	Yes (email only)	Yes, any channel combination
Workflow simulator for dry run testing	Yes	Yes
Execution logs with per-step audit trail	Yes	Yes
Failure notifications and automatic retry	Yes	Yes

Cost Comparison at Black Friday Scale

Option	Year 1 cost	Year 2 cost	Per-task billing	Self-hosted data
Krom Automation free (email only)	$0	$0	No	Yes
Krom Automation Pro (Slack, SMS, Telegram)	From $69/year	From $69/year	No	Yes
Uncanny Automator (as of September 2026)	From $199/year	From $199/year	No	Yes
Zapier Professional (as of September 2026)	Around $240/year	Around $240/year	Yes, 750 tasks/month then overage	No

Zapier’s task-based billing is the critical difference at scale. On Black Friday, 800 orders across two days pushes a 750-task-per-month plan into overage territory immediately. Krom Automation has no per-task or per-execution billing at any tier.

Black Friday Setup Timeline

Work backwards from November 27. Here is the schedule we recommend:

• November 10 (17 days out): Install Krom Automation and activate Pro if you need Slack, Telegram or SMS. Configure your messaging API keys. The Pro installation guide covers the activation steps.
• November 13 (14 days out): Build the high value order workflow. Set your threshold, build your branches, write your alert message bodies using merge tags.
• November 17 (10 days out): Run the workflow simulator. The simulator documentation explains how to fire a dry run with zero side effects. Confirm the correct branch fires for an order of $499, $501, $1,999 and $2,001 if you are using tiered thresholds.
• November 20 (7 days out): Place a real test order on your store. Confirm the alert arrives in Slack, Telegram or SMS within 30 seconds. Check the execution log to verify per-step status. Fix any delivery issues before the volume arrives.
• November 24 (3 days out): Final check. Confirm server cron is configured if you are on shared hosting. Review failure notification settings so your team is alerted if a workflow errors under load.
• November 27 (Black Friday): Workflows running. Monitor the analytics dashboard. Total executions, failed execution count and the execution trend chart are all visible without opening individual workflow logs.

The broader Black Friday automation picture, including abandoned cart recovery and post-sale sequences, is covered in how to automate your WooCommerce store for Black Friday.

Testing with the Workflow Simulator Before the Sale

The workflow simulator lets you fire a dry run using real order data without triggering any action. No Slack message is sent. No SMS fires.

No coupon is created. You see exactly which branch the workflow takes and whether the condition logic evaluates correctly.

This matters more on Black Friday than any other day. A condition that evaluates on the wrong field, a merge tag that returns an empty string, or a Slack webhook URL that has expired will fail silently unless you have tested it.

Silent automation failures during a sale are expensive. When an automation fails silently on WordPress covers how to catch these before they cost you.

Testing on a quiet Wednesday is free. Discovering a broken condition on Black Friday afternoon costs real money.

After the dry run, check the execution log. Every step shows its status, the data it received and the data it passed forward. If a condition branch is evaluating against the wrong value, it is visible in the log within 30 seconds of the test run.

What to Watch for on the Day

Even a correctly built workflow can encounter issues under Black Friday volume. Here is what to watch:

• WP-Cron timing on shared hosting: If your site goes quiet between order bursts, delayed actions may fire late. A real server cron eliminates this. Set it up before the sale, not during.
• Slack rate limits: Slack’s API has a per-channel rate limit of 1 message per second by default. If 50 orders arrive in 30 seconds, some messages will queue. This is a Slack constraint, not a Krom constraint. Consider posting a summary rather than one message per order at extreme volume.
• Twilio SMS delivery: Twilio charges per SMS segment. A message body over 160 characters splits into two segments and costs twice as much. Keep your SMS alert body under 120 characters to stay safe. Pull only the essential merge tags: order ID, total and customer name.
• API key expiry: Messaging API keys do not expire on a schedule, but they can be invalidated if you rotate credentials elsewhere. Verify all keys are live during your November 20 test.

Also from wpRigel

Pollify is wpRigel’s Gutenberg native poll, survey and quiz plugin. Polls are built as real blocks inside the block editor, so there are no shortcodes to paste and no separate configuration interface to manage. It is a natural fit for post-purchase feedback or Black Friday promotion voting.

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

It is the only command palette with genuine WooCommerce depth: you can search orders by number, edit products, update stock and manage customers all from the keyboard. On a high-volume sale day, that speed compounds.

Frequently Asked Questions

Does the free version of Krom Automation support order total conditions?

Yes. The free plugin includes the Order Created and Order Completed triggers, conditional branching, and the Send Email action.

You can build a complete high value order email alert with a threshold condition at no cost. Slack, Telegram and Twilio SMS require Pro.

What WooCommerce data can I include in the alert message?

Merge tags let you pull in order ID, order total, customer name, customer email, billing address, shipping address, product list and order status. The merge tags documentation lists every available field. These work in email bodies, Slack messages and SMS text.

Can I notify different people for different order amounts?

Yes. Use nested conditional branches: one branch checks whether the order exceeds $500, and a second branch on that Yes path checks whether it exceeds $2,000.

Each branch can point to a different recipient or channel. The conditions and branching documentation covers nested logic in full.

Will high order volume on Black Friday cause alerts to miss or delay?

Krom Automation runs actions via Action Scheduler in the background, so no alert blocks a page load. The main timing risk is WP-Cron on low-traffic shared hosting.

Configure a real server cron before the sale and test it during your November 20 dry run. On high-traffic production sites this is not typically an issue.

Do I need a separate plugin for Slack or SMS alerts?

No. Slack, Telegram and Twilio SMS are built into Krom Automation Pro as native actions.

You connect your API credentials in the Krom settings, then select the action on the workflow canvas. No additional plugin is required.

What happens if the workflow fails during the sale?

Krom Automation sends an email failure notification and retries automatically with configurable backoff. Every failed execution appears in the execution log with a per-step trace so you can see exactly where the failure occurred.

Silent automation failures are the most common Black Friday risk. The retry and logging system is there specifically to surface them.

Our Verdict

If your store sees orders above $500 regularly and you are managing fulfilment with more than one person, a conditional notification workflow is not optional infrastructure. It is the difference between reacting to big orders and missing them until someone checks the dashboard an hour later.

The free plugin covers the email path completely. That is enough for a solo operator running a straightforward store. Agencies managing high-volume client stores, or any store where a single missed $3,000 order costs more than a year’s Pro licence, should be on Pro before Black Friday.

See full pricing details and the 14-day money-back guarantee, then get the workflow live and simulator-tested before November 24. The free plugin is available on the WordPress.org plugin directory with no trial period and no run caps.

You can send Black Friday coupon codes automatically using Krom Automation and WooCommerce. The free plugin creates coupons and sends email.

To deliver codes through Mailchimp, FluentCRM or ActiveCampaign, you need Krom Automation Pro, which starts at $69 a year. Build the workflow once, test it with the simulator, and every qualifying customer gets their own unique code without you touching a thing on November 27, 2026.

Most Black Friday coupon failures are not coupon problems. They are delivery problems.

A single shared code leaks to coupon sites within hours, unlimited-use codes bleed margin all weekend, and a manually-sent batch email misses anyone who joined the list after you hit send. Automating the full sequence, from code creation to delivery to expiry enforcement, closes all three gaps at once.

This guide covers the exact workflow structure, the setup timeline counting back from Black Friday, how to connect the right email channel, and what to watch when the campaign is live.

Browse the full feature list to see what triggers and actions are available before you start building.

What Does “Sending Coupon Codes Automatically” Actually Mean?

There are two distinct things people mean when they ask this question, and they require different setups. The first is a bulk send: one email blast to your whole list, all at the same time, with one shared code. The second is a triggered send: each subscriber or customer gets their own unique code when something happens, like placing a first order or joining a segment.

A shared code is simpler but carries real risk. Coupon aggregator sites index them within hours, and anyone can use them, not just your intended recipients. A unique-per-customer code costs slightly more to set up but eliminates sharing entirely and gives you trackable usage data per customer.

Krom Automation handles both approaches. The free plugin can generate a unique WooCommerce coupon and send it via WordPress email in a single workflow. Pro adds Mailchimp, FluentCRM and other ESP connections so the code lands in a properly branded campaign rather than a plain transactional email.

Quick Summary

Delivery Method	Free or Pro	Unique Code Per Customer	Branded Email Template
WordPress Send Email action	Free	Yes, via Create Coupon + merge tag	No, plain text
Mailchimp via Krom integration	Pro	Yes	Yes
FluentCRM via Krom integration	Pro	Yes	Yes
HTTP Request to any ESP API	Free	Yes, requires API mapping	Depends on ESP

How Does the Create Coupon Action Work?

The Create Coupon action in Krom Automation talks directly to WooCommerce. When it fires, it creates a new coupon in your WooCommerce dashboard with whatever parameters you configure on the action node. You set the discount type, the amount, the expiry date, the usage limit and whether the code is customer-specific, all inside the workflow builder without touching a PHP file.

The action returns the generated coupon code as a dynamic value. That value is then available as a merge tag in every action that runs after it in the same workflow. So the sequence is: Create Coupon fires, generates a code like BF2026-A7X3K, and the next Send Email action inserts that exact code into the message body using the merge tag.

The customer receives their own code. Nobody else has it.

You can read exactly how merge tags work in Krom Automation before you build, because getting the tag syntax right is what makes the variable code injection reliable.

A unique code per customer is not a luxury feature. It is the only way to know whether your campaign drove a sale or whether someone found the code on a deal site.

Which Trigger Should You Use?

The right trigger depends on who you want to receive the coupon. Here are the four most useful setups for Black Friday:

• Order Completed trigger: send a Black Friday coupon to customers who complete a purchase between November 27 and November 30. Rewards buyers and encourages a second order before Cyber Monday ends.
• User Registered trigger: new accounts created during the sale period automatically receive a welcome coupon. Useful for lead-generation campaigns where registering unlocks a discount.
• Schedule trigger (Pro): fire a workflow at a specific date and time, like 00:01 on November 27, to push codes to an existing segment. This is the correct approach for a timed launch send to your full list.
• Incoming Webhook trigger (Pro): an external tool, such as your ESP or CRM, pings your site when a subscriber hits a segment condition, and Krom Automation creates and returns the coupon in real time. This is the most flexible architecture for large lists.

If you are planning a timed launch, the Schedule trigger documentation explains how to set recurring and one-time schedules so your workflow fires at exactly 00:01 on Black Friday and not a minute later, assuming a real server cron is configured.

How to Build the Workflow, Step by Step

Open Krom Automation from your WordPress admin sidebar and click Add New Workflow. The visual canvas loads on a blank state. Every step below maps to a node you place on that canvas.

1. Place your trigger node. Select Order Completed for a post-purchase flow, or Schedule for a timed list send. Configure the trigger conditions, for example, order total above $0 and order date falls within the sale window.
2. Add a Delay node if needed. For a post-purchase coupon, a 10-minute delay gives the order confirmation email time to land first. Set the delay to 10 minutes in the Delays and Scheduling panel.
3. Add the Create Coupon action node. Set discount type to percentage or fixed. For Black Friday, 20 percent is a common choice. Set usage limit to 1 per code. Set expiry to November 30, 2026, so the code dies at midnight on Cyber Monday. Enable “restrict to email” if you want WooCommerce to enforce that only the recipient can use it.
4. Add the Send Email or ESP action node. In the email body, insert the coupon merge tag where the code should appear. For Mailchimp delivery, connect the Mailchimp integration and pass the coupon value as a custom field into the campaign. For FluentCRM, the FluentCRM integration lets you tag the contact and trigger a sequence that contains the code.
5. Add a Run Once setting. Open Workflow Settings and enable Run Once Per Entity. This prevents a single customer from triggering the workflow multiple times and receiving multiple codes.
6. Save and run the simulator. The workflow simulator fires the workflow with dummy data and logs every step result without creating a real coupon or sending a real email. Check that the coupon node shows the expected parameters and that the email node shows the merge tag resolved.

The step-by-step workflow builder guide covers the exact canvas interactions and node connection method if you are building your first workflow.

Which Email Channel Should You Use?

The channel choice affects how the coupon email looks, how it gets delivered and how you track opens and clicks. Here is the honest comparison for Black Friday:

Channel	Deliverability	Branded Design	Open Tracking	Setup Effort
WordPress Send Email (free)	Depends on your SMTP setup	No	No	Under 5 minutes
Mailchimp (Pro)	High, dedicated sending infrastructure	Yes, full template builder	Yes	20 to 30 minutes
FluentCRM (Pro)	Depends on your SMTP setup	Yes, block editor templates	Yes	15 to 20 minutes
HTTP Request to any ESP (free)	Depends on ESP	Yes, if the ESP supports it	Yes, if the ESP supports it	45 to 90 minutes

For most WooCommerce stores sending to under 5,000 customers, the free Send Email action with a properly configured SMTP plugin is sufficient. For stores with larger lists or complex segments, routing through Mailchimp or FluentCRM gives you deliverability infrastructure and click tracking that WordPress email cannot match.

One warning worth naming: if you are using WordPress email without an SMTP plugin and your hosting server’s mail reputation is poor, Black Friday coupon emails will land in spam at a rate that makes the campaign pointless. Read why automated WordPress emails go to spam before you build, not after.

Deliverability is not a nice-to-have on Black Friday. An email that arrives on December 2 is not a coupon email. It is an apology waiting to happen.

Setting Expiry Dates and Usage Limits the Right Way

The Create Coupon action gives you four parameters that matter most for a Black Friday campaign:

• Expiry date: set to November 30, 2026. This is Cyber Monday and a natural end to the sale window. A coupon with no expiry that someone finds in their inbox in February is a margin problem.
• Usage limit per coupon: set to 1. This makes the code single-use, so it cannot be shared. Even if a customer posts it somewhere, it redeems once and becomes invalid.
• Usage limit per customer: set to 1. WooCommerce enforces this at checkout. The same customer cannot use the code twice by checking out from different browsers.
• Restrict to email: when enabled, WooCommerce checks that the billing email matches the email the coupon was assigned to. This is the strongest protection against code sharing and it requires the customer to be logged in or to enter the matching email at checkout.

Setting all four correctly takes about 3 minutes inside the Create Coupon node. Skipping the usage limit is the most common mistake and the one that costs the most money when a campaign runs over a 72-hour sale window.

How to Monitor the Campaign When It Goes Live

This is the section most coupon automation guides skip, and it is the one that separates a campaign that runs cleanly from one that silently fails partway through. Krom Automation’s execution log records every workflow run at the step level, so you can see exactly which coupon was created, what code was assigned and whether the email action succeeded.

Check these three things within the first 30 minutes of your campaign going live:

• Execution log: go to Krom Automation, open the workflow, and click Execution History. Every run should show a green success state on both the Create Coupon step and the Send Email step. A red step means the action failed, and the customer did not receive their code.
• Failure notification emails: Krom Automation sends an email alert when a workflow execution fails. Make sure the notification address in settings is one you check on sale day, not a shared inbox that nobody monitors on a Saturday.
• WooCommerce coupon list: go to WooCommerce, Marketing, Coupons. You should see new coupons appearing with the BF prefix you configured. If the list is not growing during the sale, the trigger is not firing.

The analytics dashboard shows total executions and failed execution count in real time. If your failed count climbs above 2 to 3 percent, pause the workflow and check the execution log before it runs further. A failed workflow that runs 1,000 times without anyone noticing is 1,000 customers who expected a code and did not receive one.

For a broader look at what can go wrong and how to catch it early, this guide on silent automation failures is worth reading before the campaign starts.

Set It Up By: A Countdown Timeline

Black Friday is November 27, 2026. Work backwards from that date and you have enough time to build, test and fix anything that breaks before the sale starts.

• By November 10: install Krom Automation and configure your trigger and Create Coupon action. Set expiry to November 30 and usage limit to 1.
• By November 14: run the workflow simulator at least 3 times with different test scenarios. Confirm the merge tag resolves correctly in the email body.
• By November 17: connect your ESP if you are using Mailchimp or FluentCRM. Send a real test email to yourself and check that the coupon code appears in the correct position and that the code exists in WooCommerce.
• By November 21: enable Run Once Per Entity, set failure notification email, and export the workflow JSON as a backup. If something breaks on November 27, you can reimport and restart in under 5 minutes.
• November 26, evening: run the simulator one final time. Check the execution log is empty and ready. Confirm the workflow is set to active.

The workflow simulator documentation explains what the dry run does and does not test, including which steps are skipped in simulation mode so you know what still needs a live test.

What Are the Real Limits of This Approach?

Krom Automation is WordPress native, so there are a few constraints worth naming before you commit to this setup.

WP-Cron timing: if you are using the Schedule trigger on a low-traffic site, WP-Cron only fires when someone visits the site. On a site that receives no visits between midnight and 8am, your 00:01 Black Friday launch fires late. The fix is a real server cron job that pings WordPress on a defined schedule.

This is a one-time server configuration and most managed WordPress hosts support it. The delays and scheduling documentation covers this constraint.

WooCommerce required: the Create Coupon and Update Order Status actions only appear when WooCommerce is installed and active. If you are running a non-WooCommerce store, those actions are not available and the coupon creation step needs a different approach, such as an HTTP Request to your commerce platform’s API.

ESP rate limits: if you are passing coupon codes to Mailchimp or FluentCRM via the integration, those services have their own API rate limits. Sending 10,000 codes in 30 seconds will hit a rate limit wall. For large list sends, space the triggers with a delay node or use the batch architecture described in the incoming webhook receiver documentation.

Building the workflow in October means you have time to discover the WP-Cron problem before it costs you the first hour of your sale.

How Much Does This Cost?

The free version of Krom Automation covers the core coupon-and-email workflow with no trial period and no run caps. You can build and run the workflow for the entire sale window at zero cost if you are using the WordPress Send Email action for delivery.

Krom Automation Pro adds the Mailchimp and FluentCRM integrations, the Schedule trigger for timed launches, and the incoming webhook receiver. Pro starts at $69 a year for a single site or $199 for a lifetime licence on one site. See the full plan breakdown to compare the annual and lifetime options across all three tiers.

For comparison, Uncanny Automator’s automation plans start from $199 a year for one site as of September 2026, and do not include a lifetime option. Zapier’s Professional plan is around $240 a year billed annually for 750 tasks a month, with task-based billing that adds up during a high-volume sale weekend. Krom Automation has no per-task or per-execution charge at any tier.

You can download the free plugin from the WordPress.org plugin directory and have the workflow running in the same afternoon.

For more on the full Black Friday automation picture, including order status updates, inventory alerts and post-sale follow-ups, see our guide to automating your WooCommerce store for Black Friday.

Also from wpRigel

Pollify is our Gutenberg native poll, survey and quiz plugin. Polls are built as real blocks inside the block editor with no shortcodes and no separate interface to learn. It is useful for post-sale feedback and NPS surveys after your Black Friday campaign closes.

Commandify gives the WordPress admin a keyboard-first command palette. Press Cmd or Ctrl plus K to jump anywhere in the admin, search orders by customer name, update product prices and run maintenance tasks without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product and customer commands built in.

Our Verdict

If you are running a WooCommerce store and Black Friday is in your calendar, build this workflow now. The free plugin is enough to get a unique coupon into every qualifying customer’s inbox with zero manual work on sale day. If your list is larger than a few hundred contacts or you need branded email delivery, add Pro for $69 a year and connect Mailchimp or FluentCRM.

Who should not build this: stores not using WooCommerce, or anyone who needs automation between two external services with no WordPress involvement. Krom Automation is WordPress native, so the trigger or action needs to touch your site. If your commerce platform is entirely external, the HTTP Request action can reach it, but you will need to map the API fields yourself.

The setup takes under two hours including testing. The simulator means you can verify the workflow produces the right coupon with the right expiry before a single real customer sees it. Build it in October, test it in November, and spend Black Friday watching the execution log rather than manually copying and pasting codes.

Compare plans and start your setup before the November timeline runs out.

Frequently Asked Questions

Does the free version of Krom Automation create unique WooCommerce coupon codes?

Yes. The Create Coupon action is included in the free plugin. It creates a unique code in WooCommerce and makes that code available as a merge tag in the following Send Email action. No Pro licence is needed for this core flow.

Can I send different coupon codes to different customer segments automatically?

Yes, using conditional branching. Add a Yes/No condition node after your trigger and route different customer groups, such as first-time buyers versus returning customers, to separate Create Coupon nodes with different discount amounts. Each path generates its own code and sends its own email. The conditions and branching documentation covers the full logic options.

How do I prevent customers from sharing their Black Friday coupon code?

Set the usage limit to 1 per coupon and enable the Restrict to Email option in the Create Coupon action. WooCommerce then checks that the billing email at checkout matches the email the coupon was issued to. A code posted to a deal site will only work for the original recipient, and only once.

Will the Schedule trigger fire at exactly midnight on Black Friday?

On a high-traffic site with real server cron configured, yes. On a low-traffic site relying on WP-Cron, the trigger fires the next time a page request hits WordPress after the scheduled time. If your site receives visits continuously, the delay is negligible. If traffic drops overnight, the delay could be 30 minutes or more. Configure a real server cron job before Black Friday if timing precision matters to your campaign.

Can I track which customers actually used the coupon code I sent them?

WooCommerce records coupon usage against the order. Every coupon created by Krom Automation appears in WooCommerce under Marketing, Coupons, and the usage count updates when the code is redeemed. For richer per-customer tracking, connect FluentCRM and tag each contact when their code is used, which lets you filter your list by redemption status after the sale.

Does Krom Automation work with Mailchimp for sending Black Friday coupon emails?

Yes, with Krom Automation Pro. The Mailchimp integration lets you pass the generated coupon code as a custom merge field into a Mailchimp campaign or automation sequence. The Mailchimp integration documentation covers the field mapping and authentication steps.

You can automate your WooCommerce store for Black Friday using Krom Automation, a visual workflow plugin for WordPress. The free version covers Order Created and Order Completed triggers plus 21 built-in actions, which handles most of what you need. If you want a Schedule trigger, incoming webhooks, or email marketing integrations like Mailchimp or FluentCRM, you will need Pro, which starts at $69 a year.

Black Friday 2026 falls on November 27 and Cyber Monday on November 30. That gives you roughly four weeks from today to build, test, and run your automations, which is enough time if you start this week. The stores that struggle are not the ones with small budgets, they are the ones that set up workflows two days before and never test them.

This guide covers which triggers to use, which actions to pair them with, how to test without sending real emails, and what to automate after the sale ends. That last part is the angle almost every other resource skips entirely.

Browse the full feature list to see every trigger and action available before you plan your workflows.

Quick Summary

Workflow	Trigger	Key Action	Free or Pro?
Order confirmation + upsell	Order Completed	Send Email	Free
First-purchase welcome	Order Completed + condition	Send Email, Change User Role	Free
Low stock alert to Slack	Order Completed + condition	HTTP Request to Slack	Free
Failed payment recovery	Order Created (status: failed)	Send Email	Free
Scheduled sale price emails	Schedule Trigger	Send Email via visual builder	Pro
Post-sale Mailchimp tagging	Order Completed	Mailchimp integration	Pro
Post-BFCM re-engagement	Schedule Trigger (Dec 3)	Send Email sequence	Pro

What Should I Set Up Four Weeks Before Black Friday?

Four weeks out, your job is infrastructure, not campaigns. This is when you install and configure Krom Automation, connect your email provider, and build one test workflow end to end. Trying to build five workflows at once without a working baseline is how things break on the day.

Start with the installation guide if Krom Automation is not already active. Once it is, build a simple Order Completed workflow that sends you a plain-text notification email. This confirms your WooCommerce triggers are firing correctly and that Action Scheduler is processing jobs in the background.

Your four-week checklist, in priority order:

• Week 4 (now): Install Krom Automation, configure Action Scheduler, run one test Order Completed workflow, confirm emails arrive
• Week 3: Build your core sale workflows, order confirmation, first-purchase welcome, low-stock alert
• Week 2: Add post-sale and recovery workflows, failed payment email, Mailchimp tagging if using Pro
• Week 1: Stress test everything using the workflow simulator, fix edge cases, freeze changes
• Nov 27 to Nov 30: Monitor the execution log dashboard, do not edit live workflows
• Dec 1 onward: Run post-BFCM re-engagement sequence, reconcile inventory, review analytics

Work through these in order. Skipping to Week 2 workflows before Week 4 infrastructure is confirmed means you will not catch configuration problems until they fail silently on the actual day.

The stores that struggle are not the ones with small budgets. They are the ones that set up workflows two days before and never run a single test.

Which Triggers Should I Use for Black Friday Automation?

Krom Automation’s free version includes 2 WooCommerce triggers: Order Created and Order Completed. Those two cover the majority of what a Black Friday campaign actually needs. You can see every available trigger in the free triggers reference.

Here is how to use each one:

• Order Completed: Fires when payment is confirmed and fulfillment is marked complete. Use this for post-purchase emails, loyalty tagging, and first-purchase detection. This is your highest-value trigger because it only fires for customers who actually paid.
• Order Created (status: failed): Use conditional branching to check whether the order status is “failed” immediately after creation. This is your failed payment recovery trigger. A one-email recovery sequence sent within 30 minutes recovers a meaningful share of abandoned checkouts.
• Schedule Trigger (Pro): Fires on a date and time you define. Use this to send your Black Friday teaser email on November 25, your launch email at midnight November 27, and your last-chance email on November 30 at 6 PM. The Schedule Trigger documentation covers one-time and recurring options.
• User Registered: If you gate a Black Friday deal behind account creation, this trigger fires the moment someone signs up. Pair it with a Send Email action and a coupon code in the body.

For low-stock alerts, there is no dedicated inventory trigger in the free version. The practical workaround is a conditional branch on the Order Completed trigger: after each order, check the remaining stock count using a merge tag and branch to a Slack or email notification if it falls below your threshold. This is documented in the conditions and branching guide.

Which Actions Should I Pair With Each Trigger?

Krom Automation’s free version includes 21 built-in actions. The ones that matter most for Black Friday are Send Email, HTTP Request, Change User Role, and Update Post Field. The free actions reference lists every option with field descriptions.

Send Email is the workhorse. Use merge tags to pull the customer’s first name, order total, and order number directly into the email body. The merge tags documentation shows exactly which variables are available from WooCommerce order events.

HTTP Request lets you hit any external endpoint, including Slack’s incoming webhook URL, without a Pro integration. A five-line JSON payload to a Slack webhook is enough to get real-time low-stock and failed-payment alerts into your team’s channel. We have a full walkthrough of WooCommerce order alerts to Slack and SMS if you want the exact payload structure.

Change User Role lets you tag first-time buyers with a custom WordPress role the moment their order completes. That role can then gate loyalty pricing, exclusive content, or early access to future sales. It runs entirely inside WordPress with no external CRM required.

If you are on Pro, the Mailchimp integration and FluentCRM integration let you subscribe contacts, apply tags, and trigger sequences directly from Order Completed without an HTTP Request workaround.

How Do I Build the Four Core Black Friday Workflows?

These four workflows cover the most valuable automation ground for a BFCM sale. Build them in this order because each one teaches you something about the canvas before the next one adds complexity.

Workflow 1: Order Confirmation Email

Trigger: Order Completed. Action: Send Email. Use merge tags for first name, order number, and order total.

Add a one-line cross-sell suggestion pointing to a related product. This replaces WooCommerce’s default plain-text receipt with something that actually represents your brand.

Workflow 2: First-Purchase Welcome

Trigger: Order Completed. Add a conditional branch immediately after the trigger: check whether the customer’s total order count equals 1. The Yes path sends a welcome email with a loyalty discount code for their next purchase.

The No path ends. The step-by-step workflow builder guide shows how to add conditions to any workflow.

Workflow 3: Failed Payment Recovery

Trigger: Order Created. Add a conditional branch checking order status equals “failed”.

The Yes path waits 30 minutes using a delay action, then sends a recovery email with a direct link to the cart. Enable “run once per entity” in workflow settings so the same customer does not receive the email twice if two orders fail in the same session.

Workflow 4: Low-Stock Team Alert

Trigger: Order Completed. Add a conditional branch checking remaining stock on the purchased product. Set the threshold to whatever your reorder point is, say 10 units.

The Yes path sends an HTTP Request to your Slack webhook with the product name, SKU, and remaining quantity as merge tag values. This workflow alone saves your team from discovering a stockout on the morning of Black Friday.

A low-stock alert that fires after every order costs you nothing and prevents the one situation no discount strategy can fix: running out of stock at peak traffic.

How Do I Test Workflows Before the Sale Starts?

Krom Automation includes a workflow simulator that runs a dry-run of any workflow with zero side effects. No emails send, no Slack messages fire, no database records change. You supply the trigger data manually and the simulator steps through every node, showing you what each action would do and flagging any configuration error before it reaches a real customer.

Run the simulator on every workflow at least once before November 27. Pay particular attention to:

• Conditional branch logic: Simulate both the Yes and No paths separately to confirm each one behaves correctly
• Merge tag resolution: Check that order number, customer name, and product fields populate with real-looking values rather than empty strings
• Delay timing: Verify the delay unit is set correctly. A delay set to “30” with the unit left on “days” instead of “minutes” sends your recovery email a month late
• Run once per entity: Confirm it is enabled on any workflow that could fire multiple times for the same order or customer

The simulator documentation explains how to supply custom trigger data for WooCommerce order events specifically. Use it on November 24 or 25 at the latest. Freezing changes at least 48 hours before the sale starts is a discipline worth enforcing.

One honest constraint: workflow execution runs on Action Scheduler, which depends on WordPress Cron. On very low-traffic sites where no page loads occur for hours, WP-Cron fires late.

If your store is running a major sale, traffic will not be the problem. But if you are running Black Friday automation on a staging or low-traffic site, configure a real server cron job to call wp-cron.php on a one-minute interval.

What Should I Automate After Cyber Monday?

Almost every Black Friday automation guide stops at November 30. That is the wrong place to stop. The customers who bought from you during BFCM are your highest-intent audience for the next 90 days, and most stores do nothing with them beyond a generic December newsletter.

Here is what to build for the post-sale period:

• Re-engagement sequence (Dec 3): Use the Schedule Trigger to send a “thank you for your BFCM order” email on December 3, including a preview of upcoming holiday deals. Buyers who hear from you within a week of purchase are significantly more likely to return before Christmas.
• Review request (Dec 5 to 7): Trigger: Order Completed, with a 7-day delay action. Action: Send Email asking for a product review. Seven days gives the customer time to use the product before you ask.
• Inventory reconciliation alert: Use the Schedule Trigger set to December 1 at 9 AM to send an HTTP Request to your warehouse system or a Slack message summarising which SKUs dropped below reorder thresholds during the sale period.
• Segment buyers for January: If you are on Pro and using FluentCRM, the Order Completed trigger can apply a “BFCM 2026 buyer” tag to every customer automatically. That tag becomes your January re-engagement segment without any manual list building.

Our companion post on WordPress automations to set up before Black Friday covers the broader pre-sale preparation if you want to go deeper on timing.

The post-sale window is where most stores leave money on the table. Your BFCM buyers are warmer than any other segment you have, and the window to act is short.

Free vs Pro: Which Plan Do You Actually Need for Black Friday?

What you want to do	Free	Pro
Order Completed and Order Created triggers	Yes	Yes
Send transactional emails with merge tags	Yes	Yes
Conditional branching (first purchase, failed payment, low stock)	Yes	Yes
Delay scheduling (30-minute recovery email, 7-day review request)	Yes	Yes
Slack and SMS alerts via HTTP Request	Yes	Yes
Workflow simulator for dry-run testing	Yes	Yes
Schedule Trigger for timed campaign emails	No	Yes
Mailchimp, FluentCRM, ActiveCampaign integration	No	Yes
Visual email builder for branded transactional emails	No	Yes
Incoming webhook receiver for external triggers	No	Yes
80+ additional triggers and 60+ additional actions	No	Yes

The free version handles the four core workflows described above without restriction. You need Pro if you want timed campaign emails, native email marketing integrations, or branded transactional emails built with the visual email builder. See the free vs Pro comparison for the complete breakdown.

Pro plans start at $69 a year for one site, or $199 as a one-time lifetime payment. There is a 14-day money-back guarantee on every plan. Compare all three plans to find the right fit for your number of sites.

What Are the Real Costs of Running This Manually Instead?

If you skip automation and handle BFCM manually, here is what that actually looks like in hours. A typical BFCM weekend for a mid-size WooCommerce store involves roughly 200 to 500 orders over four days. Manually sending order follow-ups, checking stock levels, and fielding failed payment queries at that volume takes 8 to 12 hours of staff time across the weekend, at a minimum.

A developer building these workflows from scratch in custom code would charge between $500 and $1,500 depending on complexity. Krom Automation Pro for one site costs $69 a year, or $199 as a lifetime purchase. The math is not close.

If you are managing Black Friday automation across multiple client stores, the Standard plan at $149 a year covers 5 site activations. The WordPress automation across multiple client sites post covers how to structure that work efficiently.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. If you want to run a Black Friday customer preference survey or a product feedback poll, Pollify builds it as real editor blocks with no shortcodes and no separate interface to configure.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to search orders, switch products, update stock status, and run WooCommerce actions without clicking through menus. During a high-volume sale weekend when speed matters, it saves more time than it sounds like it would.

Our Verdict: Who Should Act on This Now?

If you are running a WooCommerce store and Black Friday is four weeks away, start with the free plugin today. Install it, build the Order Completed confirmation workflow, and confirm your Action Scheduler is processing correctly. That single step eliminates the most common failure mode: discovering on November 27 that background jobs are not running.

If you want timed campaign emails, email marketing integrations, or branded transactional emails, upgrade to Pro before November 14. That gives you two weeks to build and test the additional workflows before the sale starts. Do not upgrade on November 25 and expect to have everything working correctly by the 27th.

If you are an agency running BFCM automation across multiple client stores, the Standard plan covers 5 sites and includes every Pro feature. That is the right tier. Trying to manage client automations on individual free installs is the slower path.

Download the free plugin from the WordPress.org plugin directory and run your first workflow today. See full pricing details for Pro if you need the Schedule Trigger or integrations before November 27.

Frequently Asked Questions

Does Krom Automation work with WooCommerce Subscriptions?

Yes. The WooCommerce Subscriptions integration adds subscription-specific triggers in Pro, including renewal events and cancellation triggers. For a Black Friday subscription promotion, you can fire a workflow whenever a new subscription is created during the sale window.

Can I send emails to Mailchimp lists automatically when an order completes?

Yes, but this requires Pro. The Mailchimp integration lets you subscribe contacts, apply tags, and trigger automations directly from Order Completed. On the free version, you can approximate this with an HTTP Request action pointing to the Mailchimp API.

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

Krom Automation sends a failure notification email and retries automatically with configurable backoff. Every execution is logged step by step in the execution history, so you can see exactly where a workflow failed and why. Our post on automations that fail silently explains how to catch these before they cause real problems.

Can I run the same Black Friday workflows on multiple client stores?

Yes. Krom Automation supports workflow import and export as portable JSON.

Build the workflow once, export it, and import it on each client site. You will need to update site-specific settings like email addresses and Slack webhook URLs after importing, but the workflow structure transfers completely.

Will WP-Cron cause delays during a high-traffic Black Friday sale?

On a high-traffic store during BFCM, WP-Cron fires frequently because every page load can trigger it. The risk of late execution is highest on low-traffic sites.

If your store is expecting significant Black Friday volume, WP-Cron timing is not the thing to worry about. If you are cautious, configure a real server cron job to call wp-cron.php every minute for the sale weekend.

Is there a way to test my Black Friday workflows without sending real emails?

Yes. The workflow simulator runs a complete dry-run with zero side effects.

You supply test order data and the simulator steps through every node, showing what each action would produce without actually executing it. Use it on every workflow at least once before November 27.

The eight WordPress automations every store needs before Black Friday 2026 are: order alerts to your team, low stock warnings, failed payment recovery, post-purchase review requests, VIP early access emails, Cyber Monday follow-up, post-sale teardown workflows, and a stress test run before the sale opens. Krom Automation covers all eight, and most run on the free plugin. The Schedule trigger, incoming webhook, and visual email builder require Pro, but the core order and stock workflows do not.

Black Friday 2026 falls on November 27. Cyber Monday is November 30. That gives you a hard deadline, not a rough target.

Workflows you build in October run during the quietest week of the retail year. Workflows you try to configure on November 26 get tested under real load, with real customers, with no margin for error.

This checklist is ordered by impact. Work through it in sequence. Skipping ahead to the VIP email sequence before order alerts are wired up means your team will not know an order failed while you are busy crafting subject lines.

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

Quick Summary: 8 Automations, Free vs Pro, and When to Build Each

Workflow	Free or Pro	Build by	Template available
Order alerts to team	Free	Oct 31	Yes
Low stock warnings	Free	Oct 31	Yes
Failed payment recovery	Free	Nov 7	Yes
Post-purchase review request	Free	Nov 7	Yes
VIP early access email	Pro (Schedule trigger)	Nov 14	Yes
Cyber Monday follow-up	Pro (Schedule trigger)	Nov 14	Yes
Post-sale teardown	Pro (Schedule trigger)	Nov 14	No
Simulator stress test	Free	Nov 21	N/A

Why Black Friday Breaks Manual Processes

On a normal Tuesday your store might process 20 orders. On Black Friday it might process 200, and those orders arrive in bursts rather than spread evenly through the day. Every manual step that takes 2 minutes on a quiet day takes the same 2 minutes on a peak day, except now there are 10 times as many of them and customers are watching a countdown timer.

The workflows below replace manual steps with automated responses that fire the moment a trigger condition is met, whether that is an order placed, a stock level crossed, or a payment declined. How Krom Automation works is a useful reference if you are new to the trigger-action model before you start building.

The workflows you skip in October are the ones you will spend Black Friday morning building by hand, under pressure, in front of angry customers.

Workflow 1: Order Alerts to Your Team (Build by October 31)

When an order completes, your fulfilment team needs to know within seconds, not when someone next checks the WooCommerce dashboard. The Order Completed trigger in Krom Automation fires immediately and can send a Slack message, an email, or both, with the order number, customer name and total pulled in via merge tags.

On peak days this matters because delayed fulfilment is the most common source of 1-star reviews after Black Friday. A team alert that fires 30 seconds after payment clears means picking and packing can start before the customer has closed the confirmation tab. The messaging integrations for Slack, Discord, Twilio and Telegram cover setup for each channel.

• Trigger: Order Completed (WooCommerce, free)
• Action: Send Email to fulfilment team, or HTTP Request to Slack webhook
• Merge tags to include: order number, customer name, order total, items ordered
• Template: Available in the 20 free templates under the WooCommerce category

Workflow 2: Low Stock Warnings (Build by October 31)

Running out of a bestseller at 11am on Black Friday and not knowing until a customer complains is an avoidable problem. WooCommerce does send a default low stock email, but it goes to the admin email address and carries no context about which supplier to contact or what the reorder lead time is.

A Krom Automation workflow triggered by a stock threshold can send a richer alert, route it to the right person, and log the event for reporting. Our full guide on setting up WooCommerce low stock notification emails covers the trigger configuration in detail. Set the threshold higher than you think you need it: if your reorder lead time is 3 days and you sell 50 units a day on Black Friday, a warning at 100 units remaining is not paranoid, it is arithmetic.

• Trigger: Order Completed, with a conditional branch checking remaining stock
• Action: Send Email to purchasing manager
• Condition: Stock quantity falls below your reorder point
• Template: Available in the free WooCommerce workflow templates

Workflow 3: Failed Payment Recovery (Build by November 7)

Payment failures spike on Black Friday because customers are using unfamiliar cards, hitting credit limits, or experiencing bank fraud holds triggered by an unusual large purchase. WooCommerce records these as failed orders. Without automation, they sit there until someone manually reviews the order list, which on a peak day may be never.

A workflow triggered by Order Created with a conditional branch checking for failed status can send a recovery email within 5 minutes of the failure, while the customer is still at their desk and still wants to buy. A 5-minute recovery window converts at a significantly higher rate than an email sent hours later. The conditions and branching documentation explains how to build the Yes/No logic that routes failed orders to the recovery email and successful orders elsewhere.

• Trigger: Order Created (free)
• Condition: Order status equals Failed
• Action: Send Email with payment retry link and alternative payment options
• Delay: Optional 10-minute delay before a second recovery email if status has not changed

A failed payment email sent 5 minutes after the failure recovers customers. The same email sent 5 hours later recovers receipts they have already forgotten about.

Workflow 4: Post-Purchase Review Request (Build by November 7)

Black Friday generates more orders in 24 hours than many stores see in a typical fortnight. That volume of verified purchases is a rare opportunity to build review count quickly, but only if you ask at the right time.

A review request sent immediately after an order is placed lands before the product arrives. A request sent 7 days after delivery lands when the product is fresh and the customer has formed an opinion.

Build this with a Delay of 7 days after the Order Completed trigger, then send a personalised email using merge tags to pull in the product name and order number. The delays and scheduling documentation shows exactly how to configure the delay unit so it counts from the trigger moment rather than from when the workflow was created. Enable run once per entity to prevent a customer who placed three separate orders from receiving three review requests in the same week.

• Trigger: Order Completed (free)
• Delay: 7 days
• Action: Send Email with review link, personalised with product name merge tag
• Setting: Run once per user to prevent duplicate sends

Workflow 5: VIP Early Access Email (Build by November 14, Pro Required)

Your best customers are the ones most likely to buy again, and the ones most likely to leave if a competitor gives them a better experience. An early access email sent 24 to 48 hours before the public sale opens gives VIP customers a reason to stay subscribed and rewards the behaviour you want to encourage.

This workflow uses the Schedule trigger, which is a Pro feature. You set the exact date and time the email fires, and Krom Automation handles the rest. Set it for November 25 at 9am and the email reaches your VIP segment 48 hours before Black Friday opens.

Combine it with the visual email builder to design a branded email without touching code. If you are syncing your VIP list to Mailchimp or ActiveCampaign, the Mailchimp integration and ActiveCampaign integration let you tag or segment contacts automatically when the workflow fires.

• Trigger: Schedule trigger, November 25 at 9am (Pro)
• Condition: User role equals VIP customer, or user has a specific tag in your CRM
• Action: Send Email with early access link and exclusive discount
• Template: Available in the Pro template library

Workflow 6: Cyber Monday Follow-Up (Build by November 14, Pro Required)

Cyber Monday on November 30 is 3 days after Black Friday closes. Customers who browsed but did not convert on Black Friday are warm leads with a short memory. A Cyber Monday email that references their Black Friday browsing or abandoned cart, sent automatically on the morning of November 30, catches them at a moment when they are already in a buying mindset.

This also uses the Schedule trigger. Build it alongside the VIP early access workflow in the same session, so both are live and tested before November 21. The Schedule trigger documentation covers how to configure one-time sends versus recurring schedules, which matters here because you want this to fire once and not repeat the following Monday.

• Trigger: Schedule trigger, November 30 at 8am (Pro)
• Action: Send Email to your full list or a segment of non-converters
• Merge tags: First name, last browsed product if available via your CRM integration
• Template: Available in the Pro template library

Workflow 7: Post-Sale Teardown (Build by November 14, Pro Required)

This is the workflow nobody else talks about. Every checklist covers setup. Nobody covers teardown.

On December 1 you need sale prices reverted, countdown banners removed, Black Friday coupon codes deactivated, and social posts paused. If you do this manually you will forget at least one thing, and it will stay live for days until a customer queries it.

A teardown workflow uses the Schedule trigger set for December 1 at midnight. Actions can include HTTP Requests to your banner plugin’s API to disable banners, a Change Post Status action to move Black Friday promotional posts back to draft, and an Update Post Field action to revert sale prices.

For coupon deactivation you can use the Update Order Status action combined with a coupon expiry date set in WooCommerce itself, which is simpler than an API call. There is no pre-built template for teardown because every store’s setup is different, but the step-by-step workflow builder guide walks through constructing a multi-action sequence from scratch.

• Trigger: Schedule trigger, December 1 at 12:00am (Pro)
• Actions (sequence): Change Post Status on promotional posts to Draft, HTTP Request to disable banner plugin, Update Post Field to clear sale prices
• Benefit: Nothing stays live past its end date because a human forgot to log in

The teardown is where manual processes fail most visibly. A sale price still showing on December 5 creates refund requests, not repeat customers.

Workflow 8: Team Alerts via Slack or SMS (Bonus, Free)

Beyond order fulfilment alerts, your team benefits from real-time notifications for anything that requires human attention: a very high value order that needs manual review, a refund request on a specific product category, or a spike in failed payments that might indicate a card testing attack. Each of these is a separate workflow with a different trigger condition.

The HTTP Request action in the free version supports POST requests with JSON bodies, which is all Slack’s incoming webhook needs. See our post on WooCommerce order alerts to Slack and SMS with Twilio for the exact payload structure. For SMS you will need a Twilio account, and the same HTTP Request action handles the Twilio API call directly.

What Breaks at Scale: WP-Cron and the Honest Limitation

Krom Automation runs workflows via Action Scheduler, which means nothing executes during a page load. That is the right architecture.

However, Action Scheduler depends on WordPress Cron, and WordPress Cron depends on site traffic to fire. On a low-traffic site where no visitors arrive for 2 hours, a workflow scheduled for 3pm might not fire until 5pm.

On Black Friday your traffic is not low, so this is less of a concern than on a quiet Tuesday in March. But the Schedule trigger workflows, specifically the VIP email and Cyber Monday follow-up, should have a real server cron job configured rather than relying on WP-Cron alone.

Most managed WordPress hosts provide this via their control panel in under 5 minutes. This is worth doing before November 21 so you can verify it is firing on schedule during your stress test.

How to Stress Test Before the Sale Starts (Do This by November 21)

Krom Automation includes a workflow simulator that runs a dry-run of any workflow with zero side effects. No emails are sent, no posts are changed, no Slack messages fire.

The simulator steps through each node and shows you exactly what data would flow through, where a conditional branch would route, and which merge tags would resolve to what values. Use it on every workflow in this list before Black Friday week begins.

The workflow simulator documentation explains how to load test data into the simulator and read the per-step audit output. Pay specific attention to workflows with conditional branches: a branch condition that is too narrow may route every order down the No path and silently skip all your recovery emails. Silent failures on automation are the hardest kind to diagnose under pressure, which is why we wrote a separate post on what happens when an automation fails silently.

• Run the simulator on every workflow by November 21, 6 days before Black Friday
• Check that merge tags resolve to real values, not empty strings
• Verify that conditional branches route correctly for both the Yes and No paths
• Confirm that run once per entity is enabled on any workflow that should not repeat per customer
• Check the execution log after one live test order to confirm the workflow fired and all steps completed

What Each Plan Costs Across Different Store Sizes

Store count	Free tier	Pro Basic (1 site)	Pro Standard (5 sites)	Pro Enterprise (unlimited)
1 store	$0/year	$119/year or $299 lifetime	$199/year or $499 lifetime	$369/year or $799 lifetime
5 stores	$0/year	5 x Basic = $595/year	$199/year or $499 lifetime	$369/year or $799 lifetime
10+ stores	$0/year	Not viable per-site	Not viable per-site	$369/year or $799 lifetime

For a single store running Black Friday campaigns, Pro Basic at $119 per year unlocks the Schedule trigger, visual email builder, and all 101 Pro templates. The breakeven against the Standard plan is at 2 stores.

Agencies managing 10 or more client stores should compare the Enterprise lifetime price of $799 against annual fees: year 3 and beyond is fully covered with no renewal. Compare all three plans in detail before choosing.

The Setup Timeline Counting Back from Black Friday

• October 31: Order alerts and low stock warnings live and tested
• November 7: Failed payment recovery and review request workflows live
• November 14: VIP early access, Cyber Monday follow-up, and teardown workflows built
• November 21: Simulator stress test complete on all 7 workflows, server cron confirmed
• November 25, 9am: VIP early access email fires automatically
• November 27: Black Friday opens. All workflows running in the background.
• November 30, 8am: Cyber Monday follow-up fires automatically
• December 1, 12am: Teardown workflow fires. Sale is over and cleaned up.

Also from wpRigel

Pollify is our Gutenberg native poll, survey and quiz plugin. If you want to run a post-Black Friday customer satisfaction survey or gather product feedback during the sale, Pollify adds it as a real block inside the editor with no shortcodes and no separate interface to learn.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump to any order, product, customer or setting without clicking through menus.

During Black Friday when speed matters, it is the fastest way to review a flagged order or update a stock level without navigating the full WooCommerce screen. It is the only WordPress command palette with real WooCommerce order, product and customer commands built in.

Our Verdict: Who Should Act on This Now

If your store processed more than 50 orders on last Black Friday, every workflow in this list will pay for itself before Cyber Monday closes. The free plugin covers the highest-impact workflows: order alerts, low stock warnings, failed payment recovery, and review requests. Those four alone, built by November 7, will reduce manual intervention by several hours over the sale weekend.

Pro is worth adding if you want the Schedule trigger for timed emails and the teardown workflow. At $119 for a single store, the cost is recovered by one recovered failed payment or one repeat customer from the Cyber Monday follow-up.

Download the free plugin from the WordPress.org plugin directory and build the first two workflows today. The remaining six will follow naturally once you see how the canvas works.

Who should not act yet: stores that have not confirmed their hosting can handle Black Friday traffic levels. Automation adds value on a stable site.

On a site that will slow to a crawl under load, fix infrastructure first. That is a separate conversation from automation, and not one we can shortcut.

See Krom Automation pricing and choose the right plan for your store count.

Frequently Asked Questions

Does the free version of Krom Automation cover the most important Black Friday workflows?

Yes. Order alerts, low stock warnings, failed payment recovery, and post-purchase review requests all run on the free plugin. The Schedule trigger for timed VIP emails and the teardown workflow requires Pro, but those are secondary priorities.

What is the Schedule trigger and why do I need it for timed emails?

The Schedule trigger fires a workflow at a specific date and time, or on a recurring interval. It is a Pro feature. Without it, you can only trigger workflows in response to events like an order or a user action, not at a fixed point in the calendar.

Will the workflows still fire on Black Friday if my site gets a lot of traffic?

Krom Automation uses Action Scheduler to run workflows in the background, so they do not compete with page loads. High traffic actually helps WP-Cron fire on time. Configure a real server cron if you are using the Schedule trigger and want precise timing regardless of traffic levels.

How do I know if a workflow ran correctly during the sale?

Every workflow execution is logged with a per-step audit trail. The analytics dashboard shows total executions, success rate, and failed execution count. Failed workflows trigger an email notification and retry automatically with configurable backoff.

Can I run these automations on multiple WooCommerce stores?

The free plugin runs on as many sites as you like. Pro licences cover 1 site (Basic), 5 sites (Standard), or unlimited sites (Enterprise). For agencies running Black Friday campaigns across multiple client stores, the Enterprise plan is the only one that scales without per-site costs.

What happens to my workflows after Black Friday? Do I need to delete them?

You can pause any workflow without deleting it. The teardown workflow handles time-sensitive cleanup automatically on December 1. Evergreen workflows like order alerts and review requests should stay active year-round since they add value on every order, not just during the sale.

Good WordPress automation documentation is not a nice-to-have. It is the difference between a client who can operate a site independently and one who calls you every time a workflow stops firing. If you are handing over a site built on Krom Automation, this guide covers exactly what to capture, what to abstract for non-technical clients, and how to use the built-in notes field and export features as a documentation layer that travels with the site.

Most automation documentation fails because it describes what a workflow does, not why it exists or what happens when it stops. A client reading “Send Email on User Registered” learns nothing useful.

A client reading “Sends the welcome email with the login link. If this fails, new users see no confirmation and email support volume spikes” knows what to watch and when to panic.

The guide below is written for agency owners and developers handing off client sites. The same principles apply if you are building internal tooling and documenting for a team rather than a client.

Browse the full Krom Automation feature list to see what is available before you decide what needs documenting.

Why Automation Documentation Fails at Handover

The standard handover document covers credentials, hosting details, and plugin licences. It almost never covers the automation layer. That gap matters because automations are invisible when they work and catastrophic when they do not.

A silent automation failure on a WooCommerce site can mean hundreds of orders processed without fulfilment notifications. On a membership site it can mean new subscribers who never receive their access email.

Neither failure throws an error the client sees. They only surface when a customer complains, and by then the damage is done.

An undocumented automation is a liability that transfers with the site. The client inherits the risk but none of the context needed to manage it.

There are three failure modes that handover documentation must prevent:

• The trigger changes and nobody knows the workflow depended on it. A form is renamed or a post type is removed. The workflow still shows as active. Nothing fires.
• A plugin that a workflow depends on gets deactivated or updated. WooCommerce, a CRM plugin, or a forms plugin changes its hook structure. The workflow breaks silently.
• The client edits a workflow without understanding the downstream effects. They change a delay from 24 hours to 0 hours because they want emails faster. Three actions that depended on that delay window now fire simultaneously.

Good documentation does not prevent all of these. It makes each one diagnosable in under 10 minutes rather than 3 hours.

What to Document: The Non-Negotiable List

For each workflow on the site, capture the following. This is the minimum. Anything below this and the handover is incomplete.

1. Business purpose in one sentence. Not a technical description. What happens in the business if this workflow stops running?
2. Trigger: what fires it, and under what conditions. Name the exact trigger, any conditions on the trigger, and what the source is (a specific form, a specific post type, a specific user role).
3. Actions in sequence. List every action in order. Include delays as part of the sequence, not as an afterthought.
4. Dependencies. Which plugins must be active for this workflow to run? If the FluentCRM integration powers a contact tagging step, note that FluentCRM must stay active and at a minimum version.
5. Owner. Who is responsible for this workflow? Whose job breaks if it fails?
6. Last tested date and tester. A workflow that has never been tested in production is an assumption, not a fact.
7. Failure behaviour. What does the client see or not see when this fails? How do they check the execution log?

Seven fields per workflow. On a site with 12 active workflows, that is roughly 4 hours of documentation work.

A developer billing at $120/hour should charge for it, and most should. The alternative is a support ticket backlog that costs more.

Using the Krom Automation Notes Field

Krom Automation includes a notes field on every workflow, visible inside the workflow settings panel. This is not a hidden feature. It is the right place to store the business purpose and dependency information for each workflow, because it travels with the workflow when the site is handed over.

The notes field renders inside the canvas view. A client or future developer opening a workflow sees the note before they see anything else. That means documentation that lives in a separate Google Doc or Notion page, where nobody will look, becomes documentation that is impossible to miss.

The workflow settings documentation covers the notes field alongside the run-once setting, pause controls, and import/export. Read that before you build your first client workflow so the notes habit is built in from the start, not retrofitted at handover.

Our recommended note format for each workflow:

• Purpose: [one sentence business reason]
• Trigger source: [form name, post type, or event]
• Depends on: [plugin names and minimum versions]
• Owner: [name or role]
• Last tested: [date]

Paste this as plain text into the notes field on every workflow before you hand over. It takes 3 minutes per workflow and eliminates the most common support call: “We changed something and now the emails stopped. Can you look at it?”

Export as Portable Documentation

Krom Automation supports workflow export as JSON. Each exported file contains the complete workflow structure: trigger configuration, all actions, delays, conditions, merge tags, and settings. The notes field travels with the export.

For a client handover, export every active workflow and include the JSON files in the handover package alongside credentials and hosting details. This gives you three things:

• A point-in-time snapshot of every workflow as it was at handover
• A restore path if a workflow is accidentally deleted or corrupted
• A portable copy that can be imported to a staging or development environment for testing

The JSON export is also your migration safety net if the client ever moves hosts. Importing 12 workflows from JSON takes under 10 minutes. Rebuilding 12 workflows from memory takes a day.

The export file is the closest thing to version control that most WordPress automation setups will ever have. Treat it like a build artefact, not an afterthought.

Store the exports in the same place as the site backup. If the client uses a project management tool, attach the JSON files to the project closeout ticket so they are searchable later.

What to Abstract for Non-Technical Clients

Not every client needs to understand conditional branching or merge tags. Most need to understand three things: what the workflow does, what it costs them if it stops, and how to tell if it has stopped.

Build a separate one-page summary for the client. This is distinct from the technical documentation above, which is for the next developer. The client summary covers:

• Workflow name (match the name in Krom Automation exactly, so they can find it)
• What it does in plain English (two sentences maximum)
• How often it should run (on every order, daily, on new user registration)
• How to check if it is running (point them to the execution log in the analytics dashboard)
• Who to call if it stops (your support contact or their internal team)

The analytics dashboard in Krom Automation shows total executions, success rate, failed execution count, and an execution trend chart. A client who checks this once a week will catch a silent failure within 7 days. A client who has never been shown the dashboard will call you 6 weeks later wondering why conversion rates dropped.

Documenting Integrations Separately

Integrations deserve their own section in the handover document because they carry external dependencies the client controls, and those dependencies can change without warning.

For each external integration in use, document:

• Which service it connects to (Mailchimp, FluentCRM, Google Sheets, Slack)
• What credential or API key is stored in WordPress
• Who owns that credential (the agency or the client)
• What happens to the workflow if the API key is revoked or the account is closed
• Where to regenerate the credential if needed

If the site sends data to Google Sheets or Google Calendar, note which Google account owns the connection and what happens if that account loses access. If the site posts to social media via the social media integration, note the connected page, the connected account, and the token expiry behaviour.

Messaging integrations to Slack, Discord, Twilio or Telegram are particularly fragile at handover because they use workspace-level credentials the client may rotate during an internal IT change. A single paragraph in the handover document explaining this saves a support call.

For form-triggered workflows, link the integration doc so the next developer can verify the setup. For example, a workflow triggered by Gravity Forms or WPForms will break if the form is renamed or the field mapping changes. That is worth one sentence in the handover notes.

The Handover Documentation Structure

A complete handover documentation package for a site running Krom Automation has four parts. The table below shows who reads each part and what they do with it.

Document	Audience	Format	Lives Where
Workflow notes (per workflow)	Next developer	Plain text in Krom Automation notes field	Inside the plugin, travels with export
Technical handover document	Next developer or internal team	Markdown or PDF	Project folder, handover package
Client summary (one page)	Client or site owner	PDF or shared doc	Client’s preferred tool (Notion, Google Drive, email)
Workflow JSON exports	Next developer, disaster recovery	JSON files	Site backup folder, project archive

The technical handover document should list every active workflow, its dependencies, the credential owner for each integration, and the support contact. It does not need to explain how Krom Automation works. It needs to explain how this specific site’s workflows work.

Cost of Getting This Wrong

Skipping automation documentation is a pricing decision, even if it does not feel like one. The cost lands somewhere. The question is whether it lands on your support hours or on the client’s operations.

Scenario	Without documentation	With documentation
Workflow breaks 3 months post-handover	2 to 4 hours to diagnose without context. $240 to $480 in unbilled support at $120/hr	Client checks execution log, finds the failed step, calls you with the error. 30 minutes to fix
Client changes a plugin and breaks an integration	Root cause unclear. Developer rebuilds from memory. 3 to 6 hours	Dependency listed in notes. Developer restores from JSON export. Under 1 hour
New developer takes over the site	Discovery audit needed. 4 to 8 hours billed to client	Technical handover document covers it. 1 hour onboarding
API key rotated, integration breaks	Unknown which workflows are affected. Full audit required	Integration doc lists credential owner and regeneration steps. Fixed in 20 minutes

Across an agency running 20 client sites with automation, the difference between documented and undocumented handovers is realistically 40 to 80 support hours per year. At $120/hour, that is $4,800 to $9,600 in unrecoverable time.

Charging $300 to $500 per site for a documentation package at handover is not overhead. It is margin recovery.

Charging for handover documentation is not adding a line item. It is pricing the risk correctly instead of absorbing it silently in your support queue.

Testing Before You Hand Over

Documentation of an untested workflow is documentation of an assumption. Before any handover, run every workflow through the simulator.

Krom Automation includes a workflow simulator for dry-run testing with zero side effects. It runs the workflow logic without sending emails, creating posts, or firing HTTP requests. Use it to verify that every branch executes as expected and that merge tags resolve correctly.

For workflows that cannot be fully validated by simulation, such as those that depend on a live payment gateway or a production form submission, document the test procedure in the handover notes. Describe the exact steps, the expected output, and how to check the execution log to confirm it ran. The client or next developer should be able to run the test themselves in under 15 minutes.

If a workflow has never been tested in production, say so in the handover document. An honest note that says “validated in staging but not confirmed in production” is more useful than silence. It tells the next person where to start.

Multi-Site and Agency Considerations

If you are managing automation across multiple client sites, the documentation burden multiplies quickly. The answer is not to document less. It is to standardise the documentation format so each site takes less time.

We cover the broader strategy for WordPress automation across multiple client sites in a separate guide, including how to build reusable workflow templates and what to centralise versus what to configure per site. The short version: standardise the workflow structure, standardise the notes format, and export templates from your reference build rather than rebuilding from scratch for each client.

Krom Automation’s import/export system is designed for exactly this. Build a workflow on one site, export the JSON, and import it to a new client site in under 2 minutes. The notes field travels with the import, which means your documentation template travels too.

For agencies evaluating the cost model across client sites, the per-site cost analysis we published covers what automation tooling actually costs at 1, 5, 10 and 20 sites, including licence costs, time costs, and the break-even point between free and Pro tiers.

Also from wpRigel

Pollify is wpRigel’s Gutenberg-native poll, survey and quiz plugin. Polls are built as real blocks inside the block editor, so there are no shortcodes to paste and no separate interface to learn. It pairs naturally with automation workflows that trigger on user responses.

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.

For developers managing client sites, it is the fastest way to navigate without knowing every menu path. It is the only command palette with real WooCommerce order, product and customer commands built in.

Our Verdict

If you are handing over a WordPress site with active automations and you have not written workflow notes, exported the JSON files, and produced a one-page client summary, the handover is not complete. It will cost you or your client time within 6 months.

That is not a prediction. It is the pattern we see repeatedly across agency builds.

The tools to do this correctly are built into Krom Automation: the notes field, the JSON export, the execution log, the analytics dashboard, and the workflow simulator. None of them require extra setup. They require the habit of using them before you hand over, not after the first support ticket arrives.

Who should invest in this now: any agency handing over more than 3 client sites per quarter, and any developer who has ever spent a Saturday debugging an automation they built 8 months ago and cannot remember. Who can wait: teams where all automation is internal, the codebase is under version control, and the same developer maintains it indefinitely.

The free version of Krom Automation is available on the WordPress.org plugin directory with no trial period and no feature caps. If you are evaluating it for client work, start there and review the free vs Pro comparison before you decide whether the Pro integrations are worth it for your stack.

See the full Krom Automation pricing and plan details to find the right licence for your site count.

Frequently Asked Questions

Where does automation documentation live in Krom Automation?

Each workflow has a notes field inside the workflow settings panel. Text entered there travels with the workflow when exported as JSON, making it the most reliable place for handover documentation. It is visible to any developer who opens the workflow on the destination site.

What happens to workflows if a dependent plugin is deactivated?

The workflow remains active in Krom Automation but the affected triggers or actions will fail to execute. The failure is logged in the execution history with a per-step audit trail, which is how you diagnose it. Documenting plugin dependencies at handover is what makes this diagnosable in minutes rather than hours.

Can I export all workflows at once for a client handover package?

Krom Automation exports workflows individually as JSON files. For a full site handover, export each active workflow separately and bundle the files in the handover package. Each file is self-contained and can be imported to a new or staging environment without any additional configuration.

How does the workflow simulator help with handover testing?

The simulator runs the full workflow logic without executing any real actions, so you can verify trigger conditions, branch logic, and merge tag resolution without sending emails or modifying data. It is the right tool for pre-handover validation and for testing changes on a live site without side effects.

Is Pro required to use the notes field and JSON export?

No. Both the workflow notes field and JSON import/export are included in the free version of Krom Automation. You do not need a Pro licence to document and export workflows as part of a client handover.

You can connect WooCommerce to Mailchimp without Zapier using Krom Automation, a native WordPress plugin. The free version handles basic subscriber sync. The Pro version adds the Mailchimp action that subscribes contacts, applies tags, and updates audience fields directly from any WooCommerce trigger, at no per-task cost.

The official Mailchimp plugin for WooCommerce handles audience sync reasonably well, but it gives you a fixed pipeline. You cannot add conditional logic, delay the subscription, branch based on order value, or chain Mailchimp into a wider workflow. Krom Automation treats Mailchimp as one action inside a workflow you control, which means you can subscribe a customer, send an internal Slack alert, and update a Google Sheet in the same automation without touching Zapier.

This guide follows the integration post structure: what syncs, how to set it up step by step, what does not transfer, the three real failure modes, and a verdict on when this approach makes sense versus the official plugin.

Browse the full Krom Automation feature list to see what else you can connect alongside Mailchimp.

What Gets Synced: WooCommerce to Mailchimp

The table below shows every data point the Krom Automation Mailchimp integration can pass from WooCommerce to Mailchimp, and exactly where it lands in your audience. Fields not listed here do not transfer automatically and require a custom HTTP Request action or a separate workflow step.

WooCommerce Field	Where It Lands in Mailchimp
Customer email address	Audience contact email (primary identifier)
First name	FNAME merge field
Last name	LNAME merge field
Order total	Custom merge field (mapped manually in workflow)
Order status	Tag applied to contact (e.g., “order-completed”)
Product name(s)	Tag or custom merge field (one per workflow action)
Billing country	Custom merge field or audience segment data
Opt-in status at checkout	Subscribed vs. non-subscribed contact status
Workflow-assigned tag	Tag on Mailchimp contact, set per workflow branch

Order line items beyond the first product require a loop or separate action per product. There is no native array-to-tag bulk operation. If your store sells bundles with 8 to 12 line items and you need every product tagged individually, plan for that complexity before you build the workflow.

Requirements Before You Start

• WordPress 6.2 or higher
• PHP 7.4 or higher
• WooCommerce installed and active
• Krom Automation free plugin active (handles the WooCommerce triggers)
• Krom Automation Pro active (required for the Mailchimp subscribe action)
• A Mailchimp account with at least one audience created
• A Mailchimp API key with read/write access

The free Krom Automation plugin gives you the Order Created and Order Completed WooCommerce triggers at no cost. The Mailchimp action itself is a Pro integration.

See the full free vs. Pro comparison if you want to check which other actions require the Pro licence before committing.

Step-by-Step Setup

Step 1: Install and Activate Krom Automation

Go to Plugins > Add New Plugin in your WordPress admin. Search for “Krom Automation” and install the plugin listed by wpRigel. Activate it.

A new Krom Automation menu item will appear in your left admin sidebar. If you have the Pro licence, upload the Pro zip at Plugins > Add New Plugin > Upload Plugin and activate it alongside the free plugin. The Pro installation guide covers licence key activation and what to do if the Pro features do not appear after activation.

Step 2: Connect Your Mailchimp Account

Go to Krom Automation > Settings > Integrations. Find the Mailchimp card and click Connect. You will be prompted for your Mailchimp API key.

Paste it into the API Key field and click Save. Krom Automation will verify the key and display your account name if the connection succeeds. If you see a “401 Unauthorized” error, the key does not have the required audience read/write scope, generate a new one from your Mailchimp account under Account > Extras > API Keys.

Step 3: Create a New Workflow

Go to Krom Automation > Workflows > Add New. This opens the visual workflow builder canvas. Click the Add Trigger node at the top of the canvas.

From the trigger panel on the right, select the WooCommerce category, then choose Order Completed as your trigger. If you want to subscribe customers the moment they place an order rather than after payment clears, choose Order Created instead. The difference matters for refund handling, which we cover in the limitations section below.

Step 4: Add the Mailchimp Subscribe Action

Click the plus icon below your trigger node to add an action. Select the Mailchimp category from the action panel.

Choose Subscribe Contact. The action card will show the following fields, all of which are required unless marked optional:

• Audience: select your Mailchimp audience from the dropdown (populated automatically from your connected account)
• Email Address: use the merge tag {{order.billing_email}}
• First Name: use {{order.billing_first_name}}
• Last Name: use {{order.billing_last_name}}
• Status: set to Subscribed if opt-in was captured, or Pending to trigger Mailchimp’s double opt-in email
• Tags (optional): enter a static tag such as “woo-customer” or use a merge tag to apply a dynamic value

The merge tags documentation lists every available WooCommerce order variable you can inject into action fields, including order total, product names, and billing address components.

Step 5: Add Conditional Branching (Recommended)

If you only want to subscribe customers who opted in at checkout, add a Condition node between the trigger and the Mailchimp action. Click the branch icon on the trigger node. Set the condition to: Order > Customer opt-in > equals > true.

Connect the Yes path to the Mailchimp subscribe action. Leave the No path empty or route it to a different action.

This single step prevents you from adding non-consenting contacts to your audience, which matters for GDPR compliance and Mailchimp’s own terms of service. The conditions and branching documentation covers every available operator and how to stack multiple conditions in a single node.

Step 6: Test with the Workflow Simulator

Before setting the workflow live, click Simulate in the top toolbar. The simulator runs every node against a sample payload with zero side effects: no real Mailchimp contact is created, no email is sent.

You can verify that your merge tags resolve correctly and that the conditional branch routes as expected. Fix any errors the simulator flags, then click Activate to set the workflow live.

A workflow that looks correct in the builder and fails silently on real orders is the most expensive kind of mistake. Run the simulator before you activate, not after you notice missing subscribers.

What Does NOT Transfer: Honest Limitations

Most integration guides skip this section. We will not, because this is where stores waste hours debugging something that was never going to work.

• Historical orders: Krom Automation is event-driven. It fires when something happens from the moment the workflow is active. Customers who ordered before you activated the workflow are not synced retroactively. If you need to backfill 3,000 existing customers, export them from WooCommerce as CSV and import directly into Mailchimp.
• Automatic unsubscribes on refund or cancellation: The free WooCommerce triggers include Order Created and Order Completed, but not a dedicated “Order Refunded” trigger in the free tier. You can handle this in Pro with a Post Status Changed trigger on the shop_order post type, but it requires an additional workflow. Do not assume a cancelled order removes the contact from Mailchimp automatically.
• Mailchimp e-commerce data (purchase history, revenue): The Mailchimp subscribe action adds and updates contacts. It does not write to Mailchimp’s e-commerce data layer (orders, products, revenue), which the official Mailchimp plugin populates via a separate API. If you rely on Mailchimp’s purchase-based segments or revenue reporting, you need the official plugin running alongside Krom Automation, or you need to write to Mailchimp’s Orders API via the HTTP Request action.
• Abandoned cart: Krom Automation does not currently fire a trigger on cart abandonment. Abandoned cart emails require the official Mailchimp plugin or a dedicated WooCommerce abandoned cart plugin that exposes a hook Krom can listen to.
• Checkout Block opt-in checkbox: The native WooCommerce Checkout Block does not expose a Mailchimp opt-in checkbox in the same way the classic checkout does. If your store uses the Checkout Block, test the opt-in field rendering before going live. The Mailchimp official plugin has better handling of the Checkout Block opt-in at present.

For stores that need WooCommerce Subscriptions events such as subscription created, cancelled, or renewed, the WooCommerce Subscriptions integration documentation covers the additional triggers available in Pro and how to chain them into Mailchimp or any other email platform.

The official Mailchimp plugin and Krom Automation are not rivals here. For stores that need Mailchimp’s e-commerce data layer populated, running both is the honest answer.

Troubleshooting: The Three Real Failure Modes

Failure 1: Customers Appear as “Non-Subscribed” Instead of “Subscribed”

This is the most common complaint. The cause is almost always one of two things. First, the Status field in your Mailchimp subscribe action is set to Pending, which means Mailchimp sends a confirmation email and the contact stays non-subscribed until they click.

If you captured consent at checkout and want immediate subscription, change the Status field to Subscribed. Second, Mailchimp’s own audience settings may have double opt-in forced on at the audience level. Check under Audience > Settings > Audience name and defaults in Mailchimp and disable double opt-in if you want single opt-in behaviour from the API.

Failure 2: Workflow Fires but No Contact Appears in Mailchimp

Open Krom Automation > Execution Logs. Find the execution for the order in question and expand the Mailchimp action step. The log will show either a success response or the exact error Mailchimp returned.

The two most common errors are “Invalid API Key” (the key was regenerated in Mailchimp after you connected) and “Audience not found” (the audience ID stored in the action no longer matches your Mailchimp account). For the API key issue, go to Krom Automation > Settings > Integrations > Mailchimp and reconnect. For the audience mismatch, open the workflow, click the Mailchimp action node, and reselect the audience from the dropdown.

The per-step audit trail in the execution log is the fastest path to the actual error. If you have had silent failures before and want to understand why they are hard to catch, this post on silent automation failures covers the structural reasons and how to set up failure notifications.

Failure 3: Duplicate Contacts or Duplicate Emails

Duplicate contacts in Mailchimp usually mean the workflow is firing more than once per order. This happens when both Order Created and Order Completed triggers are active in separate workflows pointing to the same Mailchimp subscribe action. Decide which event is the correct subscription point and disable the other workflow.

Duplicate transactional emails (the customer receiving two order confirmation emails) are a separate issue caused by WooCommerce’s own emails and a Krom Automation send email action both firing. If Krom Automation handles your order email, disable the equivalent email under WooCommerce > Settings > Emails. Enable Run Once Per Entity in the workflow settings to prevent the same order ID from triggering the same workflow twice, regardless of how many times the order status changes.

Official Plugin vs. Krom Automation: Which Setup Fits Your Store

The right choice depends on what you are trying to accomplish. This table answers the decision rather than listing features side by side.

Your Situation	Better Fit	Why
You need Mailchimp’s purchase history, revenue data, and e-commerce segments	Official Mailchimp plugin	Writes to Mailchimp’s e-commerce API layer; Krom does not
You want abandoned cart emails through Mailchimp	Official Mailchimp plugin	Has built-in cart abandonment tracking
You want to subscribe customers AND post to Slack, update a Sheet, and tag in a CRM in one workflow	Krom Automation Pro	Mailchimp is one action in a multi-step workflow; official plugin is Mailchimp only
You need conditional logic (only subscribe if order total exceeds $100)	Krom Automation Pro	Visual conditional branching; official plugin has no equivalent
You want to avoid per-task fees from Zapier at scale	Krom Automation Pro	Flat annual fee, no execution caps, self-hosted
You run 10+ WooCommerce client sites and need one licence	Krom Automation Pro Enterprise	Unlimited sites for $369/year or $799 lifetime
You use the WooCommerce Checkout Block and need opt-in checkbox support	Official Mailchimp plugin (currently)	Better Checkout Block integration at this time

For stores that need both the e-commerce data layer AND multi-step workflow logic, running the official plugin and Krom Automation together is a workable combination. The official plugin handles the Mailchimp-specific data sync.

Krom handles everything else. They do not conflict.

Scaling Considerations for High-Volume Stores

Krom Automation executes workflows via Action Scheduler, which means no workflow runs during a page load. At 500 to 1,000 orders per day, the queue processes in the background without affecting frontend performance.

The execution log stores a per-step audit trail in 9 custom database tables, so log size grows with volume. For stores processing more than 2,000 orders per day, review your log retention settings under Krom Automation > Settings > Logs and set a retention window (30 or 60 days) to prevent table bloat.

The Mailchimp API enforces a rate limit of 10 concurrent connections. On very high volume days (Black Friday, for example), queued workflows may take 20 to 40 minutes to fully process if order volume spikes above normal. Contacts will be subscribed, just with a delay.

If same-day subscription timing is critical for a campaign, test your queue throughput before the event. Our Black Friday WooCommerce prep guide covers queue and performance considerations in more detail.

Going Further: Related Integrations

If Mailchimp is not the right fit for your store, Krom Automation connects to several other email platforms using the same workflow structure. The setup pattern is identical: pick your WooCommerce trigger, add the platform action, map your merge tags, add a condition if needed. Detailed documentation is available for ConvertKit, MailerLite, ActiveCampaign, and FluentCRM.

For form-based subscription workflows, where a Gravity Forms or WPForms submission triggers the Mailchimp subscribe action rather than a WooCommerce order, see the Gravity Forms integration documentation and the WPForms integration documentation. The merge tag structure differs slightly from the WooCommerce fields shown above, but the Mailchimp action configuration is identical.

Every hour you spend configuring Zapier tasks for a WooCommerce-to-Mailchimp connection is an hour you are paying for infrastructure that lives outside your site, outside your control, and on a billing meter that grows with your order volume.

Also from wpRigel

Pollify is our 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 configuration interface to learn. It is a natural complement to a WooCommerce store running post-purchase surveys or NPS feedback collection.

Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search anything, and run admin actions without clicking through menus. It is the only command palette plugin with genuine WooCommerce depth: search orders by number, customer name or email, change order status, update product prices and stock, and manage customers, all without leaving the keyboard.

Our Verdict

Use Krom Automation for this integration if you need Mailchimp as part of a wider workflow, want to avoid Zapier’s per-task billing, or manage multiple WooCommerce sites under one licence. The Pro Enterprise plan at $369 per year covers unlimited sites, which works out to under $37 per site across a 10-site agency portfolio. That compares well against Zapier’s Growth plan at $299 per month for 2,000 tasks, which a mid-size WooCommerce store can exhaust in a week during a promotion.

Do not use Krom Automation as your sole Mailchimp connection if Mailchimp’s e-commerce segments, purchase-based automations, or revenue reporting are central to your marketing strategy. Those depend on Mailchimp’s e-commerce data layer, which requires the official plugin.

For stores where abandoned cart is the primary use case, the official Mailchimp plugin remains the simpler path. The honest answer is that these two tools solve different parts of the problem, and for many stores, both running together is the right call.

Download the free Krom Automation plugin from the WordPress.org plugin directory to get the WooCommerce triggers active, then see the Pro pricing when you are ready to add the Mailchimp action.

Frequently Asked Questions

Does WooCommerce integrate with Mailchimp natively, or do I need a plugin?

You need a plugin. WooCommerce has no built-in Mailchimp connection.

The two main options are the official Mailchimp for WooCommerce plugin (free, handles the e-commerce data layer) and Krom Automation Pro (paid, handles Mailchimp as part of a multi-step workflow). For most stores, the choice depends on whether you need Mailchimp’s purchase-based segments or whether you need Mailchimp connected alongside other tools in the same automation.

Why are my customers showing up as non-subscribed contacts in Mailchimp?

The two most common causes are: the Status field in the Mailchimp action is set to “Pending” instead of “Subscribed”, which triggers Mailchimp’s double opt-in flow before the contact activates; or double opt-in is forced on at the audience level in Mailchimp under Audience > Settings > Audience name and defaults. Change the Status field to “Subscribed” and disable audience-level double opt-in if you want immediate subscription without a confirmation email.

Can I send abandoned cart emails through this setup?

Not with Krom Automation alone. Krom Automation fires on WordPress and WooCommerce events, and abandoned cart is not a WooCommerce event in the standard sense as no order is created.

You need a dedicated abandoned cart plugin that captures the incomplete session and fires a hook, or you use the official Mailchimp plugin, which has built-in cart tracking. Krom Automation can handle everything that happens after an order exists.

How do I stop WooCommerce and my Mailchimp workflow from sending duplicate order emails?

If Krom Automation is sending a custom order confirmation email, disable the equivalent WooCommerce default email under WooCommerce > Settings > Emails. Find the email type (e.g., “Processing Order”), click Manage, and set it to disabled. The two systems will otherwise both fire independently for the same order event, and the customer receives two identical emails within seconds of each other.

What does this cost compared to running the same workflow through Zapier?

Krom Automation Pro starts at $119 per year for one site with no execution caps. Zapier’s Starter plan is $29.99 per month ($359.88 per year) with a 750-task cap per month. A WooCommerce store completing 100 orders per month and running 3 Zap steps per order uses 300 tasks monthly, leaving 450 in the buffer.

At 250 orders per month with 3 steps, you exceed the Starter cap and move to the Professional plan at $73.50 per month ($882 per year). Krom Automation’s cost does not change regardless of order volume.

Does this integration work with WooCommerce Subscriptions?

Yes, through Krom Automation Pro. The WooCommerce Subscriptions integration adds triggers for subscription created, cancelled, expired, and renewed.

You can subscribe a customer to a Mailchimp audience on initial sign-up and apply a different tag on renewal or cancellation, all in separate workflows. See the WooCommerce Subscriptions integration documentation for the full trigger list and setup steps.