A message for each side.
A purchase means a confirmation for the buyer, a new-order alert for the seller and maybe a note for your operations team. Send separate emails so each person sees only what is meant for them and no one’s address is exposed.
Budget by recipient: one order that notifies a buyer and a seller is two emails.
Your brand, or the seller’s.
Most marketplaces send from their own verified domain, for example orders@yourmarket.com, with the seller’s name as the display name. Sellers who want their own domain can verify it, and you can restrict an API key to it.
Pro includes 10 domains and Scale includes 100.
Replies that stay on your platform.
Give each conversation its own reply address, such as order-1042@reply.yourmarket.com. Turn on receiving for that subdomain and every reply arrives in your app as a signed webhook, ready to show in the buyer-seller thread.
Because replies pass through your platform, you can moderate messages, hide personal email addresses and keep a complete history of each transaction.
Who gets which email
| Event | Buyer | Seller |
|---|---|---|
| Order placed | Order confirmation | New order with shipping details |
| Item shipped | Tracking information | Shipping confirmed |
| New message | Reply notification | Reply notification |
| Payout sent | — | Payout confirmation |
Email for marketplaces: common questions
- How do I hide buyer and seller email addresses?
- Use platform reply addresses on a receiving subdomain. Replies arrive in your app by webhook and you pass on the content without revealing anyone’s personal address.
- Can sellers send from their own domain?
- Yes, once the domain is verified in your workspace. Most marketplaces use their own domain with the seller’s name as the display name, which needs no setup from sellers.
- Is this different from the ecommerce setup?
- The API is the same. Marketplaces add a second audience, the sellers, and usually route replies through inbound email.
- How do I avoid duplicate order emails?
- Use an Idempotency-Key per email, such as order-1042-buyer and order-1042-seller, so retries never send twice.