Feature deep-dive

Per-tenant email senders

Order confirmations to your customers come from your domain via AWS SES. No more shared "from" addresses.

Start free trial → All features

Most multi-vendor platforms send order confirmations from a shared "from" address. Your customers see a generic third-party sender — which hurts deliverability and breaks brand consistency. Ordnance runs AWS SES domain identities per tenant — your customers see your domain, your branding, your deliverability reputation.

How it works

Per-tenant SES domain identity

Verify your sending domain (orders.yourstore.com). DKIM CNAMEs + SPF TXT, all displayed in the setup wizard.

Customer-facing emails from you

Order confirmations, tracking notifications, status updates — all from your domain.

Operations alerts still platform

Internal alerts (sync failures, DLQ pending, billing issues) come from the platform. Customer-facing emails come from you. Clean separation.

Setup wizard with DNS records

Add a domain, get the exact CNAME + TXT records. Paste at your registrar. Click "verify" — done.

Side-by-side

WhatOrdnanceSparkShipping
Custom from-addressYes — per-tenant SESShared sender
DeliverabilityCustomer's domain reputationShared reputation hit

Per-tenant email senders FAQ

Do I need an AWS account?
No — we host the SES setup. You add DNS records to your domain to verify ownership. Nothing else needed.
When does this go live?
Schema and UI are ready now. Live SES API integration ships with the production deployment (Q3 2026). Until then, all emails come from the platform-default address.
What about reply-to handling?
Configurable per identity. Default: customer replies go to your support inbox.

See it in your tenant.

14-day trial · no card · cancel anytime.

Start free trial →