Table of Contents:
Overview
Configuration → Settings
Configuration → Restrictions
Configuration → Rate Model
Configuration → Booking
Sandbox - Configuration (TPS)
The Sandbox – Configuration (TPS) section allows Third Party Suppliers to review and manage how their system connects to the platform in a test environment.
This page is read-only and configurable, depending on permissions. It defines how your system handles ARI delivery, booking actions, restrictions, and pricing logic during sandbox testing.
⚠️ Changes made here affect sandbox behaviour only, not production.
Configuration → Settings
This section controls the core system communication settings between your platform and Bakuun.
Table Reference – Configuration → Settings
| Field | Explanation |
| Configuration Status |
Displays the current setup state of your Sandbox configuration.
The configuration must be fully completed before enrolment. |
| Last Update | Shows the date and time of the most recent configuration update. If it shows NA, no configuration has been saved yet. |
| Setup Progress (e.g., 0/4) | Indicates how many required setup items have been completed. All required fields must be configured before enrolment. |
| Enroll Configuration | Finalizes and activates the Sandbox configuration. This button becomes relevant once all required fields are completed. |
| Connection | Defines how ARI data is exchanged between your system and Bakuun. |
| Server Timezone | Select your server’s timezone to ensure accurate date and time alignment for bookings and ARI updates. |
| Mapping | Defines how rooms and rate plans are mapped between your system and Bakuun. Supports API Push or API Pull depending on integration type. |
| Max Booking | Sets the maximum number of bookings allowed or processed per request/property based on your system capability. |
| Max ARI Update | Defines the maximum number of Availability, Rates, and Inventory updates your system can send in a single batch or request. |
Configuration → Restrictions
The Restrictions section defines which restriction types your system supports and can exchange with Bakuun via API.
These settings determine how booking rules such as length of stay, close to arrival, stop sell, and advance booking rules are handled.
Each restriction must be marked as supported (Yes or No) before the configuration can be enrolled.
Table Reference – Configuration → Restrictions
| Field | Explanation |
| Setup Progress (e.g., 0/13) | Indicates how many restriction types have been configured. All required items must be reviewed before enrolment. |
| Status (Pending) | Shows whether the restriction has been configured. “Pending” means a selection (Yes/No) is still required. |
| Info Icon (ℹ️) | Click to view additional technical details about how the restriction is handled in the API. |
| Supported (Yes / No) |
Defines whether your system supports sending and receiving this restriction via API.
|
Available Restriction Types
| Restriction | Description |
| Inventory Rate Plan Level | Indicates if inventory can be managed at the rate plan level instead of room level only. |
| Release | Defines advance booking release periods, e.g., minimum days before arrival. |
| Minimum Stay Through (Rate Plan Level) | Minimum number of nights required across the entire stay. |
| Maximum Stay Through (Rate Plan Level) | Maximum number of nights allowed across the entire stay. |
| Minimum Stay Arrival (Rate Plan Level) | Minimum length of stay required when checking in on a specific date. |
| Maximum Stay Arrival (Rate Plan Level) | Maximum stay allowed when arriving on a specific date. |
| Close to Arrival (CTA) | Prevents check-in on selected dates. |
| Close to Departure (CTD) | Prevents check-out on selected dates. |
| Stop Sales | Blocks availability for selected dates. |
| Minimum Advance Booking Offset | Minimum number of days before arrival a booking can be made. |
| Maximum Advance Booking Offset | Maximum number of days in advance a booking can be made. |
| Cancellation Policy | Indicates support for pushing or retrieving cancellation rules. |
| Deposit | Indicates support for managing deposit rules or payment guarantees. |
Important Notes
- All restrictions must be reviewed before clicking Enroll Configuration.
- Selecting “Yes” confirms your system can technically handle and synchronize that rule.
- Incorrect configuration may result in booking errors, invalid stays, or restriction mismatches across connected partners.
Configuration → Rate Model
The Rate Model section defines which pricing structures your system supports and can exchange with Bakuun via API.
These settings determine how guest-based pricing, occupancy rules, LOS pricing logic, and advanced pricing models are handled during synchronization.
Each rate component must be marked as supported (Yes or No) before configuration can be enrolled.
Table Reference – Configuration → Rate Model
| Field | Explanation |
| Setup Progress (e.g., 0/10) | Indicates how many rate model components have been reviewed and configured. All required items must be completed before enrollment. |
| Status (Pending) | Shows whether the item has been configured. “Pending” means a Yes/No selection is still required. |
| Info Icon (ℹ️) | Displays additional technical information about how the pricing component behaves in the API. |
| Supported (Yes / No) |
Defines whether your system supports sending and receiving this pricing logic via API.
|
Available Rate Model Components
| Component | Description |
| Extra Guest Rate | Allows pricing adjustments based on additional guests beyond base occupancy. |
| Extra Guest Count | Defines how many extra guests are allowed per room. |
| Child Rate | Supports different pricing logic for children. |
| Child Age | Defines age ranges used to classify child pricing. |
| Child Count | Specifies the number of children allowed per booking. |
| Static Extra Guest & Child Combination | Supports fixed pricing combinations for extra guests and children. |
| Dynamic Extra Guest & Child Combination | Supports flexible pricing combinations based on dynamic occupancy rules. |
| Length of Stay (LOS) | Enables pricing rules based on number of nights stayed. |
| FPLOS (Full Pattern Length of Stay) | Supports day-based LOS pricing patterns, e.g., different prices depending on arrival day and stay length. |
| Rate Hurdles | Enables minimum price thresholds before availability is shown. |
Important Notes:
- All components must be reviewed before clicking Enroll Configuration.
- Selecting “Yes” confirms your system can technically handle and synchronize that pricing logic.
- Incorrect configuration may result in pricing discrepancies, booking errors, or unsupported occupancy combinations.
Configuration → Booking
The Booking section defines which reservation actions your system supports and can exchange with Bakuun via API.
These settings determine how booking messages are processed between your system and connected partners, including new reservations, modifications, and cancellations.
Each booking action must be marked as supported (Yes or No) before configuration can be enrolled.
Table Reference – Configuration → Booking
| Field | Explanation |
| Setup Progress (e.g., 0/5) | Indicates how many booking capabilities have been reviewed and configured. All required items must be completed before enrollment. |
| Status (Pending) | Shows whether the item has been configured. “Pending” means a Yes/No selection is still required. |
| Info Icon (ℹ️) | Displays additional technical information about how the booking message is structured and transmitted via API. |
| Supported (Yes / No) |
Defines whether your system supports processing this booking action.
|
Available Booking Actions
| Booking Action | Description |
| New Booking | Confirms that your system can receive and create new reservations. |
| Modify Booking | Supports updates to existing reservations, such as date changes, guest details, or room adjustments. |
| Cancel Booking | Confirms that your system can process full booking cancellations. |
| Cancel Room | Supports partial cancellations where only specific rooms within a multi-room booking are canceled. |
| Multi Room | Confirms that your system supports reservations that include multiple rooms under a single booking reference. |
Important Notes:
- All booking capabilities must be reviewed before clicking Enroll Configuration.
- Selecting “Yes” confirms your system can technically process and synchronize that booking action.
- Incorrect configuration may result in booking delivery failures, modification errors, or incomplete cancellation handling.