How Do I Sync WooCommerce Customers to FluentCRM?
You can sync WooCommerce customers to FluentCRM in two ways: using FluentCRM’s built-in WooCommerce integration for real-time contact creation at checkout, or using Krom Automation Pro to add tagging workflows, conditional branching, and historical data imports. The native integration is free and covers the basics. Krom Automation Pro is where you build logic around what those customers bought, how much they spent, and what happens next.
This guide covers both paths honestly, including what each one does not do and where things break in practice. If you have been staring at FluentCRM wondering why yesterday’s orders have not appeared as contacts, the troubleshooting section is where to start.
Browse the full Krom Automation feature list to see every WooCommerce trigger and FluentCRM action available before you read on.
Quick Summary
| What you want to do | Native FluentCRM (free) | Krom Automation Pro |
|---|---|---|
| Create a contact when a customer checks out | Yes | Yes |
| Add an opt-in checkbox at checkout | Yes | Not required |
| Tag contacts by product purchased | Basic, via automations | Yes, with conditional branching |
| Import historical WooCommerce customers | Yes, one-time bulk import tool | Via workflow + HTTP Request action |
| React to subscription renewals and cancellations | Limited | Yes, via WooCommerce Subscriptions triggers |
| Branch logic on order total or product category | No | Yes |
| Send to Slack or Google Sheets on purchase | No | Yes, in the same workflow |
| Execution logs per step | No | Yes |
Does FluentCRM Sync WooCommerce Customers Automatically?
Yes, but only for new customers going forward once the integration is enabled. Inside FluentCRM, go to FluentCRM Settings > Integrations > WooCommerce and toggle the integration on. From that point, every completed order creates or updates a contact record automatically, with no third-party plugin required.
What the native integration does at checkout:
- Creates a FluentCRM contact using the billing email address
- Maps billing first name, last name, phone, and address fields to the contact record
- Assigns the contact to any lists or tags you configure in the integration settings
- Optionally shows an opt-in checkbox so the customer actively consents before being added
The opt-in checkbox question matters for GDPR compliance. If you operate in the EU or sell to EU customers, auto-adding every buyer to your CRM without explicit consent sits in a legal grey area. FluentCRM’s opt-in checkbox is the safest route.
The alternative argument, that a purchase relationship constitutes a legitimate interest for transactional email, applies narrowly and should not be treated as blanket permission for marketing. Consult your own legal counsel rather than treating plugin documentation as compliance advice.
How Do I Import Historical WooCommerce Customers?
FluentCRM includes a one-time bulk import tool under Contacts > Import > WooCommerce. It pulls existing customers from your order history and creates contact records in bulk. You can filter by order status, so you can import only customers with completed orders and skip refunded or cancelled ones.
Run this import once after enabling the native integration. After that, new orders are handled automatically. There is no need to re-run the import unless you want to catch customers who checked out as guests during a period before the integration was active.
Guest checkout is the most common reason historical customers are missing. FluentCRM links contacts by email address. If a guest placed an order before FluentCRM was installed, the import tool will still pick them up as long as they provided an email at checkout and their order status matches your filter.
Why Aren’t My WooCommerce Customers Showing Up in FluentCRM?
This is the question nobody else answers directly. Here are the four real causes, in order of how often we see them:
- The integration was not active when the order completed. FluentCRM only syncs orders that complete after the integration is switched on. Orders that completed before that date need the bulk import described above.
- The order status was not “Completed”. The native integration triggers on order completion by default. An order stuck in “Processing” does not create a contact until it reaches the status you have configured.
- A plugin conflict is blocking the WooCommerce hook. Some payment gateways and fulfilment plugins fire their own hooks in a sequence that can interrupt FluentCRM’s listener. Deactivate other plugins in a staging environment to isolate the conflict.
- The contact already exists under a different email. If the customer used a different email for a previous order, FluentCRM treats it as a new contact rather than merging. Check by searching the billing email directly in the Contacts view.
A sync that looks broken is usually a timing problem, not a data problem. Check the order status and the date the integration went live before digging into hooks.
How Do I Tag WooCommerce Customers by Product Purchased?
This is where the native integration starts to show its limits and where Krom Automation Pro earns its place. FluentCRM’s native WooCommerce integration lets you assign a single set of global tags to every buyer. If you want different tags for different products, you need FluentCRM’s own automation builder or a workflow plugin.
With Krom Automation Pro, the setup looks like this:
- Open the visual workflow builder and add an Order Completed trigger from WooCommerce.
- Add a Condition node and set the condition to check which product ID appears in the order.
- On the Yes branch, add the FluentCRM action to add a specific tag to the contact.
- On the No branch, add a second condition to check for a different product, or let the workflow end.
You can stack as many condition branches as you need. An agency running 20 WooCommerce stores will build this once, export it as a portable JSON file, and import it to each new site in under a minute. The workflow import and export documentation covers exactly how that works.
The FluentCRM actions available in Krom Automation Pro include adding contacts to lists, adding tags, removing tags, and updating contact fields. The full reference is in the FluentCRM integration documentation.
What About WooCommerce Subscriptions?
WooCommerce Subscriptions renewals, cancellations, and payment failures are not handled by FluentCRM’s native WooCommerce integration in any meaningful depth. This is the gap that pushes people toward WP Fusion or Make.com, neither of which is self-hosted.
Krom Automation Pro includes a dedicated WooCommerce Subscriptions integration with triggers for renewal payments, cancellations, subscription pauses, and trial expirations. You connect those triggers directly to FluentCRM actions in the same workflow. No external service, no webhook middleman, no per-task billing.
A practical example: when a subscription is cancelled, a workflow removes the “Active Subscriber” tag in FluentCRM, revokes course access in LearnDash (if applicable), and sends a win-back email 3 days later using a delay node. All three steps run from a single workflow, self-hosted on your own server, with full per-step execution logs.
Subscription lifecycle events, renewal, cancellation, trial expiry, are where most native CRM integrations quietly give up. That is exactly where a workflow layer earns its cost.
Building a Full Purchase-to-CRM Workflow in Krom Automation
A complete post-purchase FluentCRM workflow in Krom Automation Pro looks like this, ordered by what has the most impact:
- Trigger: Order Completed (WooCommerce). Fires once per order, enforced by the run-once setting so a customer who places two orders in quick succession does not create duplicate executions.
- Action: Add or Update Contact (FluentCRM). Creates the contact if they do not exist, or updates the record if they do. Merge tags pull the billing name, email, phone, and address directly from the order.
- Action: Add to List (FluentCRM). Adds the contact to your post-purchase nurture list.
- Condition: Check product ID. Branches the workflow based on what was purchased.
- Action: Add Tag (FluentCRM). Applies a product-specific tag on the matching branch.
- Delay: 3 days. Waits before the next action.
- Action: Send Email. Delivers a follow-up email. If you are using the Pro visual email builder, this is a fully branded block-based email, not a plain-text message.
The merge tags documentation shows every dynamic variable available inside action fields, including order total, product names, customer first name, and billing city. Those variables work in email subject lines, email bodies, and any HTTP Request payloads you add later.
You can also add a Google Sheets logging step in the same workflow if you want a spreadsheet record of every purchase alongside your CRM data. The guide to sending WooCommerce orders to Google Sheets shows that setup end to end.
Does Krom Automation Replace FluentCRM’s Native Integration?
No, and we would not recommend treating it that way. The native FluentCRM WooCommerce integration is fast, lightweight, and handles the checkout-to-contact creation step with no overhead. Keep it active.
Krom Automation Pro sits on top of the native integration and handles the logic layer: conditional tagging, subscription events, multi-step sequences, and connections to other tools in the same workflow. The two work alongside each other rather than competing.
If your only requirement is creating a contact in FluentCRM when someone buys, enable the native integration and stop there. If you need product-specific tags, subscription lifecycle handling, or purchase events that also update a Google Sheet, notify a Slack channel, or grant course access, that is where Krom Automation Pro adds value.
| Scenario | Right tool | Time to set up |
|---|---|---|
| Create FluentCRM contact at checkout | Native FluentCRM integration | Under 5 minutes |
| Import existing customer history | Native FluentCRM bulk import | Under 10 minutes |
| Tag contacts by product purchased | Krom Automation Pro | 15 to 30 minutes |
| Handle subscription renewals and cancellations | Krom Automation Pro | 20 to 40 minutes |
| Multi-step post-purchase sequence | Krom Automation Pro | 30 to 60 minutes |
| Cross-tool workflow (CRM + Slack + Sheets) | Krom Automation Pro | 45 to 90 minutes |
A Honest Look at the Limits
Krom Automation Pro runs workflows via Action Scheduler in the background, so nothing executes during page loads and it will not slow down checkout. However, delays in workflows depend on WordPress Cron.
On very low-traffic sites where no page is visited for several hours, WP-Cron fires late. If a 3-day delay needs to be precise, configure a real server cron job rather than relying on WP-Cron alone.
AI actions in Krom Automation require you to supply your own API key. wpRigel never charges per AI call and never marks up tokens.
You pay your AI provider directly at standard rates. That is a deliberate choice that keeps costs predictable at scale, but it does mean one extra setup step.
If you want to test a workflow before it touches live customer data, the workflow simulator runs a dry-run with zero side effects. Use it before enabling any new workflow on a production store.
Every workflow that runs on live customer data should pass a simulator test first. A misfired tag on 3,000 contacts is not a quick fix.
What Krom Automation Pro Costs
The free version of Krom Automation is available on the WordPress.org plugin directory and includes the WooCommerce Order Created and Order Completed triggers, plus 21 built-in actions. FluentCRM-specific actions are a Pro feature.
Pro plans start at $69 a year for a single site, or $199 for a lifetime licence. Agency plans covering 5 sites cost $149 a year or $399 lifetime.
The comparison against the tools ranking above this article is worth spelling out: at the time of writing, Uncanny Automator’s automation plans start at $199 a year for one site. Krom Automation Pro covers the same site for $69 a year, includes every Pro feature and all 25 integrations on every plan, and carries no per-task billing at any tier.
Every Pro plan includes a 14-day money-back guarantee. See the full pricing breakdown before deciding which plan fits your site count.
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 the right tool when you want reader feedback that lives inside the content rather than embedded from an external service.
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere, search every post and user, and run admin actions without clicking through menus. It is the only command palette with genuine WooCommerce depth: search orders by number or customer name, update stock, change order status, and email a customer, all without leaving the palette.
Frequently Asked Questions
Do I need FluentCRM Pro to sync WooCommerce customers?
No. The native WooCommerce integration that creates contacts at checkout is included in the free version of FluentCRM. FluentCRM Pro adds advanced automation sequences, email series, and reporting, but the basic sync works without it.
Can I sync WooCommerce customers to FluentCRM without any third-party plugin?
Yes, for new customers going forward. Enable the native WooCommerce integration inside FluentCRM Settings, and every completed order creates a contact automatically. For conditional tagging, subscription events, and multi-step workflows, a plugin like Krom Automation Pro adds the logic layer that the native integration does not include.
Does Krom Automation Pro require a Krom Automation free plugin as well?
Yes. Krom Automation Pro is an add-on that requires the free plugin installed and active alongside it. The Pro installation guide walks through both steps.
Will the FluentCRM sync break during high-traffic events like Black Friday?
The native FluentCRM integration runs synchronously at checkout. Krom Automation runs workflows via Action Scheduler in the background, so the checkout process itself is not affected. The article on whether Black Friday traffic breaks WordPress automations covers this in more detail, including what to check on shared hosting before a sale event.
How do I tag FluentCRM contacts differently based on what product they bought?
Use a Condition node in Krom Automation Pro after the Order Completed trigger. Set the condition to check the product ID in the order, then apply a different FluentCRM tag on each branch. The conditions and branching documentation shows the exact node configuration.
Can I also tag Black Friday customers separately in FluentCRM?
Yes. Add a second condition to your purchase workflow that checks the order date or a specific coupon code, then applies a Black Friday tag on the matching branch. The guide to tagging Black Friday customers in FluentCRM covers this exact use case with step-by-step instructions.
Our Verdict
Enable FluentCRM’s native WooCommerce integration today. It takes under 5 minutes, it is free, and it handles the majority of what most stores need. Run the bulk import once to bring in historical customers, configure the opt-in checkbox if you have EU customers, and you are done with the basics.
Add Krom Automation Pro when your tagging logic becomes more complex than “every buyer gets the same tag”, when you are selling subscriptions, or when you want purchase events to flow into other tools in the same workflow. At $69 a year for a single site, it costs less than two hours of developer time and pays for itself the first time it prevents a manually missed tag from breaking a post-purchase sequence.
If you are running client sites, the 5-site plan at $149 a year is the one to consider. Build the workflow template once, export it, and import it across every client store. Download the free plugin from the WordPress.org plugin directory to start, and upgrade when the conditional logic is ready.
Compare all Krom Automation Pro plans and pick the right site count.