> 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/offer-one-off-products-at-a-discount.md).

# Offer one-off products at a discount

Discount the products customers add as one-time additions to an upcoming order, with separate offers for different groups of customers.

One-off products are the items a customer can add as a one-time addition to an upcoming subscription order. You can discount them, and you can discount them differently for different customers.

This is a useful lever for add-ons. A subscriber topping up their next box is already committed to the order, so a small saving on an extra item is cheap incremental revenue.

### Where to set it up

Open the subscription plan and find the **One-off products** card.

That card already controls which products customers can add at all, through **Available products** and **Include unlisted products**. Those are covered in [How to set up a subscription plan](https://docs.roadmap.so/subscriptions/getting-started/how-to-set-up-a-subscription-plan.md).

To start discounting, tick **Offer one-off products at a discount**. Your offers appear underneath, each with an edit and a delete icon, and an **Add offer** button below them.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2Fne9kYlSQkZUOy8JV6XqH%2FScreenshot%202026-11-04%20at%2011.59.35%E2%80%AFAM.png?alt=media&amp;token=9b9d5400-0ab2-4ef7-9398-217f2101b043" alt="" width="563"><figcaption></figcaption></figure>

### How offers work

An offer is a discount plus the group of customers it applies to. You can run several at once.

{% hint style="info" %}
Customers receive the **best discount among the offers they match**. Offers never stack, so a customer who qualifies for both a 10% offer and a 50% offer gets 50%, not 60%.
{% endhint %}

That makes the pattern straightforward: set a baseline offer for everyone, then add richer offers for the groups you want to treat better. You do not need to exclude anyone from the baseline, because the better offer simply wins.

### Add an offer

Click **Add offer**.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FfHwSNhfWYwhjOKjAPLZJ%2FScreenshot%202026-11-04%20at%2012.00.41%E2%80%AFPM.png?alt=media&amp;token=df055418-a08a-4994-9aca-529de388ddbb" alt="" width="375"><figcaption></figcaption></figure>

{% stepper %}
{% step %}

#### Set the discount

Enter the **Discount** amount and choose the **Type**, a percentage or a fixed amount off.
{% endstep %}

{% step %}

#### Choose who gets it

**Customer eligibility** is a choice of five. Three of them open a second field once selected.

* **All customers**
* **Customers tagged with**, then nominate a Shopify customer tag
* **Customers NOT tagged with**, the inverse of the above
* **Members**, then pick one or more **membership tiers**, so the offer reaches only customers in those tiers
* **Non-members**, for customers who are not in your loyalty program

Tags are your own Shopify customer tags, and customers never see them.
{% endstep %}

{% step %}

#### Write the customer-facing copy, or leave it

Both copy fields are optional, and both fall back to a standard message if you leave them blank.

**Customer-facing label** is the headline eligible customers see in the picker and on their order, for example `Save 50% on add-ons`.

**Customer-facing description** is the supporting line underneath, for example `Add a product to your next order and save.`
{% endstep %}

{% step %}

#### Save it

Click **Add offer**. It appears in the list on the plan showing the discount, that it is standing, and who it applies to, for example **50% off**, *Standing · All customers*.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
If you write your own description and mention the discount amount in it, update it whenever you change the offer. The standard description always shows the current discount. Your own wording does not.
{% endhint %}

To change an offer later, click its edit icon. The **Edit offer** dialog is the same form, with **Delete offer** alongside **Save**.

### Tiered offers without tiered admin

Because only the best matching offer applies, membership tiers are easy to reward without building a rule for every combination.

Set one offer at **All customers** for your baseline, then add a richer offer for **Members** in your upper tiers. A Gold customer matches both and receives the better one. Nobody needs excluding from the baseline, and adding a tier later does not mean revisiting the offers you already have.

### What customers see

The offer shows up in two places on the customer's subscription dashboard.

**In the product picker.** When a customer opens **Add to next order only**, your label and description appear as a callout above the product list, and every product is priced with the discount applied and the original price struck through.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2Fob3IkH5B05rguPFBacap%2FScreenshot%202026-11-04%20at%2012.10.10%E2%80%AFPM.png?alt=media&amp;token=ec4c85b8-ee83-4033-a18f-577880c51c2a" alt="" width="375"><figcaption></figcaption></figure>

**On the upcoming order.** Once a product is added, its line carries a **Next order only** badge, the discounted price with the original struck through, a badge showing the discount, and a line naming the offer.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FPRS1pMKZFFfIJFqK9t6U%2FScreenshot%202026-11-04%20at%2012.09.44%E2%80%AFPM.png?alt=media&amp;token=5dd2bc13-ea83-4786-87d0-c4aba2fe6c3f" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
The offer applies to the one-time addition only, not to the subscribed products on the same order. So a contract with a 10% subscription discount and a 50% add-on offer shows both at once: the subscription line at 10% off, and the added product at 50% off.
{% endhint %}

Customers who match no offer see the normal price, with no callout and no mention of a discount they cannot have.

### What you see in the admin

Offers are visible on the subscription contract too, so you can add a product for a customer and see exactly which offer they are getting.

**Adding a product on their behalf.** **Add Product** on the contract opens **Select Product & Variant**. A banner under the search names the offer that applies to this customer, for example `50% off · Standing · All customers · their best available offer`, and every variant is listed at its discounted price with the original struck through.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FmcftJZZRrgH1UEIRm2Au%2FScreenshot%202026-11-04%20at%2012.13.16%E2%80%AFPM.png?alt=media&amp;token=24271023-f333-4e40-a6c4-fd9b1b5291f8" alt="" width="563"><figcaption></figcaption></figure>

**On the upcoming order.** The added line carries a **One-time** badge and a discount badge, with the offer named underneath it and the price struck through, so a discounted add-on is never mistaken for a mispriced subscription product.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2F4UWMK4eFDCHEksyHIahN%2FScreenshot%202026-11-04%20at%2012.14.25%E2%80%AFPM.png?alt=media&amp;token=41b037c4-3ded-458b-8fb4-a0d22831915e" alt="" width="563"><figcaption></figcaption></figure>

#### Why a customer is getting a particular offer

The **Loyalty Points** card on the contract answers this. It shows the customer's **Points**, their **Tier**, and their **Offer tags**.

<figure><img src="https://393112916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ8asLD4FVCFagK40xEr4%2Fuploads%2FVlET3GL55AqruZqCLpVH%2FScreenshot%202026-11-04%20at%2012.17.39%E2%80%AFPM.png?alt=media&amp;token=0a8134e1-a5e4-4af2-8b1d-90c028947c8c" alt=""><figcaption></figcaption></figure>

**Offer tags** are the tags on that customer which this plan's one-off offers actually look for. They come from offers set to **Customers tagged with** or **Customers NOT tagged with**, and they decide which of those offers the customer gets on one-time add-ons.

* **None** means the customer has none of the tags your offers look for.
* Tags that no offer uses, such as tier tags, are not listed.

Read it alongside **Tier** on the same card: between them, the tier explains any **Members** offer and the offer tags explain any tag-based one. That is the fastest answer to "why is this customer seeing this discount", without opening the plan to work it out.

### Related guides

* [How to set up a subscription plan](https://docs.roadmap.so/subscriptions/getting-started/how-to-set-up-a-subscription-plan.md)
* [Adjusting an upcoming subscription order](https://docs.roadmap.so/subscriptions/managing-subscriptions/adjusting-an-upcoming-subscription-order.md)
* [The customer subscription dashboard: a tour](https://docs.roadmap.so/subscriptions/storefront-and-accounts/the-customer-subscription-dashboard-a-tour.md)
* [Shipping discounts for subscription orders](https://docs.roadmap.so/subscriptions/getting-started/shipping-discounts-for-subscription-orders.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/getting-started/offer-one-off-products-at-a-discount.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.
