Vardast

WhatsApp Catalog Selling: Build One That Takes Orders

Category: Guides & Tools
WhatsApp Catalog Selling: Build One That Takes Orders

Most WhatsApp catalogs are half-built photo albums. Here is how to set one up so it answers questions, takes orders, and keeps selling while you sleep.

A seller I watched a while back had eleven photos of the same coat sitting in one WhatsApp thread. Not eleven coats. Eleven photos of the same coat, sent one after another at eleven at night, each with a caption typed by hand.

The customer wrote back: the third one, how much?

She scrolled up, counted, guessed wrong, and sent the price of a different item. Two messages later she corrected herself. The customer said she would think about it, which in chat language usually means goodbye.

That exchange is exactly what a catalog exists to prevent. And yet most of the catalogs I open are half-built: nine products, no prices, descriptions that say DM for details. Selling with a WhatsApp catalog is not about having one. It is about building one that can carry a conversation while you are asleep.

A catalog is a shelf, not a photo album

The mental shift is small but it changes everything. A photo album asks the buyer to imagine. A shelf lets them point.

When a product lives in your catalog, the customer taps it and the chat gets a card: image, name, price. Now they are not asking which one. They are asking when can I have it. Those are two completely different conversations, and only one of them ends in an order.

Every item needs four things filled in properly:

  • One clean photo on a plain background. The lifestyle shot belongs in your feed, not in the catalog card.
  • A name a human would actually say out loud.
  • A real price. Not zero, not 1, not a placeholder you meant to fix.
  • A description that answers the next question before it gets asked.

Skip any of the four and you have rebuilt the photo album with extra steps.

Name products the way customers say them

Internal codes are the quietest sales killer in any catalog. Model 402-B means something to you and nothing to the person holding the phone. She is going to type the cream oversized coat, because that is what she sees.

So name it that: Cream oversized wool coat. Put the color and the defining feature in the name. If you sell forty items, this alone cuts a real number of back-and-forth messages, because both a human search and an assistant looking things up rely on the same words the buyer already used.

One rule I would defend: never put the price inside the product image. Prices change. Images get cached, forwarded, screenshotted, and shown back to you three months later by a customer who wants that price honored.

The description field is the part everyone skips

This is where your best sales rep lives, and most sellers leave it blank or paste one adjective.

Open your last hundred chats and write down the questions people asked after seeing a product. It is never mysterious. Material. Sizes. Does it run small. How long does delivery take. Is it washable. Then put those answers in the description.

Something like this works far better than high quality, limited stock:

Wool blend, unlined. Sizes S to XL, fits one size loose. Model is 168cm wearing M. Ships in 2 to 3 working days. Dry clean only. Exchange within 7 days if unworn.

Four lines. They kill maybe six future messages per buyer. If you want the full list of what to preempt, the same pattern shows up in the twenty repeat questions that eat a seller day — the catalog description is where most of them should have been answered in the first place.

Selling from a catalog is still a conversation

Sending someone a catalog link is not selling. It is handing them a menu and walking away from the table.

The order still has to be taken, and taken in a specific order, or you end up with a paid order and no address:

  1. Confirm the exact item by sending the product card back, not by describing it in words.
  2. Lock the variant — size, color, quantity. One message, one question.
  3. Confirm stock before you ask for money. Always this way round.
  4. Quote the full total, shipping included. Surprise shipping costs are where carts die.
  5. Collect the address as one block, and read it back.
  6. Send payment details, then confirm receipt in the same thread.
  7. Send a summary message: item, size, total, delivery window. This message prevents most disputes.

That sequence is boring, which is the point. Boring is repeatable, and repeatable is what you can hand to someone else, or to software.

The three questions that decide the order

Watch enough chats and the pattern gets almost dull: is it in stock in my size, when does it arrive, and how do I pay. Answer all three inside two minutes and you close. Leave one hanging and the buyer goes quiet, usually forever, and you never find out which of the three it was.

We have written about the shape of this before in the three unanswered questions that quietly kill sales, and catalogs are the cheapest place to fix it. Stock and price live on the card. Delivery time lives in the description. Payment lives in one saved message you can send in a second.

An assistant that knows your catalog beats one that knows a script

Here is where most automation disappoints people. A keyword bot matches price and fires a canned reply. Then a customer writes hey does the cream one come in 42, and can you send it before Thursday, and the bot answers with a greeting.

An assistant that has actually read your catalog handles that differently. It knows the cream coat exists, knows which sizes are listed, knows the delivery window in the description, and can answer both halves of the question in one message. When the size is gone, it can offer the two closest items instead of dead-ending the chat. When something is genuinely outside what it knows — a custom order, a complaint, a wholesale request — it should hand the thread to you with the history intact, not improvise.

That is the real test I would apply to any tool: does it answer from your products, or from a rulebook you have to maintain? Rulebooks rot. Product knowledge updates itself when you update the product.

What quietly breaks a catalog

  • Stale stock. Selling something you do not have costs more trust than the sale was worth.
  • Variants collapsed into one item. If three colors sell as one entry, expect wrong-color returns.
  • Two hundred products with no order. Nobody scrolls two hundred cards. Feature your top sellers, archive the rest.
  • Prices only in the images. Covered above, still happening everywhere.
  • A catalog nobody links to. Put it in your bio, your away message, your first reply.

Twenty minutes a week keeps it alive

Set a recurring slot. It takes less time than the messages a broken catalog generates.

  1. Check stock on your top ten items only. The tail can wait.
  2. Read last week's chats and copy any repeated question into the relevant description.
  3. Hide anything you cannot ship this week.
  4. Fix one bad product name and one missing price.

If your volume has grown past what one phone can hold, that is a different conversation about tooling, and when to move to the WhatsApp Business API is worth reading before you buy anything.

The version of this that works while you sleep

A good catalog answers the easy half of every conversation. Something still has to answer the other half at 1am, on a holiday, and during the twenty minutes you spend packing orders.

That is the job Vardast was built for: it connects to your WhatsApp, Instagram, Telegram and website, learns your products and your tone, answers buyers in seconds from what you actually sell, takes the order step by step, and passes the thread to you the moment a human is genuinely needed. You keep the shelf tidy. It keeps the conversation moving.

Build the catalog properly first, though. Automation on top of a half-filled catalog just repeats your gaps faster.

Frequently Asked Questions About WhatsApp Catalog Selling

Do I need the WhatsApp Business API to sell from a catalog?

No. The catalog is built into the free WhatsApp Business app and works fine for most small and mid-size sellers. The API matters when you need several agents in one inbox, higher message volume, or deeper integration with your store systems.

How many products should I put in my WhatsApp catalog?

Fewer than you think. Most sellers do better with 20 to 40 well-described items than with 200 half-filled ones. List what you can actually ship this month and archive the rest, since buyers rarely scroll past the first screen.

Can customers pay directly inside WhatsApp?

It depends on your country, since in-chat payment is only available in some markets. Everywhere else you send a payment link or bank details in the thread and confirm receipt there, which is why a clear order summary message matters so much.

What should I do when a catalog item goes out of stock?

Hide it the same day rather than leaving it visible. If someone asks for it anyway, reply with the two closest alternatives instead of a simple no, because an offered substitute recovers a meaningful share of those chats.

Can an AI assistant take orders from my WhatsApp catalog?

Yes, if it reads your actual product data rather than following keyword rules. A catalog-aware assistant can confirm the item, check the listed variants, quote the total with shipping, collect the address, and hand the chat to you when the request goes beyond what it knows.

Is a catalog worth building if I mostly sell on Instagram?

Yes, because plenty of Instagram buyers move to WhatsApp to finish the order. A catalog gives that second conversation a structure, so the sale does not depend on you scrolling back through photos to find a price.