Back to blog

WhatsApp Catalog and Shopping Messages for Ecommerce

Hamza Parvez

Author

Hamza Parvez | Founder

Published on

November 22, 2026

8 min read

A WhatsApp catalog is the official product list attached to your business presence, so a customer can browse items, open a detail view, and start an order without pretending the chat is a search engine. Shopping messages — product, catalog, and multi-product messages on the Business Platform — are how you bring those items into a thread at the right moment. Together they are the merchandising layer of WhatsApp ecommerce. They are not, on their own, a store. You still need accurate stock, a checkout path, and an assistant that will not invent a variant you do not sell.

This guide is for operators who already sell somewhere (often Shopify or another commerce stack) and want WhatsApp to close the gap between curiosity and checkout. We have a companion piece on WhatsApp automation for Shopify and a deeper look at grounded catalog answers. Here the focus is the catalog itself.

Why a catalog beats a PDF of products

A PDF or a photo grid cannot tell you what is out of stock, cannot be personalised, and cannot be logged as a product event. An official catalog can be maintained as a feed, referenced in a message, and used by a bot as the source of truth for price and availability. When a customer asks “do you have this in 9?” the honest answer has to come from that source, not from a model that once saw a similar shoe on the public web.

Keep the catalog boring in the best way: correct titles, current prices, images that match the SKU, and fields your team actually uses (size, colour, lead time). A beautiful catalog that is two weeks stale will create refunds.

How shopping messages should be used

Send or show products when the customer has expressed intent, not as a random store dump.

  • After a question about a category, show a short set of matching items, not the entire warehouse.
  • After a cart is abandoned, remind them of the specific items, with a path to complete or to ask a question. See cart recovery sequences.
  • After a size or compatibility question is resolved, show the exact SKU you just recommended.
  • In a broadcast, only include products that are relevant to the segment, and only if the template and opt-in allow it.

Multi-product messages are still messages. They count toward policy, quality, and, where applicable, fees. Restraint is a merchandising skill.

The bot has to read the same catalog

This is the failure I see most often: the store feed says one price, the agent says another, and the bot says a third from a stale FAQ. Pick a system of record. WhatsApp Automater is built so the assistant can be grounded in products and documents, then hand off to a human with that same context in the inbox. If you change a price in the morning, the afternoon’s chats should already know.

When the item is not in the catalog, the bot should say it cannot confirm, offer a close alternative only if you have authorised that behaviour, or pass to a person. Inventing a SKU is worse than a missed sale.

Implementation outline

  1. Build or sync the official catalog (Commerce Manager or a connected shop integration) and attach it to the WABA.
  2. Decide which fields the bot may quote.
  3. Connect the official number to your platform and test product and multi-product messages in a sandbox thread.
  4. Wire checkout — native payments where available, otherwise a reliable cart link — and confirm the order in the chat afterwards. See WhatsApp Payments.
  5. Add recovery and utility templates (order shipped, out for delivery, delay) that refer to the same SKUs.
  6. Review a weekly sample of product chats for stale prices or missing variants.

On WhatsApp Automater you can start this on the free plan at modest volume, then move to Starter, Growth, or Pro as conversations grow. Meta’s message fees are separate.

Catalog on the Business app versus the API

The Business app can host a catalog for a small seller. The API is how you automate shopping messages, team selling, and recovery at volume. If you use coexistence, confirm how the app-side catalog and the API-side journeys interact in Meta’s current rules so you do not maintain two contradictory lists.

Merchandising rules for chat

In a shop, you can put a hundred products on a wall. In a thread, a customer can only look at a few. Default to a tight set: the item they asked about, one alternative in stock, and a path to a human. Seasonal collections can live in a catalog section and be opened on request, not pushed unsolicited every morning. If you would not send the same montage as an SMS to a loyal customer, do not send it as a shopping message either. Review the catalog feed on the same cadence you review paid ads, because a wrong price in chat is as public as a wrong price in a campaign. Keep a simple changelog of catalog edits so you can explain a disputed price later.

Put these playbooks into production

Start with WhatsApp Automater's free tier, connect WhatsApp, and iterate on real customer conversations — with analytics built in. Get started free or see plans on whatsappautomater.com.

FAQ’s

Put these playbooks into production

Start with WhatsApp Automater's free tier, connect WhatsApp, and iterate on real customer conversations — with analytics built in.

Related Posts