Skip to content
Illustration: Envelopes for orders, shipping and customer correspondence

JTL-Shop 5 Communications Design

Email Templates

Transactional emails govern critical touchpoints throughout the purchase journey and ensure the reliable delivery of statutory consumer information. In JTL-Shop, all system templates can be configured and tailored directly within the admin panel using the integrated Smarty template engine.

Key takeawayStructured Customer Communications from the Outset

JTL-Shop provides predefined email templates for all key store actions. These can be adjusted per language, supplemented with up to three PDF attachments, and aligned with your corporate identity via bespoke HTML and plain-text layouts.

Centralised Email Management Directly in JTL-Shop

In JTL-Shop, automated notifications are triggered on an event-driven basis. Whenever a customer creates an account, completes an order, or submits an availability enquiry, the system accesses the templates stored in the backend. Each message is available in both HTML and plain-text formats to guarantee accessible delivery across diverse email clients.

The underlying technical framework is the Smarty template engine. This allows dynamic variables—such as customer names, order line items, invoice totals, or delivery addresses—to be rendered accurately into the message body at runtime. Configuration is handled modularly via the shop backend without requiring direct modifications to server-side source code.

Default System Templates for All Store Events

JTL-Shop is delivered with a comprehensive suite of preconfigured email templates as standard. This covers every stage of the order lifecycle—from the initial order confirmation to status updates (including amendments, payment receipt, partial dispatch, cancellation, or reactivation) right through to the dispatch notification.

Alongside commercial transactions, the system includes templates for account management and customer interactions. These cover registrations, password resets, customer group assignments, account deletions, and enquiries sent via contact forms or product detail pages. Marketing functions—such as review requests, bonus credit updates, back-in-stock alerts, coupons, and wish list recommendations—are also natively integrated.

Schematic illustration

Event-Driven Email Workflow in JTL-Shop

From the customer action in the storefront to rendered email dispatch

  1. 01Event Trigger in Shop

    A customer triggers an action in the storefront, such as placing an order or registering an account.

  2. 02Template Selection

    The system retrieves the appropriate template based on the event ID and selected language.

  3. 03Smarty Compilation

    Dynamic order and customer data are populated into the designated placeholders.

  4. 04Document Attachment

    Assigned PDF documents, such as Terms & Conditions or cancellation terms, are appended to the email.

  5. 05SMTP Handoff

    The fully formatted message is handed over to the configured mail server for final delivery.

Multilingual Versions and Automated PDF Attachments

For internationally active retailers, JTL-Shop allows every email template to be maintained on a per-language basis. Copy, subject lines, and placeholders are stored separately for each language enabled in the store, ensuring overseas customers automatically receive correspondence in their selected language.

Furthermore, the template engine supports attaching up to three separate PDF files per template and language version. This functionality is primarily used to provide legally compliant statutory information—for instance, attaching Terms & Conditions, Cancellation Policies alongside model withdrawal forms, or product guidance notes directly to the order confirmation.

Customisation via Smarty Variables and Template Testing

When customising email templates, merchants have access to a wide array of predefined Smarty objects. Conditional statements (utilising {if} logic) make it possible to display specific sections only for particular payment methods, customer groups, or shipping options. This enables targeted customer communication without having to maintain redundant templates.

Prior to deployment in production, structured functional testing is strongly recommended. The integrated test dispatch tool in the JTL-Shop backend allows generated layouts to be sent to a designated test address. Note that successful generation in the backend does not guarantee flawless inbox delivery; the latter depends decisively on external mail server authentication (SPF, DKIM, DMARC).

Delineation Between Shop and Wawi Emails

In an integrated infrastructure comprising JTL-Shop and JTL-Wawi, operational responsibility for email dispatch must be clearly defined. While real-time notifications such as order confirmations or registration emails are typically triggered directly by the webshop, many merchants handle the dispatch of invoices, delivery notes, and tracking links via JTL-Wawi.

Overlapping email triggers should be avoided to prevent customers from receiving duplicate status updates. Depending on your process architecture and installed extensions, dispatch-related notifications can be disabled in JTL-Shop once they are automated via JTL-Wawi document output.

Terms explained

Smarty Template Engine
A PHP-based templating system that separates application logic from presentation, enabling dynamic variables within email bodies.
Transactional Email
An automated message triggered by a user action, such as an order confirmation or password reset request.
Plain-Text Version
An unformatted text alternative of an email provided as a fallback for email clients that do not render HTML.
SPF/DKIM/DMARC
DNS-based authentication standards for email servers that mitigate sender address spoofing and safeguard deliverability.

Good to know: requirements & limits

  • Actual email inbox deliverability depends on external mail servers and DNS records; JTL-Shop cannot guarantee successful inbox arrival.
  • JTL-Shop natively supports a maximum of three PDF attachments per template and language version via the backend.
  • When running JTL-Wawi in tandem, certain email triggers are best managed directly within the ERP system rather than the online store.
  • Mandatory statutory documents (e.g. Terms & Conditions, Cancellation Policy) must be maintained manually and are not automatically vetted by the system.

Contact

Let’s discuss your project.

Free initial consultation on JTL-Wawi, JTL-Shop, JTL-WMS and hosting.