🛠️ How-to tutorials

Using WhatsApp carousel templates to show product cards

Updated 2026-09-19 · 4 min read · By the Convo360 team

In short

A carousel template shows several swipeable cards, each with its own image, text and buttons, inside one WhatsApp message — built in WhatsApp Studio, submitted for Meta approval, and used in a flow or broadcast. Give each card's button a unique payload so a Condition step in your flow can tell which product the customer tapped and branch accordingly.

Key takeaways

Each carousel card needs its own image, short body text and one or two buttons.
Carousel templates need Meta approval, just like any other WhatsApp template.
Unique button payloads per card are what let your flow know which product was tapped.
Carousels suit a small catalogue — 3 to 6 cards read well; more becomes a lot of swiping.
The template's image quality matters more than usual since it's the first thing a customer sees.

What a carousel template is, and when to use one

A carousel is a single WhatsApp message that shows a set of swipeable cards, each with its own image, short body text and buttons: think of it as a compact product catalogue inside the chat. It's a good fit for showing 3–6 options at once: a jewellery collection, a set of room types at a hotel, or a shortlist of services, letting the customer tap through and choose rather than reading a long list of text.

It works especially well when the products themselves are visual, such as jewellery, food, room interiors and apparel, where a photo tells the customer more in a glance than a paragraph of description would.

It is less useful for a service business with nothing visual to show. A carousel of stock icons rarely outperforms a simple Buttons or List Menu step for that kind of choice.

Prerequisites

You need your WhatsApp Cloud API connected, product images ready in a consistent aspect ratio (mismatched image sizes make the carousel look untidy), and short body text for each card. WhatsApp templates have character limits, so plan concise copy before you start building.

Also decide the click-through goal for every card before designing them, whether Enquire, Add to cart or Book now, since the button text and the flow branch behind it should match exactly what you promised the customer.

The exact click path

Open WhatsApp Studio → Templates → New and choose the carousel template type.
Add each card: upload its image, write the body text, and add one or two buttons (e.g. 'View details', 'Enquire').
Give each card's button a distinct, meaningful payload value: this is what your flow reads back later.
Submit the template for Meta approval.

Order the cards deliberately too. Most customers only swipe through the first two or three, so lead with your best-selling or highest-margin option rather than an alphabetical or random order.

Worked example: branching on the tapped card

A jewellery store builds a 4-card carousel: Necklaces, Earrings, Bangles, Rings, each with an 'Enquire' button carrying a payload like category_necklaces. In the flow builder, a Condition step checks which payload came back and routes to a category-specific message. Necklace enquiries go to one script with relevant price ranges, ring enquiries to another that asks about sizing. Without unique payloads, the flow would have no way to tell which card the customer actually tapped.

The same pattern works for any catalogue: a hotel using cards for Deluxe, Suite and Family rooms, or a restaurant using cards for its top dishes, each routing to its own price and availability message once tapped.

Keep the follow-up message after a tap specific to that card too. A generic 'thanks for your interest' reply undoes much of the value of letting the customer choose a specific item in the first place. If the Necklaces card was tapped, the reply should talk about necklaces, ideally with a price range and a next step like sharing a catalogue link or booking a store visit.

A quick habit worth building: check the tap-through rate per card after the first week live, and drop or replace whichever card gets the fewest taps rather than leaving a weak option in the rotation indefinitely.

This small review habit keeps a catalogue carousel genuinely useful over time, rather than a one-off launch that slowly drifts out of date.

Catalogue ideas across a few industries

A jewellery store can run one carousel per collection (bridal, daily-wear, gifting) rather than mixing categories in one set of cards. A hotel can show room types with rate and view details on tap. A restaurant can showcase its top dishes with an Order button that drops straight into an ordering flow. In each case the pattern is the same: a handful of visual options, one clear button per card, and a flow branch keyed off which button was tapped.

Troubleshooting

Symptom	Likely fix
Template rejected by Meta	Usually an image issue (wrong ratio, watermark, or content policy). Check Meta's rejection reason in WhatsApp Studio and re-submit.
Cards look inconsistent	Standardise all images to the same aspect ratio before uploading.
Flow can't tell which card was tapped	Two cards share the same button payload; give each one a unique value.
Template stuck pending for a long time	Meta review can take longer for new template types; avoid resubmitting repeatedly, which can reset the queue position.
Carousel doesn't render for some customers	A small share of very old WhatsApp versions may fall back to plain text, so keep the body copy meaningful on its own.

What to test before going live, and cost

Send the approved template to your own number and swipe through every card.
Tap each card's button and confirm the flow branches to the right response.
Check the images look sharp and consistent, not stretched or cropped oddly.
Confirm the carousel still reads sensibly on a small phone screen, not just a tablet or desktop preview.

Meta's per-message fees apply as with any template message, billed directly at Meta's rate with no Convo360 markup.

Step by step

Prepare consistent card imagesStandardise image size and aspect ratio across all cards before uploading.
Build the carousel templateIn WhatsApp Studio → Templates → New, add each card's image, text and buttons.
Set unique button payloadsGive each card's button a distinct payload so your flow can identify which was tapped.
Submit for Meta approvalSend the template for review before using it in a flow or broadcast.
Branch on the tapped card in your flowAdd a Condition step that reads the button payload and routes accordingly.

Example conversation

Show me your best-selling sarees

Here are our top 4 this week — swipe through and tap 'View details' on any that catch your eye, or 'Buy now' to get a payment link instantly.

Create a carousel template

Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.

Start 14-day free trial →See pricing

Frequently asked questions

How many cards should a carousel have?

3 to 6 usually reads best. More becomes a lot of swiping and can dilute the customer's attention, so lead with your best-selling or highest-margin option first.

Do carousel templates need Meta approval?

Yes, exactly like any other WhatsApp template. Submit it in WhatsApp Studio and wait for approval before using it in a flow or a broadcast campaign.

How does my flow know which product card was tapped?

Give each card's button a unique payload value, then use a Condition step in your flow to branch based on which payload came back. Two cards sharing the same payload is the usual cause of a flow that can't tell them apart.

What image size should I use for carousel cards?

Use a consistent aspect ratio across every card in the same carousel, since mismatched sizes make it look untidy on a phone screen and can hurt the template's approval odds.

Can I use a carousel in a broadcast campaign?

Yes, once approved, use it the same way as any other template in a campaign or a flow's Send Template step, and Meta's per-message fee applies as it does for any template.