Library / apparel brands / Apparel lives on returns, second purchase, and segments that are not all subscribers

apparel brandsHow to wire it

Apparel lives on returns, second purchase, and segments that are not all subscribersReturns and second purchase are different states. Mailing a returner like a VIP is how you look careless.

Apparel leaks when campaigns go to the full list, returners get the same drop hype as fans, post-purchase is a review on day zero, and second-purchase is 'we miss you'. This vertical wires return as a state, second-purchase in post-purchase (attach, second pair, replenish basics), suppress recent buyers from acquire, and flows that stay on in drop week. Drops are pulses. States are flows.

00

The short version

Intern through CEO

Apparel leaks when campaigns go to the full list, returners get the same drop hype as fans, post-purchase is a review on day zero, and second-purchase is 'we miss you'. This vertical wires return as a state, second-purchase in post-purchase (attach, second pair, replenish basics), suppress recent buyers from acquire, and flows that stay on in drop week. Drops are pulses. States are flows.

  1. 01

    The weekly number is second-purchase rate (windowed) and return-state exclusions on the next drop. Full-list drop revenue is a vanity if it includes yesterday’s buyers and yesterday’s returners.

  2. 02

    Fit and care are post-purchase jobs. They reduce returns and set up the second item. A review beg while the parcel is in transit is the wrong job.

  3. 03

    Browse and cart must not clone. Apparel consideration can be long — coupon-first cart trains waiters.

  4. 04

    Drops are campaigns. They do not get to pause welcome and cart.

  5. 05

    Size properties help if you will use them. Asking and ignoring is junk data.

Who

Same system. Three jobs.

Read your row

Intern

What you actually do

Previews and delays. Return test. You are lifecycle ops, not merchandising.

Operator

What you protect

Return manners. Second-yes path. Drops as pulses. Flows stay. Fit before review.

CEO

What you refuse to fund

Apparel LTV is second purchase and not annoying returners. Those states are the numbers. Full-list drops are optional pulses, not the system.

Wire

How to connect it

Objects, then edges

Placed Order, refund/return event, RFM or recency, second-purchase path, drop campaign segment, browse vs cart, size/fit content, returner suppression.

  1. 01

    Return/refund → exclude from review-ask and from hype drops for a window

  2. 02

    Post-purchase → fit/care, then attach or second-item path — not review at T+0

  3. 03

    Drop campaigns → exclude recent buyers and in-cart flow members as mapped

  4. 04

    Win-back finite; January hangover planned before peak

Steps

Do this in order

Why, then done when
  1. 01

    Return as a state

    Event or property. Exclusions written.

    Why: Hype-mailing a returner is careless automation.

    Done when: Refunded test out of the next drop preview.

  2. 02

    Second-purchase path

    In post-purchase: attach, second pair, basics replenish — pick one to ship.

    Why: 'We miss you' covers none of them well.

    Done when: One path live.

  3. 03

    Drop exclusions

    Recent purchasers, return window, flow collisions.

    Why: All subscribers is how you train wait-for-20%.

    Done when: Preview.

  4. 04

    Fit/care before review

    Delay review until they have the piece.

    Why: Day-zero review is shipping comments.

    Done when: Delay holds.

  5. 05

    Flows on during drops

    Write the rule. Peak plan.

    Why: Pause is paying twice.

    Done when: Q note includes the rule.

What an intern should wire first

Return exclusion on drop preview. One second-purchase path. Review delay. Flow-on-during-drop note. You are not designing a lookbook.

What the brand should refuse

A bigger drop, more full-list sends, or a loyalty points vendor until return state and second-purchase path exist. Points on a missing second-yes are a discount costume.

The usual failure

Full-list drop. Returners in VIP. Review day 0. Cart coupons. Flows paused for the drop. That is a calendar with a warehouse problem.

The weekly number

Second-purchase rate, returner exclusion on drops, flow RPR. Not drop GMVs that include people who already bought this week.

Why

Questions people actually ask

Pushback is normal

Drops are our brand.

Then they are pulses on segments. Brand is not a license to mail returners and yesterday’s buyers the same hype.

We don’t have RFM.

Start with recency and return state. RFM can wait. Exclusions cannot.

Returns are a warehouse thing.

Warehouse is the event. Email is the manners. The state must reach Klaviyo.

This week

This week: return state, one second-purchase path, drop exclusions, review delay, flows-on rule. No extra full-list drop.

DTC brands

Other verticals in this lane

apparel brands
beauty brands

Beauty retention is a cadence problem more than a creative problem

Revenue per recipient on flows is the number. Open rate is a meeting.

Read ↗
supplement brands

Supplements are a subscription and replenishment system pretending to be a brand

If Placed Order is dirty, every flow metric is theatre. Fix the event before the subject line.

Read ↗
coffee brands

Coffee is replenishment. If flows are weak, you paid for one-time caffeine

Subscribe vs one-time must be different journeys or you will discount people who already pay you monthly.

Read ↗

All DTC brands · coaches franchise systems training brands

Working notes

DTC Retention Scorecard

Score your Klaviyo and lifecycle system the way an operator would. Request the file. It arrives by email — not a public dump, not a drip of slogans.

Request the notes ↗
Next

If the leak is expensive, talk.

Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.