Used when vendors can provide multiple sessions for a type of service
The Seat-Based rendering type allows offerors to define time slots and limit the number of participants for each session.
The Seat-Based rendering type is a policy where the cost of a service is directly related to the number of people who use it.
This is a common pricing policy in education booking engines (price per student), entertainment industry booking engines (price per ticket), and collective activities booking engines such as yoga lessons (price per participant).
You can find here all interface documentation related to the Seat-Based rendering type
Front:
Dashboard:
There is no specific workflow for the Session bundle
The Session bundle must be enabled with the stock bundle.
Enables participant management for offerers when seat-based rendering type is activated
The stock feature will bring participant management to the Seat-Based rendering type.
Offerors will be able to define the number of participants per session.
Asker can now select a number of participants, within the limit of the remaining number of participants, for an available session.
The price will be calculated automatically according to the number of participants.
The stock bundle will bring two major changes to sessions:
The price will no longer be per session but per participant
Each session will have its own number of participants.
Please, find all interface documentation related to the Stock bundle, here:
Front:
Dashboard:
This feature is enabled automatically when the Seat-Based rendering type is activated.
The session’s stock can be set and modified by the offeror at any time. He can manually increase it or decrease it.
When a booking of X participants is accepted, the system will decrease the stock by this number.
When a booking of X participants is canceled then the system will increment the stock by this number.
The system checks each time the stock and if it is 0 then the session becomes unavailable.