Overview
This article explains the various weighting settings against plan objects and how they are used.
Package Plan Weighting in Contract Pools
In the realm of contract pools, the weighting is used when a package subscription migration is performed. The following plan migration transitions are possible:
| Transition | Weighting |
|---|---|
| Upgrade | When a customer migrates from a plan with a given weighting to a plan of a higher weighting. |
| Crossgrade | When a customer migrates from a plan with a given weighting to a plan of the same weighting. |
| Downgrade | When a customer migrates from a plan with a given weighting to a plan of a lower weighting. |
Example Weightings and Results
In the example above, the system would behave as follows
| Migrates from | Migrates to | Result |
|---|---|---|
| Emersion Email Domain - Sell Package Plan (w: 10) | Test domain sell (w: 20) | Upgrade |
| Test domain sell (w: 20) | Domain Registration - Sell Package Plan (w: 20) | Crossgrade |
| RedGum Domain Registration (12m) (w: 50) | Domain Registration - Sell Package Plan (w: 20) | Downgrade |
Bolt-on Add-on Weighting
Bolt on add-ons cab be weighted to give service providers control over the order of bolt on add-ons. Put another way, if an end user subscribes to multiple add-ons under a bolt-on, the weight will be used to determine the sequence of subscriptions.
Preference is given to weights of a higher number.
For example, in the case of 3 bolt on add-on subscriptions, the order the subscriptions will be used is:
- Add On 1 – highest weight
- Add On 2 – next highest weight
- Add On 3 – lowest weight