The UGC lookbook on WhatsApp: one link, real customers, an offer that expires

Why a link and not a PDF

A PDF is a file. It has to be downloaded before it can be seen, it renders at whatever page size the designer picked, and once it is on someone's phone you cannot change the price in it, close the offer in it, or learn whether page seven was ever opened. Every one of those hurts on WhatsApp, where the reader is on mobile data, the screen is a portrait rectangle, and the offer has a date on it. A link fixes each in turn. It opens without a download, renders as pages sized for the phone, pulls prices from the feed at open time, lets an offer stop rendering on the day it expires, and reports what was opened, how far people got, and which product got tapped.

What makes it a UGC lookbook rather than a nicer PDF is where the pictures come from. Idukki builds the pages from rights-cleared customer photos and video already in your library, each page credited to the creator, with the products you tag from your catalogue. That changes how the thing reads in a chat. A studio catalogue forwarded into a group is an advert. A page of real customers wearing the product is a recommendation, which is the register WhatsApp runs on. The WhatsApp UGC funnel piece makes the wider argument.

The incumbents price this as three separate upgrades. On Publitas's published pricing and its Shopify listing at the time of writing, product hotspots arrive on the Gold tier at €396 a month, while vertical scroll, WhatsApp checkout and the analytics dashboard are Enterprise features, listed on Shopify at roughly $1,130 a month. Those are the three things a WhatsApp lookbook cannot do without.

The 256 problem: broadcast lists versus forwards

The WhatsApp Business app sends a broadcast to a list of up to 256 saved contacts, and only people who have saved your number receive it. Fine for a boutique with a regulars list, not a distribution channel. The WhatsApp Business Platform lifts the cap, with message pricing and template approval, and still reaches only people who opted in.

A forwardable link has no such ceiling. The person who forwards it is not you, so the recipient does not need your number saved, and the message arrives from someone they trust. The design question is therefore not "how do I reach more contacts" but "what makes a customer forward this". Real customers on the pages help, because people forward people. So does a visible offer with a date, because urgency gives the forward a reason to happen today. And so does a card that looks worth opening. Treat the broadcast list as the seed and the forward as the reach, and give each its own utm_source so you can tell them apart.

How the preview card actually works

When a link lands in a WhatsApp chat, WhatsApp fetches the page and builds a preview card from its Open Graph tags. Meta publishes the rules, and they are strict enough that most catalogue pages fail at least one. The og:image must be under 600 KB. It must be at least 300 pixels wide. Its aspect ratio must be 4:1 or squarer, so a wide banner gets ignored. And the tags must sit within the first 300 KB of the HTML, which rules out pages that put a large inline style block ahead of the metadata.

Get those four right and the card shows an image, a title and a description. Get one wrong and the link shows as bare text, which is the difference between a tap and a scroll-past. Idukki generates the preview image from the cover at a size and ratio that passes, puts the tags at the top of the document, and lets you set the card's title and description apart from the page heading.

Sharing uses the wa.me format WhatsApp documents for pre-filled messages, so the "Share on WhatsApp" button makes a forward one tap, with your wording and the preview attached. "Order on WhatsApp" runs the other way: a chat with your business number, the shopper's basket written into the message, the click-to-chat pattern the SMS and WhatsApp social proof piece describes.

Build, share, measure

The sequence is short, and the shortest version is a button. "Generate lookbook" on any collection in the Idukki dashboard seeds the pages from that collection's approved content, one page per post, products already tagged.

PDF versus UGC lookbook versus a native WhatsApp catalog

Three objects compete for the same job. Compare them by what the reader experiences in the chat.

What to measure, and what to ignore

The dashboard carries more metrics than you need, so pick the three that answer a question. Completion rate tells you whether the story holds: if half the openers leave by page three, the sequencing is wrong, not the offer. Product taps per open tells you whether the pages are shoppable in practice; a beautiful photo with no tap has either a weak product or a hidden pin. Offer-code copies set against WhatsApp orders and store orders tells you whether the urgency worked. Shares are the WhatsApp-specific metric and the one to watch over time: a drop that gets forwarded earned its reach, and a drop that does not reached the broadcast list and stopped.

On Shopify, the visitor id the lookbook sets travels with the shopper to the store, and the existing order-webhook attribution matches the order back to the lookbook the same way it matches a widget click. The revenue line is the same reconciled number the rest of the dashboard uses, not a separate model. Off Shopify, you get everything up to the store boundary.

One number nobody has yet: what any of this converts at. Publitas's benchmarks (3.9 minutes per publication, 10.1 seconds per page, 28% bounce) are a fair floor for a studio catalogue. There is no public dataset for a UGC lookbook shared on WhatsApp, and we are not going to invent one. Run two drops and read the completion and share rates. That is a better benchmark for your audience than any vendor can give you.