Product Basic Setup

Simple 2-step to kick start your first product.

By clicking the Product Builder tab on the side menu, you should be able to access the Product Builder area and you will see a list of existing products and you should be to create your first product from there too.

Before going into the details of the product configurations, the first step is to create a surface-level overview of how your product should function.

Product Basic Configuration Example

Fields	Description
Product Name	The name of your insurance product. This will be the primary identification for this product through KASKO Dashboard.
Languages & Default Language	The language(s) this product should support. This will link to the languages of Documents, Emails, Contents (of your webapp). When you select more than 1 language, you will need to set a Default Language. Default language is used when end users do not specify a language.
Timezone	This is the timezone your product should operate in. For all the recorded timestamps (such as policy purchased time), it will be adjusted based on this timezone and show the adjusted time on KASKO Dashboard.
Policy Prefix	Policy Identification Number (assigned when an offer is created) is comprised of Policy Prefix & 8-digit randomly generated letters. Policy Prefix helps you quickly identify the product based on the Policy ID.
Product Admin	The main contact(s) for this product. Should there be any issues, updates or communication required, KASKO will reach out to the Product Admin(s).

Apart from these general product settings, you will also need to think about how you want to sell/use the product and define the structure of your product.

Product Structure Example

⭐Base Product & Subproduct

In general, a Product would have all the necessary configurations (such as Emails, Pricing Logic, Webapp, etc), but these configurations can be split into Base Product and Subproducts, 2 different levels.

You can create a Product with any Subproducts which means there will be only 1 version of the product used for all the distributors. In this case, you will not need to configure Base Product and Subproducts.

❓When should you consider Subproducts?

If your product is meant to be sold by different distributors via different channels and they should work slightly differently, you should consider having Subproducts. This will help you create the variation of the product more easily.

Base Product: When a configuration is defined on the Base Product level, this configuration will be shared across all Subproducts and you only need to configure it once.

Example If you set Pricing Logic on the Base Product level, you will only need to configure 1 Pricing Logic on your Base Product regardless of the amount of Subproducts you created. You will NOT need to configure Pricing Logic on the Subproduct level as all of the Subproducts will be using the same Pricing Logic.

Subproducts: When a configuration is defined on the Subproduct level, this configuration will be unique per Subproduct and you will need to configure it each time you create a Subproduct.

Example If you set Pricing Logic on the Subproduct level, you will NOT need to configure this on your Base Product. Instead, you will need to configure Pricing Logic on each of your Subproduct, which allows you to set up different variations of the Pricing Logic for each Subproduct.

There are 3 configuration sets you can select and you can select 1 or up to all 3. The selected configuration set(s) will be configured on the Subproduct level, hence, creating the variations. Please be aware, that if you select all 3, you will be configuring all settings on the Subproduct level (for each of the subproducts you create) which means it will be similar to creating a brand new product.

Webapp, Customer upload & Field Definition

You should select this when you want the variation on the customer journey, be it hiding/showing certain screens, showing different things on certain screens, or collecting extra data, etc.

Documents & Emails

You should select this when you want the variation on the Documents or Emails, be it having different brandings & layouts, or different Email settings (email sender/email subject/attachments/recipients), etc.

Pricing Logic & Payment Plans

You should select this when you want the variation on the Pricing Logic or Payment Plans, be it having different premium calculations, or different payment providers, etc.

*You will get all the details about these configurations later in this documentation.