Multiple sender identities
By default, every automated email your store sends — order confirmations, shipping notices, campaigns, welcome emails, Domain Inbox replies — goes out from the single Defaultsender you set up when you connected Resend. Sender identities let you add more named “From” addresses on the same connection (e.g. orders@, support@, hello@) and control which one each type of email actually sends from, without connecting a second Resend account.
One connection, several names
It’s easy to assume “adding a sender” means a second Resend account, a second API key, or a second billing relationship. It’s none of those. A sender identity is just a label + display name + email address, layered on top of the one Resend connection and the domain(s) you’ve already verified there.
| What it is | |
|---|---|
| Default sender | The one address set up during Resend connect. Every automated email uses this unless a purpose (below) is pointed at a different identity. |
| Sender identity | An additional name + address on the same connection — e.g. a “Support” identity at support@yourdomain.com. Doesn’t require its own API key or its own domain verification if it shares a domain you’ve already verified. |
Adding a sender identity
This section sits directly below the “Sending from” (Default) card in the connected Resend panel — it only appears once Resend is connected.
Three fields appear inline: a short internal Label (e.g. Support — this is just for your own reference, recipients never see it), a Display name (what shows in the recipient’s inbox, e.g. My Store Support), and the email address itself.
The identity appears in the list immediately. There’s no separate verification step for the identity itself — only the underlying domain needs to be verified in Resend.
Pointing email types at an identity
Adding an identity doesn’t change anything by itself — nothing switches senders automatically. Below the identities list is a Default senderssection with one dropdown per automated email type; each one defaults to blank (meaning “use the Default sender”) until you point it at an identity.
| Purpose | Covers |
|---|---|
| Orders & shipping | Order confirmation and shipping-notification emails from Product CMS purchases. |
| Campaigns | Bulk sends from the Campaigns tab. |
| Welcome emails | Sent when someone joins an Email Signup Form list. |
hello@address, point “Orders & shipping” at an orders@identity, and leave Campaigns/Welcome on Default. Each dropdown is independent — you don’t have to fill in all three.Sending as an identity from the Domain Inbox
If you’ve enabled receiving (see Enabling receiving), the Domain Inbox tab's compose and reply forms both have their own From dropdown listing your Default sender and every identity — independent of the purpose assignments above. This is a per-message choice, not a saved setting.
Removing an identity
Click the ×next to an identity in the list to delete it. Any purpose dropdown pointed at that identity falls back to the Default sender automatically — it doesn’t leave that email type broken or unset.
Troubleshooting
| Symptom | What it means |
|---|---|
| New identity shows "Domain not verified in Resend — sends may fail" | The identity saved correctly, but its domain (the part after the @) hasn't been verified in Resend yet. Verify it the same way you verified your first sending domain, then the warning clears on its own. |
| Order confirmations still arrive from the old address after adding an "Orders" identity | The identity alone doesn't redirect anything — you also need to point the "Orders & shipping" purpose dropdown at it. |
| Deleted an identity and a purpose dropdown now shows "Default" | Expected — deleting an identity that was assigned to a purpose resets that purpose to Default rather than leaving it broken. |
| Identity dropdown in Domain Inbox compose is empty | No identities have been added yet — this dropdown always includes Default, so if it looks empty rather than showing just Default, check that Resend itself is connected. |