---
title: Inspect content and properties
slug: n8ge0096
canonical_url: https://docs.coveo.com/en/n8ge0096/
collection: coveo-for-commerce
source_format: adoc
---
# Inspect content and properties
Once you've [pushed or updated](https://docs.coveo.com/en/p48b0322/) your product data in your [Catalog source](https://docs.coveo.com/en/n8of0593/), you can use tools from the [Coveo Administration Console](https://docs.coveo.com/en/183/) to validate the accuracy of indexing, categorization, and information completeness for your [items](https://docs.coveo.com/en/pa8f6515/).

The [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) page of the Coveo Administration Console lets you inspect the content indexed in your [Coveo organization](https://docs.coveo.com/en/185/).

## Inspect object types

Once you've integrated your product data into your Catalog source, whether through an initial stream or an update, you can review your items to ensure the accurate display and categorization of your [products](https://docs.coveo.com/en/m53g7119/), [variants](https://docs.coveo.com/en/m53g0506/), and [availabilities](https://docs.coveo.com/en/m53g0124/).

To do this, access the **Content Browser** page of the Coveo Administration Console.
This tool incorporates a [search interface](https://docs.coveo.com/en/2741/) that lets you browse your content.

During the configuration of your product data (using the JSON file), you establish the `objecttype` metadata on your items, which determines whether each item should be classified as a `Product`, `Variant`, or `Availability`.

At this stage, it's crucial to confirm the presence of all your items and to verify their proper categorization by examining the item's `objecttype` value.

**Example**

You streamed the following products to your Catalog source:

* Coveo Soccer Shoes - Red

* Coveo Soccer Shoes - Blue

* Coveo Soccer Shoes - Yellow

These products are available in different sizes, which are translated in variants:

* 8

* 9

* 10

You also configured an [availability channel](https://docs.coveo.com/en/mc7e9096/), which is the `Montreal store`.

To ensure that everything was indexed in your Catalog source, you use the **Content Browser** page of the Coveo Administration Console and verify that all items appear and that they're categorized with the proper `objecttype`.

![Inspecting Content Browser | Coveo for Commerce](https://docs.coveo.com/en/assets/images/coveo-for-commerce/images/inspect-content-browser.png)

You see that you have items representing the different [catalog objects](https://docs.coveo.com/en/ncig0154/) since they were categorized with the correct `objecttype` value.

You can even use the facets on the left to filter your items by catalog object type.

If you don't see all your items, or some items aren't categorized properly, review your JSON files and make sure that all items are present and contain an `objecttype` property with the expected value (`Product`, `Variant`, or `Availability`).

> **Important**
>
> If you must make any modifications to your product data (JSON file), you'll have to perform the [full update operation](https://docs.coveo.com/en/p4eb0129/) for the changes to be effective in your source.

## Review item properties

After you've pushed or updated your product inventory in your Catalog source, review your item properties to ensure that everything was indexed as expected.

To achieve this, you can access the **Content Browser** page of the Coveo Administration Console.
See [Review item properties](https://docs.coveo.com/en/1712/) for instructions on how to access the properties indexed for a specific item.

When inspecting an item, you'll see all the [fields](https://docs.coveo.com/en/200/) and [metadata](https://docs.coveo.com/en/218/) associated to this item.
At this stage, you should verify whether the items contain all the fields you intend to have available.

While your items can contain a lot of information relevant to your use case, you should verify the following categories:

* [Standard commerce fields](#inspect-standard-commerce-fields)

* [Catalog structure fields](#inspect-catalog-structure-fields)

* [Additional relevant fields](#inspect-additional-fields)

### Inspect standard commerce fields

To ensure the optimal performance of your Coveo for Commerce implementation, it's essential to populate the Coveo for Commerce standard [fields](https://docs.coveo.com/en/200/).
These commerce-related fields store vital [metadata](https://docs.coveo.com/en/218/) on your products, such as price, name, and description.
For more information about standard commerce fields, see [Commerce fields](https://docs.coveo.com/en/n73f0502/).

After you've confirmed the accurate [mapping](https://docs.coveo.com/en/217/) of these fields, verify that these fields are populated with the correct information.

To achieve this, ensure that the fields prefixed with `ec_` are appropriately populated.

**Example**

When inspecting the `Coveo Soccer Shoes - Red` product, you want to verify whether the standard commerce fields are populated with the relevant metadata contained in your [catalog data](https://docs.coveo.com/en/obcf0333/) (JSON file).

Suppose your product data designates the price of a product through the `price` metadata.
Once you've linked the `ec_price` standard field to the `price` metadata and uploaded your [catalog data](https://docs.coveo.com/en/obcf0333/) to the Catalog source, confirm that the `ec_price` field accurately reflects the intended value.

To verify this, navigate to the **Content Browser** and examine the properties of a **product** object type.
The **Fields** tab will show each field name and associated value.

![inspecting items in Content Browser | Coveo](https://docs.coveo.com/en/assets/images/coveo-for-commerce/images/inspect-standard-fields.png)

If you come across any inconsistencies, we recommend reviewing your JSON files to confirm the existence of all pertinent metadata and to ensure that your [mapping](https://docs.coveo.com/en/217/) rules accurately associate the metadata with the corresponding fields within your Coveo organization and adjusting accordingly.

> **Important**
>
> If you must make any modifications to your product data (JSON file) or mapping rules affecting the items of your Catalog source, you'll have to perform the [full update operation](https://docs.coveo.com/en/p4eb0129/) for the changes to be effective in your source.

### Inspect catalog structure fields

To simplify the management of catalog configuration, you must [create an additional set of fields](https://docs.coveo.com/en/n73f0502#structure-fields).

While you can use different names for these fields, you must ensure that this information exists in the items of your Catalog source.

For example, if you leverage availability channels, you must have a field that uniquely identifies each availability channel, along with another field that specifies the list of available products/variants within a particular availability channel.

To ensure the accuracy of this data, you can inspect your items to ensure that these fields are populated with the correct information.

**Example**

In your Catalog source, you have items categorized with the `Product`, `Variant`, and `Availability` catalog objects.

Assuming that you're using the [recommended unique product identifier](https://docs.coveo.com/en/n73f0502#define-a-unique-product-identifier) and [recommended field names](https://docs.coveo.com/en/n73f0502#structure-fields), you want to verify the following:

* Every item, regardless of its catalog object (`Product`, `Variant`, or `Availability`), has an `ec_product_id`.

> **Note**
>
> To train [Coveo Machine Learning (Coveo ML)](https://docs.coveo.com/en/188/) [models](https://docs.coveo.com/en/1012/), this field can't contain the `#` character.

* Items categorized as `Variant` must include an `ec_variant_id` field.

* Items categorized as `Availability` must include an `ec_availability_id` field and an `ec_available_items` field.

If you come across any inconsistencies, we recommend reviewing your JSON files to confirm the existence of all pertinent metadata and to ensure that your [mapping](https://docs.coveo.com/en/217/) rules accurately associate the metadata with the corresponding fields within your Coveo organization and adjusting accordingly.

> **Important**
>
> If you must make any modifications to your product data (JSON file) or mapping rules affecting the items of your Catalog source, you'll have to perform the [full update operation](https://docs.coveo.com/en/p4eb0129/) for the changes to be effective in your source.

### Inspect additional fields

Additional fields are often needed to store more specific metadata for your products.
For example, if you sell shoes, you'll likely want your items of the `Product` catalog object type to contain information such as `gender`, `style`, and `collection`, or items of the `Variant` catalog object type to contain information such as `size` and `width`.

To ensure comprehensive information, review your items to confirm the presence of these fields for relevant items and their alignment with the anticipated metadata.

**Example**

Before streaming your product inventory into your Catalog source, you created fields to provide your customers with relevant variant information for the shoes you're selling, such as `size` and `width`.

You then mapped these fields with the metadata available in your [catalog data](https://docs.coveo.com/en/obcf0333/) (JSON file) so that the products show this information when users are browsing them.

Therefore, you inspect your items to make sure that they all contain the correct information.

![inspecting items in Content Browser | Coveo](https://docs.coveo.com/en/assets/images/coveo-for-commerce/images/inspect-additional-fields.png)

If you come across any inconsistencies, we recommend reviewing your JSON files to confirm the existence of all pertinent metadata and to ensure that your [mapping](https://docs.coveo.com/en/217/) rules accurately associate the metadata with the corresponding fields within your Coveo organization and adjusting accordingly.

> **Important**
>
> If you must make any modifications to your product data (JSON file) or mapping rules affecting the items of your Catalog source, you'll have to perform the [full update operation](https://docs.coveo.com/en/p4eb0129/) for the changes to be effective in your source.