Foundation · 2 min
What you need to know
How should transactional email be tested during migration?
Trigger every required transactional message in a production-like environment and verify recipient, timing, language, values, links and sender identity. Check provider delivery events as well as the rendered email.
How should order-confirmation emails be validated?
Place controlled orders with different products, discounts, tax, shipping, and payment results. Confirm the message shows the correct order, totals, customer, links and support information exactly once.
How should shipping notifications be validated?
Test shipment creation, partial fulfillment, multiple packages, tracking updates, and delivery events. Confirm customers receive the right carrier, tracking link and item information without duplicate notices.
How should email authentication be checked after migration?
Verify SPF, DKIM and DMARC for every sending domain and provider, including alignment with the visible From address. Send controlled messages and inspect authentication results rather than assuming DNS presence is enough.
Why did email deliverability change after migration?
Deliverability can change when sender authentication, domains, IP reputation, content, recipient handling or provider configuration changes. Review authentication and provider events for controlled test messages.
A quick store check
Send each critical message to controlled accounts and inspect authentication results, rendered content and duplicate or missing triggers.
Foundation · 2 min
Frequently asked questions
Is receiving a test email enough?
No. Verify the correct trigger, recipient, values, links, authentication and provider status.
Can transactional and marketing email share the same rules?
They have different purposes and consent requirements; configure and test each according to its role.