An arboretum’s ticketing problem rarely looks like a museum’s. General admission might be free, cheap, or covered by membership most of the year. Then the cherry trees bloom, or the fall color hits, or the holiday light walk opens, and for a few weeks you are running a timed-entry attraction with a parking lot that fills by 10 a.m. A few weeks after that, it’s mostly plant sale tickets and Saturday pruning workshops.
If you already run Altru for memberships, donations, and admissions, the question usually isn’t “should we replace it?” It’s “what do we need around it so ticketing works for a place that changes shape every season?” This page is meant to help you answer that.
What arboretum ticketing actually has to cover
Before comparing tools, list the kinds of tickets you really sell. For most arboretums and public gardens, it looks something like this:
- Everyday admission, often walk-up, sometimes free with a suggested donation, sometimes with member reservations required when the weather and the bloom line up.
- Seasonal timed entry for bloom peaks, light shows, and evening walks, where capacity is set by paths, parking, or shuttles rather than building size.
- Classes and workshops with small caps: pruning, botanical illustration, guided tree walks, forest bathing.
- Plant sales, frequently with a members-only preview hour before the public opens.
- School and group visits booked ahead, often with deposits and headcounts that change.
- Rentals and private events, which may or may not run through the same system.
Each one has different needs. A workshop needs a clear capacity and a waitlist conversation. A light show needs time slots that sell out evenly instead of all at 6 p.m. Everyday admission needs to stay fast at the gate, especially when people arrive in waves after a sunny forecast.
What Altru already handles well
Altru is a reasonable backbone for this. It handles daily sales at the admission window, advance sales for scheduled programs and events, group sales, memberships and their benefits, and donations, all tied to constituent records. That last part matters: when a plant sale buyer, a workshop attendee, and a donor turn out to be the same household, Altru is where you see it.
Its reports and queries are where you go to answer the questions your board will ask, such as how members used their benefits during bloom season or whether first-time visitors came back for a class. How easily you can answer a specific question depends on how your programs and memberships are set up, so it’s worth building those queries before the season rather than after. Keeping ticketing in Altru keeps that history in one place.
Where arboretums tend to feel the gaps
The friction usually shows up online, not at the window.
Showing availability the way visitors think
A visitor planning a fall color trip wants to see a calendar: which days are open, which times are filling, which are gone. If your website shows a list of program links or a generic form, people guess, then call. When the trees peak, those calls land on the same small team running the gate.
Seasonal programs that change fast
Arboretums add and cancel things on short notice: an extra evening slot because the peak bloom ran late, a closed trail after a storm. You want the website to reflect what’s in Altru without someone rebuilding a web page every time.
Members versus the public
Member previews and member reservation windows are common at gardens. Decide early how you want those to work online, and test whether your current web setup can show different options to members. If you aren’t sure what Altru’s own web forms support for your configuration, build a test program in a sandbox or ask Blackbaud support before promising members anything.
Checking tickets outdoors
Many arboretums have more than one entrance, and some have no building at the gate at all. Think about how staff or volunteers will confirm tickets when there’s no counter, no reliable power, and spotty signal near the back lot.
Questions to ask before you add anything
- Does it read availability from Altru directly, or keep its own copy that can drift?
- Do sales post back to Altru as normal transactions on the right constituent, so membership and giving history stay intact?
- Can marketing staff place it on your website without a developer each season?
- How does it look on a phone? Plenty of bloom-season visitors check availability from the car or the night before.
- What happens when a slot sells out mid-checkout?
- Who maintains it when Altru is updated, and what does support look like?
Any vendor, including us, should be able to answer those plainly. If the answer to the first two is vague, expect reconciliation work later.
A practical setup for most gardens
Keep programs, time slots, and capacities built in Altru, since that’s where your staff already manage them. Name programs so a visitor would recognize them (“Lantern Walk, 7:00 p.m.”, not an internal code). Set capacities by the real constraint, which at an arboretum is often parking or the narrowest stretch of trail, not total acreage. Then focus your effort on the website piece: how visitors see dates and times and get into a purchase.
Where Calendar Builder fits
That website piece is what Calendar Builder is for. It gives you an embeddable timed-ticketing calendar for your website that shows real-time availability from Altru, so visitors see which days and times are open before they start buying, and Altru stays where your programs and capacities live.
