Description
Order Events Without the Manual Follow-Up
Someone buys a course, and you have to remember to enroll them. A customer asks for a refund, and their access stays live until you notice. A subscription lapses, and the member keeps getting content they stopped paying for. Every one of these is a small chore that grows into a real headache as orders pile up. AutomatorWP – PublishPress Cart connects your checkout to AutomatorWP so those events fire the actions you’ve already decided on, with no one watching the orders screen.
The add-on listens to what happens in PublishPress Cart, the checkout system used to sell digital products, online courses, coaching, memberships, events, and services. When a purchase, refund, renewal, or cancellation takes place, AutomatorWP treats it as a trigger and runs whatever steps you have attached to it. Those steps can be anything AutomatorWP supports: assigning a role, adding a tag in your email tool, sending a message, granting access to content, or logging the event somewhere useful.
Standout Capability: Triggers for the Full Order Lifecycle
Most order integrations stop at “a purchase happened.” The AutomatorWP – PublishPress Cart WordPress plugin goes further and covers what comes after the sale, which is where manual work tends to hide.
Purchase, refund, renewal, and cancellation
Four user-based triggers cover the life of an order or subscription. Each one is tied to a specific product, so you can build a different automation for each thing you sell rather than one rule that fires for everything.
- User purchases a product. Fires when a logged-in customer buys the product you pick.
- User’s order is refunded for a product. Fires when a refund is issued, so you can pull back access or notify your team.
- User’s subscription is renewed for a product. Fires on each renewal, useful for loyalty rewards or keeping a membership level in place.
- User’s subscription is canceled for a product. Fires on cancellation, so you can start an exit sequence or remove privileges.
A guest trigger for checkouts without an account
Not every buyer has an account. The anonymous trigger, Guest completes an order for a product, handles the visitor who checks out without registering. You can still react to that sale, for example by sending a receipt-style follow-up, notifying a team member, or recording the order in another system. That gap is where a lot of stores lose track of customers, and it’s closed here.
Complete Feature Set
The add-on is deliberately focused. It does a handful of things and covers each of them properly.
- A purchase trigger for registered users, scoped to a chosen product.
- A refund trigger that responds when an order is refunded for a product.
- A subscription renewal trigger tied to a specific product.
- A subscription cancellation trigger tied to a specific product.
- An anonymous trigger for guests who complete an order.
- Order tags that expose order information inside the actions you build.
Order tags put real data in your actions
Triggers tell AutomatorWP that something happened. Order tags tell it the details. Drop them into the fields of any action, and the order’s information travels with the automation. A confirmation email can reference what was bought. A note added to a user record can include the order it came from. A webhook sent to an outside service can carry the order data along instead of just announcing that a sale occurred.
This is what makes the automations feel specific rather than generic. Two customers buying two different products can receive two different messages from the same rule, because the content is filled in from each order.
Product-level control
Every trigger asks which product it applies to. That keeps your automations tidy. A coaching package can start an onboarding sequence while a downloadable template pack triggers nothing more than a thank-you note. You build only what each product needs.
How It Fits Your Workflow
You set this up in the AutomatorWP editor, the same place you build every other automation. Pick a trigger from the PublishPress Cart group, choose the product, then add one or more actions underneath. Order tags are available when you fill in those actions. There is no separate dashboard to learn and no second system to monitor.
A typical build looks like this. A member buys an annual plan, and the purchase trigger assigns a role and sends a welcome message with order details. When the subscription renews, a second automation records the renewal. If it’s canceled, a third one removes the role and sends a short note. Three small automations replace a recurring manual checklist.
Because AutomatorWP – PublishPress Cart builds on a framework you may already use, the logic you write is visible and editable. You can see what fires, when, and why. If a refund policy changes, you open the automation and adjust it. The code is released under the GPL, so developers who want to extend or modify the add-on for a particular store are free to do so, and the license lets you use it across your own projects.
Ideal Use Cases
Online course sellers
A course creator can enroll a buyer the moment payment clears and revoke access if the order is refunded. Renewals on a subscription-based course library can keep students active, and a cancellation can trigger a short feedback request. No one has to open the orders list to make any of this happen.
Membership sites
Memberships live and die by renewals and cancellations, and those are exactly the events this add-on tracks. Role changes, content access, and member communications can follow the subscription state automatically, so your member list always reflects who is actually paying.
Coaches and service providers
When a client buys a coaching package, an automation can notify you, send intake instructions, and tag the client record. Guest checkout support matters here, because many one-off service buyers never create an account.
Event organizers
Selling tickets often means a lot of repeat messaging. A purchase trigger can send event details to each buyer, and a refund trigger can alert your team so the attendee list stays accurate.
Digital product stores
For downloads and templates, the guest order trigger is the useful one. A visitor buys, you react, and the sale is logged or passed to another tool without needing the buyer to register first.
Frequently Asked Questions
Can I trigger an automation for a guest who never created an account?
Yes. The “Guest completes an order for a product” trigger is built for this situation. It fires when a visitor finishes checkout without logging in, so you can still send a message, notify your team, or pass the order along. Actions that need a user account, such as assigning a role, will not apply to someone who has no account.
Which order details can I use inside my actions?
The add-on provides order tags that give you access to the order’s information. You insert them into action fields, such as an email body or a note, and they fill in with the details from the order that fired the trigger. That lets one automation produce personalized output for every purchase.
Can I run different automations for different products?
Yes. Each trigger is tied to a specific product that you select when building the automation. You can create one set of steps for a membership and a completely different set for a one-time digital download. Nothing forces every product through the same rule.
What happens when a customer cancels a subscription or gets a refund?
The cancellation and refund triggers each fire at that moment, and you decide the response. Common choices include removing a role, ending access to restricted content, sending a closing message, or alerting yourself. If you do nothing, nothing happens, so you stay in control of how generous or strict your policy is.

