> For the complete documentation index, see [llms.txt](https://docs.prioticket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prioticket.com/key-concepts/availability-and-capacity/availability.md).

# Availability

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.prioticket.com/key-concepts/availability-and-capacity/availability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.