For the complete documentation index, see llms.txt. This page is also available as Markdown.
Products Overview
The Product Catalog (Commerce → Product Catalog) is your tenant-wide list of sellable products and the single source of truth for what PeakCommerce can put in front of a buyer. Everything a journey, offer, or payment page can sell starts as a product here, so getting the catalog right is the foundation for accurate pricing, clean checkout, and correct billing.
Each product carries a SKU, a category (for example Base Products or Add On Services), one or more priced charges, a status, and — when it originates in a billing system — a link to its provider record and last-synced time.
The Product Catalog (Commerce → Product Catalog) — each product's type, pricing, and status in one list.
The catalog model: where products come from
A product's Type tells you its origin and how it's maintained:
Synced — mirrored from your billing provider (e.g. Zuora rate plans + charges) via Sync from Provider, and kept in step with the provider catalog. Synced products show their provider, source instance, and last-synced time. PeakCommerce prices most charges locally and falls back to the billing system for any charge it can't model.
Internal — PeakCommerce-native products you create directly with Create Product, for offerings that don't live in (or don't yet need) your billing system.
Bundle — a product that groups other products together to sell as one item, with optional per-item activation timing. See Product Bundles Overview.
How you work with the catalog
Search by name, SKU, or description, and filter by Type, Status, Provider, Category, Support Level, or Instance. Expand a row to inspect its charges, or open a product for full pricing and plan detail. A Synced product with No plans synced signals a sync gap worth resolving before you try to sell it.
Grouping products for sale
To present a curated set of products in a storefront or journey, group them into a Product Set (Commerce → Product Sets) rather than tying products to a single flow. Product Sets carry their own status and commerce rules, and are how Offers and Audiences target who sees what. This replaces the legacy journey-scoped "Categories" model. See Product Sets for the full picture.
Who and when
Catalog and commerce admins curate products as your offerings evolve — after a billing-system catalog change, re-run Sync from Provider; for native offerings, create Internal products as needed.
