Shopify's Native Complete the Look: What It Does and What It Can't (for Fashion Brands)
In short: Shopify's built-in Search & Discovery app gives you two recommendation blocks on a product page: "related products," which Shopify generates automatically, and "complementary products," which you pick by hand. Both are useful and both are free. Neither one builds a styled outfit. Related products often surface another version of the same thing, and complementary products only work as well as the time you spend setting them up one product at a time. For a fashion brand, that gap is the whole problem: a shopper looking at a shirt does not need three more shirts, and does not want to dig through your catalog to find the trousers that go with it. This post covers what the native tool actually does, where it stops being enough, and how to decide if you need a styling layer on top.
What "complete the look" means on a Shopify product page
Walk onto almost any fashion product page and you will find a row of other products somewhere below the buy button. It might say "You may also like," "Pair it with," "Complete the look," or "Wear it with." Most of those rows are powered by one of two things: Shopify's own free recommendation engine, or a third-party app sitting on top of it.
The free one is Shopify's Search & Discovery app. It is a first-party app, it costs nothing, and a large share of stores run it without ever installing anything else. So before a fashion brand reaches for a paid tool, the honest first question is: what does the free native version already do, and is that enough?
The two native blocks, and how each one is built
Shopify's native product recommendations come in two flavours, and the difference matters more than most merchants realise.
Related products are generated automatically. Shopify builds this list for you using signals like purchase history, the text in your product descriptions, and which collections products share. You do not curate it. Per Shopify's own documentation, only related recommendations are generated automatically; you cannot edit the auto-generated list directly, only supplement it or hide individual products.
Complementary products are picked by hand. For each product, you go into Search & Discovery and manually choose up to ten items you consider complementary. Shopify shows those in the "Pair it with" style block. Nothing is automatic here. If you do not set them, the block does not appear.
There is a quiet tell for which one a store is using. Shopify's native recommendation links carry tracking parameters in the URL, things like pr_prod_strat, pr_rec_id, and pr_ref_pid. The pr_prod_strat value even names the underlying strategy, with values such as copurchase, use_description, and collection_fallback. If you click a "you may also like" product on a store and see those parameters, you are looking at Shopify-native recommendations.
Where the native tool is genuinely fine
The native tool does real work, and you should keep it.
For search, filtering, and merchandising rules, Search & Discovery is good and free. For surfacing a few related products on a long-tail item, the automatic related list is a reasonable baseline that needs zero effort. And for a small catalog where an owner can sit down and hand-pick complementary items for each product, the manual complementary block can produce decent pairings, because a human chose them.
Small catalog, time on the team, products that do not really form outfits? Native may be all you need, and an app would be overkill. That is a real answer.
Where it stops being enough for fashion
The trouble starts when the catalog is a fashion catalog.
Related products tend to surface more of the same. Because the automatic list leans on descriptions and shared collections, a black dress often pulls up three more black dresses. The shopper viewing that dress already has the dress. What grows the basket is the jacket or the belt or the bag that finishes it, and a list built on similarity will keep handing back near-copies of the thing they are already looking at. Independent research in fashion recommendation has made this point for years: similarity and compatibility are different problems that need to be modelled separately. An engine tuned to find lookalikes is doing its job correctly and still failing the styling task.
The automatic list can mix things it should not. Merchants regularly report native related products pulling across categories, surfacing menswear on a womenswear page, for example, because the algorithm is matching on text and collection overlap rather than on whether the items belong in the same outfit.
Manual complementary setup does not scale, and it goes stale. Hand-picking up to ten complementary products per item is fine for fifty products. For five hundred to fifteen hundred, which is where most established contemporary fashion catalogs sit, it is a real job, and it is never finished. Every new drop needs pairings added. Every product that sells out leaves a dead link in someone else's "pair it with" block until a person goes back and fixes it. The work is invisible until inventory moves, and then it quietly rots.
None of it is styled. This is the part that matters most and is easiest to miss. The native block shows products in a grid or a row. It does not present them as a look. There is no styling logic underneath, no sense of silhouette, occasion, formality, colour coordination, or fabric. It is a list of items, and the shopper still has to do the imagining.
The real distinction: recommendation versus styling
Here is the line that separates the native tool from a styling layer.
A recommendation answers "what else might this shopper buy?" It uses co-purchase data or attribute similarity, and it is a genuinely useful question for a cart or a checkout upsell.
Styling answers a different question: "how do I wear this?" It assembles a coherent outfit, the way a stylist would, by reasoning about how pieces go together rather than which pieces statistically sold together.
Shopify native, and most of the third-party recommendation apps built on the same behavioural logic, answer the first question. They show what sold together or what looks textually similar. That is not the same as showing a shopper a look they can picture themselves in. For a lot of stores the first question is enough. For a fashion brand whose whole value is taste and coordination, it usually is not.
How to decide which you need
| Your situation | What to use |
|---|---|
| Small catalog, products do not form outfits, you have time to curate | Shopify native Search & Discovery (free) |
| You need search and filters | Shopify native, regardless of anything else (keep it) |
| You mainly want cart and checkout AOV mechanics | A behavioural upsell app, alongside native |
| Fashion catalog where products form outfits, and you want them shown as coordinated looks | A styling layer built for fashion |
| You want every pairing to be on-brand and approved before it goes live | A styling tool with brand approval, not an auto-generated engine |
The native tool and a styling layer do different jobs. Keep native for search. The only real question is whether your product pages need styling that the free tool was never designed to do.
A note on what we build
Full disclosure: Angadi is our product. It is a styling layer for Shopify fashion brands. It pairs your products into coherent looks using fashion attributes like silhouette, occasion, formality, and colour, it shows them as a styled "complete the look" and "style it with" on the product page, and every pairing is suggested by the AI but approved by you before it appears. It reads your own catalog and uses your own photography. There is a free plan, then Growth at $29 and Pro at $59 a month. We think native Search & Discovery is the right tool for search, and we built Angadi for the styling job it was never meant to do.
Frequently asked questions
Does Shopify have a built-in complete the look feature? Sort of. Shopify's free Search & Discovery app offers two recommendation blocks: related products, generated automatically, and complementary products, which you select by hand. Neither presents items as a styled outfit, but the complementary block is the closest native equivalent to "complete the look."
Are Shopify's native product recommendations automatic or manual? Both, depending on which block. Related products are generated automatically by Shopify and cannot be directly edited. Complementary products are chosen manually, up to ten per product.
Why do Shopify's related products sometimes show similar items instead of matching ones? Because the automatic related list leans on signals like product descriptions and shared collections, which tend to surface similar products rather than complementary ones. A dress page pulling up more dresses is similarity at work, not coordination.
Do I need an app for complete the look on Shopify? Not always. If your catalog is small, you have time to hand-pick complementary products, and your items do not really form outfits, native is enough. If you sell fashion, have a few hundred or more products, and want coordinated looks shown as outfits without curating every pairing by hand, a styling layer is worth it.
Is it worth keeping Shopify's native Search & Discovery if I add a styling app? Yes. Search & Discovery powers your on-site search, filters, and merchandising rules, which a styling layer does not replace. The two do different jobs and run side by side.
Angadi builds complete outfits from your catalog and places them on every product page. It installs free on Shopify with a 30-day trial, and nothing goes live without your approval. See it on your store →