WooCommerce High Value Order Notification: Get Instant Alerts
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:
- Trigger: Order Created
- Branch 1: Order total is greater than or equal to $500. Yes path continues. No path exits.
- 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.
- 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.