> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/ecommerce/push-products-to-meta-catalog.md).

# Push Products To Meta Catalog

You can sync your e-commerce products or recent updates directly to your Meta catalog.

**Steps:**

1. Go to **E-commerce**
2. Select your **Store**
3. Click **Push Products** (top options)

All products from your e-commerce section will be sent to the Meta catalog.

**What Happens Next?**

* If the **SKU already exists** in Meta → The product will be **updated**
* If the **SKU is new** → The product will be **created automatically**

Note: Meta and WhatsApp follow an approval process, so changes may take a few hours to reflect in the WhatsApp catalog.

Your products are now successfully synced with Meta.

{% embed url="<https://youtu.be/iY1ETUXfopA?si=OKjB6cCwgdP_bRkO>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/ecommerce/push-products-to-meta-catalog.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.