Index and manage catalog data

This is for:

Developer System Administrator
In this article

A catalog entity is a structure that represents the relationships between items in a source. It’s composed of a source containing products, variants, and availabilities that are unique, and a catalog configuration.

Note

A catalog entity can also contain an extra source dedicated for availabilities if they’re not contained in the product source.

The articles in this section explore how to integrate your catalog data into the Coveo Platform’s infrastructure. This integration establishes the relationships between your items, their variants, and their availabilities.

Coveo stores your catalog data in a way that can be leveraged through search and Coveo Machine Learning. You still manage them in your content management system (CMS) of choice.

Index content

Coveo offers tools to index catalog data, as well as a wide array of website content, all stored in a secured unified index.

To index your items, Coveo uses information sourced from your product information management (PIM) system, digital asset management (DAM) system, and other storage locations. It’s your responsibility to consolidate and structure this information in a format that can be processed by Coveo. Every item that needs to be indexed should include the necessary metadata as per Coveo’s requirements in one or more JSON files.

In this section, you’ll find articles with instructions for integrating your catalog data into your index and configuring your catalog entity:

Notes

Alternatives to the Catalog source

We strongly advise all Coveo for Commerce implementations to use the Catalog source to store catalog data, as well as the Stream API to perform push and update operations. This source is specifically designed to handle the complexity of commerce data and handle Coveo’s AI personalization features.

If your use case requires the usage of one of the following sources, contact your Coveo representative to discuss your options: