> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/content-management-cms/contentful-101/adding-a-new-product-in-contentful.md).

# Adding a new product in Contentful

### Introduction

Assuming you have a new product you want to sell in your store, this guide will walk you through the steps to add it to your online store.

### Steps to add a new product to your store

Select the **Space** where you want to create the new content. We strongly recommend using a sandbox environment first to ensure it looks exactly as you want before publishing it to your Production site.

Click on **Content** and click **Add entry.**

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-437198c80a43aab57500882710f74b14625b6f0f%2Fadding-a-new-product-in-contentful-1.jpg?alt=media)

From the Content Type dropdown, select **Product**, and fill in the fields for your new content.

Below is an example; your page might differ depending on the content types you selected for your Product.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-b7f77b31719cfac38c06d4ce98755ff557d30696%2Fediting-a-product-in-contentful-5.gif?alt=media)

When you are ready to publish your content, click the **Publish** button. This will make your content available on your website. You can also schedule to **Publish** later by selecting **Set Schedule.**

If your newly created product is shared among multiple Collections, you must add them to these Collection pages and Publish them too.

{% hint style="info" %}
💡 It is best practice to minimize the number of unpublished "draft" content entries to reduce clutter and avoid confusion
{% endhint %}

### Verification OMS

Navigate to Products in the OMS and verify that the product you've created in Contentful has been published and sync'd

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-fd62c49b71d6b46e3c5bd3df9545750194a4d8a4%2Fadding-a-new-product-in-contentful-3.jpg?alt=media)

Click on the product and verify that all entries are accurately reflected.

**It is best to update your content in Contentful if you need to update it since your source of truth is your CMS.**

To add inventory to your product, click on the Product Stock tab, select your Stock location, and proceed from there.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-111563e50efee9fe371458a1899cc89bb9b65e33%2Fadding-a-new-product-in-contentful-4.gif?alt=media)


---

# 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.chord.co/chord-oms/content-management-cms/contentful-101/adding-a-new-product-in-contentful.md?ask=<question>&goal=<user_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.