Skip to article
Product Discovery2026-07-15 · 11 min read

Where to Put Product Recommendations: The Page-by-Page Ecommerce Placement Guide

The best recommendation can fail when it appears at the wrong moment. Placement determines whether a product feels like a useful next step, a distracting second task, or an unexplained carousel.

The rule: choose the page job first, set a boundary around the primary task, then place a recommendation where the shopper has enough context to understand the relationship.

6

storefront placements to evaluate separately

Placement framework

1

shopper job each module should explain

UX rule

320px

mobile width to test before shipping the layout

Mobile audit

Placement principle

The page tells you what the recommendation is allowed to ask

A product page can support comparison. A cart should support completion. A search empty state should support recovery. The heading, candidates, card content, and metric should follow that job.

Follow the working path

1 Test it

Understand

Let the shopper understand the selected product before adding comparison or add-on choices.

2 Test it

Relate

Name the relationship so the shopper knows why the candidate appears here.

3 Test it

Act

Offer one clear next action without moving the shopper away from the primary task.

4 Product capability

Measure

Track this placement separately because a cart module and a product-page module solve different jobs.

Reader takeaway: A recommendation is not ready for optimization until its placement makes sense without explanation from the team.

The direct answer

Place recommendations where the shopper has context and room to act

The same product set can feel useful on one page and irrelevant on another. A belt beside trousers has an obvious relationship on a product page. The same belt beneath an empty search for “waterproof hiking jacket” is not an answer. Placement changes the shopper’s question, so it changes the recommendation’s job.

Use five tests for every placement: context, relationship, timing, friction, and measurement. The shopper should know what page they are on, why the products are grouped, when the module appears, how to ignore or use it, and which outcome will tell you whether it helped.

Pro Tip: write the “not now” rule

For each module, write what the shopper should not be asked to do here. For example: “Do not ask for broad exploration before add to cart” or “Do not mix recovery products into exact search results.” This boundary prevents placement creep.

Placement 1

Use the product page for comparison and completion

The product page has the strongest anchor because the shopper is already looking at a specific product. Shopify supports related and complementary product sections on product pages through compatible themes and Search & Discovery configuration. The two modules should still have different jobs.

Related products support comparison. Show credible alternatives with a meaningful difference: another fit, material, color family, price point, or use case. Complementary products support completion. Show something the shopper may need to use, protect, install, or maintain the selected item.

You may also like

Compare similar products

Use when the shopper may still be choosing between credible alternatives.

Trail pack 24L

$118

Trail pack 32L

$138

Pair it with

Complete the product

Use when the shopper needs an accessory or compatible item to finish the use case.

Rain cover

$18

Bottle holder

$24

What to notice: the headings answer different questions, the candidates are not mixed, and the card price gives the shopper enough context to continue.

Place the module after the shopper has seen the main title, images, price, options, shipping, and add-to-cart action. If the recommendation is a required compatibility item, it may deserve a more prominent location, but the relationship should be explicit and the primary product should remain understandable.

Baymard’s product-page research treats the product page as a central place where shoppers decide whether to purchase. That makes the recommendation card part of the evaluation experience. A wrong price, missing option, or unavailable candidate can damage the main product’s credibility.

Read Shopify’s product recommendation requirements

Placement 2

Use collection pages to open an adjacent discovery path

Collections give shoppers a category anchor rather than a single product anchor. A recommendation module can help them move sideways into a related category, a project, or a complementary group. It should not make the main collection harder to scan.

For a home office collection, a small “Complete the workspace” module may lead to monitor arms or cable management. For a running collection, “Build your training kit” may lead to socks, hydration, and recovery products. The content should reflect the category’s shopping mission, not simply repeat the best sellers already visible in the grid.

Collection placement

Add a second path only when it clarifies the first

The primary collection answers “what is in this category?” The recommendation module should answer a different question, such as “what else belongs in this project?”

Follow the working path

1 Documented

Primary grid

Keep the collection products, filters, sort, and applied state easy to scan.

2 Test it

Context signal

Use the collection or active filter to define the adjacent relationship.

3 Test it

Helpful module

Show a small, labeled set that moves the shopper to a useful next category.

4 Test it

Measure separately

Do not combine module clicks with primary collection product clicks.

Reader takeaway: The recommendation should extend the collection mission, not create a second collection that competes with it.

Baymard’s product-list research emphasizes that list design, filtering, sorting, and product presentation work as one finding path. Treat a recommendation row as part of that path. Test whether it helps the shopper move forward or simply adds another block to scroll past.

Placement 4

Use the cart for small, optional add-ons

Cart recommendations can help when the item has a direct relationship to what the shopper already chose. They should be easy to understand and easy to ignore. A compact add-on with a direct add action is safer than a large carousel that sends the shopper back into browsing.

Be especially careful with checkout. Baymard’s cross-sell research describes strong frustration when users encounter a separate cross-sell step during checkout. That evidence supports a conservative rule: never require the shopper to reject an offer before continuing, and measure checkout completion rather than offer clicks alone.

Cart boundary

Make the add-on optional and the main action uninterrupted

The cart should confirm the order first. A recommendation can offer a useful extra, but it must not make the shopper solve another shopping task to continue.

Follow the working path

1 Documented

Cart contents

Keep selected products, quantities, price, shipping, and checkout action clear.

2 Test it

Relevant add-on

Show one or a few products that complete the selected use case.

3 Test it

Direct add

Let the shopper add a simple item without leaving the cart.

4 Test it

No detour

Do not require an offer decision before the shopper can continue.

Reader takeaway: A cart recommendation succeeds when it adds helpful choice without turning the cart into another collection page.

If an add-on requires a size, color, or compatibility decision, send the shopper to a focused product page with the cart preserved. Do not silently add an arbitrary variant because it makes the implementation easier.

Placement 5

Use post-purchase recommendations for the next use case

After purchase, the relationship changes. The shopper no longer needs the product they just bought. They may need a replacement, a compatible item, care supplies, an accessory, or the next product in a project. The order gives you stronger context than a generic home page, so use it.

Avoid recommending the same item again unless replenishment is the explicit job. A skincare store can recommend a refill after the likely usage period. A parts store can recommend maintenance kits. An office furniture store can recommend a cable tray or monitor arm after a desk purchase. Label the reason and respect timing.

Placement 6

Design mobile placement around the thumb and the primary action

Mobile changes the cost of every recommendation. The viewport is smaller, the keyboard and sticky purchase controls compete for space, and a horizontal carousel can hide the heading or price after one swipe. Test mobile as its own placement, not as a desktop row that happens to shrink.

At 320px, check that the section heading wraps cleanly, product names do not disappear, prices remain visible, touch targets are large enough, and the primary product action stays easy to find. If the recommendation appears below a long product description, consider whether it is too late to help. If it appears above the main action, consider whether it is too early.

Mobile checks

Heading explains the relationship before the swipe.
Card exposes title, price, state, and action.
Carousel has a visible continuation cue.
Primary add-to-cart action remains obvious.

Audit

Run the 30-minute placement audit

Use one anchor product, one collection, one search query, one cart, and one post-purchase example. For each surface, write the job, heading, candidate relationship, placement boundary, and success event.

1

Name the page job

Write down what the shopper is trying to do before selecting any product candidates.

2

Set the placement boundary

Decide what the module must not interrupt, hide, or replace.

3

Choose the relationship

Use similar, complementary, substitute, bundle, or replenishment language.

4

Review the card

Check image, title, price, availability, attributes, heading, and action on desktop and mobile.

5

Measure the handoff

Separate impressions, clicks, carts, and purchases by placement instead of blending them.

The output should be a placement matrix with one repair for each surface. If the product page needs better card data, fix that first. If search recommendations are mixed into primary results, separate the modules before judging candidate quality. If cart placement hurts completion, remove the detour.

Frequently asked questions

Part of a bigger picture: this is the placement spoke for the complete ecommerce product recommendations guide. Use the pillar for recommendation jobs, data readiness, measurement, and software evaluation.

Placement is a product decision, not a spacing decision. The module should appear where the shopper has enough context to understand the relationship and enough room to act without losing the primary path.

Which placement in your store needs a clearer job before it needs more products?

Next step

Make discovery paths easier to measure

ParticleSearch helps connect search, catalog, and product discovery signals around the recommendation surfaces you are improving.

Discovery test bench

Test whether the catalog speaks the shopper’s language.

Product discovery fails when the right product is present but the path to it is unclear. Use one exact query, one descriptive query, and one category query to see where the path breaks.

1

Exact

brand + model or SKU

The intended product should appear immediately and its title, variant, price, and availability should be unambiguous.

Record: Exact-match position and variant shown.

2

Descriptive

waterproof hiking boots

The first page should reflect the key use case, not just products that share one generic word.

Record: Top six products and the matching attribute.

3

Category

women’s boots

The result set should give shoppers a credible path to narrow by the attributes that matter in this category.

Record: Filter groups, counts, and time to first useful click.

The evidence rule

Keep the query, expected result, observed result, date, device, and next action together. A source can tell you what the platform documents. Only your own storefront and query log can tell you what is happening now.

Ready to test the fix?

Give your shoppers a clearer path to products.

Install ParticleSearch, run the query set from this guide, and compare the storefront behavior with your current baseline.

Install on Shopify