CMS collections

TGC

CMS collections

TGC

CMS collections

TGC

CMS collections

TGC creates two CMS collections in your Framer project: TGC Products and TGC Categories. Here's what they contain.

Contains your synced product data.

Field	Type	Description
swellId	String	Swell product ID (used for runtime fetching)
slug	String	URL-friendly identifier
title	String	Product name
description	Rich text	Product description
price	Number	Regular price snapshot
salePrice	Number	Sale price snapshot (if on sale)
isOnSale	Boolean	Whether product is currently on sale
mainImage	Image	Primary product image
hoverImage	Image	Second image (for hover effects)
galleryImages	Image array	Additional product images
designVariants	String (JSON)	Variant labels for layout purposes
categoryIds	String (JSON)	Array of category IDs this product belongs to

Contains your synced category data.

Field	Type	Description
swellId	String	Swell category ID
name	String	Category name
slug	String	URL-friendly identifier
image	Image	Category image (if set in Swell)
description	String	Category description
parentId	String	Parent category ID (null if top-level)

The CMS collections contain snapshot data for canvas editing:

Field	Canvas	Live site
title, description	From CMS	From CMS (rarely changes)
price, salePrice	From CMS (may be stale)	From Swell API (always current)
isOnSale	From CMS	From Swell API
images	From CMS	From Swell API
variants	designVariants (layout only)	Full variants from Swell API
inventory	Not stored	From Swell API

See The hybrid model for why this matters.

Technically yes, but don't.

Not recommended. TGC manages these collections and may overwrite custom fields during sync.

If you need additional product data:

Framer has CMS limits based on your plan:

Products and categories count toward your total CMS items.

Credentials

Loading variants won't go away