Automatic Subscription Build
Automatic subscription building helps managing subscriptions if your business requires to deal with a large or variable – read: increasing – number of subscriptions.
The way to set up the subscription builder depends on the nature of your products, your sales use cases and the representation of your source data in Salesforce.
(1) Billing an account-specific set of products under some account-specific conditions → parent-child relationship
(2) Billing identical products on equal conditions to multiple accounts → master subscription
(3) Creating or updating subscriptions based on additional data or custom objects → data mapping
Used to bill an account-specific set of products under some account-specific conditions
To allow for individually configured items when building subscriptions, you can use objects that are in a parent-child relationship, like orders with order products. If set up accordingly, the subscription builder takes the parent object ( order) to produce the subscription, and the child objects ( order products) to produce the subscription items.
In order to create price tiers for items, JustOn also supports subchild relations. You can configure custom objects to hold the price tier information and relate them to the child objects via lookup or master-detail relations. The subscription builder then takes the subchild records to produce the price tiers for the subscription items.
Building subscriptions based on accordingly configured objects
When creating price tiers from subchild records, be aware of the following limitations:
- Some Salesforce objects are not allowed to be the target of a lookup relation, including, for example, Order Product. When using one of these objects to create subscription items, it is not possible to configure a subchild object for creating price tiers.
- When updating subscriptions automatically, any created price tiers are not included.
Used to bill identical products on equal conditions to multiple accounts
A master subscriptions is a subscription "model" that is copied for each target. The target is the object whose records are the basis for subscriptions, like accounts, contracts, cases, quotes, etc. If set up accordingly, the subscription builder can generate an individual subscription for each new account, contract, case, quote, etc. that you create.
Building subscriptions based on a master subscription
Used to create or update subscriptions based on additional data or custom objects
Data mappings allow for retrieving the data required for creating or updating subscriptions and their items from virtually any fields of any objects. Generally, you can apply mappings to get data
- in addition to the configured fields when using master subscriptions or objects in a master-detail relationship, or
- from customized source objects whose records hold all (variable) information for creating subscriptions and items.
Building subscriptions based on a mapping
Subscription Builder Use Cases
The subscription builder supports three different use cases for the subscription building. They map typical sales use cases:
|NEW||Creates a new subscription.|
|REORDER||Creates new items and adds them to an existing subscription. If there is no existing subscription, it builds a new subscription.|
|UPGRADE||Creates a new subscription, sets an end date on the existing subscription and sets its status to
The use cases can be set in the field
ON_UseCase on the subscription source record. If the field is missing or not set, JustOn determines the use case automatically.
Use cases example
To illustrate the use cases, assume the following example: You sell phone contracts, and you keep track of your deals using opportunities. For each opportunity you generate a subscription, which is finally invoiced.
When you close a deal with a new customer, the new (or updated) opportunity triggers the creation of a new subscription. This is covered with the use case
Now an existing customer orders an additional service, which you add as a new opportunity product on a new opportunity. This opportunity product becomes a new subscription item on the existing subscription. This is the use case
REORDER – you add new subscription items, leaving the existing in place.
If, however, the customer decides to upgrade the calling plan, you must refund the amount that is already paid for the rest of the current contract term. This is where you apply the use case
UPGRADE: you create a new subscription that includes items for any new products, but also credit items for products to be refunded, and the existing subscription terminates.