WhatsApp Catalog: How to Create, Manage, and Share It

A WhatsApp catalog works as a mini storefront on your business profile and inside chats. Customers get in-app browsing of your range, with images, prices and descriptions, without a website redirect.

Complete the required fields shown for your account and market. Kanal's Shopify guide lists a unique product title and at least one image; provide a country of origin where required. MyKatalog adds a price, product description and product link.

In conversational commerce or social commerce terms, a customer can browse, ask a question and start an order in one thread. Eligible businesses can list permitted products or services, subject to applicable commerce policies.

These routes fit different teams. Compare them on who manages the catalog, where products are edited and what volume you need, using current documentation from Meta.

Confirm Platform capabilities by provider and market before you plan around them. WASenderPlus sits outside both catalogs: it sends your link and collects your replies. Check WASenderPlus's current documentation for its connection method, because requirements and limits differ by route.

Open the WhatsApp Business app, go to your business tools and choose the catalog option. Menu labels change between versions, so follow the current in-app wording. You need no coding skills.

Add each item and complete the fields shown, such as photo, name, price, description and link. Use a descriptive, unique title, so agents can name the right product when a customer asks in chat.

This manual setup suits a modest range, as MyKatalog notes. Check current linked-device access if several people help. Once your range changes often, retyping products by hand becomes the job you need to replace.

Larger teams often manage products in Meta Commerce Manager, inside their business portfolio and Meta Business Suite. Create a new catalog there using Meta's current instructions, because menu names and paths can change.

Next, connect your catalog to WhatsApp by linking it to your WhatsApp Business Account (WABA). Do this in your WhatsApp settings or through your provider. Confirm who holds admin access on the portfolio before you start.

MyKatalog notes the same catalog can also power Instagram and Facebook shopping or ads. If your team already runs those channels, one catalog gives everyone one list to correct.

You do not need an online store. Commerce Manager accepts bulk upload through a spreadsheet or a data feed, according to MyKatalog. You can skip adding products individually.

Start from the sheet your team already keeps, then map it to Meta's current feed template, including required identifiers, accepted field names and supported values. Name a person to approve every change before upload.

Scheduled feeds suit ranges that change often, such as wholesale price lists. A short, stable service menu may need nothing more than a spreadsheet refresh before each campaign.

Kanal describes the Shopify path: use the Facebook and Instagram sales channel to sync products to a Meta catalog. Then connect that catalog to WhatsApp. Your store stays the source of truth.

Unifonic names Magento, Salla and Zid alongside Shopify as central commerce systems. It warns about inventory desync, outdated inventory and pricing discrepancies from manual updates. Check those risks against your own data.

WASenderPlus does not sync products. It sends a link to whatever your catalog currently shows. Run your e-commerce sync check first, and confirm real-time pricing and promotions have landed.

Run this check before every send, and name an owner for each line. A link to a stale catalog hands your agents a queue of corrections to explain.

• Open the link on a phone and view it as a customer.
• Compare prices and promotions with your source of truth.
• Hide or remove out-of-stock items.
• Look for any product rejected in Commerce Manager.
• Confirm the link opens the intended catalog.

Give fixes a deadline ahead of the send slot. If an item is rejected, read the stated reason first, since the answer depends on the product and Meta's commerce policies.

The simplest route is a catalog link. Paste it into a chat, a broadcast or your website. Catalog access depends on the customer's WhatsApp client and supported experience, so test your link on mobile and desktop.

Customers can also forward your catalog or items to friends, which Kommo lists as a benefit. On the WhatsApp Business Platform, providers offer product messages and interactive product views through a catalog API in supported contexts.

WASenderPlus uses the link route. Your broadcast carries a catalog or product link as text. You can share any catalog that gives you a link, whichever tool built it.

Split the job by owner. Marketing chooses the segment from your sheet, such as past buyers of a product line. It then writes the message around the catalog link.

Operations checks the catalog and removes opted-out contacts. Someone then starts the paced queue from the Google Sheets add-on or Chrome extension. Pick a time when your agents are on shift.

Every reply returns to your shared team inbox, where agents handle follow-up questions. Use targeted catalog sharing for product launches, seasonal campaigns and back-in-stock alerts, not a whole-list send each time.

WASenderPlus defaults to 4–40 seconds between sends and a 250 daily cap on a fresh number. These are WASenderPlus operational settings, not WhatsApp-published limits or guarantees.

At the 4-second end, 250 sends take about 17 minutes. At the 40-second end, they take about 2 hours 47 minutes. These are theoretical estimates based on the configured interval, assuming continuous sending.

On a warm number, the cap is 6,000 sends a day. That theoretically takes 6 hours 40 minutes at the shortest gap and 66 hours 40 minutes at the longest. Actual throughput depends on active hours, interruptions and restrictions.

WASenderPlus defaults to a warm-up period of 2 weeks for a new number. Start that period with recent contacts who gave clear consent, and keep your first catalog sends small.

Use early sends to learn your reply workload. Note which catalog items draw questions, how long answers take and which agent covers which product line.

Raise volume only when your inbox clears each day. This is WASenderPlus's operational onboarding schedule, not a WhatsApp-approved warm-up method or protection against restrictions. WhatsApp's own terms still apply to your number.

A shared number means several people can see each customer. Before you send, write a rule to assign leads. Split them by product line, by region or by whoever opened the thread first.

Agents need a habit for collision avoidance during high chat volume. Check the chat history before answering, and reference the item name instead of retyping descriptions. Tell the next colleague when you hand over.

If you run automated replies or an AI agent in another tool, set a clear human agent handoff. Send price disputes, custom orders and complaints to a person.

On the WhatsApp Business Platform, approved message templates generally start conversations, and free-form replies depend on Meta's current service-window rules. LINK Mobility lists three template categories: marketing, utility and authentication, each matched to message content.

A catalog message promoting products reads as marketing. LINK Mobility warns that a mismatched template may be rejected, approved under another category or updated later. Choose the category by content, not by preferred price.

Sample marketing copy: "Hi [name], our new season range is in. Browse the catalog here: [link]." A utility label on that text is a mismatch. Check template review rules in your provider's current documentation.

Separate the bills. WASenderPlus plans cost $6/mo on Entry or $19/mo on Team. WhatsApp Business Platform charges, if you also use that route, come through Meta and your provider.

Applicable charges depend on Meta's current pricing rules, market and category, and eligibility for free messaging. Its pricing page describes charging per message, when delivered, not sent, for applicable messages, with volume tiers for some categories.

Build your model as a formula: expected billable marketing messages × the current rate for each market. Add any monthly fee from your provider. Pull rates from Meta's published table on the day you plan.

Zoho Commerce describes a full path: customers browse, add to cart and place orders. Then cart orders flow into its system for fulfillment. That direct order capture runs on its own stack.

In supported contexts, customers can send the full order in one message from the cart. Without a commerce integration, that order reaches your team as a chat. Your agent confirms stock and records it in your sheet.

For cash on delivery (COD), add a COD confirmation step before dispatch. Zoko sells this as an automation. A smaller team can run the same step by hand from the inbox.

In-chat payments availability varies by country and integration. Check Meta's current documentation for your US account rather than assuming WhatsApp Pay covers your market.

Where in-chat payment is unavailable, send a checkout link, or confirm the payment method in chat and direct the customer to your approved payment process. Confirm the order total in the thread first.

Decide your payment path before you broadcast. Treat cart submission, order confirmation and payment as separate steps. Give agents approved wording for each option, such as card link, bank transfer or COD.

Some platforms, including Zoko, pair catalogs with abandoned checkout recovery and retargeting. Those features read store events. WASenderPlus works from your sheet, so your follow-ups depend on what your team exports.

To run a manual abandoned cart reminder, export contacts who left a cart and who consented to marketing. Send the product link rather than the full catalog, and keep the message to that item.

Apply the same process to back-in-stock alerts: keep a column for who asked about each item. LINK Mobility lists these alerts among common template uses on the Platform route.

Kommo lists agencies, clinics and salons showcasing packages, plus restaurants sharing menus. List each package as an item, with a starting price where one exists and a description of what it includes.

Choose booking, checkout or a consultation workflow according to the service. Use the description to set the next step, such as "reply with your preferred day". Then have an agent confirm the booking follow-up in the thread.

Clinics should keep health details out of broadcasts and catalog text. Send general service information only, and do not move patient information into this tool unless your organization has approved the workflow, safeguards and applicable contractual arrangements.

Zoho Commerce offers a WhatsApp Orders report for catalog-driven orders on its own stores. If your orders live elsewhere, build a similar view in your sheet with campaign, contact, reply, agent and order value columns.

Fill those columns after each send. You can then total revenue per campaign and per team member. Compare channel performance using your own conversions rather than a vendor's.

Track replies that never become orders, too. Repeated follow-up questions about an item can point to a missing detail in its catalog description.

Use a product link when you promote a single item. Use a catalog when customers need to browse a range, and your team can answer questions in chat.

Remember the limits. MyKatalog says the catalog does not appear in search engines, so do not rely on it as a search-indexable storefront. A web catalog sending orders to WhatsApp can serve visitors arriving from Google.

A full online store fits when you need checkout and payments on your own site. You can also run both: a store as your source of truth, and a catalog for conversations.

Start with the editing. Use clear product images, and write titles in your customers' words. Put size, material or duration in the description, so the detail is there before anyone asks.

Review these common catalog mistakes before each campaign. Watch for duplicate titles, missing required details and stale promotions left after a sale ends. Also avoid sharing a link before the catalog is complete.

Keep your range easy to navigate in chat. Agents have to find items quickly, so remove discontinued products and use a consistent naming pattern across catalog items.

Vendor blogs publish high percentages for catalog engagement and campaign conversion. The pages reviewed for this guide gave no sample, market or method alongside them, so this page does not repeat them.

Separate the evidence. Meta-documented rules, such as pricing mechanics, can be checked on Meta's pages. Claims about ROI, engagement and brand trust stay marketing until the vendor shows how it measured them.

Run your own test instead. Send to a small consented segment, log replies and orders in your sheet, and judge the catalog on your own numbers.

Compare on fit. Zoko positions itself around Shopify brands, with catalog sync and AI agents. Unifonic pitches enterprise CX with e-commerce sync. Zoho Commerce ties catalogs to its own stores.

Kommo places catalog inquiries in a unified inbox. Capabilities change, so read each vendor's current documentation. Ask who owns the number, where the list lives and what volume you expect.

WASenderPlus fits when your list lives in Google Sheets and your team shares a number. It sends a catalog link through a paced queue. Look elsewhere if you need native catalog sync or automatic cart capture.