For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 to build one, and Managing Products to find and edit it afterward.

Related: Products Overview · Creating a Product Bundle · Journeys Overview

Last updated

Was this helpful?