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
  • Variable Pricing in Prioticket
  • What is Variable Pricing?
  • Types of Variable Pricing
  • Pricing Variations
  • Use Cases
  • Best Practices

Was this helpful?

Export as PDF
  1. Key Concepts
  2. Pricing Guide

Variable Pricing

Rule-based pricing

Variable Pricing in Prioticket

Variable pricing is a flexible strategy where product prices are adjusted based on predefined rules. This model is particularly useful for applying strategic price differentiation without requiring real-time updates.


What is Variable Pricing?

Variable pricing refers to changes in pricing based on structured, rule-based conditions. These changes are not calculated dynamically but follow logic that has been set in advance. This allows for transparent and predictable pricing strategies.


Types of Variable Pricing

Prioticket supports a wide range of variable pricing options:

  • Day of the Week (DOW): Different prices can be applied depending on the day (e.g., higher prices on weekends).

  • Date-Based Pricing: Unique prices set for specific dates.

  • Time Period Pricing: Applies different rates during defined hours (e.g., 4 PM – 5 PM).

  • Time Slot Pricing: Specific pricing for certain time slots.

  • Quantity-Based Pricing: Pricing changes based on the number of tickets or products selected.

  • Advance Booking Period: Adjust prices based on how far in advance the booking is made.


Pricing Variations

  • Increase or Decrease: Prices can be raised or discounted.

  • Types of Adjustments: Adjustments may be a fixed monetary amount or a percentage.

  • Targeted Scope: Variations may apply to all tickets or only specific ticket types (e.g., adult or child).

  • Season Duration: Price rules typically apply to entire seasons and are not changed frequently (usually not more than once per month).


Use Cases

  • Offering discounts for early bookings.

  • Charging premium rates on weekends.

  • Encouraging bulk purchases with tiered pricing.

  • Lowering prices for low-demand time slots.


Best Practices

  • Clearly define seasonal windows before setting variable rules.

  • Apply different pricing rules gradually to avoid over-complication.

  • Test and monitor API results to confirm that pricing logic behaves as expected.

PreviousConfigurationsNextDynamic Pricing

Last updated 13 days ago

Was this helpful?