Shopify merchants have long juggled separate templates for printed receipts, email confirmations, and text messages. Starting today, the platform unifies these experiences: POS receipts sent by email or SMS now use the exact same layout you’ve built in the POS receipt editor. This change eliminates the need to maintain multiple designs, reduces errors, and gives customers a consistent view of their purchase whether they walk out of the store, check their inbox, or read a text.
What Changed
The Merchant Changelog announced that the email and text receipt flows now pull directly from the unified receipt editor. Instead of a separate “email receipt” template, the system renders the same HTML/CSS you use for the printed POS receipt. For SMS, the full receipt text is sent (not just a link to the order), matching the printed version’s line items, totals, and branding.
Who Is Affected
Both merchants and developers feel the impact. Merchants who have customized their POS receipt editor will instantly see those changes reflected in email and SMS receipts. Developers building custom receipt apps or using the Admin API to modify notification templates must adjust any code that previously targeted a separate email‑receipt schema. In short, anyone who touched receipt content now has a single source of truth.
How Receipts Work Now
When an order is completed in‑store, Shopify triggers three possible delivery methods: a printed receipt, an email receipt, and an optional SMS receipt. All three now share the same template stored under Settings > Notifications > In‑store receipts. If the merchant has enabled the unified receipt editor, the system skips the old “order confirmation” email for in‑store purchases and substitutes the unified receipt HTML. For SMS, the platform sends the receipt text directly, eliminating the prior link‑to‑order approach.
Steps for Merchants
Steps for Developers
Developers should audit any scripts or apps that reference the old receipt_email_template or receipt_sms_template endpoints. The Admin API now returns a single receipt_template object that contains the HTML used for all three channels. Update your webhook payload parsers to read the unified template, and adjust any Liquid customizations that assumed a separate email schema. If you ship a custom receipt‑generation app, switch to the ReceiptTemplate resource (GET /admin/api/2024-07/receipt_templates.json) to fetch the current layout.
Sample Unified Receipt Configuration
Below is a minimal JSON payload you might send via the Admin API to update the unified receipt template. Notice the single html field – no separate email or SMS sections:
POST /admin/api/2024-07/receipt_templates.json
{
"receipt_template": {
"name": "Unified POS Receipt",
"html": "<div style='font-family:Arial'>{{ shop.name }}\n{{ order.name }}\n{% for line in line_items %}{{ line.quantity }} x {{ line.title }} – {{ line.price | money }}\n{% endfor %}\nTotal: {{ total_price | money }}</div>"
}
}
Compliance Notes for EU Markets
In France, Germany, Italy, Spain, and Sweden the email/SMS receipt is displayed as an “order confirmation.” The printed receipt still satisfies local tax‑record requirements, so merchants should keep the printed receipt layout compliant (e.g., include VAT ID, merchant address, and transaction timestamp). The unified template respects those fields, but double‑check that any locale‑specific wording remains in the printed version.
Common Pitfalls and How to Avoid Them
• Leaving old email‑only Liquid snippets (like {{ receipt_url }}) can cause broken links in the new unified receipt. Remove them from your custom HTML. • Testing only the printed receipt may hide formatting issues that appear in email clients. Send test emails to Gmail, Outlook, and a plain‑text SMS gateway to verify line breaks. • If you use a third‑party email service (Klaviyo, SendGrid) for order confirmations, ensure the integration now points to the unified template endpoint rather than the deprecated order_confirmation template.
Conclusion
The new unified receipt experience simplifies operations, reduces maintenance overhead, and gives customers a consistent record of their purchase across print, email, and text. Merchants should verify their receipt editor settings, while developers need to migrate any custom code to the single receipt template model. Take a few minutes today to test the flow, update your templates, and enjoy a cleaner, more reliable checkout experience. Need help tweaking your receipt design? Reach out to Shopify Support or drop a comment below – we’re happy to walk you through the setup!
