> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Stacked Discount Merchant Options Configuration

Subscribe **Stackable Discounts** lets you offer multiple discounts per subscription using either promotional or coupon campaigns. Merchants can define whether specific campaigns can be combined or not. Using flexible configuration options, merchants have full control of the discount order and can decide whether the discounts application (and their order) benefit the merchant or the customer. In order to prevent abuse of combined discounts, merchants can set maximal redemptions allowed per subscription and per customer.

**Note:** The order of the merchant options shown below is important. Higher placed merchant options will supersede the lower ones when a conflict occurs.

| Field Name | Values | Description |
| - | - | - |
| DISCOUNTING\_MODEL | - **1 or null** (Single campaign discounts i.e. Disco1 using 20190501) - **2** (Multiple campaign discounting i.e. Disco 2 using REST 20210401) | This field enforces to utilize the appropriate REST version. E.g- If a user uses a 20190501 rest call and the discounting\_model is set to 2, the system will send an error. **Important:** |
| DISCOUNT\_APPLICATION\_RULE\_ID | - **1** Single Only - **2** Relative First - **3** Fixed First | **Note:** This field is relevant only when DISCOUNTING\_MODEL is set to 2. This option allows merchants to define the discount application order to a subscription or transaction or their relevant items. This is a generic order for all stackable discounts and will impact the discount amount. - **Single only** allows to redeem only a single discount per Subscription/Transaction/Charge. - **Relative first** means that percentage based discounts will be the first ones applied when multiple discounts are redeemed. - **Fixed first** means that fixed price discounts will be the first ones applied when multiple discounts are redeemed. |
| RELATIVE\_DISCOUNT\_RULE\_ID | - **1** Direct First - **2**Compounded First | **Note:** This field is relevant only when DISCOUNTING\_MODEL is set to 2. This option allows merchants to define the order of applying the **percentage** discounts. For stackable discounts, percentage-based campaigns are associated a discount method (in the campaign object) which is either **Direct** (applied to the original price of the subscription/transaction/items) or **Compounded** (applied to the discounted price of the items).This is a generic field for all the merchant's stackable discounts and will impact the discount amount. - **Direct first** means that campaigns defined as Direct discount method are applied first (to the full amount of the subscription/Transaction/Item) - **Compounded first** means that campaigns defined as compounded discount method are applied first (to the discounted amount of the subscription/Transaction/Item) |
| DISCOUNT\_SORTING\_RULE\_ID | - **1** Lowest First - **2** Highest First | **Note:** This field is relevant only when DISCOUNTING\_MODEL is set to 2. This option allows merchants to define the order of the discounts by their discount value or percentage. Lowest/Highest First: - For percentage discounts - lowest/highest first means lowest/highest percentage applied first. - For flat amount discounts - lowest/highest first means lowest/highest flat amount applied first. |
| **Parent topic:**[Feature](../topics/featureConfigurationAbout) | | |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.