> 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/managing-subscriptions/discount-a-subscription-contract.md).

# Discount a subscription contract

Apply a discount to one product or to the whole order on a live subscription contract, for a set number of cycles, forever, or for a single order.

You can discount an existing contract from the admin, without touching the plan or any other customer. It is the lever for retention offers, goodwill, and win-backs: the customer keeps their subscription and simply pays less.

There are two things to decide. **What it covers**, one product or the whole order. And **how long it lasts**, a set number of cycles, forever, or a single order.

### Discount one product, every cycle

Open the contract and find the product in the **Products** card. Click its `•••` menu and choose **Apply discount**.

The dialog is headed **Apply discount to** that product, and applies it to future orders in this subscription.

* **Discount title**, which defaults to `Product Discount`. This is the label shown against the discount in the admin, so name it something you will recognise later.
* **Discount type**, such as `Percentage off`.
* The **Percentage** or amount.
* **Duration**, either a number of cycles or **Never expires**.

Click **Add discount**.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FQCLNSeW2mYZZBNWtUvTy%2FScreenshot%202026-11-04%20at%202.44.33%E2%80%AFPM.png?alt=media&amp;token=4c8cb846-668f-4cff-97ca-8a6e2a8dc1db" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
One product discount per product. Once a product has one, **Apply discount** is no longer offered on that product's menu. Remove the existing discount first if you want to change it.
{% endhint %}

### Discount the whole order, every cycle

At the bottom of the **Products** card, click **Add Order Discount**. The dialog explains that it applies to the entire order subtotal for future cycles, and takes the same four fields: title, type, value and duration.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2F0lxN3yiI4vFOqafwoFv8%2FScreenshot%202026-11-04%20at%202.41.04%E2%80%AFPM.png?alt=media&amp;token=4a83da6b-62b9-41e9-b6e6-16f0a6fef1c1" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
One order discount per contract. Once one exists, the **Add Order Discount** button disappears entirely, leaving Edit shipping rate, Add Free Shipping and Add Product.
{% endhint %}

### Discount a single order

Both of the above repeat. To discount one upcoming order and nothing else, work from **Orders → Upcoming** instead and expand the order you want.

* **For one product on that order**, open the product's `•••` menu and choose **Apply discount**. The dialog is headed **Apply discount to** that product **on order #9**, and confirms: *This discount will apply to this product on order #9 only — the subscription itself will remain unchanged.*
* **For that whole order**, use the order's own `•••` menu. The dialog is headed **Apply discount to order #9**, with the same confirmation.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2Fm10QZYqv0PkvqqstW3I9%2FScreenshot%202026-11-04%20at%203.56.43%E2%80%AFPM.png?alt=media&amp;token=f8097156-6dcc-41a8-b3f8-78bf08c0190b" alt=""><figcaption></figcaption></figure>

Both take a title, a type and a value, then **Apply discount**.

{% hint style="info" %}
Neither has a **Duration** field. A one-time discount only ever covers the order you opened it from, so there is nothing to set.
{% endhint %}

This is the right tool for a goodwill gesture on a single delivery. Use the contract-level discounts above when the customer should keep paying less.

### How the totals are calculated

The order of operations matters, and it follows Shopify's: **product discounts come off the line items first, the subtotal is recalculated, and the order discount applies to that reduced subtotal.**

On a contract with a Body Wash at `NZ$53.10` and a Body Exfoliator at `NZ$61.20`:

| Line                                         | Amount      |
| -------------------------------------------- | ----------- |
| Products                                     | `NZ$114.30` |
| Product Discount, 10% on the Body Exfoliator | `-NZ$6.12`  |
| **Subtotal**                                 | `NZ$108.18` |
| Order Discount, 10%                          | `-NZ$10.81` |
| Shipping                                     | `NZ$12.00`  |
| **Total**                                    | `NZ$109.37` |

The order discount is 10% of `108.18`, not of `114.30`.

{% hint style="warning" %}
Worth knowing before you offer both. A 10% product discount plus a 10% order discount is not 20% off. On the figures above the customer saves `NZ$16.93` on `NZ$114.30`, which is closer to 15%.
{% endhint %}

### Reading the discounts on the contract

Each discount gets its own row, with a badge showing how long it has left and a **Remove** link beside it.

* **Never expires** shows as a green badge.
* A cycle-limited discount shows a blue badge counting down, for example `3 of 3 cycles remaining`.
* A single-order discount shows a blue **One-time** badge.

A product discount row also names the product it applies to, for example `Product Discount · 10% (on Body Wash)`.

**Remove** sits next to the badge on the discount row itself, not in the product's `•••` menu.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2Fl3D6LOOFTRlyCeLj5s7O%2FScreenshot%202026-11-04%20at%202.42.40%E2%80%AFPM.png?alt=media&amp;token=04f48a3b-8bf1-4379-a489-23b448a8355d" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
When a cycle-limited discount runs out it disappears from the contract rather than lingering as expired, the same way shipping discounts behave.
{% endhint %}

### What lands on each upcoming order

Open **Orders → Upcoming** and expand an order to see the discounts applied to that specific cycle, alongside anything else attached to it.

A single order can carry several at once: a product discount, a loyalty point redemption, an order discount, and a discounted one-time add-on, each on its own row with its own badge. One-time items are marked **One-time** so they are easy to tell apart from the recurring ones.

A cycle-limited discount only appears on the orders it actually covers. Set it to 3 cycles and the fourth upcoming order simply will not show it.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FLzSqd1eqJ440WO5Srg1w%2FScreenshot%202026-11-04%20at%204.00.27%E2%80%AFPM.png?alt=media&amp;token=a2d93d79-5248-46fd-bc06-fb4799065ba9" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Discounts can only be added to cycles that have not been billed yet. An order that has already been built will not accept a new discount.
{% endhint %}

### When two discounts land on the same product

A product can end up carrying both a recurring discount and a one-time discount on the same order. The usual route is adding the one-time discount first and the contract-level one afterwards.

Roadmap allows it rather than blocking it, and flags it above the Upcoming list:

> **The order on 16 Nov 2026 has multiple discounts on the same product**\
> A one-time discount and a subscription discount both apply to this order. This can be intended. If it is not, remove the one-time discount on the order below.

The order's date also carries a warning icon, so you can spot which cycle it refers to.

Both discounts appear in that order's rows, the recurring one with its cycles badge and the one-time one with a **One-time** badge and its own **Remove**.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2F3Fajgr8VFlU8xYiF9mdO%2FScreenshot%202026-11-04%20at%202.48.35%E2%80%AFPM.png?alt=media&amp;token=42c43b9b-69bb-4981-9b56-c5557a5a299c" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The two apply in sequence, not together. Each is calculated on the price left by the one before it. On a `NZ$53.10` product, a 10% recurring discount takes `NZ$5.31`, then the 10% one-time discount takes 10% of the remaining `NZ$47.79`, which is `NZ$4.77`. The customer saves `NZ$10.08`, not `NZ$10.62`.
{% endhint %}

Only the one-time discount offers **Remove** here. The recurring one belongs to the contract rather than to this order, so it is removed from the Products card above.

### What the customer sees

Contract discounts appear on the customer's own subscription dashboard, described as **additional** savings on top of their usual subscriber price, with a line stating how many orders the discount has left.

For the full picture of how every saving renders on that screen, including plan discounts, add-on offers and loyalty redemptions, see [How discounts show on a customer's subscription](https://docs.roadmap.so/subscriptions/storefront-and-accounts/how-discounts-show-on-a-customers-subscription.md).

### Timeline

Every discount is recorded on the contract's timeline with the amount, the scope, the duration and who added it:

* `Order discount of 10% off applied to all future orders, added by you@yourstore.com.`
* `Product discount of 10% off applied to Body Exfoliator for the next 3 orders, added by you@yourstore.com.`

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2F8bsRhQgkN7l9OLe6JgEs%2FScreenshot%202026-11-04%20at%202.42.51%E2%80%AFPM.png?alt=media&amp;token=91275aa7-840f-45ba-ad7c-aeed0ce21700" alt="" width="563"><figcaption></figcaption></figure>

Because a customer cannot add these themselves, the timeline is how you tell which team member applied a discount and when. See [The Subscription Activity Timeline](https://docs.roadmap.so/subscriptions/managing-subscriptions/the-subscription-activity-timeline.md).

### Related guides

* [How discounts show on a customer's subscription](https://docs.roadmap.so/subscriptions/storefront-and-accounts/how-discounts-show-on-a-customers-subscription.md)
* [Rewarding a subscriber with free shipping](https://docs.roadmap.so/subscriptions/managing-subscriptions/rewarding-a-subscriber-with-free-shipping.md)
* [Offer one-off products at a discount](https://docs.roadmap.so/subscriptions/getting-started/offer-one-off-products-at-a-discount.md)
* [Adjusting an upcoming subscription order](https://docs.roadmap.so/subscriptions/managing-subscriptions/adjusting-an-upcoming-subscription-order.md)
* [Loyalty points × subscriptions](https://docs.roadmap.so/subscriptions/storefront-and-accounts/loyalty-points-subscriptions.md)
* [The Subscription Activity Timeline](https://docs.roadmap.so/subscriptions/managing-subscriptions/the-subscription-activity-timeline.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.roadmap.so/subscriptions/managing-subscriptions/discount-a-subscription-contract.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
