> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/subscriptions/getting-started/same-day-subscription-bundling.md).

# Same-day subscription bundling

Combine a customer's same-day subscription renewals into one order with one charge and one order number: every rule that decides whether subscriptions combine, how shipping and discounts carry over, a

When a customer has more than one subscription due to bill on the same day, **Combine Same-Day Orders** merges them into a single order, with one charge and one order number.

That means fewer duplicate shipping charges, less transaction noise, and a cleaner order history for the customer.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FpfCxiANCWFWDS0g8UKCS%2FScreenshot%202026-09-17%20at%2010.38.21%E2%80%AFPM.png?alt=media&amp;token=eec2d34f-05a7-42b2-b1f6-fe01b8a769bd" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Combining is off until you turn it on, so nothing changes for your existing contracts until you enable it and save.
{% endhint %}

### Turn on combining

{% stepper %}
{% step %}

#### Open Billing Settings

Go to **Billing Settings** and find **Combine Same-Day Orders**. The pill beside the heading shows whether it's currently enabled.
{% endstep %}

{% step %}

#### Enable it

Check **Combine same-day subscription orders**. Subscriptions billing on the same day are then charged and shipped as one order. Left off, every subscription always generates its own order.
{% endstep %}

{% step %}

#### Save your changes

Click **Save Settings** in the top-right.
{% endstep %}
{% endstepper %}

If you change this setting on a live billing day, save it before renewals start processing.

### What combines

**Subscriptions on the same schedule.** Subscriptions with the same frequency, for example two monthly subscriptions started on the same day, bill together every cycle. The customer gets one order and one charge each cycle, with all products included.

**Subscriptions on different schedules.** Subscriptions with different frequencies, for example one weekly and one monthly, combine only on the days their billing dates coincide. Each subscription keeps its own schedule and next billing date: combining an order never changes when a subscription renews next.

**Subscriptions going to different addresses.** A combined order has one delivery address, so only subscriptions delivering to the same address and recipient are combined. A customer who sends one subscription home and another to the office receives a separate order for each, delivered where it should go.

## Why subscriptions did or didn't combine

Use this section to explain any combined order, or any pair of orders that a customer expected to arrive as one.

### Every condition that has to be true

Two or more subscriptions combine into one order only when **all** of these hold:

1. **Combine same-day subscription orders** is enabled and saved in Billing Settings.
2. They belong to the **same customer**.
3. Their billing dates fall on the **same day**. Subscriptions on different frequencies only qualify on the days their dates happen to coincide.
4. They deliver to the **same address and the same recipient**.
5. Each subscription is **active**, not cancelled.
6. The products on each subscription are **in stock** that day.
7. At least one subscription in the group has a **valid payment method** to carry the charge.

Miss any one of these and the subscriptions bill on their own, each generating its own order as it normally would.

### Reasons a subscription is billed on its own

| What you're seeing                                            | Why it happened                                                                                                                                                          |
| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Two orders on the same day, different delivery addresses      | A combined order has a single delivery address, so subscriptions going to different addresses or recipients are never combined. Each is delivered where it should go.    |
| Two orders on the same day, same address                      | Something dropped one subscription out of the group. Check its timeline: the most common causes are an out-of-stock product or a cancelled contract.                     |
| A subscription was left out of an otherwise combined order    | Its products were out of stock that day. It drops out, enters dunning, and its timeline records that the combination failed. The rest of the group processes without it. |
| A cancelled subscription didn't combine                       | Cancelled contracts are never pulled into a combined order.                                                                                                              |
| Nothing is combining at all                                   | Combining is off, or the change wasn't saved. Check the pill beside **Combine Same-Day Orders** in Billing Settings.                                                     |
| Subscriptions on different frequencies rarely combine         | That's expected. They combine only on the days their billing dates coincide, which for a weekly and a monthly subscription is occasional by nature.                      |
| The customer expected combining but their dates never line up | Combining never moves a billing date. If two subscriptions are scheduled days apart, they simply never qualify.                                                          |

### What doesn't stop a subscription combining

These are the assumptions that most often send people looking in the wrong place:

* **An expired or failing card.** The subscription still joins the group. Roadmap bills the combined order against a subscription that has a valid payment method, so one bad card doesn't strand the rest.
* **Being in dunning.** A subscription already retrying can still be combined. It just won't be the one chosen to carry the charge if it's on its final retry.
* **Different billing frequencies.** Different schedules combine whenever their dates coincide; they're only excluded on the days they don't.
* **Discounts on a subscription.** Discounted subscriptions combine like any other, and their discounts carry into the order.
* **Different products or quantities.** Nothing about the contents affects whether subscriptions combine.

### Where the answer is recorded

Every subscription's timeline records what happened to it that billing day, and it's the authority when you're reconstructing an order:

* When a combination worked: *Order #2711 was billed successfully by combining this subscription with subscriptions #49996366111, #49976377631 into a single order.*

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FzGvokJZqpeicw6qz0Xe0%2FScreenshot%202026-09-17%20at%2010.25.56%E2%80%AFPM.png?alt=media&amp;token=8cd1d298-84cc-499a-a00e-e185fcf58b1a" alt="" width="337"><figcaption></figcaption></figure>

* When it didn't: *Attempted to combine this subscription with subscription #49996366111 for billing, but the combination failed. This subscription will be billed separately.*

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2Ffe8IqLNFjtZag0EpVGhS%2FScreenshot%202026-09-17%20at%2010.25.32%E2%80%AFPM.png?alt=media&amp;token=a37fba5a-01c4-4570-aec8-b49810baad5f" alt="" width="332"><figcaption></figcaption></figure>

### How combining works

When the setting is on, Roadmap:

1. Finds all billing cycles due that day for the same customer.
2. Groups them by billing date, delivery address, and recipient.
3. Picks a subscription in the group with a valid payment method to carry the charge.
4. Creates one order with the line items from every subscription in the group.
5. Keeps that order linked to each subscription it came from.

Each subscription keeps its own record, its own schedule, and its own cycle numbering, so its past and upcoming cycles still read in sequence whether it billed alone or as part of a combined order. Discounts are tracked per subscription as normal.

### Shipping and discounts

A combined order always takes the **best shipping offer** among the subscriptions in it, so the customer is never worse off for having their orders combined. If one subscription in the group carries free shipping, the combined order ships free.

Each subscription's own discount usage still counts up as normal, so a discount limited to a number of cycles decrements for that subscription when the combined order processes.

{% hint style="info" %}
On the Shopify order, a combined shipping benefit appears as a fixed-amount **order** discount rather than a shipping discount, with the value matching the shipping it covers.
{% endhint %}

### How a combined order shows in the admin

**In Shopify**, the order is tagged so you can find and report on it:

* `bundled-subscription-order` marks it as a combined subscription order.
* A `subscription:<id>` tag is added for each subscription included, so every contract in the order is identifiable from the order itself.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2F1RKIOawyMZSrmsvkSDtP%2FScreenshot%202026-09-17%20at%2010.26.36%E2%80%AFPM.png?alt=media&amp;token=98860e28-3277-46c0-b1f5-961a4e3bdae5" alt="" width="337"><figcaption></figcaption></figure>

**On the subscription**, the cycle that combined carries a blue **Bundled** badge beside its date, next to the order number and total. Cycles that billed on their own show **Billed** instead.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FnjPbyeAzMhzYcehn4cmD%2FScreenshot%202026-09-17%20at%2010.26.09%E2%80%AFPM.png?alt=media&amp;token=4deea8de-88ae-40ae-80fd-3d84daf5ac05" alt="" width="563"><figcaption></figcaption></figure>

**On the timeline**, each subscription records the combined order or the failed attempt, in the wording shown above.

### Frequently asked questions

<details>

<summary>Why did my customer receive two orders on the same day?</summary>

The most common reason is that the subscriptions deliver to different addresses or recipients, which always bill separately so each parcel goes where it should.

If they share an address, something dropped one subscription out of the group. Open that subscription's timeline: it records the failed combination. Usual causes are an out-of-stock product or a cancelled contract.

</details>

<details>

<summary>Why didn't two subscriptions combine even though they're both active?</summary>

Work through the conditions: combining enabled and saved, same customer, same billing day, same address and recipient, both active, products in stock, and at least one valid payment method in the group. Missing any one of them means each subscription bills on its own.

</details>

<details>

<summary>Why did a subscription with an expired card still get combined?</summary>

That's intended. A failing card doesn't exclude a subscription. Roadmap bills the combined order against a subscription in the group that has a valid payment method, so the rest of the customer's order isn't held up by one bad card.

</details>

<details>

<summary>Does combining change the customer's renewal dates?</summary>

No. Combining only changes how orders are created when billing dates already overlap. Each subscription keeps its own schedule and next billing date.

</details>

<details>

<summary>Which shipping rate does the customer pay on a combined order?</summary>

The best offer among the subscriptions being combined. If any of them carries free shipping, the combined order ships free.

</details>

<details>

<summary>Why does the combined order show an order discount instead of a shipping discount?</summary>

That's how a combined shipping benefit is applied. It appears as a fixed-amount order discount, with the value matching the shipping it covers, so the customer pays the same either way.

</details>

<details>

<summary>Why do the cycle numbers differ between subscriptions in the same order?</summary>

Each subscription counts its own cycles independently, whether it billed alone or as part of a combined order, so two subscriptions in one order can legitimately be at different points in their own sequences.

</details>

<details>

<summary>How do I find combined orders in Shopify?</summary>

Filter or search on the `bundled-subscription-order` tag. Each order also carries a `subscription:<id>` tag for every subscription included in it.

</details>

### Related guides

* [Failed payment retries](/subscriptions/pricing-and-billing/failed-payment-retries.md)
* [The Subscription Activity Timeline](/subscriptions/managing-subscriptions/the-subscription-activity-timeline.md)
* [Updating a customer's payment method](/subscriptions/managing-subscriptions/updating-a-customers-payment-method.md)
* [Subscription auto-tagging](/subscriptions/getting-started/subscription-auto-tagging.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.roadmap.so/subscriptions/getting-started/same-day-subscription-bundling.md?ask=<question>&goal=<endgoal>
```

`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.
