All postsWhatsApp BusinessE-commerceWhatsApp CatalogSocial Commerce

WhatsApp Collections Step by Step Setup Guide for Sellers

WhatsApp collections let you group catalog products into browsable categories inside chat. This guide walks through setup, naming strategy, API-level management, and how to actually use collections to move buyers through a decision.

WhatsApp Collections Step by Step Setup Guide for Sellers

If you're already running a WhatsApp catalog, collections are the next thing worth setting up before your product list gets unwieldy. Read: How Real Estate Teams Use WhatsApp Chatbots to Qualify Leads.


Most D2C brands on WhatsApp get the catalog live and stop there. Products are listed. Images are uploaded. The catalog link is somewhere in the bio.

Then a customer asks, "Do you have anything for oily skin?" And someone on the team manually types out three product names.

That's the gap WhatsApp collections close. Instead of a flat scroll of 80 products, collections let you slice your catalog into labeled groups that customers can navigate on their own. Skincare by concern. Apparel by occasion. Supplements by goal. The catalog stops being a product dump and starts functioning like an actual storefront.

This guide covers how to set up WhatsApp collections from scratch, how to structure them so they actually help buyers, and what changes when you're working at the API level with a proper CRM behind it.


What WhatsApp Collections Actually Are

A WhatsApp collection is a named grouping within your catalog. Think of it as a folder inside your storefront. The catalog is the shop, the collection is the aisle.

When a customer opens your catalog from the storefront icon in chat, they see your collections as browsable tabs or sections. Without collections, they land on a flat list. With collections, they can tap "New Arrivals," "Bestsellers," or "Under ₹999" and immediately narrow down to what's relevant.

Collections don't change how individual products are listed. Each product still needs its own image, name, price, and description. Collections just determine how those products are organized for the customer's browsing experience.

One product can live in multiple collections. A new skincare serum could sit in "New Arrivals" and "Oily Skin" at the same time. That flexibility matters more than most people realize, especially when you're running seasonal or promotional groupings alongside permanent category pages.


Before You Start: What You Need in Place

Setting up collections assumes your catalog is already functional. If it isn't, that comes first.

WhatsApp Business App requirements:

  • An active WhatsApp Business account
  • At least one product added to your catalog
  • Your account must comply with WhatsApp's commerce policy, which covers what product categories can and can't be listed

WhatsApp Business API requirements:

  • A verified Business Manager account on Meta
  • A catalog created and connected in Meta Commerce Manager
  • The catalog assigned to your WhatsApp Business API account (done through Business Settings > Data Sources > Catalogs)

One thing competitors' guides tend to skip: commerce policy eligibility is product-category specific. If you sell anything in restricted categories like financial services, alcohol, or certain health products, your catalog or collections might get rejected at review, even if the setup process goes fine. Check the commerce policy before you invest time building out a full catalog structure.


Step-by-Step: Creating a WhatsApp Collection on the Business App

This is the straightforward path for brands using the standard WhatsApp Business App, not the API.

Step 1: Open the catalog

Go to the three-dot menu (or Settings on iOS) > Business Tools > Catalog.

Step 2: Navigate to Collections

Inside the catalog, look for the Collections tab or option. On most Android devices, this appears as a tab above your product grid. On iOS, it may be nested under a menu icon.

Step 3: Tap "Add Collection"

Name your collection clearly. "Summer Dresses 2025" beats "Collection 1." The name is customer-facing, so treat it like a category label on a shelf.

You can optionally add a short description. Worth doing if the collection name alone doesn't signal what's inside, or if you want to call out something like "free shipping on all items in this collection."

Step 4: Add products

Tap Next after entering the name. You'll see your full catalog list. Select the products that belong in this collection. A product can be in multiple collections, so don't worry about overlap.

Step 5: Save and wait for review

Tap Done. New collections go through a review process that typically takes up to 24 hours. WhatsApp checks that the collection content aligns with commerce policy before making it visible to customers.

If a collection gets rejected, you can appeal through the same WhatsApp Business account. Rejections usually happen when products in the collection are in a restricted category, or when the collection name is misleading relative to the products inside it.


Step-by-Step: Creating Collections via Meta Commerce Manager (API)

If you're on the WhatsApp Business API, your catalog lives in Meta Commerce Manager, not inside the WhatsApp app. The collection structure works the same way conceptually, but the management interface is different.

Step 1: Log in to Meta Commerce Manager

Go to business.facebook.com and navigate to Commerce Manager. Select the catalog connected to your WhatsApp Business API account.

Step 2: Go to the Items tab

Your product inventory lives here. Before creating collections, make sure your products are already uploaded and approved. Items that are pending review or rejected won't show up properly inside collections.

Step 3: Create a product set (the API term for a collection)

In Commerce Manager, collections are called "product sets." Go to the Sets tab (or look for "Manage Product Sets" depending on your Business Manager version). Click Create Set.

Give it a name and set filter rules, or manually select products. Filter-based sets are useful for large catalogs where you want a collection to automatically include all products tagged with a certain attribute, like "category: skincare" or "price < 999."

Step 4: Connect the set to WhatsApp

Product sets created in Commerce Manager automatically sync to your connected WhatsApp catalog. The sync isn't always instant, so give it some time before checking whether the collection appears in WhatsApp catalog previews.

Step 5: Assign your catalog to the WhatsApp Business API account

If you haven't done this yet: Business Settings > Data Sources > Catalogs > select your catalog > Assign Partners > assign to your WhatsApp Business API phone number.


How to Share a Collection in Chat

This is where most guides stop at setup and miss the operational layer.

Collections aren't just passive browse structures. You can send a specific collection directly in a conversation. When a customer is chatting with your team or a bot and asks about a product category, you can share the relevant collection as a message, and they see a browsable card right inside the chat.

On the Business App: In any chat, tap the attachment icon > tap Catalog > navigate to Collections > select the collection and send.

On the API level: Using the API, you can send multi-product messages that reference a product set. This is how automation flows work: a chatbot captures intent ("I'm looking for protein supplements"), and the flow triggers a multi-product message pulling from the "Protein" collection. The customer sees a scrollable product card without leaving the conversation.

We've seen teams underuse this badly, usually because they set up automation for FAQs but never wire product discovery into the same flow. A customer asks about product recommendations, the bot gives a text response, and the catalog never enters the picture. The collection share is three lines of API logic; it just doesn't happen because nobody thinks to connect it.


How to Structure Collections That Actually Convert

Setup is the easy part. Naming and structuring your collections so they guide purchasing decisions is where most brands leave money on the table.

Organize by customer intent, not your internal taxonomy

Your warehouse organizes products by SKU. Your catalog should organize products by what the customer is trying to accomplish.

A bootstrapped D2C haircare brand reorganized its catalog collections from "Shampoos / Conditioners / Serums" to "Dry & Damaged Hair / Oily Scalp / Hair Fall / Growth & Thickness." Same products, different buckets. The shift alone reduced how often customers asked "which one is for me?" before ordering.

Intent-based collections work because they match the question already in the customer's head. If someone messages you with a problem, you send them the collection built around that problem.

Keep collection count manageable

More collections don't mean more discoverability. A catalog with 20 collections creates decision fatigue just as easily as a flat product list. Aim for somewhere between 4 and 10 collections depending on catalog size. If your catalog has under 50 products, 4 to 6 collections is plenty.

Rotate campaign collections without touching permanent ones

Permanent collections should reflect evergreen categories. Campaign collections (Sale, New Arrivals, Festive Picks, Back in Stock) should be created, activated, and retired based on what's actually current.

A 12-person athleisure brand in Surat kept a "Sale" collection live for eight months after their last discount period ended. Customers clicked in expecting deals and found full-price items. The fix is simple: set a calendar reminder to delete or archive campaign collections when the campaign ends.

Match collection names to how customers search and speak

If your customers say "office wear," name the collection "Office Wear," not "Workwear & Formals." The label should sound like something a real buyer would say, not a category manager.


Managing Collections at Scale: What Changes with the API

For brands with larger catalogs or more complex operations, the manual Business App workflow breaks down fast. The API path gives you a few advantages that matter at scale.

Automated product set rules: Instead of manually curating each collection, you can define filter logic. Any product tagged with a specific attribute automatically joins the right collection. A new "Monsoon Essentials" product just needs to be tagged correctly at upload and it appears in the right collection without any manual steps.

Real-time catalog sync from your store: If you're running Shopify or WooCommerce, you can sync your product catalog to Meta Commerce Manager. Stock updates, price changes, and new listings flow through automatically. The WhatsApp catalog reflects live inventory without anyone manually managing it.

Multi-product messages in automation flows: The API lets you trigger collection shares from within chatbot flows. Customer selects "browse skincare" from a button menu, and the next message is a scrollable product card from the skincare collection. This is the bridge between catalog infrastructure and actual conversational commerce.

Catalog-level analytics: Through the API and Business Manager, you can track which products get the most interactions from catalog views. That feedback loop helps you figure out which collection structures are working and which ones customers are ignoring.


What Still Breaks (and Honest Caveats)

A few things to know before you build too much on top of this infrastructure.

Collections don't support in-chat checkout everywhere. WhatsApp Pay and in-chat purchase flows are available in limited markets. In most geographies, including large parts of Southeast Asia and Africa, customers browse the collection and then need to be redirected to a payment link or website to complete a purchase. Plan for that handoff explicitly.

Review rejections can be opaque. If a collection gets flagged, the rejection message isn't always specific enough to know what triggered it. Businesses selling in borderline categories sometimes get rejected on items that seem compliant. The appeals process works, but it adds time.

The Business App has practical limits at scale. Managing a large product catalog manually through the app gets unwieldy fast. If you're running hundreds of SKUs across multiple collections, the API-connected Commerce Manager workflow is more sustainable. It supports bulk uploads via data feed and filter-based collection rules that don't require manual curation every time inventory changes.

Customers on older WhatsApp versions may not see collections. Collection navigation depends on the WhatsApp app version the customer is running. Most users on reasonably recent versions (last two years) are fine. This is rarely a significant issue, but it's worth knowing if you're targeting markets with lower update rates.


What Good Looks Like in Practice

Collections work when they're set up as a discovery tool, not a filing system. The brands that get mileage out of them are the ones that ask: given where this customer is in the conversation, what's the right collection to put in front of them?

A well-run catalog setup looks roughly like this: permanent intent-based collections for browse, campaign collections built and retired with each campaign cycle, and automation flows that surface the right collection based on what the customer asked. Someone who messages "I need something for gifting" sees a gift-set collection in the chat within seconds, without a human touching it.

If you're starting from zero, get three or four core collections live first. Keep the names simple. Link them into one basic chatbot flow so they get used in actual conversations, not just as passive browse content. That setup alone changes what WhatsApp feels like as a sales channel.


FAQ

What is a WhatsApp collection?

A WhatsApp collection is a named grouping of products inside your WhatsApp catalog. It works like a category page inside your storefront, letting customers browse a curated set of products instead of scrolling through your entire catalog. Collections appear in the WhatsApp Business app catalog view and can also be sent directly in conversations as browsable product cards.

How many collections can I create on WhatsApp?

WhatsApp doesn't publish a hard cap on collection count, but practical limits apply. Too many collections fragment the catalog and make navigation harder, not easier. Most businesses with catalogs under 300 products run well with 5 to 8 collections. Larger catalogs using the API can create more with filter-based product sets in Commerce Manager.

How long does WhatsApp collection review take?

New collections typically go through review within 24 hours. The review checks that collection content complies with WhatsApp's commerce policy. Rejections can happen if products in the collection fall into restricted categories or if the collection name doesn't match the products listed inside it.

Can one product appear in multiple WhatsApp collections?

Yes. A single product can be added to as many collections as relevant. This is useful when products fit more than one category, for example, a moisturizer that belongs in "Oily Skin" and "Bestsellers" at the same time.

How do I share a specific collection in a WhatsApp conversation?

On the WhatsApp Business App, open a chat, tap the attachment icon, select Catalog, navigate to Collections, and send the relevant collection. On the API level, you send a multi-product message that references a product set, which can be triggered from a chatbot flow based on customer intent.

Should I set up collections before launching my catalog?

It's fine to launch the catalog first with products listed, then layer in collections once you have a clear picture of how customers are browsing. For very small catalogs (under 20 products), collections may not add much. For anything above 30 products, collections are worth setting up before customers start asking "which one is right for me."

When should I avoid automating collection delivery and handle it manually?

When a customer's question is genuinely complex or ambiguous. If someone asks "I have sensitive skin and I'm also pregnant, what's safe?", the right response is a human with knowledge, not a product card. Automate collection delivery for clear-intent queries. Keep humans in the loop for nuanced, high-stakes conversations where the wrong recommendation creates a real problem.

Can I use WhatsApp collections if I'm on the free Business App (not the API)?

Yes. Collections are available on both the WhatsApp Business App and the API. The Business App version requires manual product selection and management. The API version supports filter-based rules, automated catalog sync from your store, and multi-product messages in chatbot flows. For most small sellers, the Business App setup is sufficient to start.

Get started today

Your store on autopilot.
Starting this week.

Join brands automating discovery, cart recovery, and support with Fufa AI — and watch revenue compound while you sleep.

No credit card requiredLive in under 48 hoursCancel anytime