Mailgun
A useful scenario is custom email logic that connects sending, delivery events and diagnostics. Retain message IDs and limit logged personal data; a retried request must not send a second confirmation.
Configure and trace confirmations, order updates and password resets. Separate message creation in the store from acceptance and delivery by the email service.
An order generates a confirmation → the selected provider accepts it → we record the message ID and status. A bounce or complaint updates the suppression process. If a request times out, check whether the message was already accepted before retrying.
A useful scenario is custom email logic that connects sending, delivery events and diagnostics. Retain message IDs and limit logged personal data; a retried request must not send a second confirmation.
Send system messages with managed templates and status tracking. Decide whether templates live in the store or at the provider, who approves edits and how sending stops for permanently failing recipients.
For WooCommerce, move sending away from hosting mail through SMTP or the AWS API. Check domain verification, region, IAM permissions, sandbox/production status and quotas. Bounce and complaint handling belong in the implementation; monitoring and templates need planning beyond the sending connection.
Do not assume that it can. Shopify’s built-in notifications and app-generated messages use different sending paths. First identify who generates each message and what control the specific setup provides.
No. We distinguish accepted requests, delivery to the recipient server, bounces and complaints. No provider guarantees inbox placement; tracing makes failures diagnosable.
For WooCommerce, configure SMTP or API sending with appropriate AWS permissions, a verified domain and bounce handling. Before launch, check the region, sending limits and required production access.
Tell us about your project and we'll figure out how we can help.