How to Structure a WhatsApp Product Catalog Message

Dumping dozens of product photos at once usually gets you ignored. The client won't tap through every image; they'll swipe away. The fix is to break your catalog into structured messages of 3-4 products per group, each message solving one decision. Below are grouping methods, message skeletons, and image ordering rules you can apply directly. In short, how to structure a WhatsApp product catalog message is about giving reps leverage, not replacing them.

Why Do Clients Disappear When You Send 20+ Photos?

When 20+ unread messages hit a client's notification bar, the first reaction is to swipe past, not open each one. This isn't impatience; it's that your message structure transfers the decision cost to them.

Three specific problems:

Information overload: 20 images mean the client has to scroll, compare, and remember on their own. A phone screen shows only 3-4 thumbnails at a time, so images after that are basically unsent.

Missing context: The client doesn't know which image matches their need. For the same product, a wholesaler cares about MOQ and tiered pricing, while a retail buyer cares about unit price and drop-shipping. Send the same group to both, and neither feels it's relevant.

Decision cost shifted: Putting the filtering and matching burden on the client means making them do your sales work. They added you to find products, not to build a spreadsheet.

A common contrast: Salesperson A adds a client and immediately sends 25 product photos. The client replies "I'll take a look" and goes silent. Salesperson B sends only 4 products with one line: "The waterproof models you asked about are these 3." The client replies directly: "How much for the second one?" The difference isn't the product; it's the message structure.

Three Types of Catalog Messages: Icebreaker, Follow-up, Closing

A catalog message isn't one thing; it's three. Using the wrong type is worse than not sending at all.

Icebreaker catalog: The client just added you or sent a one-liner like "What products do you make?" Send only 3-5 best-sellers or items matching their inquiry keywords, with a line like "This is the category you asked about." The goal is to confirm direction, not show your entire inventory.

Follow-up catalog: Based on what the client previously asked about, send the same series or upgraded versions, each with a one-sentence core selling point. For example, if they asked about a LED strip last week, send three brightness levels from the same series, each with one line explaining the difference. The goal is to advance their choice, not reintroduce your company.

Closing catalog: The client has narrowed down to 1-2 items. Send only specs, price, MOQ, and lead time. Images are secondary; text is primary. At this stage, they want to confirm parameters, not see pretty pictures again.

Choosing is simple: if the client hasn't clarified their need, use icebreaker; if they've asked about specific models, use follow-up; if they're asking about price and lead time, use closing.

Group by Scenario: Turn Your Catalog into a "Solutions Menu"

Regroup products by usage scenario so clients can self-identify.

Group by usage scenario: For example, "Outdoor Waterproof Series," "Custom Gift Series," "Hotel Bulk Purchase Series," with 3-4 items per group. When a client sees "Outdoor Waterproof," they immediately know if it's relevant, without opening each image.

Group by client type: Wholesale clients look at MOQ and tiered pricing; retail clients look at unit price and shipping speed. For the same product, write "MOQ 500, three tiers: 500/1000/3000" for wholesalers, and "Single unit available, ships in 3 days" for retailers.

Add a one-line scenario note per group: For example, "If you're supplying chain hotels, this group meets fire safety standards." This lets clients claim the group themselves instead of you guessing for them.

In practice, a hardware accessories team compressed 80+ SKUs into 6 scenario groups of 4 items each. Average client reply time went from "read and no response" to "Is the second item in group 3 in stock?" Grouping doesn't reduce information; it adds an index to it.

After grouping, the real challenge is remembering which scenario and stage each client belongs to. Manually maintaining a spreadsheet gets messy after 50 clients. Sellenca's automatic client profiling and six-dimension segmentation (region/intent/client type/value/relationship/stage) solves this step: once profiles are built, you don't rely on memory to decide which catalog to send. You can see the specific dimensions on the features page.

The Skeleton of a Catalog Message: Title, Scenario, Items, Call to Action

Every catalog message has four fixed parts. Miss one, and the client asks an extra question.

Title: Use the client's own words or inquiry keywords, like "The waterproof LED strip you asked about." Don't write "New Arrivals" or "Best Sellers"—that's your language, not theirs.

Scenario: One line explaining who this group is for and where it's used. For example, "This group is for outdoor signage, IP65 waterproof."

Items: One line per product, uniform format: "Model + core difference + price range + MOQ." For example:

• Model A12: Single color, constant light, $2.8-3.5/m, MOQ 100m
• Model A15: Adjustable color temperature, $3.6-4.2/m, MOQ 100m
• Model A20: RGB remote control, $5.1-5.8/m, MOQ 50m

Uniform format matters more than more information. Clients can scan and compare horizontally without hunting for common ground across three different description styles.

Call to action: End with one action only, like "Reply with number 2 and I'll send the detailed spec sheet." Don't ask "Which one do you want? How many? Which country?"—three questions stacked means they answer none.

Image Ordering: Sequence, Naming, and Quantity Control

Three controllable variables for images.

Sequence: Send one scenario or collection image as the cover first, then individual product images. The cover helps clients recognize the group from the thumbnail in their chat list, so they don't get lost after opening. The order of product images should match the text items: the image for product number 2 goes second.

Naming: Use model or scenario words in filenames, like A15-outdoor-waterproof.jpg, not IMG_2043.jpg. Clients can search for it after saving, and later you can say "the A15 image I sent" to reduce back-and-forth.

Quantity: No more than 6 images per catalog message. If more, split into two messages with a 10-15 second gap. Splitting lets clients process the first message and still see the second, instead of being overwhelmed. The number 6 comes from phone screen browsing rhythm; beyond that, completion rates drop noticeably.

Use Client Profiles to Decide What to Send: Segmentation in Practice

The same catalog should have different versions for different clients.

By intent: High-intent clients get the closing catalog with specs and prices directly; low-intent clients get the icebreaker catalog with direction and scenarios only. Sending a detailed quote to a low-intent client wastes your negotiation room early.

By stage: Inquiry stage gets scenario groups to help confirm needs; comparison stage gets a price comparison table highlighting differences; negotiation stage gets real sample photos to build trust. Wrong stage judgment makes even the right content useless.

By region: Different markets prefer different colors, certifications, and packaging. European and American clients often ask about CE and RoHS; Middle Eastern clients about packaging and shipping marks; Southeast Asian clients care more about price tiers and mixed batches. Adjust catalog content accordingly—one set of images for the whole world doesn't work.

Multilingual Catalogs: Translation Is Not Word-for-Word Replacement, It's Reordering

Translating catalog messages word-for-word causes problems because reading order differs by market.

Spanish-speaking clients tend to look at price and lead time first, while English-speaking clients often look at specs and certifications first. So reorder items: for Spanish clients, put price range and lead time first; for English clients, put specs and certifications first. Same product, two orderings.

When translating product names, keep model codes and translate only descriptions and scenario words. The model is your only anchor; translating it means clients can't match. For example, keep A15 as A15, and only translate "adjustable color temperature" into the target language.

Use fixed templates to reduce translation errors: scenario title, items, call to action—three parts, each within two lines. Shorter templates mean smaller translation deviations.

Doing multilingual reply templates and knowledge base management manually gets exhausting. Sellenca supports Chinese/English/Spanish translation and replies, drafting from your company's own product knowledge base, with sales confirming before sending. Pricing is $19/seat/month, or $190/seat annually. You can compare plans on the pricing page.

FAQ

How many images should I send in one WhatsApp product catalog message?

No more than 6 per message. If more, split into two messages with a 10-15 second gap. The cover image counts, and the cover should be a scenario or collection image, not a single product shot.

A client read my catalog message but didn't reply. How long should I wait to follow up?

Don't chase the same day. Wait 24 hours and send a message with new information, like "One more thing you might care about: this model supports custom packaging." Follow-ups should add value, not just ask "Did you see it?"

Is WhatsApp Business's built-in catalog enough?

The built-in catalog works for displaying a fixed SKU list, but it can't group by client scenario or adjust content by stage. If your client types are uniform and your product line is simple, it's enough. If your clients are clearly segmented, you still need to manually organize message structure in the chat.

How do I know which product in the catalog the client is interested in?

Look at the numbers they mention in replies and the conversation context after they open images. A more systematic approach is to record the catalog content you send and the models clients ask about afterward. After a few times, you'll see preference patterns.

The essence of organizing catalog messages is turning "clients find things themselves" into "you categorize for them." If you want to see how scenario-grouped catalog messages run in real conversations, book a demo to walk through the full flow.