--- title: Setup checklist slug: p2oe0516 canonical_url: https://docs.coveo.com/en/p2oe0516/ collection: coveo-for-commerce source_format: adoc --- # Setup checklist This article provides a checklist to verify that your Coveo for Commerce implementation includes all the essential components for a fully functional and optimized setup. > **Note** > > This checklist supports only implementations that target the Commerce API. ## Map your storefront architecture Before you start setting up Coveo for Commerce, you must map your [storefront](https://docs.coveo.com/en/p33g0410/) architecture in a way that's compatible with Coveo. * Have you identified the storefronts you want to integrate with Coveo for Commerce? ** Have you defined a [tracking ID](https://docs.coveo.com/en/o8rb0139/) for each of these storefronts? See [What's a tracking ID?](https://docs.coveo.com/en/n8tg0567/) for more information on how to define a tracking ID. ** Have you registered each [tracking ID](https://docs.coveo.com/en/o8rb0139/) as a [property](https://docs.coveo.com/en/p4ue0547/) using the [**Properties**](https://platform.cloud.coveo.com/admin/#/orgid/usage/properties/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/usage/properties/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/usage/properties/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/usage/properties/)) page of the Coveo Administration Console? For more information on how to map your storefront architecture to Coveo, see [Map your storefront architecture to Coveo](https://docs.coveo.com/en/o25a0034#map-your-storefront-architecture-to-coveo). ## Product catalog indexing . Have you ensured that all your products, their [variants](https://docs.coveo.com/en/mc7f0326/), and the various [availability](https://docs.coveo.com/en/mc7e9096/) channels are correctly indexed within your [Catalog source](https://docs.coveo.com/en/l5if0244/)? See [Push and update your catalog data](https://docs.coveo.com/en/p48b0322/) for details. ** If you're supporting multiple combinations of languages and currencies, have you created a [Catalog source](https://docs.coveo.com/en/l5if0244/) for each combination? ** If your product offering differs depending on regions (for example, different products in different countries), have you created a [Catalog source](https://docs.coveo.com/en/l5if0244/) for each region? . Are the [standard commerce fields](https://docs.coveo.com/en/n73f0502#standard-commerce-fields) appropriately mapped to relevant [metadata](https://docs.coveo.com/en/218/) in your [catalog configuration](https://docs.coveo.com/en/3139#catalog-configuration)? . Have you set up fields to help you structure your catalog entity with products, variants and/or availability, and mapped them to the relevant metadata? See [catalog structure fields](https://docs.coveo.com/en/n73f0502#structure-fields) for details. . Have you created and mapped [additional commerce fields](https://docs.coveo.com/en/n73f0502#create-additional-commerce-fields) with relevant metadata? . Is your [catalog entity](https://docs.coveo.com/en/3139/) fully configured to support your products, variants, and availabilities? ** If you're supporting multiple combinations of languages and currencies, have you created a catalog entity for each combination? ** If your product offering differs depending on regions (for example, different products in different countries), have you created a catalog entity for each region? . Have you implemented a system that allows for convenient [updates](https://docs.coveo.com/en/p4eb0515/) without requiring you to re-upload your entire [catalog data](https://docs.coveo.com/en/obcf0333/) every time? ## Configure Coveo ML . Have you [configured the recommended Coveo ML models](https://docs.coveo.com/en/o25a0034#machine-learning-models-for-coveo-for-commerce) for each product discovery interface that you've built? ** Are the models associated with the correct query pipelines? . When using product grouping to group products in commerce interfaces, have you done the required configurations? See [Product grouping](https://docs.coveo.com/en/l78i2152/) for all configuration details. ## Build commerce interfaces Your storefront visitors use commerce interfaces to search, browse, and purchase products. Each of these interfaces is powered by a [product discovery solution](https://docs.coveo.com/en/o9cf0524/). . Have you identified every [locale](https://docs.coveo.com/en/p4tf0351/) that each [storefront](https://docs.coveo.com/en/p33g0410/) can support and [defined your storefront associations](https://docs.coveo.com/en/o48e0216/) using the [**Storefront associations**](https://platform.cloud.coveo.com/admin/#/orgid/commerce/storefront/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/commerce/storefront/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/commerce/storefront/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/commerce/storefront/)) page? . Have you [built and configured your commerce search pages](https://docs.coveo.com/en/o4ue0200/)? ** Once you've built and configured your search pages, have you verified that search requests being sent to the Coveo Commerce API? . Have you [built and configured your commerce product listing pages](https://docs.coveo.com/en/o4ue0471/)? ** Once you've built and configured your product listing pages, have you verified that product listing requests are being sent to the Coveo Commerce API? . Have you [built and configured your commerce recommendation interfaces](https://docs.coveo.com/en/o4ue0204/)? ** Once you've built and configured your recommendation interfaces, have you verified that recommendation requests are being sent to the Coveo Commerce API? . Do your commerce interfaces comply with [Coveo's SEO best practices](https://docs.coveo.com/en/2775/)? > **Leading practice** > > * Building commerce interfaces with a Coveo UI library, such as [Coveo Headless](https://docs.coveo.com/en/o52e9091/), considerably simplifies the implementation process. > > * Coveo Headless allows you to build server-side rendered commerce interfaces, which enhances performance and SEO. > See [Headless commerce usage (server-side rendering)](https://docs.coveo.com/en/obif0156/) for details. ## Log commerce events It's crucial that you track [touchpoints](https://docs.coveo.com/en/o6ha0421/) to analyze storefront performance, create reports, and power [Coveo Machine Learning (Coveo ML)](https://docs.coveo.com/en/188/). > **Leading practices** > > * Building commerce interfaces with a Coveo UI library, such as [Coveo Headless](https://docs.coveo.com/en/o52e9091/), considerably simplifies the implementation of commerce events tracking. > > In particular, the [Coveo Headless Commerce controllers](https://docs.coveo.com/en/headless/latest/reference/modules/Commerce.html) automatically log specific commerce events that track behaviors, such as when a purchase is made or when a product is added to a cart. > > * It's recommended to start logging commerce events before going live with your Coveo for Commerce implementation. > This allows Coveo ML models to start learning from your data and provide more relevant results from the get-go. > If you want to use this approach, you can [use Relay](https://docs.coveo.com/en/o1n90002/) in your current storefront to log commerce events. . Are product clicks being logged? . Are product views being logged? . Are products being added/removed from the cart being logged? ** If products can be added to a cart directly from the search results page, product listing pages, or recommendation slots, are you [sending an additional click event](https://docs.coveo.com/en/o1n93466#send-an-additional-click-event)? . Are purchases being logged? . Have you performed [data validation](https://docs.coveo.com/en/o2170365/) to ensure that the events are being sent to Coveo and contain accurate information? For more information on how to log commerce events, see [Log commerce events](https://docs.coveo.com/en/3188/). ## Commerce authentication * Have you [configured your commerce authentication method](https://docs.coveo.com/en/o8ld0051/) to authenticate requests to the Commerce and Events APIs? > **Important** > > Ensure that the chosen authentication method doesn't specify a search hub value. > In Coveo for Commerce implementations, this is automatically handled by the Coveo Commerce API. ## Coveo Merchandising Hub * Are you using the [Coveo Merchandising Hub (CMH)](https://docs.coveo.com/en/o5290573/) to manage search queries, product listing pages, and [recommendation slots](https://docs.coveo.com/en/o9b80563/)? See [Coveo Merchandising Hub (CMH)](https://docs.coveo.com/en/ncce4140/) for more information.