Amazon SES for eCommerce: Scaling Promotional and Transactional Email That Actually Reaches the Inbox

Email is still the highest-ROI marketing channel in retail. A well-configured email infrastructure means every promotional send, order confirmation, and abandoned cart recovery reaches the inbox. A poorly configured one means your campaigns go to spam — or worse, you get blacklisted mid-send during a major promotional event.

Amazon SES is the right infrastructure choice for retail email at scale. But “setting up SES” and “setting up SES for reliable inbox placement” are two different projects.

Why eCommerce Email Deliverability Is a Revenue Problem

Inbox placement rates directly affect campaign revenue. A promotional email with 20% open rate that goes to spam for 30% of your list is actually a 14% open rate campaign. At scale, that gap between measured open rate and actual inbox delivery represents real revenue — the customers who would have converted if they had seen the email.

The deliverability problem is compounding. If your bounces, complaints, or spam placements climb above threshold levels at major inbox providers, your sending reputation deteriorates. Deteriorating reputation further reduces inbox placement. The spiral is difficult to reverse once it starts.

For transactional email — order confirmations, shipping notifications, password resets — deliverability failure has direct customer service consequences. A customer who does not receive their order confirmation calls support. At scale, that is measurable support cost tied directly to email infrastructure.

SES vs. SendGrid vs. Mailchimp for High-Volume Retail Sends

The comparison matters for retail teams deciding where to invest in email infrastructure.

Amazon SES costs $0.10 per 1,000 emails sent from EC2 or Lambda — for context, sending 10 million emails costs $1,000 in SES fees versus $20,000–$50,000 on commercial ESPs at equivalent volume. The trade-off is that SES requires more configuration work upfront: dedicated IPs, domain authentication, bounce handling, and reputation monitoring are not pre-configured out of the box.

SendGrid and Mailchimp offer managed deliverability infrastructure at significantly higher per-email cost. They make sense for lower-volume senders who need email campaign management features, not for retail platforms sending 10M+ emails per month where the cost differential is material.

For eCommerce teams sending high-volume promotional email, building on SES with proper configuration delivers better economics and comparable deliverability to commercial ESPs — with the added benefit of tight AWS integration for event-driven transactional email triggered by order and fulfillment events.

Setting Up Dedicated IPs for eCommerce Sending

Shared SES IP pools assign sending reputation across all accounts using those IPs. If another account on your shared pool triggers a spam complaint spike, your sending reputation is affected. For retail senders where deliverability is a revenue issue, dedicated IPs are not optional.

Dedicated IPs in SES cost $24.95 per IP per month. For high-volume senders, this is a small cost compared to the revenue protection they provide.

The configuration involves requesting dedicated IPs through the SES console, associating them with a configuration set, and routing your sending traffic through that configuration set. The more important part is what happens next: IP warm-up.

Automating Bounce and Complaint Handling

Automated bounce and complaint processing is mandatory for inbox placement. Major inbox providers track sender complaint rates — if your complaint rate exceeds 0.1%, deliverability degrades. If it exceeds 0.3%, blacklisting risk becomes serious.

The correct SES architecture routes all delivery events through Amazon SNS topics: one for bounces, one for complaints, one for delivery confirmations. SNS delivers these events to SQS queues. Lambda functions process the queues and suppress problematic addresses in real time, before the next send goes out.

This automation prevents your suppression list from falling behind your sending list — which is what causes complaint spikes. Without automated handling, a hard-bounce address stays on your list until someone manually removes it. With automation, it is suppressed within seconds of the first bounce event.

IP Warm-Up: The Step Most Teams Skip

New dedicated IPs have no sending history. Major inbox providers do not know whether the IPs are trustworthy. Sending at full volume from a cold IP triggers immediate spam filtering — your first large campaign would go directly to spam for most recipients.

IP warm-up is the process of gradually increasing sending volume over several weeks, starting with a small percentage of your most engaged subscribers (recent openers and purchasers), and growing volume as positive engagement signals (opens, clicks) accumulate and inbox providers recognize the IPs as legitimate.

A typical warm-up schedule:

• Week 1: 1,000–2,000 emails per day
• Week 2: 5,000–10,000 per day
• Week 3: 25,000–50,000 per day
• Week 4: 100,000–200,000 per day
• Weeks 5–8: Scale to full volume

The key is sending to your most engaged segments during warm-up. High engagement on warm-up sends builds reputation faster and creates headroom for the inevitable lower-engagement promotional sends that follow.

Case Study: Scaling to 200M Emails Per Month for an eCommerce Marketing Platform

TargetBay, a marketing automation platform serving eCommerce retailers, needed to scale to over 200 million emails per month with consistent inbox placement for both transactional and promotional sends.

FactualMinds designed and implemented a production-grade SES infrastructure that covered every layer: sandbox removal and production access approval, dedicated IP provisioning and phased warm-up over six weeks, SPF/DKIM/DMARC domain authentication across all sending domains, and automated bounce and complaint handling using SNS, SQS, and Lambda.

CloudWatch dashboards monitored bounce rate, complaint rate, and inbox placement continuously, with automated alerts when any metric approached risk thresholds. The system was designed to support TargetBay’s growth without requiring ongoing manual reputation management.

The result was a scalable, 200M+ emails per month infrastructure with improved deliverability, managed sender reputation, and automated compliance with major inbox provider requirements.

For more on Amazon SES deliverability services, see our SES service page. For the full picture on AWS for retail, see our retail industry page.

Get your SES deliverability reviewed