Set up useful notifications

Open Automations to review the sending controls. Saving a wishlist never subscribes anyone. Account notifications require the relevant selected category; guest alerts and recovery require explicit choices and email confirmation. Pro email sending starts paused. Configuring a new feature does not unpause it.

Open Email templates, expand a message type, edit it, then choose Preview & test. The preview includes unsaved edits and uses clearly labeled sample values with the same renderer as production email. It does not save the template, contact shoppers, or create coupons.

Select Send this test only when you want that reviewed draft sent to your own WordPress profile email. Template and delivery tests share a five-minute cooldown. Use Save templates separately to apply edits to future messages.

WooCommerce product updates enqueue a refresh of watched selections. The worker processes due work through Action Scheduler when available, with WordPress cron as the fallback. The nominal worker interval is one minute; actual timing depends on your site’s scheduler and traffic.

A fallback scan checks up to 200 watched selections per pass. The health panel shows the estimated full scan time, queue depth, and oldest due work. On a low-traffic store, configure a reliable server cron to run WordPress scheduled work.

Select a product and, if required, its variation by name. Choose saved-quantity and recency filters, enter a unique campaign reference, and review before queuing. The generated reference refreshes after a confirmed request. Identical retries using the same reference are acknowledged without scheduling again. Reusing a reference with different product or audience criteria is rejected; use a new reference for a new campaign.

Followers can opt in to updates from public lists. The plugin checks consent and visibility again before sending and groups list-change notices by day. Making a list private or withdrawing consent prevents delivery.

Transport accepted means WordPress’s mail transport accepted a message, not that it reached the inbox. Confirmed failures can be retried. Unknown outcomes are held for review and are not automatically resent. The delivery health summary shows Needs attention when held or failed jobs exist. A per-account daily limit also applies, so not every eligible event results in an immediate message.

Mail delivery depends on your hosting and mail provider. The website’s Email alerts preview simulates eligibility and sends no email.

Open Automations → Product alerts. Guest signup and low-stock alerts start off. Guests choose specific saved products and separate price-drop, back-in-stock and low-stock categories, then confirm their email. No account is required. Changing an existing guest signup requires stopping it and confirming the new choices.

Low-stock messages require managed inventory moving from outside the low-stock range into positive stock at or below the threshold, including a restock into that range; the first observation and threshold changes are silent. Sold-out, backordered and unmanaged stock do not create urgency messages. Current consent, purchases, expiry, removed selections and shared sending limits are checked before delivery.

Open Automations → Recovery sequence to review timing, messages, previews and audience. The sequence offers one reminder and an optional follow-up offer, with separate offer consent. Guest email confirmation and private return links do not create a WordPress account. Relevant purchases, unsubscribe, expiry, removed items and changed sequence settings stop eligible pending follow-ups.

Settings → Integrations offers a named AutomateWoo save trigger and a signed HTTPS webhook. Connections start off and require reviewed settings. They use current account campaign consent and respect the store sending pause. The webhook sends event ID, time, product/variation IDs, quantity and currency; it excludes email, account identifiers, private notes and access tokens. Its provider sees the connection IP. Review that provider’s privacy terms and your store notice first.

The AutomateWoo adapter supports the immediate workflow boundary; delayed workflows are not enabled through this trigger. Actions and downstream providers configured in AutomateWoo follow its settings. Verify the actual vendor version and complete workflow on staging. Turning a connection off prevents eligible queued delivery; it cannot recall data already received.