Resend

Orchard doesn’t send email on your tenant’s behalf — every store brings its own Resend account, so order confirmations, shipping notices, and marketing mail come from the store’s own domain and brand, never Orchard’s.

What the store owner configures

From Integrations → Resend in the admin:

  • API key (re_...) — must be a real Resend key; Orchard validates the prefix before saving.
  • From address, in Name <address@yourdomain.com> form — must already be a verified sender on the tenant’s own Resend account. Orchard doesn’t provide a DNS/domain-verification wizard; that verification happens entirely on Resend’s side before the address is entered here.
  • Reply-to (optional — defaults to the from-address).
  • Test / live mode, matching the split everywhere else.

A “send a test email” action on the same page confirms the key and from-address actually work before the store owner relies on them.

What this means for you as an integrator

You don’t pass email credentials or a from-address anywhere in the API — Resend is resolved entirely from the tenant’s configuration. The relevant signal from your side is the order.paid webhook (and the other order/subscription lifecycle events) if you want to trigger your own messaging in parallel with the store’s transactional email.

Delivery model — what’s durable vs. direct

Two different paths exist internally, worth knowing if you’re troubleshooting a missing email report from a store owner:

  • Order, shipping, and subscription transactional email sends synchronously through the tenant’s Resend account at the moment it’s triggered. Every send — successful or not — is logged to the customer’s Communications history in the admin.
  • Digests and a few other flows (password reset, weekly digest) go through a durable, retrying send queue rather than firing directly.

Both paths ultimately use the same per-tenant Resend credentials; the difference is only in retry behavior on transient failure, not in which account the mail comes from.

Bounces and complaints

Resend delivery events (bounce, complaint) are received by Orchard and used to suppress future sends to that address and, for marketing mail, flip the customer’s marketing consent off automatically — the store owner doesn’t need to prune their own list by hand.