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 Capacity?
  • Capacity Types
  • Configuration Strategies
  • Capacity Visuals
  • Capacity Best Practices

Was this helpful?

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

Capacity

Manage resources

What is Capacity?

Capacity limits how many participants can book a product within a time slot, preventing overbooking and managing resource allocation.


Capacity Types

  1. Unlimited Capacity

    • No maximum limit; bookings are always accepted.

    • Common for virtual experiences or events without physical constraints.

  2. Fixed (Limited) Capacity

    • A hard limit on how many participants can book a slot.

    • Once full, no additional bookings can be made.

  3. Product-Dependent Capacity

    • Specific to an individual product.

    • Even if multiple products are similar, each has its own separate capacity pool.

  4. Shared Capacity

    • Several products draw from the same capacity pool.

    • Example: A tour and a museum ticket share the same 30-seat bus.

  5. Combined Capacity

    • A hybrid setup where multiple capacities (shared, fixed, or new) are merged for a product.

    • Used for custom reseller rules or group packages.

  6. Allocated Capacity

    • Reserved capacity segments for specific distributors or channels.

    • Ensures availability for high-priority partners even when general capacity is exhausted.


Configuration Strategies

Per Sub-Product

  • Each sub-product in a combi setup must have its own capacity setting.

  • Bookings fail if one sub-product lacks capacity, even if others have availability.

Combi-Level Capacity

  • Can reflect the lowest capacity among sub-products or be configured independently.

  • Example: A "Tour + Meal" product can have its own 20-person limit, even if the meal supports 50.

Capacity IDs

  • Unique identifiers used to track capacity pools.

  • Helpful for linking shared and allocated capacities across APIs and systems.

Booking Validation

  • Capacity checks are enforced during the booking request.

  • Must ensure the requested number of people or tickets doesn’t exceed the limit.


Capacity Visuals

  • Often displayed as color-coded slots:

    • 🟢 Green: High availability

    • 🟡 Yellow: Limited slots remaining

    • 🔴 Red: Fully booked or blocked

  • Be aware of UI discrepancies across systems or resellers.


Capacity Best Practices

  • Use shared capacity only where operationally justified (e.g., same room, guide, or equipment).

  • Regularly audit capacity usage to spot bottlenecks or over-allocations.

  • Configure fallback logic (e.g., alternate time slots) to improve booking success rates.

  • Keep capacity ID naming clear and consistent.

  • Simulate edge cases (e.g., near-full or last-minute bookings) in staging environments.

PreviousAvailabilityNextShared and Allocated Capacity

Last updated 11 days ago

Was this helpful?