Notifications & Transactional Messaging

Every store sends messages on its own: a signup confirmation, a password reset, an order confirmation, an invoice, a quote, a back-in-stock alert, an invitation to join a buying organization. Changing the wording in any of them means filing a developer ticket and waiting for a release.

Notifications & Transactional Messaging puts every one of these messages in one place: editable without a developer, in multiple languages, and set separately per store or brand.

The person who owns this content is usually marketing or ecommerce operations. The person who gets asked about it when something goes wrong is IT, who has to answer whether a customer actually received a message. Both work from the same system.

• One list of every message the platform can send: The ones that ship with the platform, plus any custom ones your team has added. Email and text message are supported channels out of the box.
• Templates, one per language: Template content uses placeholders that pull real order and customer data in at send time, so one template serves every customer. Templates that ship with the platform are labeled as such, with a one-click restore back to the original if an edit goes wrong.
• Layouts: Reusable header and footer wrappers, so every message carries the same branding without editing each template individually, the fix for "our emails all look slightly different."
• Per-store templates: Run different message content per store or brand from the same platform instance, set from the store’s own settings.
• Preview and test before going live: Preview a template rendered with sample data, and send a test message to yourself before it reaches a customer.
• A rebuilt editor, new: The template editor was one long scrolling form. It’s a compact, tabbed workspace: a live preview beside the content, a proper editor for the sample data, autocomplete for the available placeholders, and a full-screen mode. Editing a customer email feels like editing a document, not filling in a form.
• Delivery through your own provider: Email via SMTP, SendGrid, or Microsoft Graph for Microsoft 365. Text messages via Twilio. Switching provider is a configuration change; templates stay untouched.
• Automatic retry: Sending is asynchronous with a built-in retry policy, so a provider hiccup doesn’t silently lose a customer’s order confirmation.
• A delivery log: Every message is recorded with its status, send attempts, and any error, which is how support answers "the customer says they never got it."
• Templates can live in source control: Teams that want to version templates alongside code, and promote them between environments, can keep them as files instead of database records. Export and import cover backup and migration.
• PDF invoice templates: Managed through the same template system as every other message, not a separate tool.

• Marketing owns the wording: Changing what a message says means editing it in the admin panel, not waiting for a developer to ship a release.
• Consistent branding everywhere: The same layout and branding apply across every automated message and every store.
• Localized communication without duplicating a store: One store, one set of layouts, many languages.
• Support can prove what happened: Every message’s status, attempts, and errors are on record, so "did the customer get it" has an answer.
• No lock-in to one email vendor: Switch providers without rewriting templates.

• A brand running five country stores keeps one set of layouts and swaps only the language-specific content.
• A team moves its in-house SMTP server to a cloud email provider without rewriting a single template.
• Ops traces a "missing order confirmation" complaint to a bounced address in the delivery log in minutes.

Notifications & Transactional Messaging works alongside several other capabilities. Invoice content is covered in more depth on Invoicing, and stock alerts on Back-in-Stock. Store-specific content ties into Multi-Store and Language Support, and invitations to join a buying organization connect to Multi-Account & Company Structure. Message history sits next to Order History. This covers transactional messages, not marketing campaigns.