On this page
The Meta Catalog integration connects a Commerce Manager catalog to VGraple CRM so agents and flows can send product messages inside WhatsApp conversations, customers can browse and build a cart, and orders arrive in the inbox with items and quantities ready for a payment link. It is native: you authorise VGraple CRM with Meta, pick the catalog, and products sync into your workspace through Meta's Graph API.
What syncs
| Data | Direction | Timing |
|---|---|---|
| Products: retailer ID, name, description, price, currency, image, availability, category | Meta to VGraple CRM | Initial sync on connect; Re-sync on demand |
| Single product, multi-product and catalog messages | VGraple CRM to WhatsApp | Immediate, inside the window or via catalog templates |
| Order messages (cart contents) from customers | WhatsApp to VGraple CRM | Real time |
| Payment link for the order | VGraple CRM to WhatsApp | On agent or automation action |
Setup
- Go to Settings, then Meta Catalog, and click Continue with Meta.
- Pick the catalog from the list (your Business Manager may have several) and confirm.
- Wait for the initial sync; large catalogs take a few minutes. The product browser in Settings shows what arrived.
- Turn on Catalog enabled to put the shop icon in the inbox composer. Turn on Allow add-to-cart when you are ready to accept carts as orders.
- In Flow Builder, add a Send Product step where a bot should show a product, with a fixed retailer ID or a variable.
- Click Re-sync whenever prices or stock change in Commerce Manager.
Who uses it
Retail and D2C brands that sell a fixed range (fashion, cosmetics, electronics accessories), restaurants and cloud kitchens that treat the menu as a catalog, and service businesses that list packages as products so a bot can quote a price with a picture. Businesses with thousands of SKUs and daily price changes usually keep the catalog in a feed (CSV or scheduled URL in Commerce Manager) and rely on Re-sync after each feed run.
How it fits with the rest of VGraple CRM
Product messages are session messages, so they pair naturally with anything that opens a window: a QR code on packaging, a click-to-WhatsApp ad, a comment automation that DMs the commenter. Once the customer sends a cart, the order message lands in the inbox with the items, the agent or a rule sends a Stripe or Cashfree payment link, and the paid amount is attributed to the campaign or flow that started the conversation. Analytics reports revenue by product message and by campaign, and the Conversions API sends the purchase back to Meta when the chat began from an ad.
Before you connect
Check three things in Commerce Manager: the catalog belongs to the same Business Portfolio as your WhatsApp Business Account, every item has a unique retailer ID (the value flows and templates reference), and item review status is approved. A catalog attached to a different portfolio does not appear in the picker, and rejected items sync but do not display in WhatsApp.
Three recipes
- Customer types a product name -> AI or flow sends the matching product card -> customer adds to cart -> order lands in inbox -> payment link. The whole sale happens inside WhatsApp.
- Restaurant menu as sections -> multi-product message from a "menu" keyword -> cart becomes an order for the kitchen.
- Marketing broadcast with a catalog template -> customers browse the collection and reply -> agents follow up with the product they viewed.
Limits and gotchas
- Multi-product messages carry up to 30 products in up to 10 sections; single product messages carry one.
- Product messages are session messages (inside the 24-hour window); outside it, use a catalog template where Meta offers it.
- Items that fail Meta's commerce review do not display in WhatsApp; fix them in Commerce Manager.
- Coexistence numbers show the app's catalog on the WhatsApp profile; API product messages use the Commerce Manager catalog connected here.
- Re-sync is manual; schedule a habit after price changes.
The catalog guide covers every setting and the review states.