Session pricing
Set what customers pay per session duration. These prices show up on your public booking page and are used when the gateway charges the card — you don't need to touch prices anywhere else.
Where to configure
Settings → Session pricing. Each row is one pricing tier: a duration in minutes plus a price in your venue currency (set on Settings → Profile). Add as many tiers as you want — typical venues run with three (15, 30, 60 min).
Fields
- Duration (minutes)— the booking length shown to customers. Must be unique per venue; you can't have two “30 min” tiers.
- Price— integer in the smallest currency unit for your venue's currency (so paise for INR, cents for USD). The customer sees the formatted value on the booking form.
- Label(optional) — friendly name shown alongside the duration. e.g. “Quick lap”, “Full session”. Keep it short.
- Active— deactivated tiers are hidden from the booking page but preserved for historical bookings. Prefer deactivating over deleting; deleted rows break receipts for bookings that referenced them.
How prices apply
- Customer bookingspay whatever the tier costs at the moment of order creation. Later price changes don't retroactively affect existing bookings.
- Walk-in sessions from Sim Controluse the same tier prices — picking a duration on the walk-in dialog pulls the matching tier.
- Group racesaren't priced through this page; they inherit the duration of the parent session for each rig. Set up shared discounts through events instead.
Skipping payments entirely
If your venue runs without a payment gateway, bookings stay tagged pay at venueand the price is used purely as a reference amount for reconciliation. Pricing is still worth setting because it powers the customer- facing booking page — a venue with no tiers set up will show an empty booking form.
Currency
Currency is a venue-level setting on Settings → Profileand is locked once you've taken your first payment. Changing it after that would break historical receipts. If you truly need to change currency, email hello@pitwallos.com — it's a support-side migration.