Configurations

Configurable pricing

Pricing Configurations in Prioticket

Prioticket provides powerful configuration options for implementing detailed pricing strategies across a wide range of business models. These configurations let you define base prices, apply rules, and manage price variations for different audiences.

---

Core Pricing Parameters

You can set pricing logic based on the following dimensions:

• Product Type: Define base prices per ticket type (e.g., Adult, Child).

• Age Group: Tailor pricing for different age brackets.

• Booking Quantity: Apply bulk discounts or quantity-based changes.

• Seasonal Pricing: Adjust prices based on season (e.g., peak vs. off-peak).

• Daily Pricing: Set different prices for specific days.

• Custom or Dynamic Pricing: Use real-time integrations to override default pricing.

---

Price Calculation Flow

1. Base Price: Retrieved based on product type and optionally seasonal context.

2. Variations: Any applicable surcharges or discounts are applied.

3. Dynamic Price: Delivered through the Reservation API and Order API.

---

Determining Enabled Pricing Features

You can check which pricing features are enabled by inspecting these parameters in the product metadata:

🎛️ Parameter	✏ Title	📝 Description
product_seasonal_pricing	Product Seasonal Pricing	Whether pricing differentiates between specific date ranges (product types may repeat with different settings).
product_quantity_pricing	Product Quantity Pricing	Different pricing based on the booking quantity.
product_daily_pricing	Product Daily Pricing	Whether pricing differentiates between specific days.
product_dynamic_pricing	Product Dynamic Pricing	Whether pricing differentiates between specific availability slots (e.g., peak hours).

---

Ensuring Accuracy

To ensure accuracy of pricing:

• Always test changes using the API.

• Verify price breakdown in the Reservation response.

• Compare API results with expected calculations for each product configuration.

---

Best Practices

• Group similar pricing rules together using templates.

• Use consistent naming for tickets and pricing tiers.

• Document all custom pricing logic for internal audits.