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

Catalog & Commerce overview

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

Conversa Labs

Last updated on Jun 27, 2026

Overview

The Catalog & Commerce module brings together everything about products and sales inside your conversations. With it you keep a native catalog (products, categories, images and prices), sync that catalog with Meta's WhatsApp Business Catalog, send products and product lists directly in the chat, receive customer orders as a ready-to-charge card, and track the e-commerce lifecycle of external platforms (Kiwify, Hotmart, Nuvemshop, Shopify) without leaving the platform.

The goal is to turn the conversation into a sales counter: the customer sees the product, builds the order, and you collect payment — all in one place, integrated with CRM, Payments and Follow-ups.

Prerequisites

  • An active ConversaLabs account with the Catalog & Commerce module enabled for your plan and access role. If you don't see the module, talk to an administrator.
  • For WhatsApp Business Catalog: a connected WhatsApp (Cloud API) Inbox that can be bound to the Meta catalog.
  • For the e-commerce lifecycle: access to the external platform (Kiwify, Hotmart, Nuvemshop or Shopify) to set up the webhook.
  • To charge orders: the Payments module configured (gateways such as Asaas or Mercado Pago).

Step by step

  1. Create or import your native product catalog (with categories, images and prices).
  2. If you serve customers over WhatsApp, bind and sync the catalog with the WhatsApp Business Catalog.
  3. During a conversation, send products (a single product or a list) to the customer.
  4. When the customer builds a cart, receive the order as a card and generate a charge or a subscription.
  5. Connect e-commerce platforms to track the lifecycle (abandoned cart, pending PIX, approved purchase, refund) and recover sales with Follow-ups.

Settings & options

  • Native catalog: product records, categories, images, price and availability.
  • Sync sources: binding to the WhatsApp Business Catalog (Meta) and to external connectors, with a configurable sync interval.
  • Sending in the conversation: send a single product, a product list, or open the WhatsApp catalog.
  • Orders: order card with items, total and shortcuts to Create charge / Create subscription.
  • Commerce (lifecycle): external platform webhooks with a per-source URL and verification secret.

Use cases

  • A store that serves customers over WhatsApp and wants to show native products without sending the customer to a website.
  • An operation that receives orders from the WhatsApp cart and bills immediately with PIX or boleto.
  • A digital-product seller using Kiwify/Hotmart who wants to recover abandoned carts and pending PIX.
  • A Nuvemshop/Shopify store that centralizes sales recovery inside support.

Tips, limits & best practices

  • Major-unit amounts: a price of 4.97 means R$4.97 — never divide by 100. An order total is the sum of price × quantity for each item.
  • Native WhatsApp products and orders (catalog, list, order card) work on the Cloud API; on WhatsApp Web, sales use the enriched product card as a fallback.
  • Keep product images publicly accessible so the sync can download them.
  • Start with a well-organized native catalog before enabling sync and external connectors.

Troubleshooting

  • I don't see the module: it may not be enabled for your account or role — talk to an administrator.
  • Products without images after sync: check that the original images are reachable and run the sync again (each run re-attempts the image download).
  • The customer doesn't receive the native product/order: confirm the inbox is WhatsApp Cloud API.

See also