Klaviyo Flows for Fashion Brands on Shopify

Key takeaways

• Klaviyo flows for fashion differ from the generic ecommerce playbook in four ways: fit is unknowable from a photo, shoppers self-identify by size and style, inventory moves in drops and seasons, and the second purchase is an outfit rather than a refill.
• Back in stock is the flow this category makes mandatory. Fashion sells out by size, and Klaviyo’s Subscribed to Back in Stock trigger turns every sellout into a send.
• Use the welcome flow to capture size and style as profile properties. Every later flow gets sharper because that data exists.
• Time the review request past the exchange window, not to delivery. Klaviyo Reviews defaults to seven days after delivery, which lands while many fashion customers are still deciding whether to keep the item.
• Cross-sell the outfit, not the bestseller. Ordered Product events carry the product’s collections and tags, so a trigger split can branch on what was actually bought.

Klaviyo flows for fashion brands are not the standard five-flow template with different photos. Fashion has category facts that change what each flow should do, when it should fire, and what it should say.

This guide assumes Klaviyo is already connected to your store. If it is not, start with our Klaviyo and Shopify setup guide and come back. What follows is the flow architecture for a fashion brand: the triggers, the timing, the branching, and the reason each flow exists in this category specifically.

Why you can trust us

We have been in the Shopify space for over four years and have worked with hundreds of Shopify brands on their storefronts, many of them in fashion and apparel. We build Fudge, an AI storefront editor with a 4.9 rating on the Shopify App Store and Built for Shopify status, so we work daily on the storefront layer that feeds Klaviyo its data.

What makes fashion email different from generic ecommerce?

Four category facts drive every flow decision below.

Fit is unknowable from a photo. The shopper cannot try the garment on, so sizing doubt blocks the purchase before it happens and drives returns after. NRF and Happy Returns put US retail returns at roughly $890 billion for 2024, with retailers estimating 16.9% of annual sales coming back, and 51% of Gen Z shoppers say they bracket - ordering multiple sizes with the intent to return some.¹

Shoppers self-identify by size and style. A fashion buyer knows their size, the categories they shop, and the aesthetic they want. Few categories hand over that much zero-party data this willingly.

Inventory moves in drops and seasons. Nothing replenishes on a usage cycle. Sizes sell out, collections turn over, and the calendar sets the sending rhythm more than any individual customer’s behaviour does.

The second purchase is an outfit, not a refill. The reason to come back is that something goes with what they already bought. That single fact rewrites the cross-sell and winback flows.

Compare this with a consumable category: our sister guide to Klaviyo flows for skincare brands is built around usage cycles and results windows. Neither exists in fashion, which is why copying a generic flow map underperforms in both categories.

The stakes are the same, though. Klaviyo’s 2026 benchmarks, drawn from more than 183,000 brands, put automated flows at nearly 41% of email revenue from 5.3% of sends, with a 5.58% average flow click rate against 1.69% for campaigns. In clothing and accessories specifically, flows average a 2.15% placed order rate against 0.12% for campaigns.² That gap is the argument for building the flows below before scheduling another campaign.

The welcome flow: capture size and style before you sell

Fashion signups are usually incentive-led, and that is fine. The mistake is collecting only the email address when the shopper would have told you far more.

Where the size and style questions go

Klaviyo sign-up forms store any field beyond the standard ones as a custom profile property. Radio buttons and dropdowns each carry a label the visitor sees and a value saved to the profile, so “Shop womenswear” can save cleanly as womens.

Keep the popup to one question, because every extra field costs signups. “Who do you shop for?” or a category preference earns its place; a size question usually does not convert well at first touch.

Collect the rest inside the flow. Email two can link a short style-profile page that asks size, fit preference and favourite categories, and writes each answer back to the profile. The shopper who just took a welcome offer is far more willing to answer there than in a popup.

Branch the welcome by category, hold size for later

Add a conditional split after the first email on the category property. A womenswear branch and a menswear branch with accurate imagery beat one generic sequence, and two or three branches you maintain beat eight you abandon.

The size property works differently. Do not branch on it - use it later, for back in stock alerts, fit notes in post-purchase emails, and proof selection (“reviewed by customers who wear a medium”).

A workable sequence: the offer and brand point of view in email one, the style-profile ask in email two, styling content keyed to the branch in email three, social proof and the offer reminder in emails four and five.

Browse abandonment: segment by the category they viewed

Klaviyo triggers browse abandonment on the Viewed Product metric, which requires onsite tracking. On Shopify that tracking comes from Klaviyo’s app embed, and it only follows known browsers - profiles already identified by an email address.

Fashion consideration is long. A shopper visits the same jacket four times over two weeks before buying, which makes browse abandonment more productive here than in most categories - and also easier to get wrong with generic sends.

The fix is a trigger split on the viewed product’s category. A trigger split branches on data from the event that triggered the flow, so the denim viewer gets denim content and the dress viewer gets dresses. Klaviyo’s own branching guidance recommends splitting browse and cart flows by category or collection when the catalogue is large.

Keep the content editorial rather than transactional: the product styled on a body, two adjacent picks from the same category, no discount. A first-touch discount for viewing a page trains expensive behaviour.

Abandoned cart: answer the fit question before the price question

The structure is standard. Klaviyo’s guidance is two to three messages, the first 2-4 hours after someone starts a checkout and the second 20-48 hours later, with a flow filter for “Placed Order zero times since starting this flow.”³ Across ecommerce as a whole, Baymard’s running average puts documented cart abandonment at 70.22% across 50 studies.⁴

The fashion-specific part is what the first email says. The abandoning shopper is rarely stuck on price - they are stuck on “will it fit?” So email one should carry the sizing answer:

• Garment measurements, not just S/M/L, plus the model’s height and the size they wear.
• Fabric behaviour - stretch, drape, whether it runs small, whether reviewers sized up.
• The exchange policy in one sentence. “Free size exchanges within 30 days” removes the risk that keeps the card in the wallet.

If your size guide is a cramped table in a modal, give the flow a real page to land on. A proper size-guide page with measurements, fit notes and photos is a quick build in a Shopify page builder, and it does double duty on the product page itself.

Hold any discount for the final message. A code in message one teaches shoppers to abandon on purpose.

Back in stock: the flow fashion cannot skip

A fashion product is not sold out - a size of it is. Sellouts happen constantly, by variant, all season. That makes back in stock the highest-frequency recovery flow in the category.

The mechanics, verified against Klaviyo’s docs: the flow triggers on the Subscribed to Back in Stock metric, which fires when a shopper submits the restock alert form Klaviyo’s form builder places on out-of-stock products (available for Shopify). Subscribers then wait at a back in stock delay until the item restocks, and the flow must carry no trigger or flow filters.⁵

Two settings matter for fashion:

• Minimum inventory rules set how many units must restock before notifications send, so a return trickling back into stock does not fire alerts for one unit.
• Notification quantity sends to all waiting subscribers at once or in batches.⁵ When 400 people are waiting on a restock of 60, batching keeps you from disappointing 340 of them.

Keep the flow to a single message. Klaviyo cannot re-check stock before a second send, so a follow-up can promote an item that is already gone again.

The waitlist is also merchandising data. The sizes and styles with the longest back in stock queues are your recut list for next season.

Drops and end of season: campaigns on a calendar, flows on behaviour

A new drop is time-specific, so the announcement itself is a campaign to engaged segments, not a flow. A simple cadence works: a teaser to your VIP and most engaged segments, the launch send, then a “last sizes” send once variants start selling out - at which point the back in stock flow takes over automatically.

Send the campaign to a drop landing page rather than a filtered collection. A page that carries the story, the lookbook and the full lineup converts the hype the email created; a bare product grid wastes it. For how the best brands structure those pages, see our guide to Shopify store design for fashion brands.

End of season has an automated half most brands miss: Klaviyo’s price drop flow. It triggers when a catalogue item’s price falls by an amount or percentage you set, and it pulls in people who viewed or started checkout with that item within a lookback window defaulting to the past 30 days, for in-stock items only.⁶ When you run seasonal markdowns, every shopper who hesitated on a now-discounted piece gets told automatically - a personally relevant sale email no campaign segment can match.

One goodwill rule for the campaign layer: exclude customers who bought an item at full price in the last few weeks from the email announcing it at 40% off.

Post-purchase: set fit expectations before the parcel lands

Returns are structural in fashion, and the post-purchase window is where email can bend the rate. The flow triggers on Placed Order or Fulfilled Order - use Fulfilled Order when the sequence should track delivery.

The fit-notes email travels with the parcel. If the community sizing feedback says the knit runs large, say so before they try it on. A customer braced for an oversized fit keeps the item a customer surprised by it returns.

Steer returns into exchanges. Every return email and policy mention should put the size exchange first and the refund second. An exchange keeps the revenue and, more importantly, the customer.

Care instructions are return prevention. A garment washed hot and tumble-dried becomes a “poor quality” return and a one-star review. One short email - wash cold, dry flat, here is why - protects the product’s reputation in the customer’s hands.

Why the review request waits for the exchange window

Klaviyo Reviews sends its request 7 days after a package is delivered by default, and 3 days after purchase for POS orders.⁷ In fashion, day seven is often mid-decision: the customer is holding a return slip, waiting on an exchange, or has worn the piece once.

Push the delay past your exchange window. The reviews you collect then come from people who kept the garment, which is both fairer and more persuasive. The change applies only to fulfilments recorded after you update the setting, so existing orders keep their original timing.⁷

Complete the look: cross-sell around what they bought

A generic cross-sell recommends whatever sells most. In fashion the reason to buy again is that something completes what they already bought, and Klaviyo has the data to act on that: Ordered Product events from Shopify carry the product’s collections and any product tags.⁸

Trigger on Placed Order or Fulfilled Order, then add a trigger split on the ordered product’s collection or tags:

Tag with the split in mind. Tags like capsule-fall26 or palette-ecru cost nothing to add in Shopify and turn a crude category split into genuine outfit logic.

Time it to the fit decision, not the order. A complete-the-look email that arrives while the customer is exchanging a size sells nothing. Send it a few days after delivery, once the post-purchase flow has done its work.

For brands that merchandise outfits well enough to steal from, see our roundup of the best Shopify fashion and apparel stores.

The VIP segment: who sees the drop first

Fashion revenue concentrates in repeat buyers, so define the segment early: two or more orders in the last 12 months, or lifetime spend above a threshold, plus recent engagement.

Give them access, not discounts. Early entry to drops, first pick of end-of-season, priority restock alerts. Access costs no margin and reads as status; a standing discount just reprices the brand for your best customers.

A segment-triggered flow can welcome people the moment they qualify: name the perks, set the expectation that VIP email means early access, and watch open rates on drop teasers climb.

Winback keyed to the season instead of a 90-day timer

A generic winback fires at 60 or 90 days for everyone. In fashion that timer misreads the category: a coat buyer from November is not lapsed in February - they are between seasons.

Key winback to the season of the last purchase. When the new season’s equivalent of what they bought arrives, that is the send: “the new version of the coat you loved” is a reason to return, where “we miss you” is not. Build it as segments on last order date and category, refreshed each season.

Two or three emails is enough, with the incentive held for the final message. Anyone still silent flows into a sunset sequence - fashion lists accumulate discount-code signups like every incentive-led category, and unengaged profiles cost deliverability. The skincare guide covers the sunset mechanics, which transfer unchanged.

The full Klaviyo flow map for fashion brands

Where Fudge fits

Klaviyo owns the email. Your storefront owns everything the email links to, and in fashion that is where flows are won: the size-guide page in the cart email, the drop landing page under the campaign, the style-profile page in the welcome flow.

Fudge is an AI storefront editor that writes native theme code: Liquid, CSS and JavaScript, directly in your theme. Describe the drop page, the lookbook or the size guide, and it builds them on your existing theme - no extra app scripts on top of the Klaviyo snippet you already run, and the pages survive uninstall.

FAQ