> 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/managing-products.md).
# Managing Products
The **Product Catalog** is the tenant-wide list of everything you can sell. Keeping it accurate matters because every journey, storefront, and Change-Plan flow draws on these records — a product's charges, status, and provider link decide what a customer or CSR can actually buy and at what price. You manage it all from **Commerce → Product Catalog**.
A product's detail — its catalog metadata and provider link up top, then each plan and its charges below.
## Add products
There are two ways to get a product into the catalog, surfaced as buttons at the top of the page:
* **Sync from Provider** — pull products from your billing system (e.g. Zuora) into the catalog and keep them in step. **Synced** products carry their provider link, the source integration name, and a **last-synced** timestamp; the provider stays the source of truth for their underlying charges. Re-run **Sync from Provider** (or **Re-sync from** on a single row) to pick up provider changes.
* **Create Product** — add a product directly in PeakCommerce. Pick a **Product Type**: **Internal Product** (a PeakCommerce-native product whose charges you define here), or **Bundle** (groups two or more products to sell together — see [Creating a Product Bundle](/product/using-peakcommerce/products-and-bundles/creating-a-product-bundle.md)).
## Edit a product
Open a product to review or change its **name, SKU, category, description**, and **charges/pricing**. The **Plan presentation** section controls how the product appears in the customer/CSR Change-Plan journey — bullet-list **features**, a **quantity unit** and **price-tier** table for tiered base plans, an add-on **markup %**, and a **non-renewable** flag for trials and one-shots. Internal products also have a **Pricing Tiers** section where you add charges (Flat Fee, Per Unit, Tiered, or Volume bands). For **Synced** products, edit charges in the billing system and re-sync instead.
## Status and filters
A product's **Status** (for example Active) controls whether it can be sold. Use the **Type, Status, Provider, Category, Support Level,** and **Instance** filters — plus search by name, SKU, or description — to find what you need, and expand a row to see its charges. Last-synced times honor your [Zuora tenant timezone](https://gitlab.com/peak-hercules/peak-help-docs/-/blob/main/integrations/zuora-integration/zuora-billing-integration.md).
## Gotchas
* Only **Active** products are sellable. A draft or inactive product won't resolve in a journey or storefront even if it's added to a Product Set.
* To present a curated group of products in a flow, build a **Product Set** (**Commerce → Product Sets**) — don't tie products to a single journey.
* Bulk spreadsheet import/export of products is no longer required — products are synced from the provider or created in the catalog directly.
## Related
* [Products Overview](/product/using-peakcommerce/products-and-bundles/products-overview.md)
* [Creating a Product Bundle](/product/using-peakcommerce/products-and-bundles/creating-a-product-bundle.md)
* [Commerce actions in journeys](/product/journeys-and-pages/journey-steps/commerce-actions.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/managing-products.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.