The Configuration area allows you to view and manage key aspects of your integration setup. Here, you’ll find several sub-sections → Settings, Restrictions, Rate Model, Add-ons, and Booking, each giving you visibility over how your connection to B-Aggregate is structured.
While many fields reflect pre-agreed settings, certain areas may be editable if updates are required. This ensures you can align your integration preferences without needing to start from scratch.
Note: Hover over the ⓘ icon next to any item to read a short explanation of that setting.
Configuration → Settings
The Settings tab under Configuration allows you to review and update the key technical parameters of your integration setup. This section allows users to configure technical details related to the connection, booking behavior, mapping method, and IP access.
Table Reference - Configuration → Settings
| Category | Description |
| Indicates whether your integration/connection is either API Push or API Pull. |
| Shows the timezone of your server. This ensures that availability and rate data align correctly with your local time configuration. |
| Indicates how the room and rate data is integrated. |
| Defines how far in advance guests can book through the system (e.g., up to 18 nights). |
| Set how many days of ARI your platform can receive in each update. |
✨ Tip: These settings should align with your system’s capabilities and business rules. Review carefully before going live. If unsure, contact your technical team or support@bakuun.com.
Configuration → Restrictions
This section defines the specific restriction rules your system supports. Each item reflects whether your system can handle and process that restriction when syncing with Bakuun. These settings are important for ensuring consistency across rate plans, availability, and booking rules.
Note: Use the toggle to mark each item as Yes (supported) or No (not supported) based on your system’s capabilities.
Table Reference - Configuration → Restrictions
| Category | Description |
| Inventory Room Level | Allows pushing inventory (number of rooms available) at the room type level. |
| Minimum Stay Through Room Level / Rate Plan Level | Minimum Stay Through that must be booked, defined either per room type or per specific rate plan. |
| Maximum Stay Through Room Level / Rate Plan Level | Maximum Stay Through allowed for booking. Controls longer stays either by room or rate plan. |
| Minimum Stay Arrival Room Level / Rate Plan Level | Sets the minimum nights required starting from the arrival date, per room or rate plan. |
| Maximum Stay Arrival Room Level / Rate Plan Level | Sets a limit on how many nights can be booked starting from arrival, typically used for promo control. |
| Close to Arrival Room Level / Rate Plan Level | Restricts check-in on specific dates (stop sell by arrival), useful during peak or blackout dates. |
| Close to Departure Room Level / Rate Plan Level | Restricts check-out on certain dates (stop sell by departure), also used for blackout periods. |
| Stop Sales Room Level / Rate Plan Level | Completely stops selling the room or rate plan for selected dates. No availability shown to buyers. |
| Min Advance Booking Room Level / Rate Plan Level | Requires bookings to be made at least X days in advance. Helps suppliers prepare for arrivals. |
| Max Advance Booking Room Level / Rate Plan Level | Limits how far into the future a booking can be made (e.g., up to 6 months only). |
| Sell Threshold | Controls visibility based on inventory. For example, if stock drops below a threshold, it can trigger a stop-sell or hide availability. |
| Cancellation Policy and Deposit | Indicates whether cancellation terms and deposit rules are pushed and visible via API. |
Configuration → Rate Model
This section states which rate model types are supported by the current connection. Each model outlines how rates are calculated based on occupancy, taxes, and pricing type.
Table Reference - Configuration → Rate Model (API Pull)
| Rate Model Type | Description |
| Room Base | Indicates whether your connection supports room-based pricing regardless of guest count. |
| Occupancy Based | Indicates whether your connection supports pricing that varies by number of occupants. |
| Length of Stay Rate | Indicates wheter your connection support pricing that changes according to how many nights are booked (e.g., discount for longer stays). |
| FPLOS | Indicates support for stay restriction, also known as the Full Pattern Length of Stay (FPLOS), where no arrivals are allowed for the length of stay selected |
| Rate Hurdles | Rate hurdles are based on an entire length of stay, which is why FPLOS is the ideal method of communicating them. RateDock assesses the availability of a rate by comparing the total price for a length of stay to the hurdles for the same length of stay. If the pricing exceeds the total hurdle, it is available. If the total pricing falls below the total hurdle, it is considered unavailable. This method allows individual dates that fall below a hurdle to still be available if they are part of a stay that exceeds the overall hurdle. |
| Before Tax Included | Indicates support for a total rate that includes tax, calculated before tax breakdown. |
| Before Tax Excluded | Indicates support for base rates where tax is added separately before calculation. |
| After Tax Included | Indicates support for a total rate with tax already applied after base rate calculation. |
| After Tax Excluded | Indicates support for rates where tax is calculated after the base rate and shown separately. |
| NET Rate | Indicates support for NET rates (pre-commission), commonly used in B2B distribution. |
| BAR Rate | Indicates support for BAR (Best Available Rate), dynamically adjusted based on market demand. |
✨ Tips:
Supported rate models are indicated as Yes or No per connection.
Rate models impact ARI push/pull compatibility with connected systems.
Configuration → Addons
This section shows whether your B-Aggregate connection supports optional add-on services or upsells. These extras can enhance the guest experience and boost revenue.
Table Reference - Addons
| Addons Type | Description |
| Addons Pre Booking | Extras that can be offered during the booking process. Examples include airport transfers, breakfast, or early check-in options. |
| Addons Post Booking | Extras that can be offered after a booking is confirmed. These may include spa reservations, late check-out, or activity bookings. |
Configuration → Booking
This section indicates which booking-related actions your system can perform and exchange with Bakuun. These actions are essential to ensure full reservation lifecycle support from initial booking to cancellation or modification.
Note: Mark each item as Yes if your system supports the feature, or No if it doesn’t.
Table Reference - Configuration → Booking
| Category | Description |
| New Booking | Allows creation of new bookings directly via the API connection. |
| Modify Booking | Supports changes to existing bookings, such as date, guest, or room updates. |
| Cancel Booking | Enables full cancellation of a confirmed booking through the API. |
| Cancel Room | Allows cancellation of individual rooms within a multi-room booking. |
| Multi Room | Enables support for booking more than one room in a single reservation. |