Request Form

★★★★★

Love the look? Tap "Try it on" and upload a photo. See the entire outfit on your body in under 15 seconds. Save it, share it, or go straight to checkout. The fitting room comes to you.

Natali Simpson eCom Director, premium fashion store
Tryora Блог CRO Outfit builder vs «Схожі товари»
CRO Для Head of eCommerce На цифрах

Outfit builder vs «Схожі товари»:
що насправді продає більше?

Outfit Builder vs "Related Products":
What Actually Sells More?

Від команди Tryora ~8 хв читання
Поширити: ↗ LinkedIn ↗ Twitter
Outfit builder vs Related Products — що продає більше у fashion ecommerce

Almost every fashion store's product page has a "Related products" or "You may also like" block. And increasingly, something else sits next to it — an outfit builder, "build the look," "complete the look." Both promise the same thing: get the shopper to put more than one item in the cart. But they work in opposite ways. One shows a replacement for what you're already looking at. The other shows a complement to it. And once you look at the numbers, the gap between "replacement" and "complement" turns out to be not cosmetic but financial. Let's break it down without the hype: what actually sells more — and where each one belongs.

Частина 01

Substitution or Complement: Two Different Logics

Let's start with definitions, because that's the whole point.

"Related products" run on substitution logic. You're looking at a black dress — the block shows five more similar black dresses. These are alternatives. The shopper picks one of many lookalikes: in effect, the block says "maybe this one's better?"

An outfit builder ("complete the look") runs on complement logic. You're looking at that same dress — the module shows what goes with it: sandals, a bag, earrings. Not alternatives, but companion pieces. The block says "here's what completes it."

The difference is simple but decisive. Substitution makes the shopper choose between options — that is, hesitate. A complement helps assemble a whole — that is, add. The first works against the basket (one item instead of another); the second works for it (several items together).

Схема: заміна (схожі товари) проти доповнення (образ)
Частина 02

Why "Related Products" Often Work Against You

The "related" block feels safe — it's almost everywhere. But in fashion it has three side effects.

First: it competes with the item the shopper has nearly chosen. You show five alternatives to the dress they're browsing — and push them back into the choosing mode they were just leaving. "I'll take it" turns into "hmm, maybe a different one."

Second: decision fatigue. The more lookalike options, the harder the decision. In fashion, where the choice is already emotionally loaded, five more near-identical dresses aren't help — they're noise.

Third: orphaned SKUs — individual items with no context. The shopper sees products but not how to wear them together. And fashion conversion is already low: the industry average is around 1.9%, and only the top 20% of stores climb past 4.3%. Pouring more noise into that narrow funnel isn't the best idea.

This doesn't make "related" evil (we'll come back to that). But as the main basket-growth tool they're weak by definition: they're about choosing, not adding.

Частина 03

What the Numbers Say

Now the interesting part for those who live by metrics. The comparison of styled outfits against plain recommendations is fairly well documented.

2,87×
більше кліків у стилізованих образів проти нестилізованих рекомендацій (кейс JD Sports)
+25%
конверсії, коли контент містить рекомендації у вигляді образів (дослідження Stylitics)
+25%
середнього кошика від персоналізованих луків (дані Veesual)
−30%
повернень, коли образ зібрано і приміряно віртуально (+15% чека там само)

The figures come from different sources, but the vector is the same: when a product is shown as part of an outfit rather than alone, people click more, add more to the cart and return less. None of these gains come from a "related products" block — because it's not about the outfit, it's about an alternative.

Most of these figures are studies from industry vendors (Stylitics, Veesual) and their client cases. We cite them as a market reference, not as Tryora's own results. Actual numbers depend on the catalog, audience and implementation.

Частина 04

Why the Outfit Wins Specifically in Fashion

Behind the numbers is simple behavior. In fashion, a person buys not a SKU but how they'll look. The decision is visual and emotional.

It shows even in what shoppers look at first. Per a Veesual survey, the first thing people examine on a product page is the photo of the item worn as part of a look, not on a hanger. And nearly one in two deliberately scans the photo for the companion pieces in the model's outfit.

So the shopper already wants to assemble a look. "Related products" don't satisfy that urge — they toss in more of the same. An outfit module does: it shows a finished whole and takes the "what do I wear this with" work off the person. A complement removes friction. Substitution adds it. In a category where decisions are made with the eyes, that's decisive.

"Related products" give more choice. An outfit gives fewer doubts. In fashion, the second one wins.

Частина 05

When "Related Products" Are Actually Needed

Now, honestly, so this doesn't come out one-sided: you shouldn't delete "related products." They have a job — just a different one.

Substitution belongs exactly where an alternative is needed. Item out of stock — show a similar one in stock. Wrong price — show a cheaper equivalent. Wrong size or color — offer a close option. This saves a sale that would otherwise fall through. Not by accident do even specialist players keep a separate "shop similar" module alongside their outfit tools.

So the right question isn't "which is better" but "which tool for which job." Substitution (related products) — for when the chosen item doesn't fit the need. Complement (the outfit) — for basket growth, when the item does fit. The mistake is using substitution where a complement is needed and expecting a bigger basket from it. That's simply not what it's built for.

Частина 06

Static Banner vs Interactive Builder

And one more level that often gets confused. Complement comes in different forms too.

The simplest form is a static "wear it with" banner: a row of three items under the product. That's already better than "related," because it's a complement. But it's a ready-made answer someone else assembled. The shopper either accepts it or scrolls past.

The stronger form is an interactive outfit builder, where the shopper assembles the look themselves: swaps the top, adds an accessory, sees how the pieces work together. This is where engagement kicks in — and more time with the catalog means a bigger basket. Even Veesual, in its own piece, questions whether a static "complete the look" banner is enough. Often it isn't: it shows, but doesn't engage.

Параметр «Схожі товари» Статичний банер Інтерактивний конструктор
Logic Substitution Complement Complement
Who assembles No one (similarity algo) Stylist/brand, in advance The shopper
Engagement Low Medium High
Basket impact Weak Moderate Strongest

This is exactly the level where Style Canvas lives — not a static row, but a builder where the shopper assembles the look themselves and adds the whole outfit to the cart in one move. Alongside it — Virtual Try-On (they see the look on themselves, so fewer returns) and Look Generation (outfits assembled automatically from your real products, with nothing invented). Already live on the Andreas Moskin and bado.ua catalogs.

Статичний банер «носіть з цим» проти інтерактивного конструктора образу
Підсумок

What to Do With This

The verdict, no spin: "Related products" and an outfit builder are different tools. The first is about substitution, the second about complement. For basket growth, complement wins, and the numbers back it. But keep substitution for "out of stock / wrong budget" cases. And if you're choosing a form of complement — an interactive builder beats a static banner on engagement.

Що протестувати цього тижня
  • Check what's on your product page: substitution ("related") or complement (an outfit). Often it's only substitution.
  • Run an A/B: an outfit module against "related products" on the same pages.
  • Measure not just conversion but UPT (items per order) and AOV — that's where the complement effect shows.
  • Don't switch "related" off entirely — move it to the "out of stock / wrong budget" scenario.
  • If you already have an outfit module — check whether it's interactive or a static banner. Engagement converts better.

Want to see this on your catalog?

20 minutes — we'll build a look from your real products and show how the builder works alongside "related." If it doesn't fit, we'll tell you straight.