Configure quantity change rules

Introduction

This article explains how to configure post-purchase restrictions for Subscription modifications in Product Management. These restrictions enable Vendors to control whether Customers can increase or decrease Quantities after purchase, which is particularly useful for enforcing Commitment Period requirements or other business rules.

In this article:

• Understanding post-purchase restrictions
• Configuring restrictions in the Design section
• Setting up restriction rules
• Allowed options configuration
• Bypass in operation settings

Understanding post-purchase restrictions

Post-purchase restrictions allow Vendors to configure whether Customers can modify Subscription Quantities after the initial purchase. This feature provides control over Subscription changes and helps enforce business policies such as Commitment Periods or minimum purchase requirements.

Common use cases

• Preventing Quantity decreases during Commitment Periods
• Enforcing minimum License counts
• Restricting changes based on Billing Cycle or Term Duration
• Implementing cancellation policies

Configuring restrictions in the Design section

Step 1: Access the Design section

1. Navigate to Product Management and select your Offer.
2. Select the Design tab.
3. Locate the control you want to restrict from the control list.

Step 2: Select the control to restrict

Post-purchase restrictions can be configured for the following control types created in the Design section:

• Text
• Number
• Checkbox
• Date
• Radio
• Dropdown

Step 3: Enable restrictions

1. Select the control you want to restrict (for example, "Quantity").
2. In the Properties panel on the right sidebar, scroll to the "After Purchase" section.
3. Enable the "Add restrictions" checkbox.

Once enabled, you can configure detailed restriction rules in the Post-purchase tab.

Setting up restriction rules

Step 4: Configure Post-Purchase restrictions

1. Navigate to the Post-purchase tab in Product Management.
2. In the "Post-Purchase restrictions" section, configure the following:

Restrictions for [Control Name]: The section header indicates which control the restrictions apply to (for example, "Restrictions for Quantity").

Depends on field: Select the field that determines when restrictions apply. For example, "Charge Period" makes restrictions conditional based on the Billing Frequency.

Charge Period dropdown: Select the Billing Cycle values that trigger the restrictions (for example, Monthly, Annual Billing, Triennial).

Allowed options configuration

Step 5: Define allowed modification scenarios

The "Allowed options" section controls how Customers can modify the control value after purchase:

Select none: Makes all options of the control unavailable for editing. Customers cannot modify the control value in any way after purchase.

Select all: Makes all options of the control available for editing. Customers have full flexibility to modify the control value after purchase.

Conditional increase/decrease: You can configure specific conditions under which Customers can increase or decrease values:

Can increase when "[Depends on field]" equals: Select the conditions under which Customers can increase the value. For example, select "Monthly" and "Annually" to allow increases when the Billing Cycle is either Monthly or Annual Billing.

Can decrease when "[Depends on field]" equals: Select the conditions under which Customers can decrease the value. For example, leave both "Monthly" and "Annually" unselected to prevent any decreases regardless of Billing Cycle.

Based on these selections, Customers can save changes to a Subscription with a higher or lower value than the most recent configuration, according to the rules you defined.

Bypass in operation settings

Step 6: Configure bypass operations

The "Bypass In Operation" option allows you to specify provisioning operations for which the restriction should be ignored:

What it does: When you select specific operations (such as CancelOrder, PurchaseOrder), the restriction will not apply during those operations. This allows Customers to complete the Order despite the configured restrictions.

Example use case: You can implement a special cancellation policy by selecting CancelOrder as a bypass operation. As a result, Customers will be allowed to cancel the Subscription during the cancellation policy period despite all Commitment Period-related restrictions you configured in Product Management.

How to configure

1. In the Post-Purchase restrictions section, locate the "Bypass In Operation" option.
2. Select the provisioning operations that should bypass the restriction (for example, CancelOrder).
3. Multiple operations can be selected if needed.

This feature provides flexibility to enforce business rules while still allowing specific actions that align with your policies.

Summary

Post-purchase restrictions enable Vendors to control how Customers can modify Subscriptions after purchase. Product Managers configure restrictions by enabling "Add restrictions" for controls in the Design section, then defining detailed rules in the Post-purchase tab. Restrictions can depend on fields like Charge Period and control whether Customers can increase or decrease values under specific conditions. The "Allowed options" section provides granular control over modification permissions, while the "Bypass In Operation" feature allows specific provisioning operations to ignore restrictions. These tools enable Vendors to enforce Commitment Periods, implement cancellation policies, and maintain business rules while providing appropriate flexibility for Customers.