Lookbook vs flipbook vs grid: choosing a shoppable catalogue format
Flipbook for seasonal stories, lookbook for mobile-first browsing, grid for dense SKU catalogues. How to choose a shoppable catalogue format, with a decision tree.
We shipped the Digital Catalogue with one strong opinion and one deliberate non-opinion. The strong opinion: every page of a catalogue should be shoppable, hotspots and all. The non-opinion: whether it flips, slides or scrolls. The same twenty-four tagged pages can publish as a flipbook, a lookbook or a grid, and after watching brands run all three, we have a reasonable map of when each format earns its keep.
In this article
What are the three shoppable catalogue formats?
A shoppable digital catalogue is a set of composed pages (product shots, editorial layouts, UGC) where every product is tagged with a hotspot that opens a buy path. If that concept is new, start with what a shoppable digital catalogue is and come back; this piece assumes the pages exist and asks only how they should be presented.
The flipbook. Pages render as spreads with a page-flip animation, the closest digital cousin of the printed seasonal catalogue. Readers turn pages in your order, hotspots sit on each page, and the whole thing behaves like a magazine that happens to have an add-to-bag drawer. It is the natural landing place for brands converting an existing print or PDF asset; the mechanics of that conversion are covered in turning a PDF catalogue into a shoppable flipbook.
The lookbook. The same pages render as fullscreen slides, one look at a time, with pulsing hotspot dots marking each tagged product. No spread metaphor, no visible page furniture: just the image, the dots, and a swipe to the next look. If the flipbook borrows from print, the lookbook borrows from the story formats people already thumb through daily.
The grid. The pages become a scannable wall of tiles, closest in spirit to a collection page or a shoppable gallery. No enforced sequence at all. Shoppers scan, skip and jump to whatever catches them, and the format quietly gives up narrative control in exchange for speed.
One practical note on how we build this at Idukki: the Digital Catalogue publishes one set of composed, hotspot-tagged pages to any of the three formats. You tag products once; the flipbook, lookbook and grid are output modes. That matters for this article because it turns format choice from an irreversible design commitment into something closer to a setting, which you can revisit when the data disagrees with your taste.
How do people actually browse each format?
The formats do not just look different. They produce different behaviour, and pretending otherwise is how catalogues get judged unfairly.
A flipbook is lean-back browsing. The page-turn is a deliberate act, so readers move at a pace you set, in a sequence you authored. They see the opening spread, then the next, and the editorial arc (hero look, supporting pieces, accessories, closing offer) survives contact with the reader. The cost is friction: every page-turn is a small decision to continue, and readers who wanted one specific product will resent turning eleven pages to find it.
A lookbook runs on swipe cadence. Each slide gets the full screen and therefore full attention, which is more than any tile in a grid will ever receive. The pulsing dots do quiet work here: they signal shoppability without a button, and tapping one opens the product drawer while the look stays in view. Swiping is cheaper than page-turning, so people travel further, but they also skim faster. Drop-off is visible slide by slide, which is uncomfortable and useful in equal measure.
A grid is self-directed scanning. Nobody reads a grid in order; they sweep it, anchor on a tile, and jump. Intent arrives faster (a shopper who clicks a grid tile usually wanted that product), and narrative disappears almost entirely. If the collection's story matters, the grid will not tell it. If the shopper's errand matters, the grid respects it best.
Which format wins on mobile, and which on desktop?
The honest answer is that the flipbook was born on big screens and the lookbook was born on phones, and both show their birthplace.
On desktop and tablet, the flipbook is at home. Spreads render as designed, the flip animation feels like craft rather than obstacle, and hotspots are easy pointer targets. On a small portrait screen the spread metaphor suffers: pages shrink, single-page mode helps but halves the composition, and pinch-zooming a catalogue is nobody's idea of shopping. Baymard Institute's mobile commerce research has documented for years how small tap targets and dense layouts punish mobile shoppers, and a shrunken catalogue spread is both at once.
The lookbook inverts this. Fullscreen slides are exactly the shape of a phone, the dots are sized for thumbs, and the swipe gesture needs no explanation because every social app already taught it. On desktop a lookbook still works, but a single fullscreen look on a 27-inch monitor can feel sparse, like a poster where you expected a magazine.
Performance is the device question nobody asks until launch week. Flipbook runtimes have a reputation for heavy scripts and slow first paint, which is a conversion tax on mobile before a single page turns. Whichever format you pick, insist on an edge-served, Core-Web-Vitals-safe runtime; we hold the Digital Catalogue to the same performance budget as every other Idukki widget precisely because a beautiful catalogue that sinks your LCP is a net loss. A format decision made on aesthetics and reversed on page speed is a month wasted.
The grid is the format that never embarrasses itself anywhere: columns collapse cleanly from desktop to mobile, and performance stays predictable. It wins no beauty contests and loses no devices. Check your own analytics before deciding; if you have not already split behaviour by device, mobile vs desktop patterns covers why the same content earns different behaviour on each. A catalogue whose traffic is 80% mobile has had its format decision mostly made for it.
Which content type fits which format?
Format follows content. A seasonal campaign, an evergreen collection and a dense SKU catalogue are three different publishing jobs, and each has a natural home.
Flipbook
The seasonal storyteller. Authored sequence, editorial pacing, print DNA.
Wins at
- Seasonal campaigns and gift guides with a narrative arc
- Desktop + tablet audiences, email-driven traffic
- Brands migrating an existing print or PDF catalogue
- High-AOV considered purchases that reward slow browsing
Struggles with
- Small portrait screens shrink the spread
- Shoppers hunting one specific SKU
- Content that changes weekly (re-pagination overhead)
Lookbook
The mobile-first editorial. One look per screen, pulsing dots, swipe cadence.
Wins at
- Mobile-majority traffic and social-referred visitors
- Look-based merchandising: outfits, room sets, styled scenes
- Campaign drops where each image carries several tagged products
- Attention per image: every slide gets the full screen
Struggles with
- Dense SKU ranges (one slide per product gets tedious)
- Desktop-heavy B2B or trade audiences
- Shoppers who want to compare items side by side
Grid
The evergreen workhorse. Self-directed scanning, zero narrative, fastest route to a product.
Wins at
- Evergreen collections that stay published year-round
- Dense SKU catalogues (50+ products) where findability rules
- Mixed devices: collapses cleanly everywhere
- Shoppers arriving with a specific errand
Struggles with
- Telling a campaign story in a deliberate order
- Standing out: it reads like another collection page
- Per-image attention (tiles compete with each other)
The same tagged pages, three rendering decisions. Match the format to the content's job, not to whichever demo looked best.
The overlap cases are where judgement earns its money. A seasonal drop with mobile-majority traffic belongs in a lookbook even though "seasonal" says flipbook. A 200-SKU trade catalogue for wholesale buyers on desktop can genuinely suit a flipbook, because those buyers grew up on the printed version and the spread layout mirrors the order sheet. When two formats both plausibly fit, publish both from the same pages and let the numbers argue; that is precisely the argument the single-source Digital Catalogue was built to settle. Dedicated flipbook vendors (Publitas is the established one; we keep an honest side-by-side on our Publitas comparison page) tend to lock you into the one format they sell.
Content sourcing shifts the answer too. A catalogue composed from studio photography behaves like the print asset it descends from, and the flipbook flatters it. A catalogue composed from live UGC (customer photos and clips pulled from your DAM, rights cleared, products already tagged) suits the lookbook and grid better, because customer content arrives as single vertical images and short clips, not as designed spreads. This is a genuine difference between converting a PDF and composing pages natively: the PDF gives you spreads to preserve, the DAM gives you assets to arrange, and the best format follows from which one you are holding.
What analytics should each format be judged on?
The quickest way to kill a good catalogue is to grade it on another format's exam. Each format has a primary metric, and the primary metrics are not interchangeable.
- Flipbook: pages per session and per-page revenue. The format's whole promise is depth, so measure whether readers travel through the sequence. Page heatmaps show where attention pools; per-page revenue attribution shows which spreads sell rather than merely decorate. Across our fashion and furniture cohort, published flipbook and lookbook catalogues double pages per session against the same content in a plain gallery, which is the depth effect working as intended.
- Lookbook: slide completion and hotspot open rate. The drop-off curve, slide by slide, is the editorial report card: a cliff at slide four is a sequencing note, not a format failure. Hotspot opens and add-to-bag from the drawer tell you whether the dots are earning taps or just pulsing decoratively.
- Grid: click-through to PDP and scroll depth. The grid's job is routing, so grade the routing: tile CTR, how far down the wall people scan, and which tiles convert against their position. A grid with high scroll depth and low CTR has a curation problem; the inverse has a supply problem.
Whatever the format, wire the catalogue into the same attribution you use everywhere else (clicks, add-to-bag, revenue), or the format debate becomes a taste debate. The general framework in how to measure UGC ROI applies to catalogue surfaces unchanged: instrument first, opine second.
And because the same tagged pages can publish to more than one format, the strongest move available is a real test rather than a meeting. Idukki's A/B testing lets a lookbook widget host one running experiment at a time, so you can put the flipbook rendering against the lookbook rendering on the same traffic and let revenue per session settle the argument. We have watched teams spend three weeks debating a format that a two-week experiment would have decided with a confidence interval attached.
How do you choose? A decision tree
Collapse the whole article into three questions: what is the content's job, where does the traffic browse, and how dense is the range. The tree below runs them in order.
Pick your catalogue format in three questions
Start here
What is this catalogue's job: a seasonal story, an evergreen collection, or a dense SKU reference?
- Seasonal story (campaign drop, gift guide)
Editorial formats first
The sequence is the product, so pick a format that preserves your order: flipbook or lookbook, decided by where the audience browses.
- Traffic is mobile-majority: Lookbook: fullscreen slides, pulsing hotspot dots, swipe-through.
- Desktop, tablet or email-led traffic: Flipbook: spreads and page-flips do the campaign justice.
- Evergreen collection (stays live all year)
Grid by default
Repeat visitors arrive with errands, not appetite for narrative. A grid respects the errand and never dates.
- A hero sub-story emerges (new season within the range): Publish a small lookbook of the story; keep the grid canonical.
- Content is look-based (outfits, room sets): Lookbook, with the grid as the fallback view.
- Dense SKU reference (50+ products)
Grid, with one exception
Findability beats storytelling at this density. One slide per product is tedious; eleven page-turns to a SKU is worse.
- Trade or wholesale buyers on desktop, used to print: Flipbook mirroring the print catalogue's pagination.
- Consumer audience on mixed devices: Grid, tagged and filterable, judged on tile CTR.
References + further reading
- 1Idukki: What is a shoppable digital catalogue? · The concept primer this piece builds on.
- 2Idukki: Turn a PDF catalogue into a shoppable flipbook · The conversion workflow, step by step.
- 3Idukki: The shoppable gallery guide · Where grids came from and how they convert.
- 4Idukki: Mobile vs desktop social proof patterns · Why the same content behaves differently per device.
- 5Idukki: How to measure UGC ROI · The attribution framework catalogues should plug into.
- 6Baymard Institute: ecommerce UX research · Long-running evidence on mobile layouts and tap targets.
- 7Idukki vs Publitas · How a UGC-native catalogue compares with a dedicated flipbook vendor.
More from Rohin Aggarwal
- Strategy
PDP before and after UGC: what actually changes on the page
Add verified customer photos, video and reviews to the middle scroll of a brand-only PDP and conversion lifts. Here is what moves, scroll by scroll.
- Strategy
A kitchen table in Egham, why I built Idukki
Day job: SAP architect on UK government software. Night job: founder of a UGC platform. The Venn diagram of those two communities is roughly one person.
- Strategy
The Death of Impression-Based Pricing: A Finance Director's Case
Impression-based pricing made sense while impressions tracked funnel impact. They stopped. A finance director's argument for outcome-based commercial models in the agentic era.