A denim follow-up, step by step
Illustrative flow plan: help an eligible first-time denim buyer care for the item after delivery. Confirm the event names and properties supplied by the actual store integration before configuring Klaviyo. A placed order or elapsed delay is not proof of delivery.
| Flow step | Rule for this example |
|---|---|
| 1. Enter | A valid first denim purchase enters the proposed journey. Exclude test orders and cancellations. |
| 2. Wait or hold | Wait for a verified delivery signal. Hold promotional follow-up when a known return or unresolved service issue makes it unsuitable. |
| 3. Send useful guidance | Check sending eligibility and overlapping journeys, then use the approved care information for that item. Keep essential service messages separate. |
| 4. Review the outcome | Track delivery and useful engagement, then compare qualifying second purchases over equal observation periods. Attributed flow revenue remains separate from incremental effect. |
1. Map the moment before the message
A customer waiting for a delivery needs something different from someone who has worn the product for a week. Map order placement, fulfilment and the information actually available to your team. Do not call an order shipped or delivered just because enough days have passed.
Klaviyo documents order-triggered flows with delays and splits, including first-time versus returning buyers. Use that structure to support your own journey. Confirm which events and properties the store integration really supplies before making them part of a rule.
Source: Klaviyo: post-purchase flows ↗
2. Make product context earn its place
For a first denim purchase, a helpful follow-up could explain the care instructions verified for that item. For a returning customer, another generic welcome may add little. Use known purchase facts; a bought product does not prove a person’s size, identity or lasting preference.
Write the content brief around one task: help someone use the product, resolve a question or discover a relevant next category. Verify every fabric or care claim against the product source. Recommending a complementary item also requires checking its current availability.
3. Define exceptions before the flow goes live
Review cancelled orders, returns, unresolved service issues and customers who already purchased again. A cross-sell during an unresolved delivery problem can be badly timed. Document which signals are reliable enough to suppress or reroute a message and what happens when a signal is missing.
The lifecycle owner checks sending eligibility in the sending system. An analytical segment is not permission to email everyone in it. Keep essential order communication separate from promotional ideas, and have the responsible team review the actual configuration.
4. Measure a defined customer outcome
Choose a mature first-purchase cohort and a fixed period for observing a second qualifying order. State how cancellations and refunds are handled. A flow’s attributed revenue and the brand’s incremental revenue answer different questions; do not present one as proof of the other.
Use the Email Agent conversation to prepare a focused review of audience, product facts and proposed copy within the scope agreed for your workspace. A prepared journey is not a sent campaign. The owner reviews, implements and evaluates the change in the relevant tools.
Use this at work
- Map the actual order and delivery signals.
- Choose one useful message and verify its product facts.
- Review eligibility, exclusions and overlapping journeys.
- Define the second-purchase window before evaluating.
Reference material
Platform guidance checked 3 October 2026. Examples and working checklists are Faccelerate editorial illustrations.