Membership and admission
Levels, terms, renewals, benefits, guest passes, digital wallet cards, timed tickets, and gate admission all read the same live membership state.
Built for visitor attractions
CoreFeld Visit
Admissions, membership, giving, programs, and retail finally recognize the same person.
CoreFeld Visit puts one constituent record behind timed entry, guided tours, group bookings, class registration, membership cards, donations, an online store, in-person sales, and reporting across all of it.
The constituent is the center
Every interaction adds to one useful history.
A member who books a class, brings a guest, buys a gift, renews, and makes a donation stays one person or household. Staff do not have to reconcile separate ticketing, membership, donor, and store identities to understand the relationship.
Programs and groups
Guided tours, classes, school and group visits, capacities, waitlists, and rebooking preserve the booking, payment, confirmation code, and attendance history.
Giving and commerce
Donations, recurring commitments, tribute and soft credits, member pricing, inventory, fulfilment, refunds, and receipts stay connected without double-counting revenue.
From the office to the gate
The day’s numbers lead back to the people and transactions behind them.
Before, during, and after the visit
The customer journey and the staff record stay together.
Plan and purchase
A visitor chooses admission, a tour, class, membership, donation, or merchandise in one cart that holds capacity and stock while payment completes.
Arrive and participate
Staff scan a ticket or membership card, admit guests against current entitlements, and manage tours, classes, group arrivals, and point-of-sale activity.
Continue the relationship
Renewals, acknowledgements, fulfilment, reporting, and communication exports use the constituent history already created by the visit.
Safe operational boundaries
Payments, capacity, inventory, and reporting are designed to reconcile.
Cardholder data never enters the product. Online payments use the customer’s hosted gateway and in-person payments use its P2PE terminal; the system keeps only a token and result.
Capacity and stock come from ledgers. Seats and inventory are derived from the bookings and movements that changed them, preserving the evidence behind the number on screen.
Accessible public and staff pages. Tickets, storefront, giving, membership, gate, order, and report flows are server-rendered and structurally tested against WCAG 2.1 AA.
Integrations are durable. Scoped APIs, signed retrying webhooks, Workday export batches, and communications sync have explicit state and audit history.
See one constituent move through the whole attraction.
CoreFeld can demonstrate joining, booking, checkout, digital membership, admission, giving, fulfilment, rebooking, and reporting as one connected workflow.