Ecommerce Customer Win-Back Template: Define Who Is Eligible

“Has not purchased recently” is not a complete reason to contact someone. A useful win-back workflow explains what inactive means for this business, why the message is relevant now, and when the record must leave the sequence.

Copy and fill this win-back record

Cohort and inactivity definition:
Qualifying purchase evidence:
Customer permission and preferred route:
Exclusions and suppression:
Current catalog/service source:
Relevant change or useful reason:

Evaluation trigger:
Message purpose, approved fields and CTA:
Offer terms and approval, if any:
Exit and re-entry events:
No-response state:
Control/holdout and attribution rule:
Completion evidence:
QA owner and review cadence:

Estimated completion time: 30–45 minutes once order history, permission, catalog and reporting owners are available. Copy the record into the workflow or campaign document, replace every field, then save or export the approved version with cohort query, source dates and owner.

Field guidance

  • Define inactivity from a reviewed purchase cycle or lifecycle policy, not a universal day count.
  • Exclude returns, disputes, open service cases, invalid identity matches, active purchases and suppressed contacts.
  • Give the message a current buyer-relevant reason; a discount is optional and never a substitute for relevance.
  • Record offer version, eligibility, expiry and commercial owner when an incentive exists.
  • Define attribution and a control or holdout before interpreting orders as campaign impact.
  • Record the permitted route and current preference independently of purchase eligibility.
  • Name the catalog/service source and verification date; stale products or policies stop the action.
  • Run a versioned cohort evaluation and preserve the qualifying purchase snapshot.
  • Allowlist message fields and one CTA so copy cannot invent urgency, interest or customer need.
  • Define exits and require a new approved event for re-entry; give no response a visible closed state.
  • Store cohort, source, message, delivery, action and final reason; assign QA to eligibility and attribution errors.

Klaviyo documents win-back flows as messages to previously engaged customers after a defined period and recommends using business purchase-cycle data rather than a copied delay. The product setup is vendor-specific; the mechanism does not prove performance or feature parity elsewhere. Review the documentation.

Fictional filled example: seasonal home-care customer

Cohort and inactivity definition: Customers with a completed fictional HomeCare order and no completed order in their reviewed 120-day lifecycle window
Qualifying purchase evidence: Last qualifying order HC-420 on 10 April 2026, ICT; no newer completed order as of 15 August 2026
Customer permission and preferred route: Promotional email permitted; preferred route = email
Exclusions and suppression: Return/dispute, open product issue, invalid address, opt-out, employee/test, active checkout or newer purchase
Current catalog/service source: HomeCare catalog v8 verified 15 August 2026
Relevant change or useful reason: Updated care guide is available for products already owned; no claim that the customer needs another item

Evaluation trigger: Daily cohort evaluation with a stored query version
Message purpose, approved fields and CTA: Offer the updated HomeCare guide using only prior-order context. Message: “Would the updated HomeCare guide be useful? It includes care steps for items in your April order. You can view the guide or browse current products.” CTA: view guide; secondary catalog link only
Offer terms and approval, if any: None
Exit and re-entry events: Reply, purchase, opt-out, service case, delivery failure, cohort no longer valid or owner pause; re-entry requires a new approved cohort event
No-response state: Close after one message
Control/holdout and attribution rule: Random eligible holdout defined before launch; orders attributed only under the approved analysis window
Completion evidence: Cohort snapshot, message, delivery, action and final reason stored
QA owner and review cadence: Lifecycle owner reviews false eligibility, complaints, source freshness and attribution monthly

All names, IDs, dates and policies in this example are fictional. The 120-day window is illustrative, not a recommended cadence.

Quality checklist

  • The cohort query, purchase window and source date are reviewable.
  • Current purchases, cases, returns and suppressions take precedence.
  • The message has a useful reason beyond “we miss you.”
  • Offer facts are current and approved, or no offer is used.
  • Exit and re-entry behavior prevent an evergreen loop.
  • Reporting distinguishes attributed activity from causal lift.

Common mistakes

Mistake Safer correction
Copying a 90-day rule from another store Derive and review a lifecycle definition for the category.
Targeting every old customer Validate identity, permission, service state and current activity.
Using a discount as the only reason Offer a current useful resource or change; keep incentive optional.
Counting all later orders as wins Predefine attribution and use a control when causal inference matters.

What to do next

Copy the record into a document and define the eligible customer group first. When a customer buys again, end this flow and evaluate the new order under the repeat-purchase reminder or post-purchase workflow.

Evidence and limitations

This template does not define lawful permission, a universal inactivity window, offer economics, revenue lift, product integration, or Easy AI capability.

FAQ

Recommended for you