Related Products

    relatedProducts

    Learn how to configure the Related Products app to showcase cross-sell items to customers by matching product facets, setting display styles, and defining purchase actions.

    Related Products — User Guide

    A friendly, plain-English guide for admins setting up the Related Products app.

    What does this app do?

    It shows your customers other products they might like, right next to whatever product they're currently looking at. Think "you may also like" or "complete the range" — the kind of cross-sell you see on most modern shopping experiences.

    It works by matching products that share certain characteristics (called facets) — for example, the same furniture range, the same wood finish, or the same room. You decide which characteristics matter.

    When a customer taps one of the related products, you choose what happens: open its full SmartLinks page, jump straight to its purchase URL, or show a small detail view with a Buy button.

    Getting started — first-time setup

    Open the admin page from your collection settings. You'll see three tabs: Configuration (do this first), Per-product overrides (optional fine-tuning), and Preview (see what customers will see).

    Step 1: Pick the matching facets

    In the Configuration tab, tap each facet that defines "related" for your products.

    Examples: A furniture brand might pick range and finish. An electronics brand might pick product-line. A wine producer might pick vineyard and vintage-style.

    If your collection has no facets defined yet, you can type facet keys manually — but it's much better to set up proper facets on the collection first.

    Step 2: Set the matching threshold

    Minimum shared facets — how many of your chosen facets a candidate must share. 1 (default) is inclusive; 2+ is stricter.

    Step 3: How many to show

    Max items to show — between 1 and 50. Default is 6.

    Step 4: Other collections (optional)

    If your related products live in another collection (e.g. a sister brand or a "Spare Parts" collection), enter those collection IDs comma-separated.

    Step 5: Choose the look

    • Card grid — clean grid of product cards (best for most cases)
    • Carousel — horizontally scrolling row (great when embedded near other content)
    • Compact list — small thumbnails with text (good for accessories or many items)

    Step 6: Choose what happens on tap

    • Open SmartLinks page — jumps to the product's full SmartLinks page
    • Open purchase link — opens the buy URL straight away (most direct route to sale)
    • Show details, then buy — shows a small detail view with a prominent Buy button (best for considered purchases)

    Step 7: Where is the purchase URL?

    Tell the app which field on each product holds the purchase link. Default: data.purchaseUrl. Change to data.shopUrl, extra.buyLink, etc. if your team stores it elsewhere.

    If a product has no purchase URL, the Buy button is automatically hidden for that product.

    Step 8: Labels

    Customise the section heading and button labels — useful for matching your brand voice.

    Hit Save configuration when you're done.

    Day-to-day use (what your customers see)

    When a customer scans/visits a product:

    1. They see your section heading (e.g. "You may also like")
    2. Below it, a layout of related products
    3. They tap one — the configured behaviour kicks in
    4. From the detail view, they can tap "Buy now" to go to your store

    Views, taps, and buy clicks all flow into your SmartLinks analytics.

    Per-product overrides

    Sometimes the auto-match isn't perfect for one product. Open the admin page from that specific product and use the Per-product overrides tab:

    • Pinned — product IDs that always show first for this product
    • Excluded — product IDs that never show for this product
    • Tap behaviour override — different tap behaviour just for this product
    • Purchase URL override — supply a buy URL when the product doesn't have one stored at the configured path

    Bulk import (CSV)

    For larger catalogues, use the CSV import in your admin panel. Columns:

    • productId
    • pinnedProductIds (semicolon-separated within the cell)
    • excludedProductIds (semicolon-separated within the cell)
    • tapBehaviorOverride (smartlinks | purchase | details-then-buy)
    • purchaseUrlOverride

    Example: prod_001,prod_017;prod_023,prod_099,purchase,

    Where this app appears

    • Widget — small embeddable preview meant for product pages and listing surfaces
    • Full app — the complete grid view with detail-then-buy support

    Both share the same configuration.

    FAQ

    A product I expected isn't showing. Check that it shares at least minSharedFacets facet values with the source. The Preview tab shows which facets matched on every card.

    My products don't have facets yet. Set up facet definitions on the collection first, then assign facet values to products. The app starts working immediately once products have facets.

    Can I show related products from a different brand? Yes — add their collection ID to Additional collection IDs. Make sure the facet keys mean the same thing across collections.

    The same product is in two collections — will it appear twice? No, deduplicated by product ID.

    Can customers buy without leaving SmartLinks? No — purchasing happens on your external e-commerce site. This app makes the discovery and link-out as smooth as possible.

    How do I see what's converting? Check analytics for related-product-view, related-product-click, and related-product-buy. Click outcomes carry the target product ID.