Continuing Following the recent price breakdown improvements, in this release introduces a new way to define price has been implemented, prices together with some other additional parameters of the Price Componentsnew parameters on price components.
Highlight:
- New way of defining priceprices: bottom-up
- Some new parameters for Sale Price Componentssale price components: mandatory, discount,
Details of the features
The old parameter "Price breakdown" at organization is reused, to define if the customer is working on either TOP-DOWN or BOTTOM-UP
For an organization
...
working in BOTTOM-UP mode:
Principle:
- A rate table must always have at least 1 price breakdown.
- Ticket price amount for each item must be the same for all price breakdown within the same rate table.
- Therefore, a ticket price must be selected for a rate table and use as ticket price for all price breakdown within the same rate table
- Catalog price (= ticket price + other sale price components) for each item must be same for all price breakdown within the same rate table.
...
- At least a sale price component "Ticket Price" must be created before creating a rate table
- When creating a rate table, a default "Ticket Price" price component must be selected, this ticket price component is used for all price breakdown within the same rate table.
- After rate table is created, a default price breakdown is created for the rate table.
- Operator Operators start defining prices by entering Ticket Price at a ticket price on "Amount" screen.
- Operator Operators open the default price breakdown, select sale price components to continue to calculate the price calculation :
- The "Mandatory sale price component": are selected by default and cannot be un-selected
- When calculating price: Catalog price are also updated to total price of all price components - except the "Discount sale price component"
