Webflow CMS at Scale: Lessons From a 1,100-Item Catalogue

Why a large Webflow catalogue is a different project

A blog with 40 posts and a catalogue with 1,100 products are both "CMS sites", but they are not the same job. At that size, the data model, filtering, page weight and editor workflow all stop being details and become the project.

I have been building in Webflow since 2018 and I am Webflow CMS L1 certified. The biggest catalogue I have shipped is Big Moe Watches, a Dubai dealer of pre-owned luxury watches, built as a white-label project via Landrieau Studio. It has more than 1,100 watches in the CMS and an advanced filtering system by brand, model and price. Pricing requests went up by 63%.

The rest of this article is general practice for catalogues of that kind. Where I describe a technique, it is what I recommend on large catalogues, not a claim about how a specific site was built.

CMS item limits per plan

Start here, because the limit shapes everything else. Webflow limits the number of CMS items per site plan, and the limit counts all collections together, not each one separately.

Webflow simplified its Site plans in May 2026. According to the official help article, the CMS and Business plans were merged into a single Premium plan, with the item limit raised to 20,000 (previously 2,000 on the CMS plan and 10,000 on Business). Older blog posts still quote the old figures, so always check the current pricing page before you quote a client.

• Count every item. Drafts and archived items count towards the total on typical plans, so plan for headroom.
• Count all collections. Categories, brands, authors, tags and FAQs are items too.
• Decide what is not a CMS item. If something has three entries and never changes, a static section is cheaper than a collection.

If a catalogue may grow beyond the plan, decide early whether you will upgrade, split the data, or serve part of it from outside Webflow.

Collection structure and reference fields

On large catalogues I recommend designing the data model on paper before opening the Designer. A messy model is cheap to fix with 20 items and painful with 1,100.

• One collection per real-world thing. Products, brands, categories, collections. Do not store a brand name as plain text on every product; reference it.
• Use reference fields for anything you filter by or link to. A brand reference gives you a brand page, a brand filter and one place to edit the name.
• Use option fields for short fixed lists, such as condition or availability, where a full collection would be overkill.
• Keep the field count sensible. Every field is something an editor has to fill in. If nobody will use it on the page, do not add it.
• Name fields consistently. I follow Client-First naming for classes, and the same discipline applies to fields and collections.

Webflow has limits on fields, reference fields and multi-reference fields per collection, and on the number of collections per site. They are documented in Webflow's help centre. In practice a well-designed model stays well below them.

Template pages

Design the item template for the real range of content: the longest name, the shortest, missing images, missing optional fields. Use conditional visibility so empty fields do not leave gaps.

Filtering and search: native vs Finsweet Attributes vs custom

Filtering is usually the reason a catalogue exists in the first place. You have three realistic options.

For most catalogues up to a few thousand items, I recommend starting with Finsweet Attributes. It is a well-documented, free toolkit from the team behind Client-First, and it is what I would reach for first when a client wants multi-filter browsing without a custom build.

The key limitation to understand is that a Collection List shows at most 100 items, and a client-side filter can only filter what is on the page. Finsweet explains how to go beyond that in its CMS Load documentation, including pagination and render-all modes, and it warns to consider pagination before render-all.

Design the filters from the user's questions

Ask what a buyer actually asks: brand, price range, condition, availability. Build filters for those and skip the rest. Ten filters nobody uses make the page slower and the interface noisier.

Pagination and load performance

A catalogue page that tries to render 1,100 cards at once will be heavy, however good the hosting is. Webflow serves from a CDN, but the browser still has to parse, lay out and paint every card.

• Paginate or load in batches. Show a sensible page of items and load more on demand.
• Optimise the images first. On catalogues, images are most of the weight. Use properly sized WebP, set explicit dimensions and lazy-load below the fold.
• Keep the card light. Fewer nested wrappers, no heavy animation per card, no embeds in list items.
• Limit nested collection lists. Each one multiplies the work the page has to do.
• Test on a mid-range phone. Desktop on fast wifi hides most problems.

I measure with Lighthouse and, for real-user data, Core Web Vitals in Search Console. Interaction responsiveness (INP) matters on filter-heavy pages, because every click on a filter should feel instant.

Importing 1,000+ items: CSV and API

Nobody should type 1,100 products by hand. There are two practical routes: the CSV import in the CMS and the Webflow Data API.

CSV import

Good for the first load and for one-off batches. Prepare the file carefully: unique slugs, clean text, image URLs that actually resolve, and reference fields that match existing item names exactly. Import the referenced collections first (brands, categories), then the products.

API and automation

If the catalogue changes often, for example from a stock system, an API-based sync is better than repeated CSVs. I can connect Webflow to other systems with Make, Zapier or n8n, or with a custom script. The API has rate limits, so a sync should back off and retry rather than hammer it.

Checks after any large import

1. Compare the item count in the CMS with the source file.
2. Open a random sample of 20 items and check every field.
3. Check reference fields and images on a few items from the end of the file, not just the start.
4. Publish to staging and test the filters against real data.

SEO for collection and item pages

A catalogue is a lot of landing pages. They only help if each one has something to say.

• Generate titles and descriptions from fields. Webflow lets you build SEO title and meta description from CMS fields. A pattern such as brand, model and a key attribute is better than an identical title on every page.
• One H1 per item page, taken from the item name.
• Add unique copy where it matters. A short, real description per item beats a template of identical sentences.
• Link the structure. Item pages link to their brand and category, and those pages link back to their items. Breadcrumbs help users and search engines.
• Keep the sitemap clean. Exclude filter-only or thin pages from indexing.
• Add structured data such as Product markup where it fits your business model.

For a wider list, see my Webflow SEO checklist.

Editor workflow: make the catalogue easy to maintain

The client lives in the CMS after launch. A catalogue that is hard to edit gets stale.

• Write short field help text so editors know what goes where and in what format.
• Make required fields required and keep optional fields to a minimum.
• Agree naming rules for items and images before the import, not after.
• Use the draft and publish states deliberately, and remember that drafts count towards the item limit.
• Hand over with a walkthrough. I finish projects with a Loom video that shows how to add, edit, archive and bulk-update items.

My take: what a 1,100-watch catalogue taught me

On Big Moe Watches, the challenge was to make a site feel as premium as the product and still work like a shop. The catalogue holds more than 1,100 watches from brands such as Rolex, Audemars Piguet, Richard Mille and Patek Philippe, with filtering by brand, model and price. The aim was that every visitor finds the right watch in a few clicks and is guided towards a conversation with the dealer. Pricing requests rose by 63%.

The lesson I take from that project is simple. On a catalogue, the data model and the filters are the product. The visual design matters, but it only works if the structure underneath lets a buyer narrow 1,100 items down quickly. That is why I spend the first part of a catalogue project on collections, fields and filter logic, before any styling.

It was delivered white-label via Landrieau Studio, in the agency's workspace. If you are planning a similar build, send me the product data and the filters you need and I will tell you what to watch out for. For the wider context, see Client-First explained and the Webflow SEO checklist.

FAQ

Written byPeter CekanakDesigner & Webflow developer · white-label partner for agencies

I design and build Webflow sites for agencies and startups since 2018 — Client-First, GSAP, CMS and AI automations. Sites I built helped a client to a $10M exit and tripled demo requests for a SaaS.

Webflow Certified ExpertRelume ExpertClient-First