How to Showcase Multi-SKU Products Effectively on WhatsApp

When a customer asks "how many colors does this come in?" you've already lost. The goal of how to showcase multi-SKU products effectively on WhatsApp isn't to scroll through your entire camera roll — it's to let the customer understand the spec differences on their own. Below, we break down images, videos, and Catalog: what each is good for, how to send them, and how to string them into a follow-up chain.

When a customer asks "how many colors does this come in?" you've already lost

Typical scene: the customer sends one line — "how many colors/sizes does this come in?" — and the salesperson starts digging through the album, finding images, sending them one by one. A single conversation goes back and forth 5-8 messages, the customer waits 3+ minutes, and drop-off rises noticeably. The problem isn't that you're lazy; it's that you've turned "spec explanation" into "live customer service."

For multi-SKU products, the communication cost concentrates on three questions: what specs exist, how they differ, and what the price/MOQ is for each. If a salesperson has to type out answers every time, one customer asking three times already burns half an hour.

First, identify which category you're stuck in:

• Can't send everything: images are scattered across albums and chat history. Customer asks about color A, you only find color B.
• Can't explain clearly: spec differences rely on text, like "the large is 5 cm taller than the small." Without a reference point, the customer still isn't sure.
• Can't match up: the customer can't remember which spec goes with which image, screenshots it back asking "how much is this?" and even you have to dig around.

These three problems map to three presentation formats. Let's break them down one by one.

Images, videos, Catalog: what each solves — don't mix them up

Images are for "single-spec detail confirmation": color, material, packaging. The downside: once specs multiply, the album becomes a mess and the customer can't find the key point. Send 12 images and the customer flips between #7 and #9, then just asks "can you tell me which one is blue?"

Videos are for "dynamic difference display": size comparison, function demos, usage scenarios. The downside: customers on WhatsApp often lack patience to watch to the end, and can't quickly locate a specific spec. A 2-minute video might get only the first 5 seconds of attention.

Catalog is for "spec overview and quick jumps": the customer opens it and sees all SKUs. But WhatsApp's native Catalog has limited support for multi-level specs; complex specs still need images/videos to supplement.

Decision principle: first ask what decision stage the customer is in.

1. Initial understanding: use Catalog to build the big picture — let them know how many specs you offer.
2. Comparison stage: use images for side-by-side specs, putting differences in one image.
3. Confirmation stage: use short videos to remove the last doubt, e.g., real footage of the product in use.

Don't send 10 videos the moment a customer adds you, and don't send only a Catalog link when they're already asking for a quote.

How to send images without flooding the chat: a reusable "spec card set" structure

Turn each SKU into a "spec card image": same angle, same background, labeled with a spec code (like A1/A2/B1) so the customer can match instantly. Say you sell canvas bags: A1 is off-white small, A2 is off-white large, B1 is black small. Print the code and dimensions right on the image — when the customer screenshots to ask for a price, you can reply in seconds.

Fix the sending order:

1. First send an overview image (all spec thumbnails in one), so the customer sees the whole picture.
2. Then send detail images in the order the customer asks, avoiding a 10-image flood.
3. Under each detail image, add one line: "A1 MOQ 100, A2 MOQ 50" — binding the image to the parameters.

Add text labels directly on images (color name, size, MOQ) to reduce the chance of "what color is the one on the left?" Labeled spec card sets typically cut down most "what color is this" questions.

Don't make videos into ads: 30 seconds to explain one spec difference

The goal of a video isn't to look good — it's to answer "what exactly is the difference between this spec and that one?" For example, show two sizes held side by side, or switch between colors of the same product.

Keep it 15-30 seconds. In the first 3 seconds, state the conclusion ("this is the difference between large and small"). No intro animation. Customers are on vertical screens, possibly muted, possibly on the subway. If the first 3 seconds don't grab them, the rest is wasted.

After the video, immediately follow with a text summary: "In the video, left is spec A, right is spec B. A MOQ 100, B MOQ 50." This lets the customer remember without rewatching. It also turns "watching" into "a multiple-choice question they can reply to" — they can just say "I'll take A."

A reusable 30-second script structure:

• 0-3s: conclusion first, state the difference directly.
• 3-15s: side-by-side display, finger pointing at key parts.
• 15-25s: switch to usage scenario or packaging.
• 25-30s: back to static, voiceover MOQ and lead time.

The right way to use WhatsApp Catalog: turn SKUs into a menu customers can check themselves

Catalog works as a "spec entry point": each SKU gets a main image + short description (with key specs). Customers can tap in and see for themselves, no need for the salesperson to send one by one.

Catalog's limitation: the native version doesn't support complex spec matrices (like color × size). So write clearly in the description: "For more specs, reply A/B/C." Treat Catalog as an index, not the destination. If you have 6 colors and 3 sizes, put only the 3 main combinations in Catalog and guide the rest via reply codes.

Maintenance rhythm: update Catalog within 24 hours of a new launch, remove discontinued SKUs promptly to avoid trust erosion when customers see "discontinued." If a customer opens your Catalog and sees three products marked "temporarily unavailable," they probably won't ask about a fourth.

String the three formats into a follow-up chain: from "customer asks" to "customer looks"

Step 1: On first inquiry, send the Catalog link + one line: "Take a look at the overall specs and tell me the codes you're interested in." Hand the initiative to the customer, reducing one-by-one replies.

Step 2: Once the customer names a code, send the corresponding spec card set + short video, with a line: "MOQ and lead time for this spec are XX" — pushing directly toward a quote.

Step 3: If the customer doesn't reply within 2 hours, don't just ask "how's it going?" Send a real photo or new video of that spec to reactivate the conversation visually.

Tool support: A Chrome extension like Sellenca that overlays on WhatsApp Web can draft spec replies based on your product knowledge base, which the salesperson confirms before sending — cutting down time spent digging through albums and checking parameters. It also segments customer profiles by intent and stage, helping you decide whether to send Catalog or video. It doesn't change your number, doesn't migrate to Business API, and requires zero change in sales habits. You can see the feature details here. The cost is transparent: $19/seat/month, $190/seat annually, with a 7-day full-feature free trial — good for a small-scale test first.

Common pitfalls in multi-SKU display: the more you send, the more confused they get

Pitfall 1: Sending 20 images at once. Slow loading on mobile, hard to locate, result: "I'll think about it" and they disappear.

Pitfall 2: Images without consistent naming/labeling. Customer screenshots asking "how much is this?" and even the salesperson can't tell which one it is.

Pitfall 3: Videos without subtitles or text summary. Customers in noisy environments or on mute skip right past.

Avoidance principle: push only 1-3 specs at a time, always follow with a text summary, and turn "watching" into "a replyable multiple-choice question." For example, "Do you want A1 or A2? A1 MOQ 100, A2 MOQ 50" works far better than "see which one suits you."

Want to see how this works in practice? Book a demo and we'll run through the spec display flow with your product catalog.

FAQ

Can WhatsApp Catalog display multi-SKU products?

It can display SKUs, but has limited support for complex spec matrices like color × size. Treat Catalog as a spec entry point: put main combinations in, guide other specs via description reply codes, and supplement with images or videos.

Customers keep going back and forth on color and size. How to reduce this?

Make labeled spec card images, push only 1-3 at a time, and follow with a text summary. The key is turning "asking" into "choosing" — ask "do you want A1 or A2" instead of open-ended "which one do you want to see?"

Images or videos — which is better for multi-SKU products?

Depends on the decision stage. Use Catalog for initial understanding, images for side-by-side comparison, and 15-30 second videos for final confirmation. Don't send a long video when they just asked for a price, and don't send only a Catalog link when they're ready to confirm.

Is there a tool to automatically organize multi-SKU replies?

Look at AI sales platforms that overlay on WhatsApp Web, like Sellenca. It drafts spec replies based on your company's own product knowledge base, which the salesperson confirms before sending, and automatically builds and segments customer profiles. Specific features and pricing are on the pricing page, or book a demo to see it in action.

Multi-SKU WhatsApp display is essentially turning "sales memory" into "a menu customers can check." First string Catalog, spec card sets, and short videos into a follow-up chain, then consider tools to automate repetitive spec replies. To calculate the cost for your team, start with pricing, or book a demo to run through your products.