WhatsApp catalogues: turning a product list into messages

A WhatsApp catalogue is a structured list of what a business sells, attached to its WhatsApp Business profile. Customers can browse it from the profile, and the business can send individual products or a link to the catalogue inside a conversation. It replaces the routine that most small businesses fall into otherwise, which is re-sending the same photographs and prices to every person who asks.

The value is less about presentation than about repetition. A shop that answers twenty enquiries a day about the same dozen items is retyping prices and hunting for photographs twenty times, with the errors that implies. A catalogue makes the answer a single tap, and makes it consistent — the price a customer sees is the price the business last set, rather than whatever was in the last message the staff member could find to forward.

It also changes the shape of the conversation. Sending a product entry rather than a photograph gives the customer a name, a price and a description together, which is usually enough to move to a decision. A photograph on its own invariably produces the same follow-up question about cost, and answering that question is a message the business did not need to send.

A product entry supports a name, an image, a price, a description, and typically a product link and an identifying code. Filling all of them is worth the effort, because each empty field becomes a question somebody has to answer manually later.

The name is the field most often wasted. "Blue kurta" is a description of a photograph; "Cotton straight kurta, indigo" is something a customer can search for and distinguish from four similar items. Customers scan a catalogue rather than reading it, so the name has to carry the distinguishing information.

Images should show the item plainly, on a clean background, cropped so the product fills the frame. A single clear photograph beats a styled composition where the item is one element among several, because a browsing customer is matching what they see against what they want, not appreciating the shot.

The description is the place to answer the questions the business is already tired of answering: material, dimensions, what is included, how long it lasts, whether sizes run small. Every answer written here once is an answer nobody types again. The identifying code matters more than it looks, because it is what lets an order, an invoice and a stock record refer to the same thing without ambiguity.

A catalogue with a large, unstructured list of items is harder to use than a smaller one that is organised, and this is the most common self-inflicted problem. Where the platform supports grouping products into collections or sets, using it converts an undifferentiated list into something browsable.

Ordering matters because most customers look at the top and stop. Putting what sells well, what is in season, or what a business most wants to move at the front is a decision worth making explicitly rather than accepting whatever order items happened to be added in.

The hardest discipline is leaving things out. A catalogue is not an inventory system, and listing everything the business has ever stocked makes the things it actually sells harder to find. Items that are out of stock, discontinued or rarely bought are better removed than left in place to generate enquiries that end in disappointment. A customer who taps a product, asks about it and is told it is unavailable has had a worse experience than one who never saw it — and the business has spent a message on a dead end.

Pricing deserves a decision too. Prices displayed in a catalogue are visible to anyone who looks, which is a form of transparency some businesses want and others do not. It is a legitimate choice, but it should be a choice rather than a discovery.

Catalogues have practical ceilings. There are limits on how many items a catalogue can hold, on image dimensions and file sizes, and on how many products can be included in a single multi-product message. These figures have been revised over time, so the numbers matter less than the habit of checking Meta's current documentation before designing a catalogue around an assumed capacity.

Product entries are also reviewed against Meta's Commerce Policy, and a catalogue is not a place where every category of goods can be listed. Restricted and prohibited categories exist, and a business in a regulated trade should establish whether its products can be listed at all before investing in photography and copy. Items that violate the policy can be removed, and repeated violations affect the account rather than only the listing.

Updates are not instantaneous. Edits go through processing, and there can be a lag before a change is visible to customers, which matters for anything time-sensitive. A business planning to reflect a same-day price change in its catalogue should not assume the update lands immediately, and should treat a live conversation as the authoritative place to confirm a price that has just moved.

Sending a product entry mid-conversation is a session message when the customer service window is open, which is the ordinary case: the customer asked about something, so the window is open, and the reply costs nothing extra to send today. This makes catalogues most useful as a response to enquiries rather than as an outbound broadcast.

The pattern that works is narrow. A customer describes what they are after, and the business sends the two or three items that actually match, not the whole catalogue. Sending a link to everything transfers the work of searching back to the customer, which is the opposite of helpful. Selecting on their behalf is the service.

Outbound is a different matter. Sending catalogue content to someone who has not asked, outside an open window, means a template, which means the marketing category and the consent that goes with it. The catalogue does not create an exemption from either. A restock announcement is still a promotional message however it is packaged.

One further honest note on scope: a catalogue displays products and supports enquiry. It is not a checkout, and treating it as one leads to disappointment. How an order is actually placed, confirmed and paid for is a separate design decision, and the catalogue's job ends at the point the customer knows what they want.

The failure mode for catalogues is neglect. One built carefully and then left alone becomes a liability within a season: prices drift out of date, discontinued items linger, and customers start receiving corrections instead of confirmations. An out-of-date catalogue is worse than none, because it makes promises the business then has to walk back.

A short recurring review handles most of this. Check that prices match what the business actually charges, remove what is no longer available, promote what is selling, and re-read the descriptions for questions that customers still keep asking — because a question that recurs is a description that is incomplete.

The test for whether a catalogue is doing its job is not how complete it looks but whether it has reduced repetitive typing. If staff are still sending photographs and prices manually, the catalogue is either missing the items people ask about, organised so those items cannot be found, or not being used because it is faster to send a picture than to locate an entry. All three are fixable, and all three are invisible unless somebody asks the question.