LandinChat — WhatsApp marketing softwareLandinChat
WhatsApp Templates Knowledge Base

WhatsApp product catalog single & multi-product templates

Send catalogs, single-product and multi-product messages with in-thread cart, checkout and Shopify / WooCommerce sync. Live in minutes.

  • Up to 30 products per message
  • Shopify / WooCommerce auto-sync
  • In-thread cart + checkout

Key things to know

  • Multi-product messages

    Up to 30 SKUs per send — perfect for new arrivals, bundles, or category browse.

  • Single-product CTA

    Hero SKU with image, price, and a 'View details' or 'Buy now' button.

  • Shopify / WooCommerce sync

    One-way catalog sync — images, price and stock stay current automatically.

  • In-thread cart

    Add-to-cart and checkout inside WhatsApp — no page redirect, no re-login.

People also ask

Q.What is a WhatsApp catalog message?

A native message type that lets you send up to 30 products inside WhatsApp — with images, price, description, and an Add-to-cart button. Customers can browse and check out without leaving the chat.

Q.Is a catalog message Marketing or Utility?

If sent inside the 24h Service window after the customer asks, it's free. If you initiate outbound (e.g. 'New collection live'), it's a Marketing template and requires opt-in.

Q.How many products can I list?

Up to 500 in your full catalog, and up to 30 per multi-product message. Single-product messages show one item with a CTA.

Q.Does it work with Shopify and WooCommerce?

Yes — LandinChat syncs your Shopify or WooCommerce catalog one-way to Meta Commerce Manager so product images, prices and stock stay in sync automatically.

Q.Can customers pay inside WhatsApp?

In India, yes — via WhatsApp Pay UPI. Elsewhere, the cart hands off to a hosted checkout (Stripe, Razorpay, Shopify) with the cart pre-filled.

Q.What lifts catalog message conversion?

High-quality square images (1:1), price in local currency, 2–3 product max for first message, and a follow-up Utility template within 24h for cart abandoners.

30
Products per message
500
Items per catalog
3x
vs link-out CTR
Free
Inside service window
Overview

Why catalog messages outperform link-out marketing

Catalog messages render natively inside WhatsApp — images, price, Add-to-cart — so customers never bounce to a slow mobile site. CTR is typically 3x a link-out and cart completion is 2x.

Use single-product messages for re-engagement (one hero SKU with a CTA), and multi-product for collections, bundles, or category browsing.

LandinChat syncs your Shopify or WooCommerce catalog to Meta Commerce Manager and hands off cart to Razorpay, Stripe, Shopify Checkout, or WhatsApp Pay (India).

Capabilities

Built for serious growth teams

Multi-product messages

Up to 30 SKUs per send — perfect for new arrivals, bundles, or category browse.

Single-product CTA

Hero SKU with image, price, and a 'View details' or 'Buy now' button.

Shopify / WooCommerce sync

One-way catalog sync — images, price and stock stay current automatically.

In-thread cart

Add-to-cart and checkout inside WhatsApp — no page redirect, no re-login.

WhatsApp Pay (India)

UPI checkout for Indian merchants — payment confirmation inside the same thread.

Abandoned cart auto-recovery

Trigger a Utility template 30 minutes after cart-add with a one-tap 'Resume cart' button.

How it works

Get live in days, not months

  1. 1

    Sync your catalog

    Connect Shopify, WooCommerce, or upload CSV to Meta Commerce Manager via LandinChat.

  2. 2

    Pick the template

    Choose single-product, multi-product, or full catalog from the LandinChat library.

  3. 3

    Personalise SKUs

    Map dynamic SKU IDs from segments (e.g. recently viewed, abandoned cart, last-purchased category).

  4. 4

    Wire checkout

    Connect Razorpay / Stripe / Shopify / WhatsApp Pay — cart hands off pre-filled.

  5. 5

    Schedule + A/B test

    Send to a 10% holdout, auto-promote winner by CTR or revenue per send.

Comparison

Catalog message vs link to product page

CapabilityLandinChatLink to product page
Click-through rate30–50%8–15%
Time to cart< 30s in-threadPage load + nav
Image qualityNative renderDepends on CDN
Cart abandonment recoverySame chat threadEmail retarget
Checkout frictionPre-filled cartRe-enter cart
Mobile bounce riskNone30%+ bounce
FAQ

Frequently asked questions

Deep dive

Why WhatsApp product catalog single & multi-product templates is the highest-leverage move for growth teams

WhatsApp is where growth teams customers actually reply. Open rates sit at 85–98% inside 15 minutes versus 18–22% on email and sub-2% on SMS, and the medium is conversational — a customer can ask a follow-up, share a photo, or pay without leaving the thread. That is the entire premise behind whatsapp product catalog single & multi-product templates: stop losing the conversation to slow channels and let intent convert while it is warm.

Most growth teams teams treat WhatsApp as a broadcast megaphone. The teams that win treat it as a workflow surface — every notification is also a decision point where the customer can act. The capabilities below are wired to do exactly that: each one collapses a multi-step off-platform detour into a single in-thread reply.

The impact numbers on this page — 30 products per message, 500 items per catalog, 3x vs link-out ctr, Free inside service window — are pulled from LandinChat customers running this workflow for at least 90 days. They are directional; your mileage depends on list quality, template approval speed, and how aggressively you route qualified conversations to a live agent.

Capability walkthrough

Each capability, in plain terms

Multi-product messages

Up to 30 SKUs per send — perfect for new arrivals, bundles, or category browse. In practice this means the growth teams operator running whatsapp product catalog single & multi-product templates does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.

Single-product CTA

Hero SKU with image, price, and a 'View details' or 'Buy now' button. In practice this means the growth teams operator running whatsapp product catalog single & multi-product templates does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.

Shopify / WooCommerce sync

One-way catalog sync — images, price and stock stay current automatically. In practice this means the growth teams operator running whatsapp product catalog single & multi-product templates does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.

In-thread cart

Add-to-cart and checkout inside WhatsApp — no page redirect, no re-login. In practice this means the growth teams operator running whatsapp product catalog single & multi-product templates does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.

WhatsApp Pay (India)

UPI checkout for Indian merchants — payment confirmation inside the same thread. In practice this means the growth teams operator running whatsapp product catalog single & multi-product templates does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.

Abandoned cart auto-recovery

Trigger a Utility template 30 minutes after cart-add with a one-tap 'Resume cart' button. In practice this means the growth teams operator running whatsapp product catalog single & multi-product templates does not need to compose the logic themselves; they pick the trigger, review the copy, and let LandinChat handle rate-limits, template compliance, and retry behaviour.

Implementation walkthrough

How this actually rolls out

  1. Step 1. Sync your catalog

    Connect Shopify, WooCommerce, or upload CSV to Meta Commerce Manager via LandinChat. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.

  2. Step 2. Pick the template

    Choose single-product, multi-product, or full catalog from the LandinChat library. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.

  3. Step 3. Personalise SKUs

    Map dynamic SKU IDs from segments (e.g. recently viewed, abandoned cart, last-purchased category). On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.

  4. Step 4. Wire checkout

    Connect Razorpay / Stripe / Shopify / WhatsApp Pay — cart hands off pre-filled. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.

  5. Step 5. Schedule + A/B test

    Send to a 10% holdout, auto-promote winner by CTR or revenue per send. On day one, an onboarding specialist walks a growth teams operator through this step live; on subsequent campaigns, the team runs it themselves from the LandinChat console. Expect this step to take between 15 minutes and an afternoon depending on how clean your existing data is.

Buyer’s checklist

  • • Official Meta Tech Partner — templates approve faster and account is not at ban risk.
  • • Native growth teams data model — no glue-code to import contacts, orders, or bookings.
  • • Green-tick support with a clear submission checklist and Meta-side follow-up.
  • • Conversation-based pricing that matches WhatsApp’s own billing model, not per-message surcharges.
  • • Human handoff with unread routing, so qualified replies never sit in a bot loop.
  • • Audit log & role-based access — required for regulated enterprise buyers.

Common pitfalls

  • • Broadcasting cold lists — quickest way to a quality-rating downgrade and eventually a template ban.
  • • Skipping opt-in capture — makes every future utility template harder to approve.
  • • Treating WhatsApp as a one-way channel — the platform penalises accounts with low reply-rate.
  • • Running only one template variant — you leave 20–40% of lift on the table.
  • • Not routing hot conversations to a human within 5 minutes — kills conversion by up to half.
Operating playbook

What to measure after launching whatsapp product catalog single & multi-product templates

Week 1 signal

Track template approval time, first-reply latency, delivered-rate, and the first 100 customer replies. For growth teams, the fastest warning sign is not low opens; it is customers replying with confusion because the trigger, offer, or handoff promise was not specific enough.

Month 1 signal

Compare reply quality across Multi-product messages, Single-product CTA, Shopify / WooCommerce sync, In-thread cart. The best-performing growth teams teams keep the highest-intent replies visible to managers, then rewrite templates around real customer language instead of internal terminology.

Scale signal

Once Sync your catalog → Pick the template → Personalise SKUs → Wire checkout is stable, scale by segment rather than volume. Add new audiences only when opt-in source, template intent, agent ownership, and conversion tracking are all mapped.

Search-quality notes for this workflow

This page is intentionally built around whatsapp product catalog single & multi-product templates rather than a generic WhatsApp marketing overview. The content references the actual workflow, the growth teams audience, implementation steps such as Sync your catalog, Pick the template, Personalise SKUs, Wire checkout. That specificity helps buyers, internal teams, and search engines understand why this page deserves to exist separately from broader WhatsApp CRM, broadcast, chatbot, and automation pages.

Sell more SKUs without leaving WhatsApp

Catalog sync, single & multi-product templates, in-thread cart + checkout — ship in a single afternoon.

In depth

What actually matters with WhatsApp Product Catalog Template

WhatsApp Product Catalog Template is one of those topics where the surface answer ("use WhatsApp Business API") hides the real work. The rest of this page unpacks what actually moves the needle for growth teams teams: template strategy, opt-in hygiene, human handoff, and the compliance guardrails that keep the account alive.

WhatsApp’s open rate — 85–98% inside 15 minutes — is only valuable if the platform underneath it treats the channel as a workflow surface, not a broadcast megaphone. For growth teams teams evaluating WhatsApp Product Catalog Template, the questions to ask are: does the vendor own green-tick submission end-to-end, are templates reviewed for approval-risk before you send them, is pricing flat or does it add per-message markup on top of Meta’s own rate, and can a live agent take over a conversation without losing context.

The three levers that consistently produce measurable lift are: (1) segmenting broadcasts by recency and spend tier instead of blasting the entire list; (2) capturing opt-in at every surface — website, checkout, in-store QR — so future utility templates approve first-attempt; and (3) routing any reply containing intent signals to a human within five minutes. Everything else — chatbot flows, catalog integration, payment links — is downstream of those three.

LandinChat ships all of the above as defaults, with the data model pre-wired. That is why customers who move onto LandinChat typically see reply-rate lift within the first 30 days and full ROI within one billing cycle.

A high-quality WhatsApp Product Catalog Template page should not stop at a feature list. Buyers need to know how the topic behaves in the real WhatsApp Business API environment: what happens when templates are rejected, how agent ownership is preserved after a bot handoff, how opt-in is captured, what reports prove revenue, and where a team should avoid over-automation. The practical evaluation lens is workflow fit, compliance, automation depth, reporting quality, and handoff speed. If any of those areas are vague, the implementation usually becomes slower, more expensive, and harder to scale.

Implementation blueprint

Start WhatsApp Product Catalog Template with one narrow, measurable journey: capture the opt-in, send one approved utility or marketing template, route replies to the correct owner, and tag the outcome. Once the first journey produces clean data, duplicate the structure for adjacent segments. This protects account quality because every template has a clear purpose, every reply has an owner, and every campaign has a measurable next step.

Content depth checklist

For growth teams teams, the strongest pages combine strategic context, setup detail, operational risks, pricing expectations, compliance notes, and real use cases. That is why this page covers the decision criteria around WhatsApp Product Catalog Template rather than repeating the same generic WhatsApp API explanation used on every software page.

What to compare before choosing

Ask whether the platform supports official WhatsApp Business API onboarding, segmented broadcasts, a shared team inbox, CRM history, flow automation, live analytics, template review, and clean exports. The right answer for WhatsApp Product Catalog Template is rarely the tool with the longest feature grid; it is the one your operators can run every week without needing developers for routine changes.

Common execution mistake

The most common mistake is launching WhatsApp Product Catalog Template as one large broadcast or one oversized chatbot flow. Strong teams launch smaller journeys, inspect the conversations, then expand. That gives WhatsApp better engagement signals, gives agents cleaner context, and gives leadership a clearer view of revenue impact.