> 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/when-to-use-roadmap-shopify-or-klaviyo-for-discounts.md).

# When to use Roadmap, Shopify, or Klaviyo for discounts

Choose the right place to build a discount based on the rule, the audience, and where it needs to apply.

Roadmap, Shopify, and Klaviyo are complementary.

Use the platform that matches the job.

### Quick rule

Use **Roadmap** when the discount depends on cart logic, product combinations, or Roadmap-only audience controls.

Use **Shopify** when the discount should live as a native Shopify discount, especially for code entry and broader channel compatibility.

Use **Klaviyo coupons** when the flow itself needs to generate and send a unique code to each recipient.

### Use Roadmap when

Choose Roadmap when you need one or more of these:

* automatic offers based on product mix, bundles, tiers, or excluded variants
* audience targeting such as **Members**, **Non-members**, logged-in customers, or customer tags
* storefront messaging tied to the promotion, such as cart notes, upsell messaging, or supported product-page price previews

### Use Shopify when

Choose Shopify when you need one or more of these:

* a shopper-entered discount code or a promotion that should be managed as a native Shopify discount
* one discount setup that other Shopify-native workflows, channels, or apps should rely on directly
* a simple sitewide or collection-style sale that does not need Roadmap-specific logic

### Use Klaviyo coupons when

Choose Klaviyo coupons when you need one or more of these:

* a unique discount code generated inside an email or SMS flow
* one code per recipient, rather than one shared code for the whole campaign
* the incentive to be owned by flow logic such as abandoned checkout, winback, or post-purchase follow-up

{% hint style="info" %}
If the main requirement is `send a unique code from a Klaviyo flow`, use Klaviyo coupons.

This is usually the best fit for abandoned checkout incentives.
{% endhint %}

{% hint style="info" %}
If the requirement can be handled cleanly in Shopify, use Shopify.

Do not force a native discount workflow into Roadmap.
{% endhint %}

### Common examples

#### Use Roadmap

* `Buy any 3 from this set and get 20% off`
* `Members get an automatic cart discount`
* `Discount the whole order except these variants`

#### Use Shopify

* `Enter WELCOME10 at checkout`
* `Run a simple native sale without Roadmap-only targeting`
* `Keep the discount managed inside Shopify for broader reuse`

#### Use Klaviyo coupons

* `Send a unique discount in an abandoned checkout flow`
* `Give each winback recipient their own code`
* `Keep coupon creation and send timing inside Klaviyo`

### Abandoned checkout flows

If you want to send a unique discount inside an abandoned checkout flow, use **Klaviyo coupons** rather than Roadmap.

That setup is cleaner because Klaviyo owns:

* the flow trigger
* the send timing
* the recipient-level coupon generation

Roadmap is not the best tool for this use case.

Roadmap is stronger when the discount should apply automatically on site, or when the rule depends on Roadmap discount logic such as product combinations, eligibility, tiers, or exclusions.

### Product discounts vs order discounts in Roadmap

Use a **product discount** when only selected items should change price.

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

Use a **Gift with Purchase** when the reward is an added item, not only a price change.

### How to decide fast

Ask these four questions:

1. Does the rule depend on specific cart composition or Roadmap audience logic?
2. Does the discount need to be automatic, without code entry?
3. Does the discount need to be generated and sent by a Klaviyo flow?
4. Does the discount need to live natively in Shopify for other workflows?

If the answer is mostly **yes** to the first two, choose Roadmap.

If the answer is **yes** to the third, choose Klaviyo coupons.

If the answer is **yes** to the fourth, choose Shopify.

### If you run both together

Test the combined result with a fresh cart.

A Shopify code can change subtotal, quantity, or qualification.

That can stop a Roadmap offer from applying.

The same is true for a Klaviyo-issued coupon.

If the coupon reduces the cart below a threshold, a Roadmap offer can stop qualifying.

### Related guides

* [Create a product discount](/discounts-and-gwp/using-gwp-and-discounts/create-a-product-discount.md)
* [Create an order discount](/discounts-and-gwp/using-gwp-and-discounts/create-an-order-discount.md)
* [How to integrate Roadmap with Klaviyo](/reviews/integrations/klaviyo-review-integration/how-to-integrate-roadmap-with-klaviyo.md)
* [Gift with Purchase](/discounts-and-gwp/using-gwp-and-discounts/gift-with-purchase.md)
* [Discount codes with GWPs](/discounts-and-gwp/using-gwp-and-discounts/discount-codes-with-gwps.md)

### Official references

#### Shopify

* [Shopify discounts overview](https://help.shopify.com/en/manual/discounts)
* [Shopify discount combinations](https://help.shopify.com/en/manual/discounts/discount-combinations)

#### Klaviyo

* [Klaviyo Help Center](https://help.klaviyo.com/hc/en-us)
* [Klaviyo coupon docs search](https://help.klaviyo.com/hc/en-us/search?query=coupons)
* [Klaviyo flow docs search](https://help.klaviyo.com/hc/en-us/search?query=abandoned%20cart%20flow)


---

# 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/when-to-use-roadmap-shopify-or-klaviyo-for-discounts.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.
