• Your eCommerce Module is updated to at least version 1.2.0
  • You have already created eCommerce Products and outputted them in List or Detail Layouts on the Site


Module Custom Fields allow a wide range of use cases for connecting up different areas of your Site.

In this Article we'll look at how you can create a new Custom Field for your eCommerce products to store similar, related Products which could be displayed on the Product's Detail Page.

You could of course use this same technique with the Blog Module or any other Module or WebApp.

Step By Step

Step 1) Add a new Custom Field to Products

To add a Custom Field to Products, first select Edit Module Structure from the Products List in Admin.

At the bottom of the available fields, you can find the Custom Fields section, and press the "Add new field" button.

The name of your field can be whatever you want, here we'll call it Related Products.

The Datasource Multi type prompts us to choose a Module or WebApp that we will be able to select Items from.

When you're ready, press save and your new Custom Field will be set up. You'll then be able to use this field when creating and editing Products.

In this example, we'll edit the new Custom Field on an existing Product to create a relationship with another Product.

From the Product Edit Page, select the Custom Fields tab:

As we used the Datasource Multi field type and selected Products as the Module to be linked to, Siteglide knows what we're trying to do and will help us find the related Items. By clicking in the select box and starting to type "Crow" I should be able to find other Products with a similar name to this band easily.

Select as many as you need. Each Product's unique ID will be stored in array format in your Custom Field.

When you're ready, save the Product.

For the next steps (3 - 6), we'll be navigating to Code Editor to develop custom Layouts to display the Related Products Front End. We'll start by working in the "item.liquid" file of the Layout you're using for the Product Detail View. We'll nest a new List of Related Products inside this Detail Layout.

Inside the item.liquid file, we can access the Custom Field by name:

<h2>Related Products</h2><br><br>
{{this['Related Products']}}<br><br>

This outputs an array of the IDs of each of the related Products stored against our current Product. It should look something like this:


In Step 5, we'll need to nest a new List Layout of Products inside the Detail Layout and filter this by the IDs of our Related Products. However, the IDs are currently in an Array format and the {% include %} tag's item_ids parameter expects a comma separated String.

We can change the type by assigning a new variable.

{% assign related_products = this['Related Products'] | join: "," %}

Next, we need to output a Product List, nested within our existing Product Detail Layout.

<h2>Related Products</h2>
{% assign related_products = this['Related Products'] | join: "," %}
{%- include 'ecommerce/products', layout: 'default', per_page: '3', show_pagination: 'false', sort_type: '', sort_order: 'asc', datasource: 'true', item_ids: related_products -%}

Item Ids Parameter

Without the item_ids parameter, our List outputs only the first few Products alphabetically, instead of fetching our dynamic Related Products.

We can change that by adding the item_ids parameter and feeding in our comma-separated String of IDs (that we stored in a new Liquid variable).

item_ids: related_products

Datasource Parameter

datasource: 'true'

When you output an include inside a Detail Layout, by default Siteglide will try to fetch a Detail Layout. This is one reason why it's important to set the datasource: 'true' parameter, which will then cause Siteglide to look for a List type Layout.

Another benefit of the datasource: 'true' parameter is that if no Related Product IDs are available, the List will return empty, instead of returning an unfiltered List. This prevents the List from showing unrelated Products in this situation.

Per Page Parameter

per_page: '3'

In the example, the per_page has been set to 3. In some cases, you may wish to limit the number of "related" results in this way, so they don't distract from the main subject of the Page. It is completely optional.

Layout Parameter

Select the name of a Product List Layout you'll use to style how the dynamic Related Products List will look (see Step 7).

Optionally, you can add Liquid logic to only display the subtitle and Related Products content when the field is not empty.

As the field contains an array, a safe way to check if it holds a value is to check its size (Liquid for the length of the array).

{% if this['Related Products'].size > 0  %}
<h2>Related Products</h2>
{% assign related_products = this['Related Products'] | join: "," %}
{%- include 'ecommerce/products', layout: 'default', per_page: '3', show_pagination: 'false', sort_type: '', sort_order: 'asc', datasource: 'true', item_ids: related_products -%}
{% endif %}

You can style and write Liquid for the Related Products List Layout in the same way you do for any Product List. For example, you could provide a link to the Detail Pages of those Related Products using the Slug property.

You've now completed the Step by Step guide for adding Related Products.

Did this answer your question?