> 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/chord-oms-overview/store-variables/syncing-content-with-contentful.md).

# Syncing content with Contentful

### Introduction

Contentful is a content management system (CMS) where you can create and manage content when synced with OMS.

Content managed in Contentful includes products, variants, emails, site/store content, media, and more.

Catalog items, such as products and variants, ***can not*** be created in the OMS; they must be created and managed in Contentful.

OMS imports three types of content from Contentful:

1. Products (including variants)
2. Subscriptions
3. Kits

The OMS includes a job that syncs content between Contentful and itself. The job can be manually invoked by clicking the **Sync Store Content** button on the Edit Store page. This button invokes the `ACS::SyncStoreContentJob job,` which calls the `ACS::Contentful::SyncStoreContent` service for the chosen store.

That service calls other services, such as `ACS::Contentful::SyncProduct`, to sync for the specific content type.

### Syncing Kits/Bundles

Kits and bundles in Contentful sync in the same manner as other entries, with one additional step. In Contentful, each kit includes an entry that defines the products permitted in the kit. OMS will prevent customers from adding products not on this list to the specific bundle.


---

# 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/chord-oms-overview/store-variables/syncing-content-with-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.