Migration of preference costs
A new functionality for preference costs makes the migration and splitting of existing preference costs necessary.
The new preference costs have a different structure, which improves uniform application across channels and flexibility when booking via the map.
Read more about the new setup for preference costs here: How to use preference bookings and costs, or Setting up preference costs
Your existing preference costs do not (all) fit into this format. It is necessary to migrate them so that the intended behavior can be maintained.
What has changed
Within the settings of a preference cost, the option 'Link cost to specific amenity' previously existed. This setting ensured that the cost was applied in the booking portal when selecting amenities or when selecting an object on the map, if it contained the linked amenity. This setting will be discontinued.
What happens during the migration
Existing preference costs with the above setting will be split into two preference costs that complement each other.
1. New cost item for object selection
To charge for the amenity during object selection, a cost item has been created with the settings below.
Note: change in applicability
Previously, these costs were only applied in your own booking portal.
The new preference costs for object selection are also applied when a specific object is booked via external channels (API) or in the back office.
If you do not want this, please edit the new cost to specify its applicability across channels.
2. New cost item for amenity selection
To charge for the amenity during amenity selection, a cost item has been created with the settings below. The behavior regarding the applicability of this cost item has not changed.
