Seat-Based Rendering type

Used when vendors can provide multiple sessions for a type of service

• Why

• Which context

• Interfaces

• Configurations

• Workflows

• Special rules

Why

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.

Which context

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).

Interfaces

You can find here all interface documentation related to the Seat-Based rendering type

Front:

• Listing deposit (Seat-Based rendering type)
• Listing page (Seat-Based rendering type)
• Booking confirmation pages (Seat-Based rendering type)

Dashboard:

• User KPI (Time-Based, Seat-Based, Flat-Rate, RFP rendering types)
• Listings dashboard (Session bundle)

Workflows

There is no specific workflow for the Session bundle

Special rules

The Session bundle must be enabled with the stock bundle.