Skip to content

Configure product change

To ensure that customers or portal users can only switch to appropriate tariffs, product changes must be configured in advance for the respective product in the tebio Business Portal. You determine: which target products you can switch to. What is the minimum term after the change? When the change can take place at the earliest and whether a fee will be charged.

If you introduce a new subscription product or restructure your tariff portfolio. Only if a product change is explicitly stored as a rule at this point can it be carried out later in the support process (or by the customer in the self-care / customer portal).

  • You need access to the tebio business portal with rights for product management.
  • Both the original product (from which the change is started) and the target product (which can be changed to) must exist in the system and be active.
  1. Navigate to Products in the main menu.
  2. Find and open the desired original product (e.g. standard subscription).
  3. Switch to the Product change tab.

You will now see an overview of all product change rules that have already been created for this product.

Click +Add Rule to define the rule set for a new target tariff.

Give the rule a clear name (e.g. “Switch to Premium Subscription”) and select the desired target product from the dropdown.

This area controls the commercial rules for product changes:

  • When can the change take place? Use the dropdown to decide whether the change can take place immediately, after the minimum term or at the next extension.
  • What minimum contract term applies? Here you specify whether the term of the old contract is retained in the event of a change (of the original product) or whether the minimum term of the new product also begins again with the change (of the target product).

Determine how sales partners should be dealt with (e.g. takeover of the original product). If the change option is a temporary promotion, you can set a specific start and end date for the rule under Validity.

A product change is rarely just an exchange of the main product. There are often options or properties attached to the subscription that should be adopted:

  • Rules for option switching: Define a mapping. Specify which active option from the original subscription should be automatically transferred to which option in the target subscription (e.g. from a “single option” to a “family option”).
  • Properties: Determine precisely which subscription properties should be carried over from the old contract to the new contract.
  • Fee (one-time): If there is a one-time fee for the switch, enter it here and select the tax category.
  • Messages: Associate events with this rule to automatically trigger messages to the customer when the switch is executed.

Save the rule to activate it.

The rule created is active immediately (unless a future start date was selected). Customers or portal users can now select the new target product using the “Change product” function if they have active subscriptions to the original product.

[!WARNING] Technical background Please note: Technically speaking, a product change is not a simple change to the product name on an existing subscription. The system deactivates the original subscription and activates a new subscription in the background. This also means that when you change products, the subscription number and the subscription UUID will necessarily change!

  • Target product is missing in the change process: If an employee contacts you and says: “I cannot select the target product for the customer!”, this is often because no corresponding product change rule has been defined for the original product.
  • Conflicting rules: Be careful not to create rules whose terms are mutually exclusive (e.g. a change that is supposed to take effect “immediately” even though the original product’s notice period has restrictions).

For headless systems or for migrating rules via script, the REST API offers its own endpoints for the product change rules:

End pointMethodDescriptionOperationId
/v1/product/product-changeGETSearch product change rulessearchPossibleProductChange
/v1/product/product-changePOSTCreate product change rulecreatePossibleProductChange
/v1/product/product-change/{uuid}GETRetrieve product change rulegetPossibleProductChange
/v1/product/product-change/{uuid}PATCHUpdate product change ruleupdatePossibleProductChange
/v1/product/product-change/{uuid}DELETEDelete product change ruledeletePossibleProductChange