> 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/create-a-meta-catalog-and-link-with-whatsapp-api-number.md).

# Create A Meta Catalog And Link With WhatsApp API Number

Follow these steps to create and upload products to your Meta catalog:

Step 1: Open Meta Commerce Manager

1. Go to **Channels → WhatsApp Channel**
2. Click your **WhatsApp Account (WABA)**
3. Open **WABA Business Profile**
4. Go to **Commerce Settings**
5. Click **Meta Catalog Manager**

Step 2: Create New Catalog

6. Click **Create Catalog**
7. Select **Catalog Type**
8. Choose Business Portfolio
9. Enter Catalog Name
10. Click **Next**
11. (Optional) Connect Event Tracking or skip

Step 3: Add Products

12. Choose **Manual Upload** (or Data Feed)
13. Add:

* Product Name
* Description
* Price
* Product Link
* Facebook Product Category (optional)

14. Upload Product Images (you can add multiple images)
15. Click **Save / Upload Item**

Important Notes

* You need at least **5 products** to run Advantage+ or Catalog Ads.
* Optional fields like Brand, Content ID, etc., can be added if required.

Once uploaded, your products will appear in Meta Commerce Manager and can be used in WhatsApp catalog and ads.

{% embed url="<https://youtu.be/ODC-jqPo5wE?si=SfcORl9edAxRHUI9>" %}


---

# 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/create-a-meta-catalog-and-link-with-whatsapp-api-number.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.