Skip to main content
All CollectionsOffers / SalesTips
Automatic product creation
Automatic product creation

Booking raw data api, Customer products, Product triggers

Marius Nagel-Petersen avatar
Written by Marius Nagel-Petersen
Updated over a year ago

It's normal to have a set of contracted products for each of your customers with a specific price that you agree on. You may even have to add a fee when presenting transport products to your customer. It's hard to remember to add this when creating offers, and you might have to spend time looking up what you have agreed on.

To make this easier for you, we have created the possibility to automatically add products to your offers. This will save you a lot of time. The prices and information on the products will always be correct and you won't have to remember to add these manually each time. If the product contains a supplier, this can also follow with the product (read this section for notes on supplier.)


We call this process AUTOMATIC PRODUCT CREATION! 🙌


Note: You need to have a custom implementation of the booking raw data api to use this function. Contact support@qondor.com for more information.

Note 2: As of today, automatic product creation only works when inserting tickets and transport products to Qondor. More product types will be supported in the future.


EXAMPLE

I will use the following fictional customer rule to demonstrate:

The customer "Acme Inc" has agreed on paying a €2 handling fee for each air ticket that they purchase.




SET UP A PRODUCT TRIGGER

You start by setting up Product triggers. This is the place where you set the rules for when a product will be added to your offer. You need to create this before setting up customer products.


Head over to the Office menu-> Product triggers (this is only visible to Offer administrators and Super administrators)


The list on this page is empty so you need to add a product trigger. When you click on the "New trigger"- button you will see this page:

Create a name for your trigger (for instance: "Air fee trigger").
The next step is to set conditions. 

We have 3 possible condition fields: CustomValue1, CustomValue2 and SalesPriceExclVat. These are fields that you can set through your integration. 


In our example, CustomValue1 is the indicator of what kind of ticket it is.
SalesPriceExclVat is the ticket price. The following conditions have been set for this example:


This means that if CustomValue1 on the inserted ticket equals "TransportAir" and SalesPriceExclVat is greater than 0, the trigger will be triggered.


CREATING A CUSTOMER PRODUCT


1. Create a Template project in Qondor


2. Create Add an offer and the products that your customer have agreed on. 



In our example, we will add a product called "Air handling fee" with the price of €2. This is the exact product we want to copy each time an air ticket is inserted to Qondor.


The next step is to connect this fee product to our customer "Acme Inc". The fee should only be added when this specific customer wants to buy air tickets. 

3. Go to the Customer and click Customer products (this is only visible to Offer administrators and Super administrators).

4. Create a new customer product by select the correct template project, the correct offer and the correct product. In our case the product is called "Air handling fee". Then add the product trigger and a description if you'd like (optional).


AUTOMATIC PRODUCT CREATION BASED ON API REQUESTS

Each time you send a ticket through the API with CustomValue1 set to “TransportAir” and SalesPriceExclVat value greater than 0 to a project with "Acme Inc" as customer through the Booking raw data api, the product that was first created in the template project will appear underneath the inserted product (automatically confirmed).  🎊


⭐ GOOD TO KNOW

  • If you want to add more than one customer product, try the "Save (and create another)"- button. This will let you stay on the same page with the same template project and offer chosen.

  • Everything from a customer product will be copied. This includes: prices, descriptions, design, images and so on.

  • If a supplier exists, then Qondor will also copy this over. As long as the data attributes match, we match suppliers in the data sent to us against suppliers already in Qondor. If the supplier is not already created in Qondor, then the supplier will not be copied over.

  • A product trigger that is in use can not be deleted.

  • A product can not be deleted from the template project if it is connected to a customer (listed on the customer products-page).


Did this answer your question?