Mail Revolution

Email Campaigns

Email Campaigns are treated as two different jobs within PrestaShop. A letter goes to one customer – such as a review invitation, a quote follow-up, or a post-delivery check-in – and it should read as though a colleague typed it. A newsletter is a broadcast and should be built and delivered like one.

Campaign Messages

A campaign message starts as an actual message exported from your mail client, keeping its structure, signature, and plain-text part instead of a template layout. Nothing leaves without a person saying yes. Hold every message for a named colleague to review and edit before sending - and loosen to semi-automatic or scheduled modes once a campaign has earned it.

The Preview

The preview is the message. What the approver saw is precisely what the customer receives – wording, variables, and variant choice are locked the moment a message is approved. There are no exports, and no sync to break. Targeting reads your orders and consent flags at send time, so an audience is never a stale CSV.

Sending

Sent at the pace a person sends. Personal campaigns respect a daily cap, working hours, and randomised gaps, spreading sends the way a person actually writes email. Review requests are checked before they publish. The template linter flags incentive wording and satisfaction-conditioned asks that commonly conflict with Google review policies and UK fake-review rules.

Your Consent Evidence

Your consent evidence outlives the module. Suppression lists, consent evidence, and the audit trail are deliberately preserved in the database even if the module is removed.

Email Campaigns vs. Personal Campaigns

Email Campaigns treat a shop's mail as two different jobs. A letter goes to one customer – a review invitation, a quote follow-up, a post-delivery check-in – and it should read as though a colleague typed it. A newsletter is a broadcast and should be built and delivered like one. Both live inside PrestaShop, sharing campaigns, templates, and audiences at the top and splitting into two strictly separated delivery paths underneath, where a campaign, a template, and a sender profile will only pair with their own kind.

Personal Pipeline

The personal pipeline starts from a specimen: one real email exported from the mail client your team actually uses. Its MIME structure, its signature with the embedded images, its client fingerprint, and its plain-text part are all preserved, and only the body is swapped per recipient. There are no tracking pixels, no rewritten links, and no campaign markup of any kind, so what arrives carries the same structure as mail written by hand.

Manual and Semi-Automatic Campaigns

Manual and semi-automatic campaigns create a queue item for each recipient, and each one waits for votes from the employees allowed to give them. The queue shows the exact rendered email for that customer; staff edit the personal paragraph inside the preview, leave comments for one another, and vote. An edit invalidates earlier approvals, every decision carries the employee's name, and an append-only log keeps the actor, shop, action, reason, and outcome.

Template Linter

A template combines customer, order, and shop variables with conditional blocks – trade against retail, a recent order against a settled one – and rotating phrase variants, so identical wording is the exception rather than the rule. Variant choice is deterministic per recipient, which is what makes a preview a promise rather than a sample. Every template holds a version for each shop language, and publication is gated by a linter that checks syntax, unknown variables, and the review-request wording that gets merchants into trouble.

Audience Building

The audience is your order data, read at send time. Recipient rules are built from live PrestaShop data: products bought, order states, dispatch and delivery dates, workflow statuses, support threads, and consent flags. There is no export, no separate contact database to keep in step, and no connector to an outside platform that can quietly stop syncing. Customers with an open support issue are deferred rather than silently dropped, and every message is checked against suppression lists, bounce history, and a one-per-campaign guard immediately before it is handed to the transport.

One-Click Unsubscribe

A broadcast campaign requires its own verified sending identity – a dedicated subdomain or an SMTP provider – and every message carries HTTPS List-Unsubscribe and one-click headers backed by shop-specific signed tokens, with bounce and complaint handling behind them. The link exposes no email address, and creating the same suppression twice changes nothing.

External Platform Required

No external platform needed to run it. PrestaShop 1.6 through 9 on PHP 7.1 or newer, multishop-aware, open code, and nothing outside your own shop is required to operate it.

Back-Office Actions

Back-office actions require POST, an authenticated employee, and a matching shop and token, so a stray link cannot fire a campaign. Suppressions are indexed by email hash with only masked addresses on screen, the queue resists duplicates through unique constraints, row locks, and leases, and campaign history, consent evidence, and the audit trail are deliberately left in the database when the module is removed.

Scheduling

Scheduling runs on the shared MPR cron infrastructure.