> 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/discounts-and-gwp/using-gwp-and-discounts/create-an-order-discount.md).

# Create an order discount

Build automatic cart-level discounts for the whole order, then control who qualifies and which variants stay excluded.

Use an order discount when the whole basket should receive the offer.

This is the right fit for first-order offers, member-wide discounts, and broad cart incentives.

### What an order discount changes

An order discount applies at the order level.

It is broader than a product discount.

Use it when the rule should affect the cart as a whole, not only selected lines.

### Before you start

Decide these four things first:

* whether the offer should apply to every customer or a defined audience
* whether any variants should stay excluded
* whether the discount should be one flat value or tiered by quantity
* what note shoppers should see in cart

### Create the order discount

{% stepper %}
{% step %}

#### Open the discounts dashboard

Go to **Discounts / Gift with Purchase**.

Create a new discount and choose **Order Discount**.
{% endstep %}

{% step %}

#### Add the internal setup details

Enter a clear **Name**.

Set the **Status** to **Active** when you are ready to run it.
{% endstep %}

{% step %}

#### Exclude any variants that should never qualify

Use **Excluded variants** when parts of the catalog must stay out of the offer.

This is useful for low-margin items, gift cards, or products already covered by another promotion.
{% endstep %}

{% step %}

#### Set the discount value

Add the **Discount Note** if you want customer-facing cart messaging.

Choose the discount type, then enter the value.
{% endstep %}

{% step %}

#### Add tiers if needed

Use **Add Discount Tier** when the discount should change as quantity grows.

If your store shows **Tier application method**, choose **Flat** or **Cumulative** based on how the offer should scale.
{% endstep %}

{% step %}

#### Choose the qualifying customer group

Set **Customer Eligibility**.

Common options include **All customers**, **First time customers**, **Logged in only customers**, tagged customers, **Members**, and **Non-members**.
{% endstep %}

{% step %}

#### Set dates, save, and test

Choose the **Active Dates**, save the discount, then test with a fresh cart.
{% endstep %}
{% endstepper %}

### When to use excluded variants

Use exclusions when the order discount should stay broad but not truly sitewide.

This is often cleaner than building a narrow product rule from scratch.

Examples:

* keep gift cards out of the offer
* keep clearance variants out of the offer
* protect products already in a bundle or GWP campaign

### Flat vs cumulative tiers

Use **Flat** when the highest qualifying tier should control the whole discount.

Use **Cumulative** when the discount should step up progressively across bands.

{% hint style="info" %}
If the campaign message is simple, start with **Flat**.

It is easier to explain and easier to test.
{% endhint %}

### Use order discounts when

Choose an order discount when you want:

* one offer across most of the basket
* first-order or segment-wide incentives
* a simpler setup than product-by-product discount rules

If only selected items should change price, use a product discount instead.

### Shopify vs Roadmap for order discounts

Roadmap is best when the discount should be automatic and audience-aware.

Shopify is usually better when the shopper must enter a code or the rule should live fully inside Shopify's native discount stack.

### Test before launch

Run these three tests:

1. a cart that should not qualify
2. a cart that should qualify
3. a cart containing an excluded variant

If eligibility uses first-order status, tags, membership, or login status, test with a real customer account.

### Related guides

* [When to use Roadmap or Shopify for discounts](/discounts-and-gwp/using-gwp-and-discounts/when-to-use-roadmap-shopify-or-klaviyo-for-discounts.md)
* [Use tags for discount eligibility](/discounts-and-gwp/using-gwp-and-discounts/use-tags-for-discount-eligibility.md)
* [Run multiple discounts & GWPs](/discounts-and-gwp/using-gwp-and-discounts/run-multiple-discounts-and-gwps.md)
* [Discounts not applying correctly](/discounts-and-gwp/troubleshooting/discounts-not-applying-correctly.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/discounts-and-gwp/using-gwp-and-discounts/create-an-order-discount.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.