A Dutch marketplace with 500,000 sellers and 8 million buyers was sending all email — seller payout notifications, buyer order confirmations, promotional campaigns, and platform announcements — from the same IP pool. Seller-initiated promotional campaigns were generating complaint rates above 0.2%, contaminating the reputation pool used for buyer transactional confirmations.
When buyers failed to receive order confirmations, they opened disputes assuming their payment had not processed. The marketplace was absorbing €180,000 per month in dispute resolution costs directly attributable to email non-delivery. Customer service data showed 34% of all buyer contacts were email-related follow-ups for confirmations that had gone to spam.
SolutionWe deployed a 10-IP segmented infrastructure: 4 IPs for buyer transactional email (highest trust), 3 IPs for seller operational email (payouts, reports), and 3 IPs for platform marketing. Each stream had independent authentication, monitoring, and complaint rate thresholds. Seller-generated promotional email was moved to a separate domain with its own warm-up cycle.
Results"We were losing €150,000 per month in dispute costs because buyers weren't getting their order confirmations. Email infrastructure was a €1.8M annual business problem masquerading as a technical issue."
— COO, Dutch MarketplaceMarketplace platforms have a structural email reputation problem: the behavior of one user type contaminates the reputation used for another. The only architectural solution is full stream separation with independent IP pools, domains, and complaint rate monitoring per stream.
