Framer CMS for Product Catalogs: Limits and Workarounds

Framer CMS can run a product catalog, and for a few hundred items it does the job well — especially now that the List Field can hold specs and FAQs inside a single product row. What it should not hold is live stock, variants or market pricing. Those belong in Shopify and should sync into the site, because the CMS has no concept of inventory and no way to recalculate a price per market.

The practical ceiling is not design effort. It is the item count on your plan and the number of Framer CMS pages you are allowed to publish. Get those two numbers right before you start typing products in, because moving 400 rows later is a weekend you do not get back.

What a Framer CMS Collection Holds — and What It Does Not

A Framer CMS collection is a typed table: one row per item, with fields for plain text, rich text, images, numbers, dates, links, references to other collections, and — since September — nested lists. You bind a Framer CMS detail page template to the collection once, and every row renders through it.

What it has no model for is the commerce layer. There is no stock number that decrements, no variant matrix, no tax or currency logic, no cart. Framer's own CMS Agent documentation describes collections as a way to organise repeatable content, and that framing is honest: it is a content store that happens to render beautifully.

So the question is never "can the CMS do products." It is "which half of a product belongs in the CMS." Editorial copy, lifestyle imagery, spec sheets, care instructions, size guides — yes. Price, stock, SKU, variant — no.

How Much Does Framer Cost Per Month for a Product Catalog?

Start from the caps, not the price. Here is what each plan gives you against a catalog that syncs from Shopify instead:

Two numbers matter most. Pro includes 2,500 CMS items and 150 pages, which covers a focused catalog outright. And the Framer CMS collection limit is soft: extra items run $20 per 10,000 up to a 40,000 ceiling, extra collections $40 per 10 up to 40. A 3,000-product catalog is not blocked. It is a $20 add-on.

The cost that is not on the pricing page is editing. Every row is maintained one at a time, by hand, by a person. That is fine for 80 hero products and miserable for 3,000.

What the CMS List Field Changed on September 8, 2026

Before September, a product row with six spec lines meant twelve flat fields: spec_1_label, spec_1_value, and so on down the row. Collections got wide and ugly, and adding a seventh spec meant editing the schema.

The List Field removed that. Framer's release note is blunt about the point of it:

Group items in a single list and add or reorder rows as you would in a CMS table.

— Framer, CMS List Field update, September 8, 2026

The same release landed in the plugin API as array fields. Framer's developer changelog for v5.0.0 confirms arrays can nest boolean, color, date, file, formatted text, image, link, number and string fields — which is what makes a spec table, a size chart or a per-product FAQ a single field instead of a schema problem. One caveat for anyone syncing programmatically: array items now require stable IDs across syncs, or localized values get dropped.

This is the genuinely new capability, and it is why a 2025 Framer CMS tutorial will steer you wrong. Specs and FAQs are now a solved problem inside the CMS.

Where It Still Breaks: Variants, Stock and Price

Variants are the wall. Shopify raised the limit to 2,048 variants per product in October 2025, up from 100. A single mid-sized apparel product — five colours, eight sizes, three fits — is 120 combinations, each with its own SKU, price and stock count. There is no CMS field that models that, and no amount of List Field nesting fixes it, because the problem is not storage. It is that the numbers change without anyone opening the editor.

Stock is the same failure in a worse costume. A typed-in CMS number is accurate at the moment you type it and wrong by lunchtime. Overselling a sold-out item because the site cached a hand-entered quantity is a refund and a support ticket, not a design bug.

Market pricing closes it out. Shopify Markets recalculates price per country; a CMS text field says $49 to everyone, forever.

Do Framer Templates Have a CMS Built In?

Most of the good ones do. A paid Framer CMS template for an ecommerce or portfolio site almost always ships with collections already wired to a detail page, which saves you the schema design and the first pass of styling. What none of them ship with is a commerce backend — the template's "products" collection is a content collection with a price typed into a text field.

That is the trap. A template demo with nine beautiful products looks like a store and behaves like a brochure. Treat the template as the front end it is, keep the collections it gives you for content, and point the commerce fields at Shopify. Our guide to what Framer can actually sell in 2026 walks through where that line falls.

The Split That Works

Run two systems and let each do what it is built for.

Keep in the CMS: editorial product stories, lookbook imagery, spec tables and FAQs in List Fields, care and sizing content, category landing copy. These change on your schedule and benefit from being designed on the canvas.

Sync from Shopify: product titles and handles, variants, SKUs, live inventory, price per market, and anything that drives add-to-cart. This is what FramerLink exists to do — it keeps products, variants and stock current in Framer without anyone retyping a number.

The build order matters. Set up the sync first, confirm variants and stock land correctly, then design the collection and filter layer on top of real data. Designing against hand-typed placeholder rows and retrofitting the sync afterwards is how catalogs end up with two sources of truth and a pricing error on the one page that converts.

A catalog of 200 to 2,000 products is well within Framer's range in October 2026. Just be deliberate about which half of each product the CMS is allowed to own.