Self-hosted email marketing with full source code. Pay once, own forever. Get AcelleMail — $74 →

Get AcelleMail — $74

For ecommerce stores & product teams

Ecommerce email that doesn’t tax your subscriber count.

A 50,000-contact list on Mailchimp Standard runs $385/month. The same list on AcelleMail with Amazon SES runs roughly $20/month in send fees on top of a one-time $74–$199 license. Native WooCommerce catalog sync, abandoned-cart automations, REST upserts on order events, per-subscriber merge tags for product data — the email layer your store needs, priced by the send rather than by the contact count.

Buy Standard License — $74 Try Live Demo →

The math at ecommerce-list scale

Per-subscriber pricing punishes growth. One-time licensing rewards it.

Ecommerce stores compound subscribers fast: every checkout is a subscribe-opt-in opportunity, every win-back campaign refills the list, every Black Friday adds another bracket of contacts. Per-thousand-contact pricing meets that growth with a higher invoice every month. AcelleMail separates the software from the send: pay once for the software, then pay only Amazon SES (or any SMTP service) at $0.10 per 1,000 emails. A 50,000-contact store sending one campaign per subscriber per week costs ~$20/month in SES fees, plus a small VPS for the application.

Subscribers Mailchimp Standard / mo AcelleMail + SES / mo* 3-year saving
5,000$100~$2~$3,500
10,000$135~$4~$4,700
50,000$385~$20~$13,000
200,000$1,310~$80~$44,000

*Assumes one campaign per subscriber per week sent through Amazon SES at the standard $0.10/1,000 rate, plus $1–2/mo for a small DigitalOcean droplet running PHP-FPM. Mailchimp pricing as published 2026-05. License paid once; software updates included for life. Full comparison →

Ecommerce-shaped feature surface

Catalog. Cart. Order. Win-back. The four flows ecommerce email actually ships.

WooCommerce-native catalog sync

The bundled WooCommerce connector reads your shop’s product catalog over the standard WooCommerce REST API: titles, images, prices, stock, variants. Encrypted-at-rest credentials, scoped to a single shop endpoint per source. Drop product blocks into a campaign, hit send — the merge tags resolve to the live product record at send time.

Abandoned-cart automation

A first-class automation trigger for the abandoned-cart event — not a generic webhook to wire up by hand. WooCommerce posts the cart-abandoned event into AcelleMail; the automation flows from there: 1-hour reminder, 24-hour discount, 72-hour last-call. Per-step delays measured in minutes or days, conditional branches off cart total or item count.

REST upserts on order events

Token-authenticated POST /api/v1/lists/{uid}/subscribers from your store’s order-completed hook upserts the customer in milliseconds; POST /api/v1/automations/{uid}/start kicks off the right post-purchase drip. Same API the bundled connectors use — documented in the REST API reference.

Tag & custom-field segmentation

Tag a subscriber with buyer:repeat or last_order_value:>100. Custom fields keyed on lifetime value, last-order date, top-category, preferred-collection. Campaigns segment off any tag or field combination; automations branch off them. The same merge-tag layer that fills product blocks fills the message body with personalised dynamic content.

Deliverability tooling for transactional + promo

DKIM / SPF / DMARC validation against the sending domain, IP-warmup pacing, bounce + complaint handling per provider. Run promo and transactional through separate Amazon SES identities (or different SES regions per market) to keep promo bounces from poisoning order-confirmation deliverability. 11 sending integrations ship in the box.

Multi-store gating (multi-tenant)

One AcelleMail install can serve multiple shops — each store as its own Customer with its own Plan, sending limits, and connected catalog. Useful for brand portfolios, per-region storefronts, or agency-managed shops. Plan-change billing through the bundled Cashier package or a payment-gateway plugin.

What ships, what doesn’t

WooCommerce in the box. Shopify partial. Magento via plugin.

We don’t want surprises after install. WooCommerce is the deepest integration today: catalog sync, abandoned-cart trigger, order-completed hooks, all native. Shopify ships as a catalog-source connector — product browsing works, but the abandoned-cart and order-completed wiring is webhook-do-it-yourself today (one PHP controller, ~50 lines, calls the same REST API the WooCommerce connector calls). Magento, BigCommerce, custom storefronts: same shape, same REST API, ships as a one-class plugin via the Hook system.

If you’re on WooCommerce, you’re in the fast path. If you’re on anything else, the integration is a small Laravel plugin against the same REST API documented at /api — no fork required, no third-party bridge service.

Built on what your engineers already debug

Laravel, MySQL, Redis. Same scale rules as your storefront.

AcelleMail is a Laravel application. Your team already runs Laravel queue workers and Redis in production for the storefront — the email layer scales the same way. Custom merge-tag resolvers (your store’s loyalty tier, product-feed personalisation, region-gated promos) ship as a one-class plugin under your own namespace. Eleven source-grounded developer docs walk every extension surface.

Every claim above traces back to a file path in the codebase: the Hook system for plugin contracts, the sending-driver pattern for vendor-agnostic SMTP, the testing infrastructure for the per-plugin testsuite. No black boxes, no aspirational APIs.

Ecommerce-specific FAQ

Real questions from store owners.

Does the WooCommerce integration require a WordPress plugin install?

The catalog-sync side is server-to-server — AcelleMail reads your shop’s WooCommerce REST API directly, no WP plugin needed for that. The abandoned-cart and order-completed hooks do need a small WP-side plugin to fire the events; the bundle ships with a reference plugin that you drop into wp-content/plugins/ and configure with your AcelleMail token. Same pattern Shopify and Magento integrations use, scaled.

Can I run promo and transactional sends through the same install?

Yes, but you should run them through separate sending servers (separate SES IAM identities or separate vendors entirely). Promo bounces and complaints will damage the reputation of any IP/identity they share with order-confirmation mail. The Sending Servers tab supports multiple servers per install with per-campaign routing — promo campaigns route through the promo-IP identity, transactional through the transactional one.

What about Shopify? My store isn’t on WooCommerce.

The catalog-source side speaks Shopify (read product feed, drop product blocks into a campaign). The abandoned-cart and order-completed event wiring is do-it-yourself for Shopify today — one webhook controller in your store posting to POST /api/v1/lists/{uid}/subscribers and POST /api/v1/automations/{uid}/start. About 50 lines of PHP. Shopify Plus stores often have a dedicated middleware service already; pointing it at AcelleMail’s REST API is the same shape as pointing it at Klaviyo or anyone else.

How does subscriber data residency work for EU customers?

Self-hosted means you choose the host. An EU-based DigitalOcean droplet, AWS Frankfurt, Hetzner, your own colo — subscriber records, send history, and tracking pixels all live there. The bundled Amazon SES driver supports any SES region; switching from us-east-1 to eu-west-1 is one config field change. No third-party Data Processing Agreement to sign with the email vendor — you are the email vendor for your customers.

What about rich product blocks — live price, live stock, dynamic recommendations?

Live price and live stock resolve at send time via the WooCommerce REST API connector — the catalog read happens when the campaign queue picks up the message, not when the campaign was drafted. Dynamic recommendations (“customers who bought X also bought Y”) ship as a custom merge-tag plugin: ~30 lines that query your store’s recommendation engine and inject the result into the email at send time. Pattern lives in the Hook system deep-dive under custom merge tags.

Pay once. Own the email layer. Scale with your storefront.

Standard License $74. Extended adds commercial redistribution + the plugin SDK for $199. Lifetime updates. Try the live demo before you buy.

Get AcelleMail — $74 Try Live Demo

Run your email marketing on
your own server, your own terms

Join thousands of companies that have taken control of their email marketing with full source code, no recurring fees, and unlimited sending. One-time $74 license, lifetime updates.

Get AcelleMail — $74 one-time