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

# Reseller Policies

The **Reseller Policies** space enables Resellers (Service Providers) to manage key operational and compliance settings that apply to their integrations with Merchants. This area allows Resellers to enforce policies that promote consistency, operational efficiency, and regulatory compliance.

In the **Reseller Policies** space, you can configure the following:

* Upgrade, downgrade, and cancellation policies
* Approval of Merchant-initiated requests
* The eligibility service
* Data compliance settings

**Note:** These settings are only available when using the [Platform-managed](g_platformManagedFlow) product lifecycle.

## Upgrade, Downgrade, and Cancel

**Note:** This feature is only available if you also have the Commerce Engine component enabled.

[Easily manage upgrade, downgrade, and cancellation policies](r_upgradeDowngradeCancelManage) across all services. Effective policy management improves the customer experience and helps protect revenue by ensuring consistent handling of change requests.

You can choose the default behavior for product upgrades, downgrades, and cancellations. Product upgrades, downgrades, and cancellations can go into effect:

* Immediately
* At the end of the cycle

Proration can be enabled for upgrades, downgrades, and cancellations. When the customer upgrades the product, you can ask the customer to make a prorated payment. In the case of a product downgrade or cancellation, you can make the customer eligible for a prorated refund. When there's an update request, the request is processed according to the action that occurred. For example, if a product was removed from a subscription bundle, it would be treated as a cancellation and processed accordingly.

**Note:** Some Resellers (Service Providers) have upgrade, downgrade, and cancellation policies enabled as a part of their API requests. When this is the case, any settings chosen on the **Upgrade, Downgrade, and Cancel** page won't take effect.

If settings aren't configured, the defaults are:​​​​

* Upgrades go into effect immediately​
* ​​​Downgrades and cancellations go into effect at the end of the cycle
* ​​​​Proration is turned off.

## Merchant-Initiated Requests

[Automatically approve Merchants' API requests to upgrade and downgrade subscriptions](r_merchantInitiatedUpdatesManage). When this feature is enabled, product upgrades and downgrades can be processed immediately—without requiring an approval workflow.

The automatic approval feature can be turned on or off for each Merchant at a time.

## Eligibility Service

The [eligibility service](r_eligibilityServiceManage) works with Commerce Engine to determine customer eligibility for products, campaign discounts, and billing plans. For example, the eligibility service could determine whether a customer is eligible to upgrade a certain product or receive a discount based on eligibility criteria. This service plays a key role in enabling targeted offers and eligibility-based promotions, ultimately driving subscription purchases, increasing revenue, and improving customer retention.

By default, the eligibility service is off.

**Note:** To use this service, you must have Commerce Engine.

For information about [campaign discounts](../../Commerce_Engine_User_Guide/topics/campaignAbout) and [billing plans](../../Commerce_Engine_User_Guide/topics/billingPlanAbout), see the [Commerce Engine User Guide](../../Commerce_Engine_User_Guide/topics/guideIntro).

## Data Compliance

[Easily obfuscate customer PII (Personally Identifiable Information)](r_dataComplianceManage) that is returned during subscription creation, subscription cancellation, and account validation requests.

By default, the following fields are stored:

* Mobile Identifier (**MSISDN**)
* Email Address (**EMAIL**)
* Billing Account Number (**BAN**)
* Electronic Serial Number (**ESN**)
* Set-Top Box Token (**STBTOKEN**)

Obfuscating PII can aid in protecting customer data and help your organization comply with privacy regulations such as GDPR.

**Note:** This setting does not override other configurations where you may have chosen to store PII data, such as allowlist attributes.

* **[Manage Upgrades, Downgrades, and Cancellations](r_upgradeDowngradeCancelManage)**

* **[Manage Merchant-Initiated Requests](r_merchantInitiatedUpdatesManage)**

* **[Manage the Eligibility Service](r_eligibilityServiceManage)**

* **[Manage Data Compliance](r_dataComplianceManage)**

**Parent topic:**[Platform Settings](r_platformSettingsAbout)


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