Блог EN
2026-11-14 14:58 Email Marketing

Customers keep receiving ads for products they bought: fix email exclusions

Someone buys and pays for a product, then hours later receives “Still thinking of buying it?” This wastes marketing effort and damages trust. A valid exclusion must check the specific SKU, product variant and order status, not merely whether the customer has ever bought anything. Otherwise useful service messages may be suppressed while failed payments incorrectly count as completed sales.

Define the event that ends the sales sequence

For a specific paid SKU, connect the order record, variant and confirmed status. A thank-you page view is weaker evidence than an approved purchase event: the page can be reopened and payment may fail. Reservations, partial payments and returns require separate policies. Synchronise marketing opt-outs with the CRM and distinguish essential operational notifications from promotions. A purchase event alone does not establish permission for future offers.

Verify the platform's exclusion capabilities

MailerLite supports group and segment exclusions in certain campaign and automation contexts, and purchase-based triggers for connected e-commerce platforms. Do not assume a universal SKU check across every workflow. Email automation design must begin with actual purchase events, segment refresh latency and the chosen platform's available controls.

Check exclusions close to actual sending

A segment calculated hours earlier can be obsolete. Identify whether the condition is evaluated on entering a flow, before a step or at send time. If the platform cannot check the latest purchase at the required moment, consider a different architecture or separate decision service. Do not promise immediate synchronisation without measured evidence.

Hypothetical TASK-094

Contact C-094 receives a planned SKU-A warming email at 15:00. The queue is prepared at 10:00, but the customer pays for SKU-A at 11:00.

  1. Verify a successful payment and SKU-A in the authoritative order record.
  2. Update or expose the buyer exclusion in the sending decision system.
  3. Check the SKU-A condition again before the scheduled step.
  4. Simulate a different purchase, SKU-B: that does not necessarily require suppressing every other recommendation.
  5. Test refunds, cancelled payments, slow integration updates and duplicate order events.

Positive test: no SKU-A promotion at 15:00; operational confirmations remain. Negative test: a queue built at 10:00 ignores the purchase at 11:00. Move the check closer to sending or change the integration.

Scope exclusions separately from integrations

The email commercial offer describes segmentation, automation and CRM, but not a guaranteed native SKU filter in any email system. Confirm whether product codes, actual payments and cancellation signals reach the mailing tool. If data is absent, first improve the event contract, then test suppression.

What the acceptance work includes

Provide campaign diagrams, product identifiers, payment events, order statuses, marketing permission rules and test contacts. Work may involve segments, custom integration, negative tests and monitoring. Request a quote through contacts using anonymised error examples. One tick in a segment-setting screen does not prove real queued messages will be suppressed.

Time-ordered purchase exclusion

Fictional store S-94 sells a coffee machine. Buyer C94 adds it to a cart, purchases on another device and then receives “You forgot your coffee machine.” The problem is relying only on a cart event without checking the latest paid order.

  1. For cart_added, record a reliable customer and item identifier rather than depending only on a potentially changed email address.
  2. On order_paid or another approved purchase confirmation, set the exclusion for the exact SKU.
  3. Before dispatch recheck the exclusion while accounting for possible integration delay; agree a safe outcome if the status is uncertain.
  4. After refund or cancellation, never restart sales automatically without an approved separate flow.

Filled TASK-094 checks

Test A: SKU-94 added to cart at 10:00 and paid at 10:03; reminder due at 11:00 is suppressed. Test B: cart remains unpaid; a reminder may be sent only if the lawful basis and configured rules permit. Test C: order paid at 10:59 but the event arrives after 11:00; investigate priority and the race between payment and send. Positive: purchased product is not advertised as abandoned. Negative: the segment updates, but the email queue still sends the old step.

Also check bundles, variants, partial orders, subscriptions, message frequency and marketing permission. The estimate should cover event/identity mapping, exclusion rules, test logs and monitoring, not simply one static filter.

The service-versus-marketing message guide clarifies classification and unsubscribe boundaries. Automation flow planning covers stopping a sequence after an order; post-purchase email design ties further guidance to actual delivery and status events, not just the original promotion.