> 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/product-bundles-overview.md). # Product Bundles Overview A **bundle** is a catalog product (Type: **Bundle**) that groups several products or charges so customers buy them together as a single item. Bundles are first-class catalog entries: they appear, filter, search, and sell like any other product, and they slot into Product Sets, offers, and journeys the same way. ## Why bundles matter Bundles let you package related offerings — a base plan plus add-ons, or a curated combination — into one purchasable unit. That means one item to choose, one line to manage, and a simpler buying decision for the customer. Use a bundle when you want to: * Sell a set of plans / add-ons as one purchasable item. * Present one item and one decision for a combination of charges. * Control **when each bundled product activates** — immediately on purchase, or on a delay relative to another item in the bundle. ## How it fits the catalog model A bundle sits alongside **Synced** products (mirrored from your billing system) and **Internal** products (PeakCommerce-native) as one of the three product **Types**. Its child items can themselves be Synced or Internal products, so a bundle is a composition layer over the rest of your catalog rather than a separate kind of thing to maintain. ## Bundle vs. Product Set — don't confuse them > To group products for **display** in a storefront or journey — without combining them into a single purchasable item — use a **Product Set** (**Commerce → Product Sets**) instead. A Product Set curates what a buyer *sees*; a bundle is one thing a buyer *buys*. See [Creating a Product Bundle](/product/using-peakcommerce/products-and-bundles/creating-a-product-bundle.md) to build one, and [Managing Products](/product/using-peakcommerce/products-and-bundles/managing-products.md) to find and edit it afterward. **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) · [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/product-bundles-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.