Order email that reaches the inbox.
Send confirmations, shipping notices, and delivery updates from a domain you verify yourself, with authentication and suppression handled so the message a shopper is waiting for lands where they check for it.
The order data flows in. The domain is yours.
A send call passes the order id and tracking link into a versioned template. It goes out from your own domain, signed with DKIM and backed by SPF and DMARC records Samva walks you through publishing.
POST https://api.samva.app/v1/messages
{ to: [{ email: "ada@example.com" }],
channel: "email",
email: { templateId: "order-shipped",
templateData: {
orderId: "A-1042",
trackingUrl: "https://…"
} } }
← { id: "msg_01hv8kq2", status: "pending" }TYPE HOST PURPOSE STATUS
TXT _samva ownership verified
CNAME s1._domainkey DKIM verified
MX send MAIL FROM verified
TXT send SPF verified
TXT _dmarc DMARC verifiedA shopper is waiting on a message that shows up.
Order updates land in spam.
A shopper waiting on a shipping notice checks their inbox and finds nothing, because the sending domain never built the authentication to earn a place there.
Notification templates drift.
A shipping-update email gets edited in one place and not another, and customers start seeing two different layouts for the same event.
A seasonal spike makes cost unpredictable.
Order volume triples for a week and you're left guessing what the bill looks like, or worse, hitting a cap that drops a confirmation.
From verified domain to confirmed delivery.
Verify your own domain, records managed.
Add your domain and publish the DNS records Samva generates. SPF, DKIM, and a DMARC policy establish the identity every order email sends from.
TYPE HOST PURPOSE STATUS
TXT _samva ownership verified
CNAME s1._domainkey DKIM verified
TXT _dmarc DMARC verified
# samva signs outgoing mail once verifiedOne template, every order.
A versioned template holds the order-shipped email. Pass the order id and tracking link as templateData, and the pinned version renders the same layout every time.
template order-shipped
v3 published pinned
v2 archived
v1 archived
send { templateId: "order-shipped", templateData: { orderId: "A-1042" } }
# same template, every orderA delivery event drives the confirmation.
A signed message.delivered event tells your app the notification reached the recipient's provider, so a confirmation flow can trigger off real delivery instead of a guess.
POST /webhooks/samva
{ event: "message.delivered",
messageId: "msg_01hv8kq2" }
# mark the order confirmed in your appGet the domain right first.
Questions from store engineering.
What happens during a seasonal spike?
There's no hard cap that drops a confirmation. Each plan ships a fixed monthly allowance, and every send past it settles on your invoice as itemized overage, so a big week costs more but doesn't cost you a delivery.
How do I set up DMARC?
Domain verification includes a DMARC TXT record alongside SPF and the DKIM CNAMEs. It's recommended rather than strictly required, and it ties the other two records into a policy that tells providers what to do with mail that fails authentication.
Do order confirmations need one-click unsubscribe?
No. Order confirmations and shipping updates are transactional, triggered by something the recipient did, and RFC 8058's one-click unsubscribe requirement is scoped to marketing mail. If you also send promotional campaigns from the same account, those need the unsubscribe headers; your order emails don't.
How do I confirm a delivery for my own flows?
Register a webhook for message.delivered. The event carries the message id and a status of delivered once the recipient's provider confirms it, so your app can trigger a confirmation step off a real signal instead of assuming the send worked.
Get your next order confirmation to the inbox.
Verify your domain, then send the first templated order email.