Every order in an online shop triggers the same message: the order confirmation. It is the one email that practically every customer receives - and it actually gets read. Transactional emails are opened and clicked far more often than classic promotional newsletters, because they meet an expectation that a promotional campaign first has to create. Even so, many shops treat the order confirmation as system output that was configured years ago and has run untouched ever since. This article shows how a default template becomes a considered point of contact: legally sound in structure, reliably delivered, clearly organised and embedded in a solid post-purchase sequence.
Why the order confirmation is the most-read email in your shop
The difference between a transactional email and a newsletter starts with the recipient expectation. Someone who has just ordered is waiting for the confirmation. It answers three questions at once: has the order arrived, what does it cost, and when will it be delivered. That expectation shows up directly in the metrics. Order confirmations reached a click rate of 12.5 percent (Experian 2010) in an analysis of send data from 2009 and 2010, while bulk mailings from the same period came in at 3.1 percent (Experian 2010). A substantial share of recipients open such a message at all - a level of attention promotional campaigns rarely reach. The reason lies in the situation: the message follows a deliberate action and contains details the recipient will need again later.
Channel preference points the same way: 75.1 percent of consumers choose email for transactional messages such as order confirmations, compared with 61.3 percent for promotional messages (Sinch). The gap is easy to explain. A confirmation needs to be archivable, it gets forwarded, printed and looked up again weeks later when a question comes up. Commercially, more depends on these messages than their technical character suggests: automated flows account for only around 2 percent of all sends, yet contribute roughly 30 percent of email revenue (Omnisend). Anyone building email marketing automation for online shops while leaving the order confirmation untouched skips exactly the building block that arrives most reliably.
A transactional email is triggered by a specific action of the recipient and delivers information belonging to that very action: order confirmation, dispatch notice, password reset. A newsletter is an approach initiated by the sender. The distinction is not merely editorial. It determines the legal basis, the sending path and the expectation around delivery speed. If both kinds go out through the same sender domain and the same sending path, a poor reputation earned by promotional campaigns feeds straight through to the delivery of your confirmations.
The legal framework: confirmation, contract and advertising
In electronic commerce, Section 312i (1) no. 3 of the German Civil Code (BGB) requires traders to confirm receipt of an order electronically without undue delay (BGB). This acknowledgement of receipt is expressly not an acceptance of the offer. It states only that the order has arrived. Whether the same message already forms a contract depends on the terms and conditions and on the wording of the text. If both statements are mixed carelessly - one line confirms receipt, the next speaks of the goods as bindingly sold - room for interpretation arises that can be read against the shop in a dispute. Clean separation costs nothing and saves discussions.
Section 312f BGB applies in addition: in distance contracts the consumer must be provided with a confirmation of the contract on a durable medium, including the contractual terms and the pre-contractual mandatory information (BGB). In practice the order confirmation email takes on this role, often supplemented by a PDF containing the contractual terms. The withdrawal instructions and the model withdrawal form belong with it. A mere reference to a web page whose content the shop can change at any time does not satisfy the durable medium requirement under the prevailing view - the text belongs in the email itself or in the attachment. How clearly such details are worded also shapes how the shop is perceived. Where the boundary to manipulative design patterns runs is covered in the article on dark patterns in the checkout.
| Message | What it does | Classification |
|---|---|---|
| Acknowledgement of receipt | Confirms that the order has arrived | Required by Section 312i BGB, without undue delay |
| Declaration of acceptance | Declares acceptance of the offer | Formation of contract, governed by the terms |
| Contract confirmation | Contract text and mandatory information | Durable medium under Section 312f BGB |
| Invoice | States the amount due and the tax | Separate document, not part of the confirmation |
| Dispatch notice | Reports handover to the carrier | Service information without its own obligation |
Section 7 of the German Act against Unfair Competition (UWG) treats email advertising without prior express consent as an unreasonable nuisance in principle. Section 7 (3) UWG allows a narrowly drawn exception: advertising for a trader own similar goods towards existing customers is possible if the address was obtained in connection with a sale, the customer is informed of the right to object both at collection and in every further message, and no costs beyond transmission charges arise from objecting (UWG). The German Federal Court of Justice has held that even a customer satisfaction survey attached to an invoice email constitutes advertising and can be unlawful without consent (BGH). An order confirmation promoting a discount campaign for an unrelated product range clearly leaves the transactional frame.
The five zones of a solid order confirmation
A good order confirmation is not pretty, it is ordered. It answers questions in the sequence in which they arise while reading, and it does so even when the message is opened on a small screen, without images or as plain text. In practice a structure of five zones has proven itself. Each zone has exactly one job, and each zone can be checked, tested and revised on its own - which is the real advantage over a template that has grown over the years with details scattered across the text.
- Zone 1 - header and subject: sender name, subject line and preview text decide whether the message is opened at all and whether it can be found again in the inbox. Put the order number in the subject, use a speaking sender name instead of a bare address, and let the preview text add to the subject rather than repeat it.
- Zone 2 - order summary: order number, order date, chosen payment method and total at a glance. This zone is looked up most often when a question comes up later, so it belongs near the top.
- Zone 3 - line items: item, quantity, unit and total price, shipping costs and the tax breakdown. What matters is that the figures add up: the totals must follow from the lines shown, including discounts, vouchers or mixed tax rates.
- Zone 4 - delivery and billing data: addresses, shipping method and the expected delivery window. A concrete statement reduces status enquiries considerably more than a vague phrase such as shortly.
- Zone 5 - service zone: contact route for questions, notice on withdrawal and mandatory information, trader identification. This zone belongs at the end but has to be complete - it is the legally most sensitive part of the message.
The zone logic also helps with coordination inside the team, because responsibilities map cleanly: marketing writes the subject and preview text, accounting checks the tax breakdown and the totals, legal counsel signs off on zone 5. Anyone who thinks of the order confirmation as a continuation of the payment step quickly sees which details should carry over from the checkout. Everything that was visible in the last step before the order should reappear in the confirmation - otherwise it looks as though something has changed.
Building mail templates properly in Shopware
Shopware 6 in the Community Edition manages mail templates in the administration. Every template consists of a subject, an HTML part and a plain text part, and it can be overridden per sales channel (Shopware documentation). That separation is precisely the lever for shops with several brands, countries or audiences: the B2B channel needs different details from the consumer shop, and a channel using freight shipping needs different notes from one using parcel delivery. Squeezing everything into a single template full of conditions instead produces a file nobody dares to touch. For setting up several channels, the article on Shopware 6 multistore is worth a look.
One template per sales channel
One base template with variants derived per channel. Changes to shared parts happen in one place, while channel-specific deviations remain visibly documented.
Keep languages separate
Each language gets its own subject lines and text modules. How to keep quality up in the process is covered in the article on AI translation in the shop.
Variables and test data
Check every template against real order data: with a voucher, with mixed tax rates, with a partial delivery, with a differing billing address. Empty placeholders typically only surface in live operation.
Set triggers deliberately
Which status change sends which email belongs in your documentation. The article on the Shopware Flow Builder shows how to model such sequences without custom code.
{# Order line items in the mail template #}
{% for lineItem in order.lineItems %}
{{ lineItem.quantity }} x {{ lineItem.label }}
{{ lineItem.totalPrice|currency(order.currency.isoCode) }}
{% endfor %}
{# Expected delivery window, if set #}
{% set delivery = order.deliveries.first %}
{% if delivery and delivery.shippingDateEarliest %}
Expected delivery:
{{ delivery.shippingDateEarliest|format_date('medium') }}
to {{ delivery.shippingDateLatest|format_date('medium') }}
{% endif %}The plain text part deserves the same care as the HTML part. It is served when the mail client does not allow HTML rendering, it is read out reliably by screen readers, and in many filtering systems it has a positive effect on how the message is rated. An HTML email without a maintained text part is an avoidable risk. If you are unsure how deeply your templates have already been customised and what an update would overwrite, a structured inventory by a Shopware agency helps before the next version goes in.
Deliverability: aligning SPF, DKIM and DMARC
The best-written order confirmation is of little use if it lands in the spam folder. Three mechanisms decide whether a receiving system treats the message as genuine. SPF records in DNS which servers may send for a domain (RFC 7208). DKIM signs headers and content cryptographically so that changes in transit become visible (RFC 6376). DMARC ties both to the visible sender address and defines what should happen on failure - including the reporting mechanism that tells you who is sending in your name (RFC 7489). Only in combination do they produce a reliable picture; taken individually, each mechanism leaves gaps.
| Mechanism | What it checks | Typical mistake in shops |
|---|---|---|
| SPF | Which servers may send for the domain | DNS lookup limit exceeded, sending path missing from the record |
| DKIM | Signature of headers and content | Key rotated, selector not updated in DNS |
| DMARC | Alignment of sender details, handling of failures | Policy left on none, reports are not evaluated |
| Return-Path | Where bounces are delivered | Collective mailbox without evaluation, hard bounces stay on the list |
A second point concerns the separation of sending paths. If promotional campaigns and order confirmations run through the same domain and the same addresses, the reputation of one carries over to the other. Separate subdomains for transactional and promotional messages are the usual way to keep the ratings apart. This matters most in periods of high load: in 2024, Black Friday and Cyber Monday each brought around 33 percent more email volume (Sinch), mainly transactional messages. Planning for that volume in advance avoids queues in the mail dispatch - the article on load testing and an emergency plan for peak season describes the approach for the shop as a whole.
Set up a fixed set of test orders covering all the tricky cases: voucher, partial delivery, differing billing address, two tax rates, a long product name, umlauts in the customer name. Send to several mailboxes at different providers and check the subject, preview text, rendering in dark mode and the plain text part. Building this test into the release approval means finding mistakes before the customer does. In hosting and maintenance this step can be wired permanently into every release.
Rendering: dark mode, blocked images, accessibility
Mail clients do not render web pages. They interpret a restricted subset of HTML and CSS, they block images, they invert colours in dark mode and they clip long messages. An order confirmation has to stay readable under all of these conditions. For colour choices the same yardstick applies as in the shop: body text needs a contrast ratio of at least 4.5 to 1 against the background (W3C), large text at least 3 to 1 (W3C). When the email is inverted in dark mode, a contrast that was just about sufficient can become unreadable - which is why dark mode belongs in every test run.
- No text inside images. If image display is switched off, the content disappears. Order number, total and delivery note belong in the email as real text.
- Alternative text for every image. Even decorative elements need an empty alt attribute so that screen readers skip them.
- Table layout with a clear reading order. What sits side by side visually is read out linearly. The order in the source has to match what makes sense in content terms.
- Sufficiently large tap targets. Links and buttons need enough area to be hit reliably on a phone.
- Declare the language. The language attribute in the document makes screen readers choose the right pronunciation - particularly relevant in multilingual shops.
For transactional emails, accessibility is not an add-on but simply delivery quality: a message that cannot be read out does not reach part of its recipients. The criteria for measuring this are the same as in the shop. Which ones were added most recently is summarised in the article on the new success criteria of WCAG 2.2. For the email domain, contrast, focus order and the comprehensibility of link texts are the most relevant.
Measuring without collecting recipient data
With transactional emails the measurement situation differs from newsletters. Open rates rest on a tracking pixel, and several widespread mail clients now preload images through their own servers or block them entirely. The measured open rate is therefore inflated or vanishes. More dependable are metrics that originate in your own dispatch and your own shop. They work without additional data collection at the recipient and can be compared over time because they do not depend on the default settings of third-party software.
- Delivery rate and bounces: share of successfully handed-over messages, split into hard and soft bounces. Rising hard bounces point to typos in the address field of the checkout.
- Time to delivery: the gap between order completion and handover to the receiving server. Delays beyond a few minutes generate enquiries.
- DMARC reports: aggregate feedback shows which systems send in your name and where alignment fails (RFC 7489).
- Clicks on your own destinations: visits to order tracking or the customer account, measured in your own shop rather than through external tracking pixels.
- Service volume per order: the number of status enquiries relative to orders. This metric shows most clearly whether the confirmation does its job.
In many cases the existing infrastructure is enough for the evaluation: dispatch logs, shop database and ticketing system already hold the necessary data. Where metrics need to be brought together or reports automated, a manageable amount of development work arises, which we cover in custom programming. What matters is regularity: a monthly view of delivery rate and service volume reveals shifts early enough to react before they become visible in revenue.
Revenue from the order confirmation within the permitted frame
That leaves the question of how to turn this attention into revenue without leaving the legal frame. The lever lies less in the order confirmation itself than in the sequence that follows it: follow-up emails with matching product recommendations build on the confirmation that has just been read and can raise the average order value. The confirmation lays the groundwork by creating trust and keeping the contact open. Where advertising is to be included, the conditions of Section 7 (3) UWG apply (UWG) - including the notice about the right to object in every single message. Within those limits there is still ample room for content that genuinely helps.
Additions rather than discount battles
Accessories and consumables for the item just ordered are recognisably helpful. A systematic approach is laid out in the article on cross-selling in the online shop.
Explain delivery routes
For bulky items, explaining the process saves a lot of enquiries. How to model that in the shop is shown in the article on freight shipping for bulky goods.
A service route, not an ad space
A clearly visible contact route for change requests in the first hours after the order prevents cancellations and reduces returns that arise from uncertainty.
Prepare the repeat purchase
A pointer to the customer account with order history and a reorder function is not advertising but service - and noticeably lowers the barrier to the next order.
Sequence matters: mandatory information and order details first, the supplementary part afterwards. A confirmation that opens with a promotional banner and hides the order number in the lower third misses its purpose and risks being classified as a promotional email at the same time. A useful rule of thumb is the question: would a recipient still find the message useful if they read only the first two screen heights? If the answer is no, the structure needs revising before additional content is considered.
Anchoring the order confirmation in day-to-day shop operations
Transactional emails have an inconvenient property: they only draw attention when they are missing or wrong. That is precisely why mail templates age unnoticed. A new payment method is added, a tax rate changes, an extension inserts a field - and the template stays as it was. A fixed routine prevents this slow drift and costs little time once it is set up. The following sequence has proven itself in projects and can be hooked into existing release processes.
- Take inventory: list all active mail templates per sales channel and language, noting who changed them last and which trigger sends them.
- Cut into zones: structure each template into the five zones and check whether every zone is complete and in the right place.
- Reconcile legal texts: check withdrawal instructions, mandatory information and trader identification against the current state and record the review date.
- Align the technology: verify SPF, DKIM and DMARC, point the return path at a mailbox that is actually evaluated, and separate transactional from promotional sending paths.
- Define test cases: store the set of test orders permanently and run them, automated or manually, before every update.
- Watch the metrics: review delivery rate, bounces and service volume monthly and attribute deviations to a cause.
The effort for the first pass typically amounts to a few days; after that a short check per release is enough. We build this routine into Shopware maintenance so that templates, legal texts and dispatch configuration are looked after together with the shop instead of standing beside it as a special case. The order confirmation is the message your customers are most likely to read. That attention has already been paid for - it only needs to be used.
This article is based on data from Experian, Omnisend and Sinch. The figures cited refer to the state of the respective publication.
As a rule, no. The acknowledgement of receipt under Section 312i (1) no. 3 BGB (BGB) initially confirms only that the order has arrived. Whether and when a contract comes about depends on the terms and conditions. Many shops declare acceptance only with the dispatch notice. What matters is that the email separates both statements clearly and does not inadvertently declare an acceptance that is not yet intended.
Only under the conditions of Section 7 (3) UWG (UWG): a trader own similar goods, an address obtained from a sale, and notice of the right to object at collection and in every message. The German Federal Court of Justice has already classified a customer satisfaction survey in an invoice email as advertising (BGH). In practice this means using it sparingly, separating it clearly from the transactional part and having the legal assessment reviewed by a lawyer in each individual case.
The most frequent causes are missing or faulty alignment of SPF (RFC 7208), DKIM (RFC 6376) and DMARC (RFC 7489), a shared sending path with promotional campaigns, and a high bounce rate caused by outdated addresses. Pure image emails without a maintained plain text part are also rated less favourably. A systematic review of the three mechanisms typically resolves the larger part of the problem.
Not for the plain order confirmation: it is necessary for performing the contract and is in fact required under Section 312i BGB (BGB). Consent only becomes necessary once the message contains promotional elements that do not fall under the exception in Section 7 (3) UWG (UWG). Separating mandatory content from advertising is therefore not a formality but the core of the legal assessment.
Shopware 6 allows a mail template to be overridden per sales channel (Shopware documentation). A sensible setup uses a base template with the shared parts and variants derived from it for individual channels, languages or audiences. It is important to document the deviations so that an update does not overwrite them unnoticed.
Order number, order date, complete line items with figures that add up, shipping costs and tax breakdown, delivery and billing address, chosen payment method, a reachable contact route as well as withdrawal instructions and mandatory information under Section 312f BGB (BGB). If you are unsure whether your templates are complete, we will go through the messages together in an initial consultation.