Related Products on Shopify: Place Each Block by Job

Key takeaways

• Every related-products block needs one defined job: help shoppers compare alternatives, complete a purchase, reach a price point, discover a range, or recover from an unavailable item.
• Placement and recommendation logic are separate decisions; the page position determines when the block appears, while the merchandising rule determines which products qualify.
• Product-page alternatives should preserve the shopper's main intent, whereas cart and post-add blocks should usually add complementary items rather than substitutes.
• A recommendation rule needs catalog guardrails for availability, product type, price, variant compatibility, and duplicate suppression before it needs more sophisticated personalization.
• Merchants should judge each block against its assigned job instead of using one storewide conversion metric for every recommendation placement.

A sound plan for related products on Shopify starts with the decision the shopper is trying to make, not with a carousel design or an app setting. Write the block's purpose in one sentence before choosing its location or selection rule. If the sentence contains two purposes, such as compare similar jackets and add matching gloves, split the experience into separate blocks. That distinction prevents a common merchandising failure: showing substitutes where an add-on is needed, or accessories where the shopper still needs help choosing the main product.

As of August 2026, theme capabilities, Shopify configuration options, and app interfaces can vary by store setup. Treat the framework below as the operating plan, then confirm the available controls in your current theme and app configuration.

Start with the shopper job, not the carousel

The first decision is what the recommendation block should help the shopper do next. A placement is useful only when it appears at the point where that job becomes relevant. Start by assigning one of five jobs to every planned block:

1. Compare alternatives: Show products that satisfy the same broad need but differ on price, material, style, size range, or specification.
2. Complete the purchase: Show products needed to use, protect, install, refill, or maintain the selected item.
3. Meet a budget: Offer a lower-priced alternative or a premium step-up without abandoning the original product category.
4. Explore the range: Introduce another collection, style family, or use case after the shopper understands the current product.
5. Recover the session: Provide credible substitutes when the selected product or required variant is unavailable.

Use a one-line brief such as: Help shoppers viewing a 12-inch carbon-steel pan find compatible lids. That brief identifies the shopper, the anchor item, and the desired next action. It also rules out unrelated cookware, another 12-inch pan, and lids with the wrong diameter.

Do not start with frequently bought together, same collection, or automatic recommendations. Those are selection methods, not shopper jobs. A method can be technically correct and commercially wrong. Products in the same collection may be substitutes, accessories, or merely part of the same campaign. Decide the job first, then choose the smallest rule set that produces appropriate candidates.

Where should related products appear?

Place related products where the shopper has enough context to understand them but has not already passed the relevant decision. Product pages, cart surfaces, collection pages, empty states, and post-add experiences support different jobs. Reusing the same product set across all five usually creates repetition rather than useful discovery.

Placement	Primary shopper job	Suitable recommendation logic	Main risk
Near the product information	Compare close alternatives	Same product type with controlled differences	Distracting from a product the shopper already wants
Below product details	Explore the range	Shared use case, style family, or collection with exclusions	Becoming a generic collection carousel
Near the add-to-cart action	Complete the purchase	Compatibility or required-use relationship	Competing with the main purchase decision
Cart or cart drawer	Add a low-friction complement	Compatible add-on that is not already in the cart	Adding clutter or encouraging cart abandonment
Unavailable product or variant state	Recover the session	In-stock substitutes preserving key attributes	Recommending another unavailable or incompatible item
Collection or search exit area	Continue discovery	Adjacent category, revised price band, or popular valid results	Pulling shoppers away from active filtering

On a product page, put comparison alternatives after the core buying information unless product choice is unusually difficult. A shopper should first see the product's price, variants, essential specifications, and purchase action. For products requiring compatibility confirmation, a complementary block can sit closer to the variant or specification area, but only if the relationship is explicit.

In the cart, apply a stricter standard. A useful add-on should be understandable in a few seconds and should not require the shopper to restart product research. Socks for selected footwear can work if size and use are clear. Another pair of shoes usually reopens the main decision and belongs on the product page instead.

Merchandising rules should match the assigned job

Choose recommendation logic only after placement and purpose are settled. The rule should preserve the attributes that define relevance while allowing variation on attributes that support comparison or expansion. A same-category rule is rarely sufficient on its own.

For an alternatives block, identify three attribute groups. First, preserve the non-negotiables. A substitute laptop sleeve might need the same device size; a replacement light bulb might need the same fitting and voltage. Second, permit useful differences such as color, material, brand, or price. Third, exclude candidates that make the comparison pointless, including the current product, unavailable items, duplicate color variants presented as separate products, and products outside a reasonable price range.

For complementary recommendations, use an explicit relationship whenever compatibility matters. A collection or shared tag can be a useful catalog shortcut, but it does not prove that two products work together. If a camera accessory fits only selected models, the recommendation data should encode those models rather than infer compatibility from the photography collection. Merchants defining these relationships can use the complementary product mapping template before configuring the storefront.

Price rules need context rather than one storewide percentage. For a $40 main product, a $12 add-on may feel proportionate. For a $1,200 main product, a $360 recommendation could be a serious second purchase decision despite having the same ratio. Set price bands by category and placement. A practical starting rule for a cart add-on is to cap candidates at the lower of a category-specific amount or 25% of the anchor product price, then inspect actual products rather than treating that percentage as universal.

Use manual curation when the commercial relationship is important, the assortment is small, or compatibility errors would be costly. Use rules when the catalog changes often and the qualifying attributes are reliable. Use a hybrid approach when merchandisers need to pin a few priority products while allowing valid fallbacks. The trade-off is maintenance versus control: manual sets provide precision but age quickly; rules scale but expose weaknesses in product data.

Guardrails prevent irrelevant and repetitive recommendations

A recommendation rule is not ready until it has exclusions and a fallback. Positive matching finds candidates; guardrails stop candidates that should never be shown. Build the exclusion order before tuning labels, card design, or carousel length.

Apply these checks in sequence:

1. Remove the anchor product and anything already present in the same recommendation block.
2. Exclude products that cannot currently support the intended purchase, including unavailable products or unusable variant combinations.
3. Enforce compatibility attributes such as size, model, fit, material requirement, or installation type.
4. Exclude products already in the cart when the block is intended to add a new item.
5. Apply the placement's price floor and ceiling.
6. Suppress duplicates already shown in a higher-priority block on the page.
7. If fewer than three valid products remain, use a defined fallback or hide the block.

The fallback must preserve the shopper job. If a compatible-accessories rule returns only one product, showing that one item can be better than filling four slots with generic merchandise. If an unavailable running shoe has no close substitute in the same size and use category, the fallback could broaden color before changing support level or terrain type. Write that order down.

Audit empty and oversized candidate sets. Zero candidates often indicate missing catalog data or an overly narrow rule. Fifty candidates may indicate that the rule does not preserve enough of the shopper's intent. For a visible block with four cards, aim to maintain at least six valid candidates where possible so availability changes do not immediately collapse the block. This is an operating buffer, not a universal performance benchmark.

Five placement decisions create a workable specification

A useful specification can fit on one page if it records five decisions for each block. Complete the specification before evaluating implementation options or asking a developer to build a section.

1. Job: State the single shopper action the block supports.
2. Trigger and placement: Define the page type, anchor location, and conditions under which the block appears.
3. Qualification rule: List the attributes or relationships a candidate must satisfy.
4. Exclusions and fallback: Record what must never appear and what happens when too few products qualify.
5. Success signal: Choose the behavior that indicates the block did its job.

For example, a merchant selling modular sofas could specify a product-page block as follows: Help shoppers compare sofas with the same seat count and room orientation. Place it below dimensions and configuration details. Require the same seat count and orientation, permit fabric and leg-style differences, and keep the price within 20% above or below the anchor. Exclude the current product, unavailable configurations, and any item already shown in a complementary-care block. Hide the block when fewer than two valid alternatives remain. Measure product-detail visits from the block and subsequent add-to-cart behavior for the selected alternative.

That is different from a cart specification for the same store: Help buyers add a care kit suitable for the selected upholstery. The cart block should use upholstery compatibility, exclude products already in the cart, and show no fallback if no confirmed match exists. The placement changed, so the recommendation logic changed too.

If the store also needs broader control over search, filtering, and merchandising, review Hyper Search & Filter after completing this framework. Related-product placement should be planned as part of product discovery, but it should not be confused with the separate jobs performed by search results and collection filters. The Shopify product discovery guide can help map those layers.

Measurement should follow the block's purpose

Measure whether each block completed its assigned job rather than asking whether all recommendation blocks increased the same headline metric. A comparison block and a cart add-on block should not share an identical scorecard.

For an alternatives block, track the share of shoppers who open another recommended product, whether they return to the anchor, and whether the session reaches an add-to-cart action. A high click rate with repeated backtracking may mean the cards omit a critical comparison attribute. Add size, material, capacity, or another decision-making field before changing the candidate rule.

For a complementary block, track recommendation clicks, add-to-cart actions from the block, removals before checkout, and orders containing both the anchor and complement. Cart removal matters because an aggressive recommendation can create a temporary add without helping the final order. For an unavailable-item recovery block, monitor whether shoppers reach an in-stock substitute and proceed toward purchase. The goal is session recovery, not merely carousel engagement.

Run changes in a controlled sequence. First correct obvious relevance and compatibility problems. Next adjust placement. Then change the candidate rule or card count. Finally test labels and presentation. Changing all four at once makes the result hard to interpret.

Use a practical review threshold based on volume. If a block receives only 20 eligible views per week, weekly percentage changes will be noisy. Review individual sessions and candidate quality instead. At higher volume, compare equivalent periods and keep promotions, stock changes, and traffic mix in the review notes. Do not claim success from clicks alone when the block's purpose is a completed purchase or recovery from unavailability.

Recommendation tooling follows the requirements

Choose tooling after documenting the placements, rules, guardrails, and reporting needs. Otherwise, merchants tend to select an interface first and reshape the merchandising plan around whichever controls are easiest to find.

Start with the current Shopify theme and store configuration. Determine whether the required block can appear in the intended location, whether candidates can be curated or rule-driven as needed, and whether the output can respect the store's compatibility and availability data. If the requirement is straightforward and the catalog is small, the existing setup may be sufficient. If several placements need different logic, catalog data changes frequently, or the team needs broader discovery control, evaluate apps against the written specification.

Do not choose an app solely because it offers automatic recommendations. Ask what data the logic uses, which exclusions a merchandiser can enforce, how manual priorities interact with automatic candidates, what happens when no valid candidate exists, and whether the team can audit why an item appeared. The product recommendation app overview provides a starting point for requirements research, while the product discovery requirements worksheet helps separate recommendation needs from search and filtering needs.

When related products are one part of a larger merchandising problem, compare the requirement with the Hyper Apps overview. NiagaraT's Hyper Apps catalog separates product-discovery, support, and shoppable-video products, which helps avoid buying a tool for the wrong layer. For this guide's primary use case, Hyper Search & Filter is the relevant page to review for broader product-discovery control after the placement framework is complete.

FAQ

How do related products work on Shopify?

Related products on Shopify display a set of products connected to the item or context a shopper is currently viewing. The exact selection method depends on the theme, Shopify configuration, custom implementation, or app in use. Candidates may be selected automatically, curated manually, or generated from catalog relationships such as product type, collection, attributes, or compatibility data. Merchants should still define the block's job and exclusions instead of accepting every generated candidate. Check the current product, unavailable inventory, duplicate recommendations, and incompatible variants before publishing the block.

How do I add complementary products in Shopify?

Add complementary products by first mapping which products help a shopper use, maintain, install, refill, or protect the anchor product, then configure those relationships through the options available in your current Shopify setup. Do not treat every product in the same collection as complementary. Record compatibility, placement, exclusions, and fallback behavior before entering relationships in bulk. The Shopify bundles versus complementary products comparison can help determine whether the purchase should remain optional or be presented as a predefined bundle.

Which Shopify product recommendations app should I use?

Use the Shopify product recommendations app that supports your required placements, merchandising rules, exclusions, fallbacks, catalog size, and review workflow. A small catalog with a single product-page block may not need the same controls as a store with several markets, frequent inventory changes, and compatibility-sensitive accessories. Test candidate quality with 20 representative anchor products before committing: five high sellers, five low sellers, five products with limited stock, and five products with unusual attributes. Review Hyper Search & Filter when the requirement extends into broader search, filtering, and merchandising control.

How many related products should a block show?

Show only as many products as shoppers can compare without obscuring the main page task, commonly starting with four visible candidates on desktop and fewer at once on mobile. The correct number depends on product complexity and card content. Four nearly identical technical products may already require too much comparison, while simple color-led accessories may support more. Start with three or four valid products, confirm that key attributes remain readable, and hide the block rather than filling empty positions with weak recommendations.

Should related products come from the same collection?

Related products should come from the same collection only when collection membership reliably represents the block's shopper job. A tightly governed collection for 12-inch pan lids may support a complementary rule, while a seasonal sale collection mixes categories and relationships that are not interchangeable. Test ten anchor products against the collection rule. If more than one candidate per anchor is irrelevant, add product type, compatibility, price, or metafield constraints instead of relying on collection membership alone.