> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Catalogue, product and call permission templates

> WhatsApp's catalogue, single-product, multi-product, product carousel and call permission request templates: what they need, their limits, and Flowella.

Five template types depend on Meta features beyond messaging. Four show products from a **Meta commerce catalogue** connected to your WhatsApp account: catalogue, single-product, multi-product and product card carousel templates. All four are Marketing templates, and customers can add products to a WhatsApp cart and send you an order. The fifth, the **call permission request**, asks a customer whether you may call them on WhatsApp, and only matters if you use the [Calling API](https://knowledge.flowella.io/whatsapp/capabilities/calling-api.md).

> [!NOTE]
>
> **In Flowella.** Not available. Flowella's editor can't build these templates, and Flowella doesn't add the product details Meta needs when they're sent. If you create one in WhatsApp Manager, it can appear in your Flowella templates list, but don't plan a send around it. Orders that customers send show in the Inbox as an order, and Flowella doesn't process them further. For products with images and links to your website, use a [media card carousel](https://knowledge.flowella.io/whatsapp/templates/carousel-templates.md).

## The commerce templates

| Template | What the customer sees | Limits |
| - | - | - |
| **Catalogue** | A product image, your text and a **View catalog** button that opens your whole catalogue in WhatsApp | Body up to 1,024 characters, footer up to 60 |
| **Single-product** | One product's image, title and price from your catalogue, your text and a **View** button | Body up to 160 characters, footer up to 60 |
| **Multi-product** | A header, your text and a **View items** button that opens a list of products in sections | Up to 30 products in up to 10 sections. Section titles up to 24 characters. Header up to 60 characters, body up to 1,024. |
| **Product card carousel** | Your text, then up to 10 scrolling product cards, each with a **View** or URL button | Create the template with 2 cards. It can send up to 10. Body up to 1,024 characters. |

All four need:

* **A catalogue with products** uploaded to Meta and connected to your WhatsApp account, through Meta Commerce Manager or Meta's API.
* **Product IDs at send.** The sender names the products, or for a catalogue template optionally the thumbnail product, each time.
* **A recent WhatsApp app.** Single-product and multi-product templates need WhatsApp 2.22.24 or later, and customers can't forward them.

## Carts and orders

When cart functionality is on for your number, customers can add products to a cart as they browse, then send it to you as one order.

| Rule | Detail |
| - | - |
| Carts | One per chat on each device. A cart doesn't expire until it's sent. |
| Quantity | Up to 99 of each product, with no limit on different products |
| After sending | The order can't be edited. The customer sends a new cart to change it. |
| Who sends carts | Customers only. A business can't send a cart. |
| Stock and price changes | Update the catalogue. Messages already sent show the new details, and sold-out products leave carts. |

WhatsApp sends you each order as an order message. Payment and fulfilment happen outside the order, unless you use Meta's [payments](https://knowledge.flowella.io/whatsapp/capabilities/payments.md) features where they're available. For URL buttons on product cards, the customer buys on your website and WhatsApp sends no order.

## Call permission request templates

A business must have a customer's permission before it calls them on WhatsApp. One way to ask is a call permission request template, in the Marketing or Utility category, which can include a header, body and footer. Inside the 24-hour window, the same request can go as a free-form message.

| Rule | Detail |
| - | - |
| Customer's choice | Allow temporarily, allow permanently, decline, or ignore |
| Temporary permission | Lasts 7 days from the customer's approval |
| Requests | At most 1 in 24 hours and 2 in 7 days per customer. A connected call resets these limits. |
| Expiry of a request | 7 days after the customer answers or after it's delivered, or straight away when a newer request arrives |
| Cost | Charged as a normal message in its category |

Customers can also give permission by calling you, if callbacks are on, or from your business profile. They can withdraw it at any time.

## Related

> [card] [Carousel templates](https://knowledge.flowella.io/whatsapp/templates/carousel-templates.md)
>
> Media card carousels, which Flowella supports.

> [card] [Catalogues and commerce](https://knowledge.flowella.io/whatsapp/capabilities/catalogs-and-commerce.md)
>
> How Meta's commerce catalogue works.

> [card] [Calling API](https://knowledge.flowella.io/whatsapp/capabilities/calling-api.md)
>
> WhatsApp voice calls for businesses.

> [card] [Marketing templates](https://knowledge.flowella.io/whatsapp/templates/marketing-templates.md)
>
> Rules for every Marketing template.

Checked against Meta's documentation on 18 November 2026: [Catalog templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/catalogs/catalog-template-messages), [Single-product message templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/catalogs/spm-template-messages), [Multi-product message templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/catalogs/mpm-template-messages), [Product card carousel templates](https://developers.facebook.com/documentation/business-messaging/whatsapp/catalogs/product-card-carousel-template-messages), [Catalogs overview](https://developers.facebook.com/documentation/business-messaging/whatsapp/catalogs/catalogs-overview) and [Obtain user call permissions](https://developers.facebook.com/documentation/business-messaging/whatsapp/calling/user-call-permissions).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.