ShopMagic for WooCommerce Memberships - WordPress Plugin

Guide to Configuring ShopMagic for WooCommerce Memberships for Automated Member Emails

ShopMagic for WooCommerce Memberships is not meant to replace your membership system itself. Its role is to connect WooCommerce Memberships events with automated emails, filters, actions, and member-specific data. In this guide, you'll see how to prepare your site, where to find the automation logic, which events and filters to use, how to verify delivery, and how to keep membership emails from turning into a source of errors.

This article is written for a WooCommerce store owner, site administrator, or support specialist who already understands why a site needs membership plans, protected content, access renewals, or manual member management. You will not find licensing instructions here, and this is not a rewritten product listing. Instead, this is a working framework: installation, automation setup, a pre-expiration email example, result verification, troubleshooting, and alternative options.

The key idea is simple: membership automation should be tied to a real event, a clear filter, and a verifiable outcome. If an email is not connected to the member lifecycle, it becomes hard to test, hard to explain to support, and easy to send to the wrong group of users.

How the Product Fits into the WooCommerce Memberships and ShopMagic Stack

WooCommerce Memberships controls access: membership plans, content and product restrictions, start and end dates, manual assignment, and scenarios where membership is tied to a product or subscription. ShopMagic handles communication and actions: what to do when an event happens, who should receive the email, which conditions should apply, and how the result should be logged. ShopMagic for WooCommerce Memberships adds a dedicated layer of events, filters, actions, and placeholders built specifically for memberships.

That is why it makes more sense to think of this product as a member lifecycle extension. It does more than just "send an email." It lets you build a clear response to an access change: welcome a new member, warn them that access is about to expire, react to a cancellation, segment users by plan, or update membership status through a ShopMagic action.

The basic ShopMagic model is built from three parts. Event triggers the automation, Filter limits the audience, and Action performs the task. For a standard order, that could mean an order status plus an email to the customer. For memberships, the logic becomes more nuanced: the event might be membership creation, a status change, deletion, or an upcoming expiration date. The filter might be the plan, status, start date, expiration date, number of active memberships a customer has, or a member profile field. Inside the email, you can use membership data through placeholders such as {{ membership.plan_name }} or {{ membership.expires_date }}.

This approach is especially useful when a membership is not just one-time access, but part of a retention funnel. For example, a user buys a course, gets access to protected lessons, approaches the end of the access period a few weeks later, and the store wants to send an email explaining what will remain available, where to renew, and who to contact if access should be extended manually.

Practical rule of thumb: first describe the event in plain language as "when this happens...", then define the filter as "only if...", and only then write the email. If you cannot clearly explain the event and the condition, the automation is not ready to be built yet.

One important limitation: ShopMagic for WooCommerce Memberships does not create the architecture of your membership site. Plans, content restrictions, access dates, and selling rules are configured in WooCommerce Memberships. The ShopMagic extension connects afterward and uses the data that already exists. If Memberships does not contain a valid plan or the user never received a membership, ShopMagic cannot magically build the right communication layer on top of missing data.

Who This Automation Setup Is a Good Fit For, and When Another Tool Makes More Sense

ShopMagic for WooCommerce Memberships is a strong fit for sites that already use WooCommerce Memberships and need to manage communication inside WordPress. That could be an online learning project with lesson access, a membership store with restricted products, a paid community, a B2B catalog with access levels, or a store that gives members special materials after purchase.

The main strength of this solution is that it works alongside WooCommerce and WordPress data. An administrator does not need to export members into a third-party service just to send one renewal email. The automation is created in a familiar admin panel, and conditions can be built from store and membership data. For small and mid-sized stores, that reduces the number of external integrations and failure points.

When ShopMagic for WooCommerce Memberships Is Especially Useful

• You need to send welcome emails to new members with the personalized plan name and a renewal link.
• You need to remind members that access is about to expire without manually checking the member list.
• You need to react to membership status changes: active, canceled, expired, or moved to another plan.
• You need to segment emails by membership plan, start date, expiration date, or the number of active memberships.
• You want to keep communication inside WordPress instead of moving your entire member base into an external email platform.

When You Should Consider a Different Approach

If you need a full visual builder for long email sequences, a deep CRM profile, complex branching across multiple channels, or external integrations as the core of the process, ShopMagic for WooCommerce Memberships alone may not be enough. It is strong as an on-site WooCommerce automation tool, but it is not required to cover every use case of a full marketing platform.

The product also will not solve email issues caused by poor mail server setup on your hosting. If WordPress cannot send standard WooCommerce emails, a ShopMagic email may also fail to reach the inbox. In those cases, start by checking basic deliverability, your domain sender setup, SMTP, or a transactional email service before looking for a problem in the membership automation.

Another edge case is memberships that need to trigger complex external actions: adding a contact to a CRM, assigning an achievement, enrolling someone in a learning platform, updating an external spreadsheet, or calling a webhook. Some of that can be handled through other ShopMagic add-ons or separate automation tools, but before choosing a platform, it is worth deciding which system should be the main process hub.

What to Check Before Installation and Your First Scenario

Preparation may feel boring, but it is what separates a working automation from an email that "sometimes gets sent." With ShopMagic for WooCommerce Memberships, four layers matter: WordPress, WooCommerce, ShopMagic, and WooCommerce Memberships. If one layer is not fully configured, the issue often shows up only when the email is sent or when you try to select an event.

Start by checking that ShopMagic itself is installed and active on the site. The base ShopMagic plugin can be installed from the WordPress repository, and PRO add-ons are connected on top of it. Then confirm that WooCommerce Memberships is active and that the site has at least one real membership plan. ShopMagic for WooCommerce Memberships uses Memberships data, so without an active Memberships setup, its events and placeholders have little practical value.

Quick Checklist Before You Build the Automation

• A plan exists in WooCommerce Memberships that clearly distinguishes one member group from another.
• You have a test user to whom you can assign a membership or grant one through a test order.
• WooCommerce has its basic sender email settings configured: domain-based address, sender name, and email template.
• WP-Cron is not blocked on the site, and WooCommerce Action Scheduler jobs are not piling up in Pending or Failed state.
• Your cache plugin is not caching the ShopMagic REST API, especially if you use LiteSpeed Cache.
• The administrator has access to ShopMagic, WooCommerce, the membership list, and send logs.

For testing, it is best to use a separate user and a separate membership plan that can be removed or changed easily. Do not test your first automation on a real list of active members if the action sends an email. Create a temporary plan, assign it to a test user, and make sure the email goes only to that person.

If the site has been running for a long time and already has members, do not assume that a new automation will automatically process all past events. By default, ShopMagic reacts to events after the automation is published. Separate approaches exist for past orders and customers, including manual actions, but that has to be planned separately and tested with extra care.

Installation and Initial Verification in WordPress

Installation has two parts: the base ShopMagic plugin and the WooCommerce Memberships add-on. The base plugin adds the admin area for automations, logs, queue management, and general settings. The add-on introduces membership events, filters, actions, and placeholders. If the interface shows only standard WooCommerce events, the Memberships extension is not connected or WooCommerce Memberships is not active.

General Installation Order

1. Install and activate the base ShopMagic plugin in WordPress through Plugins or by uploading the ZIP file if you use the PRO package.
2. Confirm that WooCommerce and WooCommerce Memberships are active and that Memberships includes a plan for testing.
3. Activate the ShopMagic for WooCommerce Memberships add-on.
4. Open the ShopMagic section or WooCommerce -> Automations if your interface shows automations under the WooCommerce menu.
5. Create an automation draft and open the event list. Membership events should now appear there.
6. Do not publish the automation right away. First configure a test email, a filter, and the recipient.

After activation, it is useful to run a simple check without sending a real campaign. Create an automation for a new membership event, add a filter for the test plan, and choose an email to the test user as the action. Use a clear subject line such as Membership test - {{ membership.plan_name }}. This lets you immediately see whether the plan name is being inserted and whether the email is being sent too broadly.

What Should Appear in the Interface

In a normal installation, the add-on extends ShopMagic with four kinds of entities:

• Membership events. For example, a new membership, status change, deletion, or a pre-expiration event.
• Membership filters. For example, plan, status, start date, expiration date, active membership count, and custom fields.
• Membership actions. For example, create a membership, change the plan, change the status, or remove a membership for a customer.
• Dynamic data. For example, membership ID, plan name, status, dates, and a renewal link if it is available in your configuration.

If these elements are missing, check not only whether the add-on is active, but also whether WooCommerce Memberships is active. ShopMagic documentation explicitly states that WooCommerce Memberships must be activated before you can use this add-on. You can usually spot the issue quickly in the UI: the event dropdown has no membership events, and the placeholder hints do not include membership fields.

Short takeaway: after installation, do not jump straight into a full retention workflow. First prove that the event appears, the filter limits the automation to the test plan, and the email reaches one test user.

How ShopMagic for WooCommerce Memberships Works: Events, Filters, Actions, and Member Data

This section is the core of the guide. Once you understand it, the rest of the setup becomes much easier: you stop choosing options at random and start building automation like a conditional statement.

The formula looks like this: when a membership event occurs, if the member matches the conditions, perform the action and insert membership data into the email. In ShopMagic, that is not an abstraction. It is the actual structure of the automation screen.

Membership Events

The event defines the trigger point. The add-on documentation lists events for a new membership, an upcoming expiration, deletion, and a status change. In practice, most sites can start with two scenarios: welcoming a new member and sending a reminder before access expires. They are easier to test and give you quick value without modifying membership data.

The New Membership event works well for a welcome email. It can explain where to find the protected area, which materials are available, where to ask questions, and how to verify access. The Membership - Before expires event is a good fit for a renewal or expiration warning email. The Membership - Status changed event should be used more carefully: it is powerful, but it can fire in multiple situations, so it almost always needs a status or plan filter.

Membership Filters

The filter protects the automation from unnecessary triggers. If you do not add a filter, the automation becomes global for the selected event. That is fine for a general welcome email, but risky in cases where different plans require different terms, timelines, or email copy.

For memberships, the most useful filters are plan, status, start date, expiration date, metadata, and active membership count. For example, a pre-expiration email can be sent only to members of the Premium Club plan, while a separate automation can be created for the Business Access plan with different copy and a different offer. If the site uses member profile fields, filtering by those fields helps segment the audience without a manual export.

Membership Actions

Most of the time, the action will be a standard email: Send Email, Send Email - Plain Text, or Send Email - Raw HTML. But the add-on also provides actions that modify memberships: create a membership for a customer, change the plan, change the status, or delete the membership. These actions require more care because they change access instead of simply notifying someone.

If you are just getting started, do not use status-changing actions in your first automation. Set up the emails, verify the events and logs, and only then move on to actions that modify Memberships data. For those actions, a test plan, a backup, and a clear rollback path are especially important: which membership was changed, from which status to which one, why it changed, and which event triggered it.

Placeholders for Personalization

Placeholders let you insert member and membership data into the email. In ShopMagic for WooCommerce Memberships, available fields include {{ membership.id }}, {{ membership.plan_id }}, {{ membership.plan_name }}, {{ membership.status }}, {{ membership.start_date }}, {{ membership.expires_date }}, {{ membership.renewal_url }}, and {{ membership.meta }}. The exact set and the inserted value should be tested in a sample email, because some values depend on the data in the specific membership record.

Do not overload the first email with a dozen variables. The user should see clear information: which plan is active, what is changing, which date matters, and what action they should take. The rest of the data is more useful in an internal admin email or a support log.

Detailed Email Setup After Installation

After installation, the most important task is not to create a "nice-looking email," but to build a safe and working delivery flow. It should trigger on the right event, go only to the intended group, contain verifiable data, and leave a trace in the log. Below is a sequence that works well for your first real scenario.

Automation Name and Internal Description

Name the automation in a way another administrator can understand. A weak name would be Membership mail. A good name would be Membership Premium - reminder before expiry or Club welcome - New Membership. It is also worth filling in the internal action description: the user never sees it, but it helps distinguish one email from another in the actions list and Outcomes.

Choosing the Event

For your first scenario, choose an event that is easy to reproduce. A new membership is easier to test than a complex status-change chain. If you need a pre-expiration scenario, check how the test membership expiration period is defined in Memberships. The Membership - Before expires event makes sense only when the membership truly has an end date.

Filtering by Plan or Status

A plan filter is almost mandatory for stores with multiple access levels. Without it, an email for the basic plan may go to a premium member, or the other way around. If the email depends on the status, add a status filter so the automation does not react to irrelevant transitions.

In a typical setup, the configuration looks like this:

The table does not replace testing. It simply helps you see that each part of the automation needs its own verification step. If you do not know how to verify a row, the setup is still not specific enough.

Recipient, Subject Line, and Email Copy

The recipient field usually uses the customer's email. In standard ShopMagic emails, the documentation often references the placeholder {{ customer.email }}; for membership workflows, that remains the common foundation, while membership data is added to the subject and body. Before publishing, confirm that the recipient address in the test email is populated with the real email address of the test user.

The subject line should be clear and should not look like internal code. Instead of Membership status changed, a better subject is: Your access to {{ membership.plan_name }} has changed. If the email is sent before expiration, do not promise automatic renewal if renewal actually depends on an order, a subscription, or a manual action by the administrator.

Subject: Your access to {{ membership.plan_name }} will end soon

Hello,

Your current plan: {{ membership.plan_name }}.
Access end date: {{ membership.expires_date }}.

If you want to keep access to the materials, use the link below:
{{ membership.renewal_url }}

This example should not be copied blindly. It shows the structure: plan, date, action. If your configuration does not generate a renewal link or the link does not fit the scenario, replace it with a regular account page link or a support instruction.

Email Template and Formatting

For the first email, use the standard WooCommerce template or a plain-text format. Raw HTML only makes sense if you already have a tested email template that renders correctly in email clients. The more complex the HTML, the greater the risk of responsiveness issues, spam filtering, and display problems.

If the footer shows a technical placeholder such as {site_title}, the fix is not inside ShopMagic, but in WooCommerce email settings. Check WooCommerce -> Settings -> Emails, sender options, and footer text. This is a common situation: ShopMagic sends the email, but the visual styling and some shared email settings are inherited from WooCommerce.

Practical Example: Membership Expiration Reminder

Now let us build a concrete scenario. Imagine the site sells access to a protected resource library. Members on the Premium Club plan receive access for a limited period. The site owner wants to notify the user before access ends, show the plan name, include the expiration date, and provide a clear path to renewal or support.

Goal

Create an automated email for members of a specific plan before their membership ends. The email should go only to users who have the right plan and an expiration date. The administrator should be able to see the result in the ShopMagic log.

Preparation

• A Premium Club plan or its real equivalent has been created in WooCommerce Memberships.
• A test user exists with an email address the administrator can access.
• The test user has a membership assigned with an expiration date.
• ShopMagic, WooCommerce Memberships, and the Memberships add-on are active.
• Standard WooCommerce emails successfully reach the test inbox.

Setup Steps

1. Open the ShopMagic automations list and click Add New.
2. Enter a name such as Premium Club - expiry reminder.
3. In the event block, select the event for membership expiration approaching.
4. Add a membership plan filter and choose Premium Club.
5. If you use multiple statuses, add an active status filter so the email does not go to users whose access has already been canceled.
6. Select the Send Email action.
7. Use the customer's email for the recipient, and write a clear subject line using {{ membership.plan_name }}.
8. Add the expiration date to the email body through {{ membership.expires_date }} and include a short instruction explaining what to do next.
9. Save the automation as a draft if you want to review the fields first, or publish it only after testing it on a separate user.

Expected Result

When the right event occurs for the test membership, ShopMagic will add the action to the queue and then send the email. A result with a clear status should appear in Outcomes. If the email is marked as sent but does not appear in the inbox, split the problem into two questions: did the automation run, and did the mail delivery layer actually deliver the email to the recipient?

A Common Detail That Gets in the Way

Pre-expiration scenarios depend on the membership expiration date. If the membership is lifetime access, if access is extended through a separate subscription, or if the test date does not occur in the time frame you expect, the event may not fire the way you expect. In that case, first inspect the membership record itself in WooCommerce Memberships: status, start date, end date, and plan association.

Verifying the Result: Queue, Outcomes, and Email Tracker

Result verification matters not only after the first setup. It is a habit that can save hours of support time. When a user says "I never got the email," the administrator should be able to determine quickly whether the event never happened, the filter excluded the member, the action failed to run, the email was sent but not delivered, or the email was delivered but landed in spam.

First, Check Whether the Event Actually Happened

Open the membership object in WooCommerce Memberships and make sure it matches the scenario. For a new membership, the event should be tied to the membership being created. For a status change, it should be tied to the status transition. For a pre-expiration event, it should be tied to the expiration date. If the membership record has not changed, the automation does not have to run.

Then Check the Queue and Outcomes

ShopMagic uses an action queue connected to Action Scheduler. That improves reliability and helps avoid slowing down critical WooCommerce processes. Because of that, the action may run with a slight delay. If WP-Cron is unstable or the Action Scheduler queue is overloaded, emails may be delayed.

In Outcomes, look not only for the existence of a record, but also at the status. A successful send means ShopMagic handed the email off for delivery. That does not always mean guaranteed inbox placement: your mail server, domain reputation, SPF, DKIM, DMARC, SMTP, and spam filters still matter. If the status is Failure, open the error details and save them for support.

Email Tracker and What the Metrics Actually Mean

Email Tracker helps you assess what happens after the send. In ShopMagic documentation, it is described as a log showing delivered emails, opens, and clicks, available in the logs area next to Outcomes and Queue. For membership workflows, that is useful not as "nice-looking stats," but as a reality check: members see the reminder, open it, click through to the renewal page, or ignore it.

Do not draw conclusions from a single email. A test user may never open it, and an email client may block the tracking pixel. But across a series of real sends, the tracker helps you understand whether the subject line works and whether the message looks like a useful email rather than a technical notice with no clear action.

Troubleshooting order: membership object -> ShopMagic event/filter -> Queue -> Outcomes -> delivery test -> spam score -> SMTP/domain settings. If you jump straight to SMTP, you can easily miss an incorrectly selected plan or status.

Segmenting Members and Running Manual Campaigns Without Over-Mailing

A membership database is rarely uniform. One user has a basic plan, another has expanded access, a third has canceled, and a fourth has not renewed in a long time. If you send the same message to everyone, automation quickly becomes noise. ShopMagic for WooCommerce Memberships is useful because it gives you filters and placeholders that let you communicate with members in context.

Filter by Plan

The membership plan is the most intuitive filter. It helps split messages based on what the product actually promises. A member on a basic plan does not need an email about features available only on a higher tier. A member on a corporate plan may need a different tone, a different link, and a different support contact.

Filter by Status

Status matters when the email depends on the current state of access. An active member can receive instructions on how to use the materials. A canceled member can receive a careful message explaining what changed and who to contact if the cancellation was a mistake. An expired member can receive access recovery options, if that scenario is supported on the site.

Start Date and Expiration Date

Dates matter across the lifecycle. At the beginning, you can send a welcome email and then, through separate logic, follow up with first-step guidance. Before expiration, you can warn about access ending. After expiration, you can send a separate sequence only if that does not conflict with your communication consent settings and site policies.

Manual Actions and Careful Work with an Existing Member Base

If you need to contact existing members, do not try to artificially change statuses in bulk just to trigger automations. The ShopMagic ecosystem includes manual actions designed for working with an existing customer or order base. That kind of scenario requires its own review of filters and email copy: first send to a test segment, then to a small group, and only then to a broader audience.

Be especially careful with actions that modify memberships. A mass email send is reversible: you can apologize, clarify, and stop the automation. A mass change to a status or plan directly affects access to content and can trigger a wave of support requests.

Working Scenarios Across the Member Lifecycle

After your first test automation, do not rush into building a complex map of ten different emails. It is far more useful to walk through the member lifecycle and identify the points where a message genuinely helps the user. On a membership site, there are usually four of those points: access starts, expiration approaches, status changes, and manual work with an existing member base. All of them fit the ShopMagic logic, but they require different levels of caution.

Welcome Email After Membership Creation

This is the safest and clearest starting scenario. A new membership event is easy to explain, a plan filter is easy to verify, and the email does not need to change access. In the email, you can include the plan name, a link to the account page, instructions for the protected materials, and a support contact. Do not overload the welcome email with sales messaging: the user has just received access, so what matters most is understanding where to start and how to confirm the membership is active.

For this kind of email, a three-part structure works well: what is available now, where to find it, and what to do if something goes wrong. If you have multiple plans, create separate automations or different email copy based on filters. That way, a basic-plan member will not see promises that apply only to a higher-tier plan.

Reminder Before Access Expires

This scenario is valuable for retention, but it depends on the quality of your Memberships data. The membership must have an expiration date, and the email must include an honest next step. If renewal happens through buying a product, send the user to the product page or account page. If renewal depends on a subscription, do not tell the user they can renew manually unless that is actually supported by your process. If an administrator handles renewal, the email should explain where the user should reach out.

A good reminder does not pressure the user. It answers the practical questions: which access is ending, when it will happen, what changes after expiration, and what action can be taken in advance. To test it, create a membership with a short duration and make sure the email goes only to the correct plan.

Reaction to a Status Change

A status change is a powerful but higher-risk trigger. Status can change because of cancellation, a manual edit, the end of the term, a plan transfer, or a technical recovery. That is why an automation based on Membership - Status changed almost always needs an additional condition. Otherwise, one email can be triggered in situations with very different meanings.

A safe approach would be separate automations for different cases: one for a transition to canceled status with a support email, another for restoration of active status with an access confirmation, and a separate internal note to the administrator for ambiguous statuses. If you are not sure which statuses are actually used on your site, spend time observing test memberships and logs before publishing an email to the full list.

Internal Notifications for the Team

Not every automation needs to write to the customer. Sometimes it is more useful to send an internal email to an administrator or support manager: a member changed plans, a membership was deleted, VIP access is about to expire, or a corporate-plan user needs manual review. That lowers risk because the team sees the event and can make a decision before access is changed manually.

In an internal email, you can use more operational data than you would in a customer email: membership ID, plan, status, expiration date, a link to the user in the admin panel, and a short instruction for the manager. But even internal emails should not contain unnecessary personal data. Include only what is needed for action.

Reusing and Migrating Automations

When a scenario is stable, it can be cloned or exported for use on another site. ShopMagic includes built-in options for copying, importing, and exporting automations, but successful migration depends on matching versions and active add-ons. Membership workflows introduce one more risk: the Memberships plans may differ on the new site. After import, check the plan filter, placeholders, and test user. Do not publish the imported automation until you are sure it is not pointing to old or missing data.

Limitations, Safety, and Sensible Improvements

ShopMagic for WooCommerce Memberships works inside WordPress and WooCommerce, so it inherits both their strengths and their limits. Data stays on the site unless you deliberately connect external integrations, but email delivery still depends on infrastructure. The action queue improves resilience, but it requires healthy WP-Cron or a server-level cron job. Caching speeds up the public site, but it can interfere with the dynamic admin REST API if configured too aggressively.

What Not to Do Unless You Truly Need To

• Do not launch your first automation for all members without a filter and without testing.
• Do not change membership statuses through automation if an email to the administrator is enough.
• Do not use Raw HTML unless you already have a tested email template.
• Do not clear the Action Scheduler queue directly through the database without a backup and without understanding the consequences.
• Do not promise renewal to the user if renewal depends on payment, a subscription, or a manual decision.

A Safe Improvement for LiteSpeed Cache

If ShopMagic shows stale data in the admin area, new automations do not appear, or the interface behaves as if settings were never saved, check whether the REST API is being cached. In ShopMagic documentation, the recommended LiteSpeed Cache exclusion is this specific path:

wp-json/shopmagic.*

You should add this rule in the LiteSpeed Cache settings, usually in the URI exclusions area. That does not disable caching for the whole site. It simply excludes ShopMagic's dynamic requests. After saving, clear the cache, refresh the ShopMagic page, and see whether the latest changes appear. Rolling it back is simple: remove the rule and clear the cache again if it turns out the problem was not related to the REST API.

When You Need a Server-Level Cron Job

If the site gets little traffic, WP-Cron may run irregularly. On a regular storefront, that sometimes goes unnoticed, but for membership expiration emails, delays can be critical: the user expects a notice, while the task sits in the queue. In that case, talk to your hosting provider about switching from WP-Cron to a system cron job. Do not copy commands blindly: the correct WordPress path and available commands depend on the server.

As a practical rule for administrators, this is enough: if Action Scheduler contains many overdue tasks, emails are delayed, and standard checks do not help, investigate cron and the queue instead of endlessly recreating the automation.

Common Problems and Troubleshooting

Below are the situations most commonly associated with ShopMagic, WooCommerce Memberships, and email automations. Start with the symptom, then work through the checks. Do not change several settings at once, or you will not be able to tell what actually fixed the issue.

Memberships Events Do Not Appear in the Event List

Symptom

You create an automation, but you only see standard WooCommerce or WordPress events. Events for a new membership, a status change, or an upcoming expiration do not appear.

What to Check

• Is WooCommerce Memberships active?
• Is the ShopMagic for WooCommerce Memberships add-on active?
• Is the base ShopMagic plugin installed on the site, and are you in the correct automations section?
• Are you working in an environment where PRO add-ons are disabled or some plugins are not loading?

The fix usually starts with dependencies: Memberships must be active before membership events can be configured. If the list still does not change after activation, refresh the page, clear admin cache, check the error logs, and make sure there is no conflict caused by REST API caching.

The Email Is Not Sent After a Membership Is Created or Changed

Symptom

The membership has been created or changed, but no email arrives. The user's inbox is empty, and the site owner cannot tell whether the automation actually fired.

What to Check

1. Open the membership object and verify the plan, status, and date.
2. Check the automation filter: it may be excluding the test user.
3. Check Queue and Outcomes in ShopMagic.
4. Test standard WooCommerce emails with a sample order.
5. Check SMTP, your domain email sender, and the spam folder.

If there is no record in Outcomes, the problem is closer to the event or the filter. If there is a record with Failure status, inspect the error details. If the status is successful but the email still does not appear, the issue is more likely related to delivery, spam filtering, or the sender configuration.

The Email Went to the Wrong Members

Symptom

An email intended for one specific plan was received by users on a different plan or by members with the wrong status.

Cause and Fix

Most often, the automation was created without a filter or with a filter that does not match the real Memberships data. Add a plan filter and, if needed, a status filter. Then create two test memberships: one should match the filter, the other should not. The email should go only to the first user.

Placeholders Did Not Resolve or Stayed Blank

Symptom

The email still shows technical strings such as {{ membership.plan_name }}, the date field is blank, or the renewal link is missing.

What to Check

• Is the placeholder supported by the selected event and the current add-on?
• Does the membership actually contain the corresponding value: plan, status, expiration date, or metadata?
• Is there a typo in the placeholder?
• Are you trying to insert a renewal link in a setup where Memberships does not provide a valid renewal mechanism?

The fix is to start with one or two placeholders, send a test email, and only then add more data. If a value is optional, write the email so it still works when that field is empty.

Old Data Appears in the Admin Area or New Automations Do Not Show Up

On sites that use LiteSpeed Cache, check whether ShopMagic REST API requests are being cached. Add the exclusion wp-json/shopmagic.*, clear the cache, and test again. If that resolves the issue, keep the exclusion in place and do not disable caching for the whole site without a good reason.

The ShopMagic Queue Is Not Being Processed on Time

If emails are delayed and overdue tasks are piling up in Action Scheduler, check WP-Cron. On low-traffic sites, it is better to discuss a server-level cron job with your hosting provider. Do not mass-delete pending tasks without a backup and without understanding which automations they belong to.

When ShopMagic for WooCommerce Memberships Is the Right Choice

ShopMagic for WooCommerce Memberships is worth using if your site already runs on WooCommerce Memberships and you need clear emails and actions tied to the member lifecycle. It is not a universal CRM and not a replacement for the architecture of a membership site. Its strength is the combination of a membership event, a filter, an action, and personalized data directly inside WordPress.

Before going live, run one short final check: the membership plan exists, the test user is created, the event is selected correctly, the filter limits the audience, the email contains only verified placeholders, Outcomes records the result, and email delivery works not only for ShopMagic, but also for standard WooCommerce emails.

If the scenario fits your site after that review, you can get the WordPress version and test it on a separate plan or a copy of the store. Start with one useful email instead of ten automations. That makes it easier to see the impact, catch errors, and avoid overwhelming members with unnecessary communication.