Product catalog
The structured master list of everything you sell: products, variants, prices, images, stock. Every shop page is a view of it.
See it
What it is
The catalog is the structured source of truth for everything you sell: products, their variants, prices, images, descriptions, attributes, and availability. Every storefront surface (listing grids, search results, the Google Shopping feed, the Instagram shop) is just a different view rendered from the same catalog.
The shape that matters is the hierarchy: a product holds the copy and media, options define the axes (size, color), and variants are the concrete combinations that carry price, SKU, and stock. Get that layer right and filtering, search, and feeds fall out of it. Get it wrong and you end up with 200 near-identical products that should have been one product with 200 variants.
Gotcha: attributes you never filled in are the ones your customers will filter by. Empty 'material' or 'fit' fields silently weaken faceted filtering and browsing, and they make search results feel random. Required attributes are a separate problem: each sales channel and product category has its own required set (GTIN, brand, age group, size system), and missing one of those can get the listing rejected outright from the feed. Once the catalog outgrows the store admin, the fix is a PIM that owns the data and pushes it out, not more spreadsheet imports.
Ask AI for it
Model a product catalog for this store as typed data: a Product has title, handle, description, vendor, tags, media[], and options[]; each option has a name and values. Model options independently, but store variants as an explicit list of allowed option-value combinations rather than the full cartesian product, so combinations you do not actually sell never exist. Give each variant a unique sku, price, optional compareAtPrice, availability, and optional media, and generate only valid combinations. Generate 12 realistic seed products across 3 collections (at least one with a deliberately incomplete option grid), then render an admin-style catalog table: thumbnail, title, variant count, price range, total stock, and a status pill (active, draft, sold out).