> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/product-comparisons/create-a-product-comparison.md). # Create a Product Comparison Create a product comparison, choose the properties to compare, and customize the content shoppers see. This guide walks you through creating a comparison, from choosing properties to writing the labels shoppers see. Once it's saved, you can use it in a Campaign, Product Finder, or Sagent. ## Before you begin * Make sure the properties you want to compare exist in your product data and are populated across the products you'll compare. Products with no value for a property show a dash (-) in that row. * Decide which details actually help shoppers choose. A short list of meaningful properties is easier to scan than every attribute in your feed. {% stepper %} {% step %} #### Create the comparison Go to **Experiences → Product Comparisons**. The overview lists your existing comparisons with their name, number of products, and creation date. Click **Add Comparison**, then set: * **Comparison Name** - A clear internal name, so you can find it when using it in an experience. For example, "Water Bottles Comparison." * **Max Number of Products** - The maximum number of products shoppers can compare at once. The default is 6. {% endstep %} {% step %} #### Add property sections Under **Product Properties to Compare**, use the **Property Section 1** dropdown to select the properties for your first section. You can select multiple properties per section. Click **Add Property Section** to group further properties into a separate section. For example, keep "Features" and "Benefits" in one section and "Size" and "Capacity" in another. Click the delete icon next to a section to remove it. {% endstep %} {% step %} #### Filter products (optional) Under **Product Filtering**, add filters to only include specific products in this comparison. Select a filter type from the dropdown, such as a product property or **Parent ID**. Add multiple filters to narrow the selection further. Use the drag handle to reorder filters, or the delete icon to remove one. Use filtering when a comparison is built for one category. For example, filter by **Product Category** so a bottle comparison only includes bottles. {% endstep %} {% step %} #### Customize general content The content section sets the text shoppers see throughout the comparison view. | Element | What it controls | | ----------------------------- | -------------------------------------------------------------------- | | **Title** | Heading of the comparison view. | | **Back** | Label for the button that returns shoppers to the previous view. | | **Shop now** | Label on each product's call-to-action button. | | **Empty title** | Heading shown when no products are selected. | | **Empty button** | Button label shown in the empty state. | | **Add back** | Label for re-adding a removed product. | | **View more** / **View less** | Labels for expanding and collapsing longer content. | | **Remove product aria label** | Screen reader label for removing a product. | | **Info icon aria label** | Screen reader label for the info icon next to property descriptions. | | **Image alt prefix** | Text added before each product's image alt text. | | {% endstep %} | | {% step %} #### Customize property sections Each property section has its own content block. * **Label** - The section heading shoppers see. Replace the default "Property Section 1" with a shopper-friendly name, like "Key Features." * **Default open** - Shows the section expanded when the comparison opens. For each property in the section, set: * **\[Property] label** - The row name shoppers see. Use a friendly label instead of the raw property name. For example, change `Mouth_size` to "Mouth size." * **\[Property] description** - Optional extra context, shown via the info icon next to the label. * **Show all possible values** - Shows every possible value for the property and highlights the ones each product has. Useful for features shoppers want to check off. * **Show multi value as list** - Shows multiple values as a bullet list instead of a comma-separated line. {% hint style="info" %} **Show all possible values** is only available for some properties. {% endhint %} {% endstep %} {% step %} #### Translate your content Click **Edit languages** to add translations for each locale your experiences run in. Translate the general content, section labels, and property labels and descriptions. {% endstep %} {% step %} #### Save and use the comparison Click **Save**. Then use the comparison where shoppers need it: * **Campaigns** - Select the comparison when building a comparison page campaign. * **Product Finder** - [Enable Product Comparison](/how-to-guides/product-finders/finder-editor/page-settings.md#enable-product-comparison) on your Results Page. * **Sagent** - Add it as a [Comparison tool](/how-to-guides/sagent/setup/tools.md#comparison-tool). {% endstep %} {% endstepper %} ## Best practices

Label for shoppers, not feeds

Raw property names like Primary_use confuse shoppers. Give every property a clear, human label.

Check data coverage

Empty values show as a dash. Only compare properties that are populated across the products in scope.

Group with intent

Use sections to mirror how shoppers think, like "Features," "Size," and "Care," and open the most important section by default.

Keep comparisons focused

Use product filtering to keep each comparison to one category, so every row is relevant.

## Frequently asked questions
Can I use the same comparison in more than one experience? Yes. Create the comparison once and select it in a Campaign, Product Finder, or Sagent.
Why do some rows show a dash? The product has no value for that property. Check your product data, or remove the property if coverage is low.
Do I need to translate every field? Translate any field shoppers see in each locale. Untranslated fields fall back to the default content.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.crobox.com/how-to-guides/product-comparisons/create-a-product-comparison.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.