Skip to content

Relative Products (Frequently Bought Together)

This documentation explains how the Frequently Bought Together feature works across both the Connect Side (Frontend) and the Admin Side (Backend) of the platform.

Connect Side

Multi-SKU Products

When a customer views a product with multiple variants (e.g., size, color):

  1. SKU Selection:

    • The user selects a specific SKU from a dropdown (e.g., Size: M, Color: Blue).

  2. Trigger Display:

    • Upon SKU selection, a section titled:

    Frequently bought together – Add these for the best experience

    appears below the product details.

  3. Recommended Items:

    • These are accessories, complementary items, or upgrades typically purchased with the selected SKU.
    • Each related item is displayed with:
      • Image
      • Name
      • Price
      • Option to Add to Cart
      • Link to view more details

  4. Add to Cart:

    • Users can add all items with a single click, or select individual items to add.

Single-SKU Products

For products that have no variants:

  1. Trigger Point:

    • The user must first add the product to the cart.

  2. Related Products Display:

    • After the item is added, the Frequently Bought Together section appears in the cart.

  3. User Interaction:

    • Similar interface and behavior as for multi-SKU products.

Section Text (Frontend UI)

Frequently Bought Together – Add these for the best experience
These items are commonly purchased alongside the product you’ve selected. Whether it's essential accessories, complementary tools, or popular upgrades, they’re recommended to help you get the most value and enjoyment out of your purchase. You can easily add them to your cart with just one click.

Admin Side

Location

Inventory → Related Products

Manual Setup via Admin Portal

  1. Search and select the parent product (main SKU).
  2. In the Related Products section, manually add one or more related SKUs.
  3. Save changes to persist the relationship.

Bulk Upload via Vendor Sheet

To manage large sets of related products efficiently:

  1. Download the Vendor Sheet:

    • Available from the inventory or vendor management portal.

  2. Fill the Sheet:

    • Populate the following fields:
      • SKU: Main product SKU
      • Related SKU(s): Comma-separated list of related SKUs
    • Example:

    SKU, Related SKUs 12345, 54321,67890,11223

  3. Upload the Sheet:

    • Return to the admin panel.
    • Use the Upload feature to import the updated file.
    • The system will process the file and associate the SKUs.

Notes and Tips

  • Ensure all related SKUs exist in the product catalog.
  • SKUs must be active and preferably in stock.
  • Avoid incorrect or circular relationships unless intentional.
  • Keep related products relevant and beneficial to customers.

Technical Notes

  • Frontend Trigger Events:

    • Multi-SKU: Triggered by SKU selection.
    • Single-SKU: Triggered after product is added to cart.

  • Backend Data Model:

    • Related SKUs are mapped to parent SKUs using a many-to-many relationship in the database.

Frequently Bought Together – Storefront Behavior

When a customer adds a product to the cart on the storefront, and that product has related SKUs configured in the backend, a popup is triggered.

This popup informs the user that the selected product has items that are frequently bought together.

  • The popup appears immediately after the product is added to the cart.

  • The popup message is:

  • Two buttons are shown:

  • Yes – Redirects the user to the detail page of the first related product.
  • No – Closes the popup. No redirection occurs.

Functional Notes

  • The popup only appears if the added product has related SKUs assigned.
  • No product previews or selection options are shown in the popup.
  • Only one related product is shown at a time through redirection.
  • This feature is designed to increase upsell opportunities in a simple and non-intrusive way.

Requirements

  • Related SKUs must be assigned to the product in the backend.
  • Related SKUs should:
  • Exist in the product catalog.
  • Be active.
  • Preferably be in stock.

Best Practices

  • Assign accessories, upgrades, or commonly paired items as related products.
  • Keep related products relevant to avoid disrupting the customer journey.
  • Limit the number of related items to avoid redirect loops or excessive navigation.