> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/products-and-bundles/products-overview.md).
# 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](/product/using-peakcommerce/products-and-bundles/product-bundles-overview.md).
## 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](/product/using-peakcommerce/products-and-bundles/product-sets.md) 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.
**Related:** [Managing Products](/product/using-peakcommerce/products-and-bundles/managing-products.md) · [Product Bundles Overview](/product/using-peakcommerce/products-and-bundles/product-bundles-overview.md) · [Market Locales](/product/using-peakcommerce/market-profiles.md) · [Ecommerce & Payment Pages](/product/using-peakcommerce/ecommerce-and-payment-pages.md) · [Journeys Overview](/product/journeys-and-pages/journey-basics/journeys-overview.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.peakcommerce.com/product/using-peakcommerce/products-and-bundles/products-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.