Documentation Index
Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
Use this file to discover all available pages before exploring further.
Template format determines the visual structure and interactive capabilities of a WhatsApp message. Galantis supports five formats — each with a distinct component structure, a specific use case, and different catalog requirements. The format you choose is set at template creation time and determines how the message renders in the customer’s WhatsApp client.
Standard campaigns use rich card formats. Product-focused campaigns use catalog-based formats that require a synced Meta Catalog. Choosing the right format depends on what you are promoting and whether you have catalog infrastructure in place.
What this covers
- All five template formats with their component structures
- When to use each format
- Catalog requirements per format
- A format selection guide
Single Rich Card
Multi Rich Card
Single Product Message
Multi-Product Message
Whole Catalog
SINGLE_RICH_CARD — A single promotional card combining header, body, footer, and buttons into one visual unit.Component structure:| Component | Required | Notes |
|---|
| Header | Yes | Text with optional variable |
| Body | Yes | Rich text with dynamic variables |
| Footer | Optional | Static short text |
| Buttons | Optional | Up to 3 buttons |
- Keep the header text short — it is a label, not a sentence
- Use one primary URL button for the main CTA and a
COPY_CODE button if a discount code is included
- Avoid stacking three buttons unless all three represent genuinely distinct actions the customer would choose between
Single Rich Card is the most versatile format and the right starting point for most first templates. It works for promotional and utility purposes, requires no catalog infrastructure, and renders cleanly across all WhatsApp client versions.
MULTI_RICH_CARD — A horizontally swipeable carousel of multiple individual cards, each with its own image, body text, and buttons.Component structure:| Component | Required | Notes |
|---|
| Body | Yes | Carousel-level introductory text |
| Carousel cards | Yes | Multiple cards, each with image, body, and buttons |
- Image (required per card)
- Body text (required per card)
- Buttons (optional per card)
Use for: Showcasing multiple products, offers, or content items in a single message where the customer swipes through and selects what interests them. More engaging than sending multiple sequential messages, and less overwhelming than a product list.Meta Catalog required: No — carousel card content is defined at template creation time. Content is fixed in the template and not pulled from a live catalog sync.Best practices:
- Keep card count to what is genuinely useful — a 3–5 card carousel outperforms a 10-card one because customers rarely swipe past the first few
- Use consistent image dimensions across all cards for a clean visual presentation
- Each card should have a distinct CTA — avoid repeating the same button label across all cards
Because Multi Rich Card content is fixed at template creation, it is less suitable for products with frequently changing prices or availability. For dynamic product showcasing, consider Single Product Message or Multi-Product Message formats that pull live catalog data.
SINGLE_PRODUCT_MESSAGE (SPM) — Showcases one specific product from your Meta Catalog, with variants, pricing, and a native WhatsApp commerce buy interface.Component structure:| Component | Required | Notes |
|---|
| Header | Yes | PRODUCT type — pulled from catalog |
| Body | Yes | Supporting text with dynamic variables |
| Footer | Optional | Static text |
| Buttons | Optional | Action buttons |
| Product sections | Yes | Product and variant data from Meta Catalog |
SYNCED status before this template can be used in a campaign or automation.Best practices:
- Choose products with strong imagery — the catalog product photo is the primary visual element
- Use the body text to add context that the product card alone does not provide (urgency, social proof, personalization)
- Verify the product’s
SYNCED status in the Catalog module before activating any campaign or automation that uses this template
If the product referenced in an SPM template loses its SYNCED status in the Meta Catalog — due to a sync error, image format issue, or catalog disconnection — messages using this template will fail for all recipients until the sync issue is resolved.
MULTI_PRODUCT_MESSAGE (MPM) — Displays up to 30 products from your Meta Catalog in a scrollable list, organized into sections.Component structure:| Component | Required | Notes |
|---|
| Header | Yes | Text with optional variable |
| Body | Yes | Introductory message text |
| Footer | Optional | Static text |
| Buttons | Optional | Action buttons |
| Product sections | Yes | Multiple product entries from Meta Catalog, grouped into sections |
SYNCED status. Products with PENDING or FAILED status cannot be included.Best practices:
- Organize products into meaningful sections (e.g., “New Arrivals”, “Top Sellers”, “Under $50”) — sections add context and make the list easier to browse
- Limit the total product count to what a customer would realistically browse — 8–15 well-chosen products outperforms 30 indiscriminately selected ones
- Use the body text to frame the selection: “Here are this season’s top picks” gives the customer a reason to engage with the list
WHOLE_CATALOG — A message with a catalog browse button that opens your entire WhatsApp catalog for the customer to browse freely.Component structure:| Component | Required | Notes |
|---|
| Body | Yes | Introductory message text |
| Footer | Optional | Static text |
| CATALOG button | Yes | Opens the full catalog browser in WhatsApp |
- Reserve Whole Catalog sends for audiences with demonstrated browse intent — sending it to cold or low-intent audiences typically underperforms compared to SPM or MPM with curated selections
- Use the body text to prompt browsing with a clear reason: “We just launched 50 new styles — explore them all” is more effective than a generic “Browse our catalog”
- Ensure your Meta Catalog is fully synced and up to date before sending — a Whole Catalog message that opens a catalog with missing or outdated products creates a poor experience
| Format | Catalog required | Products shown | Best for |
|---|
SINGLE_RICH_CARD | No | 0 — image or text only | Single-focus promotions, most standard campaigns |
MULTI_RICH_CARD | No | Multiple (fixed in template) | Multi-offer showcases, content carousels |
SINGLE_PRODUCT_MESSAGE | Yes | 1 specific product | Targeted product promotions, personalized picks |
MULTI_PRODUCT_MESSAGE | Yes | Up to 30 products | Collection sends, curated product selections |
WHOLE_CATALOG | Yes | Full catalog | Browse-driven sends for high-intent audiences |
- A Meta Catalog connected to your Galantis workspace — go to Catalog → Meta Sync
- Products with
SYNCED status — check Catalog → [Product] for sync status per item
- Product images meeting Meta’s format requirements — JPEG or PNG, minimum 500×500px
See Catalog for the full catalog setup and sync reference.
