ConversaLabs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Sync and WhatsApp Business Catalog

Open in
View as Markdown Open in ChatGPT Open in Claude
Conversa Labs

Conversa Labs

Last updated on Jun 27, 2026

Overview

Sync connects your native catalog to Meta's WhatsApp Business Catalog. Once bound, products exist in both places and can be kept in two-way sync: what you record on the platform is pushed to Meta, and what exists in Meta's catalog can be imported into the platform.

This is what makes it possible to send native products on WhatsApp, open the catalog inside a conversation, and receive orders from the customer's cart — all from a single, up-to-date catalog.

Prerequisites

  • A connected, working WhatsApp (Cloud API) Inbox.
  • A catalog set up in your Meta business account (Business / Commerce Manager).
  • The Catalog & Commerce module enabled and permission to manage sync sources.
  • A native catalog with products recorded (recommended before the first sync).

Step by step

  1. In the Catalog area, open the sync sources configuration.
  2. Create a source of type WhatsApp Business Catalog (Meta) and select the Meta catalog to bind.
  3. Bind the source to the matching WhatsApp Cloud inbox — the access credential is reused automatically from that inbox, with no need to enter a separate token.
  4. Set the sync interval (how often the platform checks Meta's catalog).
  5. Run the first sync and review the imported/updated products.
  6. From then on, changes flow both ways according to the configured interval, and you can force a manual sync whenever you want.

Settings & options

  • Bound Meta catalog: which catalog from the business account is connected to the source.
  • Inbox: the WhatsApp Cloud inbox used for the credential and to send products.
  • Sync interval: how frequently automatic syncs run.
  • Manual sync: a button to run the sync right away.
  • Two-way: products recorded on the platform are published to Meta; Meta products are imported into the platform, matching identifiers on each side.

Use cases

  • A store that already has a catalog in Meta and wants to bring it into the platform to serve and bill.
  • An operation that prefers to record products on the platform and publish them automatically on WhatsApp.
  • A team that maintains a single catalog and wants to avoid updating prices in two places.

Tips, limits & best practices

  • Automatic credential: when you bind the source to the WhatsApp Cloud inbox, the platform uses that inbox's credential — you don't need to register a token just for the catalog.
  • Images must be reachable: the sync downloads product images. If the original image is hosted at an address that goes offline, it won't be imported. Keep images in a public, stable location.
  • Major-unit amounts: prices stay in major units (4.97 = R$4.97) on both sides.
  • Run the first sync outside peak hours so you can review the result calmly.

Troubleshooting

  • Imported products without images: the original image may be unreachable; ensure a public address and run the sync again (each run re-attempts the image download).
  • Nothing syncs: confirm the source is bound to a valid WhatsApp Cloud inbox and that the selected Meta catalog is the right one.
  • A change didn't appear on the other side: wait for the sync interval or run a manual sync.

See also