Email Delivery Chain (Send From Your Own Address)

Where to find it: Left menu → Integrations → Email section → Email delivery chain card Who it is for: Anyone who wants their store's emails to go out from their own domain (such as orders@mystore.com) and never wants delivery to stall. In short: You define SMTP and Resend at the same time and set an order between them; your emails go out through the first working service in the order, and if none of them work, Treyza infrastructure takes over.

What is it for?

By default, every email your store sends (order confirmation, shipping notification, campaign, email flow, etc.) goes out through Treyza's own infrastructure. That means everything works without any setup.

If you want to put your brand front and center, you may prefer emails to go out from your own domain. To do that you connect your own SMTP server or your Resend account.

The delivery chain lets you define both services at once and set a priority order between them. The chain works like this:

1. The first service in the order is tried.
2. If that service cannot be reached (server down, wrong password, quota exhausted, etc.), the next service is tried.
3. If none of the services you defined can send, Treyza infrastructure steps in as a last resort.

Steps to set up the chain

1. Open the Integrations page from the left menu and scroll to the Email section.
2. Click the SMTP card and enter your server details (Host, Port, Username, Password, SSL/TLS, Sender Address).
3. Before saving, press the Test Connection button. If the details are correct you will see a green confirmation message.
4. Turn on the Enable Integration switch and press Save.
5. Repeat the same steps for Resend (API Key and Sender Address).
6. Return to the Email delivery chain card below the Email section. Both services appear in the list.
7. Drag the handle on the left of each row to set the order you want. The order is saved automatically.

What is on the card?

Active chain summary: At the top of the card, badges show the order in which your emails will be attempted, for example 1. Resend → 2. SMTP → 3. Treyza infrastructure. This order is the one actually applied.

Sortable list: Each row shows the service name, the sender address and the status (Active / Inactive / Not configured). Drag a row to change the order.

Test Connection: Checks whether the service can really be reached. For SMTP it connects to the server and verifies the username/password; for Resend it verifies the API key and checks whether your sender domain is verified in your Resend account.

Test email: Sends a real test email to an address you choose. The button on a row tries only that service (no fallback), while the Test chain button at the top runs the whole chain.

Treyza infrastructure row: It appears at the very end of the chain as a dashed row carrying the Last resort badge. This row cannot be removed or reordered; it always stays last.

Recent deliveries: When you expand this section at the bottom of the card, you see which service recent emails went out through, whether a fallback happened, and the error message if there was one.

How is the sender address determined?

The Sender Address you enter for each service determines the From field of the emails sent through that service. Treyza keeps the display name (your store name, for example) but always pins the address to the one you defined for that service.

This prevents emails from accidentally being sent from an address you do not own. For example the display name becomes "My Store" and the address orders@mystore.com.

When does it fall back, and when does it not?

Which emails go through the chain?

Emails that go through the chain (your store's own): Order and shipping notifications, abandoned cart reminders, review invitations, email campaigns and flows, contact form notifications, purchase orders sent to suppliers, the e-archive invoice link sent to the customer, panel notification emails, gallery backup notifications.

Emails that always go through Treyza infrastructure: Account verification, login code, password reset, email change, new device alert, store staff invitation, subscription and invoice emails, quota warnings, Treyza support tickets and the Treyza newsletter.

What happens to the email quota?

Even when you use your own SMTP server or Resend account, the emails you send still count against your plan's email quota. The quota does not meter the sending cost; it meters your use of Treyza infrastructure such as the template editor, the campaign engine, open/click tracking and the delivery queue.

This information is also shown as a note on the delivery chain card.

Frequently asked

What happens if I never define SMTP or Resend? Nothing changes. All of your emails keep going out through Treyza infrastructure exactly as they do today. The chain is completely optional.

I defined both services but the order does not seem to matter. Why? Only services that are both enabled and fully configured take part in the chain. The "Active chain" summary at the top of the card shows which services are really in the order.

I changed the order, when does it take effect? The order takes effect as soon as it is saved. During busy periods the previous order may still be used for a few minutes; this is normal.

The test email arrived but no email arrives for a real order. The test email only checks the delivery path. For the order email to go out, the related email template must also be enabled. Check your templates under Marketing → Email Templates.

Why do I not see every email in the recent deliveries list? Individual emails such as order and notification messages are all recorded. For campaign and email flow sends, only the problematic ones (fell back or failed) are recorded; you can see the details of successful campaign sends in the Marketing → Email Campaigns reports.

Who can see my password and API key? No one. The sensitive fields you enter are stored encrypted and are never written back to the panel; only their masked form (••••1234) is shown on screen. They are masked in error records as well.

I saw a "Suppressed" badge in the recent deliveries list — what does it mean? The recipient address is on the suppression list because it bounced earlier or reported spam, so sending was never attempted. See Sending From Your Own Email Address: SPF/DKIM Setup and Suppressed Addresses for details and how to remove a suppression.

Next step

If you send from your own domain, you also need to add the SPF/DKIM records for your email to actually arrive. You can also have bounced and complained addresses suppressed automatically:

→ Sending From Your Own Email Address: SPF/DKIM Setup and Suppressed Addresses