With our events system upgrade, specifically selling tickets, we have a grid field for defining ticket names and prices. That would likely be the best, most flexible implementation for this. Each lodge can build the price structure desired by adding the names and price (e.g. Adult Members (age 14+) | $100.00) for as many age/price ranges as desired.

This would be good even if the prices are not different to know who is in the 14-18 adult vs. 18+ "legal" adult group.

As the Mountaineers encourages more family and child participation, this item will be important for cost-conscious families. I think we need to make the pricing system more flexible so there can be toddler (0-2) child (2-5) and youth (5-13) pricing.

I'd like to register an anti-vote for made the age a radio button - creates complexity and it's fine if people approximate ages.

It might be good/better to make a configurable price table that is specific to each lodge. That way we could specific as many price categories as needed. We'd need a name and the upper and lower age boundaries for each (e.g. Toddlers 0-5, Youth 6-13, and Adults 14-100). We'd still have two sets, one for members and one for non-members. It's probably best to set this up as part fo the committee edit form, so that it is consistent on al of the lodge's stays, to prevent mistakes, and to make setting up and editing lodge stays more efficient.

NOTE: If we switch to using age radio buttons for lodge stay reservations, we'll need to be sure they are configurable based on the lodge setup.