> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/integrations/zuora-integration/manage-your-pricing/how-to-configure-subscriptions-in-limio-offers-with-initial-price-and-zuora-rate-plans/how-to-acquire-multiple-offers-in-a-single-subscription.md).
# Acquire Multiple Offers in a Single Subscription
*Available from Release 114 for Zuora. From Release 116, the setting is billing-agnostic and also applies to Stripe Billing.*
By default, when a customer purchases multiple offers in the same checkout, Limio creates one subscription per offer in your billing system. You can opt in to a different behaviour where all offers in a single checkout consolidate into a **single subscription** containing all the products.
This is intended for B2B scenarios where a company wants one renewal date, one invoice, and one record to manage covering multiple products (for example: software licence + support + training credits).
## When to use this
Enable multi-offer single subscription if you want:
* One Zuora subscription record covering multiple products
* A unified renewal cycle and invoice cadence across products
* Easier amendment, cancellation, and reporting at the customer level
Keep the default (one subscription per offer) if your customers expect to manage products independently — for example, cancelling one product without affecting another.
## How to enable
From Release 116, go to Limio **Settings → Shop** and set **"Create 1 subscription if multiple offers are purchased in the same checkout?"** This setting works the same way whether you use Zuora or Stripe Billing:
* **On** — one subscription is created containing all offers in the checkout
* **Off** — one subscription is created per offer, on the same customer account
* **Unset** — Limio falls back to the legacy Zuora setting below
Before Release 116, the setting lived in **Zuora → Zuora Orders → Subscription Options** and only controlled Zuora. That legacy setting is still honoured when the new Shop setting is unset, so existing configurations keep working unchanged.
This is a tenant-wide setting. It changes the behaviour of every checkout that contains more than one offer.
{% hint style="info" %}
Promo codes ([Discounts & Promo Codes](https://docs.limio.com/product/pricing/discounts-and-promo-codes)) apply correctly in multi-offer checkouts regardless of this setting: percentage discounts apply to each subscription or line item, and amount discounts apply in full to each relevant subscription or line item.
{% endhint %}
## Constraints
When the setting is enabled, all offers in the same basket must satisfy the following rules at checkout time. Limio validates these rules before creating the order — if they fail, the checkout will error.
* **Matching initial term.** All offers with at least one recurring charge must share the same initial term length (for example all 12-month, or all 1-year).
* **Matching renewal term.** Same constraint for renewal term length.
* **Same start date.** All offers must have the same start date.
One-time-only offers — those with no recurring charge — are exempt from the term-matching check and can always be included in the basket alongside termed offers.
Per-charge billing frequencies (the cadence inside an offer's price configuration) can still differ between offers in the same subscription. For example, one offer can have a yearly hardware fee and another can have a monthly software fee, as long as their initial and renewal terms match.
Add-ons are unaffected: they continue to attach to their parent offer exactly as they do in the default mode.
## Limitations
* The setting is tenant-wide; it cannot be enabled per-offer or per-page today.
* Mixing offers with different term lengths is not supported. If you need to sell products with different terms in the same flow, keep the default (one subscription per offer) behaviour.
---
# 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.limio.com/integrations/zuora-integration/manage-your-pricing/how-to-configure-subscriptions-in-limio-offers-with-initial-price-and-zuora-rate-plans/how-to-acquire-multiple-offers-in-a-single-subscription.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.