AutomatorWP FluentCart GPL v1.0.0

AutomatorWP FluentCart GPL Overview

Here’s a familiar scene: someone buys a product from your FluentCart store, and… that’s it. The order sits in your database. Maybe you get an email notification. Maybe you don’t even check it until you’re running reports weeks later. Meanwhile, you’re manually tagging customers, updating spreadsheets, or copy-pasting order details into a note because your store and the rest of your WordPress site don’t actually talk to each other. AutomatorWP – FluentCart exists to close that gap.

This add-on connects FluentCart, a self-hosted WordPress eCommerce platform built for physical products, subscriptions, downloads, and licenses, directly into the AutomatorWP automation engine. Instead of order events living and dying inside your store’s admin screen, they become triggers that can kick off workflows anywhere else in your WordPress ecosystem. A purchase can award points, send a targeted email, adjust a user’s role, or fire off a notification to another plugin entirely. A refund can reverse those same actions automatically. A subscription renewal can extend access without anyone lifting a finger.

What makes AutomatorWP – FluentCart worth a second look isn’t a long feature list for its own sake. It’s the specificity: distinguishing a full refund from a partial one, catching subscription activations separately from renewals, and letting you add internal notes to orders as part of an automated sequence. These aren’t generic “something happened” triggers. They’re built around how FluentCart stores actually operate day to day.

Feature Breakdown

Purchase and Order Triggers

• User completes a purchase — fires when any order is finalized, useful as a broad entry point into a workflow.
• User purchases a product — narrows things down to a specific product, so you can build workflows unique to individual offers rather than treating every sale the same way.
• User’s order is fully refunded — catches complete refunds so you can reverse access, revoke a license, or adjust user roles accordingly.
• User’s order is partially refunded — a distinct trigger for partial refunds, which matters when a customer only returns part of an order and you don’t want to treat it the same as a full cancellation.
• User’s order status changes — a flexible trigger for anyone who wants to build logic around FluentCart’s broader status flow, not just purchase and refund events.