LogoLogo
SupportChangelogAPI ReferenceStatus
Distributor API
Distributor API
  • Welcome
  • Getting Started
    • Functionalities
    • Integration Process
      • Implementation Guide
    • OCTO & Prioticket
      • Feature Comparison
    • Postman & Interactive Documentation
    • Connect Once, Reach the World
      • Featured Suppliers
        • Supplier Overview Europe
        • Supplier Overview Americas
        • Supplier Overview Middle East
      • Featured Resellers
    • Statement on API Excellence
    • Frequently Asked Questions
  • Key Concepts
    • Product Structure
      • Product types and classes
      • Admission types
      • Extra Options
      • Pickup Points
      • Combi, Clusters, Bundles & Addons
        • Cluster
        • Combi
        • Addons
        • Bundle
    • Availability and Capacity
      • Availability
      • Capacity
        • Shared and Allocated Capacity
      • Availability API
    • Pricing Guide
      • Who are you?
      • Configurations
      • Variable Pricing
      • Dynamic Pricing
      • How It All Comes Together
    • Booking Logic
      • Cart Management
      • Payments
      • Cancellation & Refunds
      • Booking Questions
    • Additional Capabilities
      • Locations, Destinations and Categories
      • Recommendations
      • Promotions
      • Webhooks
      • Translations
    • Technical Concepts
      • Authentication
      • Idempotency
      • Rate Limiting
      • Timeout Handling
      • Error Handling
      • API versioning
      • Pagination
      • Formats
      • Headers
      • Caching
  • Endpoints
    • About
    • Authentication
    • System
    • Products
      • Stock
    • Availability
    • Reservations / Cart
      • Promocodes
    • Orders
      • Email & Vouchers
    • Payments
    • Contacts
    • Notifications
    • Models
  • Resources
    • Release notes
    • Roadmap
    • Postman
    • Swagger
    • Changelogs
      • Parameter Changelog
    • API Specs
      • V3.8 (Latest)
      • V3.7
      • V3.6
      • V3.5
    • Support
    • Certification
  • Status Dashboard
Powered by GitBook
On this page
  • What is Availability?
  • Types of Availability
  • Availability in Booking Flow
  • Dependencies Between Sub-Products
  • Availability Scenarios
  • Best Practices for Availability

Was this helpful?

Export as PDF
  1. Key Concepts
  2. Availability and Capacity

Availability

Manage timeslots

What is Availability?

Availability defines the specific time slots or periods during which a product can be booked or accessed. It is essential for scheduling reservations for products with fixed sessions or operating hours.


Types of Availability

  • Open Products These products are available during general opening hours without specific time slots. Customers can visit at any point during the open window.

  • Reservation Products These require selection of a defined time slot. Often used for tours, events, or activities with limited capacity per session.

  • Seasonal or Date-Based Availability Products may only be available during specific seasons, date ranges, or recurring patterns (e.g., only on weekends or public holidays).

  • Sub-Product Availability (Combi Products) Each sub-product in a combi product must have its own independent availability settings. For example, a museum visit and a dinner may have different available times.


Availability in Booking Flow

  • When booking combi products, the system must gather and validate availability for each sub-product.

  • If one sub-product is unavailable, the overall product may be considered unbookable unless alternative configurations are in place.

  • Some configurations support selecting the number of participants first, which then loads availability based on seasonal or capacity rules. This enhances usability but can introduce errors if not carefully managed.


Dependencies Between Sub-Products

  • Sequential Dependencies You can configure the order in which products are used (e.g., you must complete a tour before you can attend the dinner).

  • Time Constraints The time between sub-products can be fixed (e.g., 30-minute buffer after activity A before activity B).

  • Optional vs. Mandatory Dependencies Some sub-products may be optional and have flexible availability, while others must be booked in sequence.


Availability Scenarios

🎭 Scenario
📝 Description

Multi-time-slot Tour

Product offers 10:00, 12:00, and 14:00 sessions; users must choose one

Combi Product (Tour + Meal)

Tour is available at 11:00, 13:00; dinner available at 17:00, 19:00

Free-flow Entry

Product is open from 09:00 to 17:00 with no slot selection

Seasonal Attraction

Product is only available from April to September, weekends only


Best Practices for Availability

  • Define availability per sub-product first before linking in combi logic.

  • Use the system’s dependency configuration tools to control flow and prevent conflicting schedules.

  • Audit availability regularly, especially after importing or duplicating product configurations.

  • Offer fallback options (e.g., suggest alternative time slots) when preferred availability is not found.

  • Use consistent naming and descriptions for time slots (e.g., "Morning Tour", "Evening Cruise").

PreviousAvailability and CapacityNextCapacity

Last updated 10 days ago

Was this helpful?