Shared and Allocated Capacity

Advanced capacity management

This section explains advanced capacity control mechanisms within the Prioticket platform that allow precise management across products and distribution channels.

---

Shared Capacity

Definition:

Shared capacity allows multiple products to draw from the same capacity pool, preventing overbooking when they rely on a common resource (e.g., tour bus, room, guide).

Use Cases

• Multiple tours using the same vehicle

• Language variants of the same experience

• Combi products reusing sub-product time slots

How It Works

• Products reference a shared capacity_id.

• Each product has its own availability calendar, pricing, and logic.

• Booking any product deducts from the same shared capacity pool.

• Capacity is updated in real time across all linked products.

Best Practices

• Only use shared capacity when there's an operational overlap.

• Ensure all linked products operate on the same time logic (start time, duration).

• Use descriptive capacity_ids (e.g., bus_30_seats_morning).

---

Allocated Capacity

Definition:

Allocated capacity reserves a portion of available capacity for a specific reseller, channel, or distributor. This ensures availability for priority partners or campaigns.

Configuration

• Managed via the Allocations Manager in the control panel.

• Set by:

  • Distributor/Reseller ID

  • Time range (specific dates or recurring days)

  • Product or capacity ID

• Allocation rules may optionally:

  • Exclude existing bookings

  • Block dates fully

  • Reclaim canceled capacity

Behavior & Sync

• Allocated capacity is enforced at booking time.

• Cancellations or modifications restore capacity to the correct allocation.

• Fully auditable; all changes logged.

• Real-time syncing ensures distributors don’t see outdated capacity.

Tips for Managing Allocations

• Allocate based on historical demand or sales targets.

• Combine with combined capacity rules to allow soft fallbacks.

• Monitor capacity leakage (e.g., allocations going unused).

• Name allocation rules clearly (alloc_OTA_may2025_peak, etc.)

Comparison: Shared vs Allocated

🚀 Feature	📊 Shared Capacity	📈 Allocated Capacity
Scope	Multiple products sharing same limit	Reserved slots for specific resellers
Use Case	Resource overlap	Channel prioritization
Control Level	Product-level	Distributor-level