Send purchase emails from your branded domain
Configure a branded sender for meal plan and product purchase emails, verify DNS for your sending subdomain, and keep replies routed to your support inbox.
On this page
Overview
Product Email Delivery lets Allspice send purchase emails from your site's branded sender after a reader buys a meal plan or product.
For example, instead of buyers receiving product emails from Allspice, they can receive them from:
Sally <hello@products.justrecipes-demo.allspicelabs.com>- Or, for your own site:
Your Brand <hello@products.yoursite.com>
This helps make purchase confirmation and meal plan delivery emails feel like they are coming directly from your brand.
Where to find this setting
In the Allspice Portal, go to:
Integrate → Domain Settings → Product Email Delivery
This section controls the sender name, reply-to address, sending subdomain, logo, brand color, and DNS verification status for product purchase emails.
Why this is needed
When a reader buys a meal plan or product through Allspice, Allspice sends a transactional email with access details and purchased content.
By default, emails may be sent from an Allspice fallback sender, such as:
Replies still go to your reply-to email address.
To send directly from your own domain, your sending subdomain must be verified. This protects your domain reputation and prevents unauthorized email spoofing.
What you need before starting
Before setting this up, make sure you have:
- Access to your domain's DNS settings
- A sender name you want buyers to see
- A reply-to email address where buyer replies should go
- A sending subdomain you want to use
We recommend using a subdomain, not your root domain.
Good examples:
products.yoursite.commail.yoursite.complans.yoursite.com
Avoid using your root domain directly:
yoursite.com
Using a subdomain keeps product email delivery separate from your main website and existing email provider.
Fields explained
Brand name
The name of your site or brand. Example: JustRecipes. This may appear in fallback sending and email branding.
Sender name
The person or brand name buyers will see in their inbox. Example: Sally.
If verified, buyers may see: Sally <hello@products.yoursite.com>
From local part
The part before the @ symbol in the sender email. Example: hello.
If your sending subdomain is products.yoursite.com, then your full sender email becomes hello@products.yoursite.com.
Reply-to email
The email address where buyer replies should go. Example: support@yoursite.com.
This can be your existing support, contact, or customer service email. It does not need to match the sending subdomain.
Sending subdomain
The subdomain Allspice will use to send product emails on your behalf. Example: products.yoursite.com.
Do not enter only products. Enter the full subdomain.
Logo URL
An optional logo URL used for email branding. Example: https://yoursite.com/logo.svg
Primary color
Your brand color. This may be used in buttons, accents, or other email styling. Example: #3093f3
Step-by-step setup
1. Enter your sender details
In the Product Email Delivery section, fill in brand name, sender name, from local part, reply-to email, sending subdomain, logo URL, and primary color.
Example setup:
- Brand name: JustRecipes
- Sender name: Sally
- From local part: hello
- Reply-to email: info@yoursite.com
- Sending subdomain: products.yoursite.com
- Logo URL: https://yoursite.com/logo.svg
- Primary color: #3093f3
The portal will show a From preview, such as Sally <hello@products.yoursite.com>.
2. Click Save sender
After you save, Allspice will generate DNS records for your sending subdomain. These records are required before Allspice can send from your branded domain.
3. Add the DNS records
Copy the DNS records shown in the portal and add them wherever your domain's DNS is managed.
The records may include:
- TXT
- TXT / DKIM
- CNAME
Add each record exactly as shown.
Do not manually invent or change these values. Use the records generated in the portal.
4. Wait for DNS propagation
DNS changes can take time to update. Some providers update quickly, while others can take longer.
After adding the records, return to the Product Email Delivery section and click Check DNS.
If the records are correct and available, the status will change to Verified.
5. Send a test email
Once verified, enter a test recipient and click Send test email.
The test email should come from your verified sender, such as Sally <hello@products.yoursite.com>.
If the sender is not verified yet, test emails may still send using the Allspice fallback sender.
What buyers receive before verification
Until your sender domain is verified, buyers can still receive product emails. They will be sent from the Allspice fallback sender, such as:
Replies will still go to your reply-to email address.
Example:
- From: JustRecipes via Allspice <delivery@mail.allspicelabs.com>
- Reply-To: info@yoursite.com
This means you can still sell products while DNS verification is pending.
What buyers receive after verification
Once verified, buyers receive emails directly from your branded sender.
Example:
- From: Sally <hello@products.yoursite.com>
- Reply-To: info@yoursite.com
This gives buyers a more branded and familiar email experience.
Understanding the DNS records
The DNS records shown in the portal are used to prove that you own or control the sending subdomain.
SPF TXT record
This authorizes the email provider to send on behalf of the subdomain.
Example:
- Type: TXT
- Host: products.yoursite.com
- Value:
v=spf1 include:mailgun.org ~all
If your DNS provider already has a TXT record beginning with v=spf1 for the exact same host, merge the include value instead of creating a second SPF record.
Only merge SPF records for the exact same host. Do not merge this with your root domain SPF record unless the host is also the root domain.
DKIM TXT record
This helps receiving inboxes verify that the email was authorized and not modified.
Example:
- Type: TXT
- Host: k1._domainkey.products.yoursite.com
- Value:
k=rsa; p=...
CNAME record
This may be used for email tracking or sending configuration.
Example:
- Type: CNAME
- Host: email.products.yoursite.com
- Value: mailgun.org
If your DNS provider uses proxying, such as Cloudflare, make this record DNS-only rather than proxied.
Recommended setup
For most sites, we recommend:
- Sending subdomain:
products.yoursite.com - From local part:
hello - Reply-to email: your normal support or contact email
This creates a clean sender like hello@products.yoursite.com while keeping replies routed to your existing inbox.
Frequently asked questions
Do I need to create an inbox for the sending subdomain?
No. The sending subdomain is used for outbound product emails. Replies go to the reply-to email address you enter in the portal.
For example, buyers may receive email from hello@products.yoursite.com, but replies can go to support@yoursite.com.
Can I use my existing email address as the sender?
Usually, we recommend using a dedicated sending subdomain instead of your main email address.
For example, use hello@products.yoursite.com instead of hello@yoursite.com. This keeps Allspice product emails separate from your regular email provider.
What happens if DNS is not verified yet?
Purchase emails can still be sent using the Allspice fallback sender. Your reply-to address will still be used.
Once DNS is verified, future purchase emails will send from your branded sender.
Do I need to add these records to my website host?
Add the records wherever your domain's DNS is managed. This may be your domain registrar, Cloudflare, GoDaddy, Namecheap, Squarespace, WP Engine, or another DNS provider.
Why does Allspice need DNS records?
DNS verification proves that you control the sending domain. This prevents unauthorized sending and helps improve deliverability.
Will this affect my normal website or existing email?
Using a dedicated subdomain like products.yoursite.com should not affect your main website or regular email setup.
Be careful not to replace existing DNS records unless you know they are for the same exact host.
Can I change the sender later?
Yes. You can update the sender details in the Product Email Delivery section. If you change the sending subdomain, new DNS records may be required.
Troubleshooting
Status says "Not set up"
You have not saved sender settings yet. Fill in the fields and click Save sender.
Status says "DNS setup required" or records are pending
The sender has been created, but DNS records have not been verified yet.
Check that:
- The records were added to the correct DNS provider
- The host/name values match exactly
- TXT values were copied fully
- CNAME records are DNS-only if using Cloudflare
- There are no duplicate SPF records for the same host
Then wait a few minutes and click Check DNS again.
Status says "Verified"
Your sender domain is ready. Product emails can now be sent from your branded sender.
Test email did not arrive
Check spam or promotions folders first. Then confirm the test recipient is correct and try again.
If the sender is verified but the email still does not arrive, contact Allspice support.
Summary
Product Email Delivery allows your site to send purchase emails through a branded sender domain.
- Before verification, buyers receive emails from Allspice with your reply-to address.
- After verification, buyers receive emails from your own branded sender, such as
Your Name <hello@products.yoursite.com>.
This improves the buyer experience and keeps product delivery emails aligned with your brand.