Creating a Product Bundle
A bundle is a catalog product (Type: Bundle) that groups two or more products so customers buy them as a single item. Bundles matter most for trial → paid offers: you combine a trial product and a paid product into one purchasable thing, then control when each member activates — so the trial starts now and the paid plan kicks in later, without maintaining a separate "bundle code" in the billing system.
Build a bundle
Go to Commerce → Product Catalog and click Create Product.
Set Product Type to Bundle.
Give the bundle a name, SKU, and category.
Under Select Products for Bundle, check the member products to include. Members can be Internal or Synced products (a bundle can't contain another bundle).
For each member, set its Activation Timing (see below).
Save, then set the bundle Active when it's ready to sell.
You can revisit a saved bundle to add or remove members and adjust each one's timing from the Bundle Products section.
Activation timing (the trial → paid model)
Each member product carries its own activation rule, so the bundle can stage a lifecycle rather than activating everything at once:
Immediate — the member activates with the bundle (typical for the trial member).
Delayed — the member activates after a set delay (a value plus days, weeks, or months). Use this to start a paid plan a fixed time after purchase.
Triggered — the member activates when another trigger product in the bundle activates or ends — e.g. the paid plan begins when the trial completes.
Delays and triggers are evaluated against the contract/service dates in your billing system, so activation offsets depend on the Zuora tenant timezone being set correctly — otherwise an offset can land a day early or late.
How pricing works
A bundle has no single "bundle price" field. Its price comes from its members' charges (and any Pricing Tiers you define), so a delayed or triggered paid member is billed only when it actually activates. Mark trial members non-renewable in their Plan presentation so they don't appear as a renewing Current plan in the Change-Plan journey.
Gotchas
A bundle won't sell until its Status is Active — and neither will an inactive member inside it.
A bundle can't contain another bundle — and the server enforces it. The member picker only offers non-bundle products, and the same rule is applied server-side, so a bundle created or modified through the API is rejected if it tries to nest a bundle — integrations get exactly the rule the picker gives admins.
Set trigger products carefully: a member can't trigger itself, and removing the trigger product later leaves the dependent member without an activation rule.
Related
Last updated
Was this helpful?