Planning and Creating Price Levels in Plus2

Problem

Administrators need to decide which price levels a site uses and create them at build, because each one must be ticked on every product and adding one later is a lot of work.

Resolution

1. Create a default price level

   • Create one default price level (usually Adult), which unknown customers pay.

2. Add age-based customer price levels

   • Add others by age, e.g. Concession (60+), Junior (e.g. 1–17), Infant (under 1, free).
   • A concession priced the same as adult can be a Price Level Override (PLO) target rather than a customer price level; members then revert to adult automatically when the concession membership ends.

3. Create override price levels up front

   • Discounts for students, corporate groups, staff, blue light and similar come from the membership via Price Level Override, not from separate customer price levels.
   • Create override price levels you're likely to need at build time (e.g. Inclusive, Staff, Blue light, spare Discount 1/2).
   • Override price levels are never assigned to a record, so they need no colour or age range.

4. Prefix the IDs so they sort

   • Prefix IDs so customer levels sort above override levels, e.g. 1 Adult, 1 Concession, 1 Junior, then 2 PLO Inclusive.

5. Tick price levels on each product

   • Price levels are ticked on each product. Juniors who only need to book specific sessions don't need an access subscription: tick only the junior price level on that session's product.

6. Hide levels staff don't need (if applicable)

   • Hide unneeded price levels and time bands from front-of-house staff with Plus2 user-group permissions.

Notes

• Adding a price level later means ticking it on every product, including every resource product.
• Volume discounts for block bookers are usually applied manually rather than with a price level.
• Impact on Go Book: in Operator each price level has a Web bookable flag. Ticked price levels are offered on Go Book to customers who aren't logged in. If members get free or cheaper bookings through their price level (rather than PLO), leave those levels unticked in Operator. Customer-friendly names can be set in Operator as alternative descriptions without renaming them in Plus2. See Making a Price Level Visible in GoBook.
• Impact on Go Join: price levels used only as PLO targets don't need a member-type button on Go Join.
• Impact on the GMC: the Sub Type price level assigned to each subscription must exist here. The GMC cooling-off price level is also chosen from these.
• Related: Price Level Override (PLO); Setting Up Price Products in Plus2.

This page as markdown · All pages · llms.txt