Skip to main content

Product · Patron registry

Know who arrived. Read the record behind them.

Join bookings, POS transactions, range activity, memberships, and household dependencies in a source-aware registry whoever greets the guest can read.

AVAILABLE The shared record every module reads from

Map your venue →
Patron relationships

Avery Williams

Everfield · demo venue

Visits, membership, access, and recent activity for one patron.

VISITS
18
LAST SEEN
TODAY
MEMBERSHIP
ACTIVE

Checked in at the range

Arrival recognized at check-in

TODAY 9:18 AM

Evening putt round

Four-player group · verified finish

JUL 29

Membership access

8 visits remain on current package

ACTIVE

PRODUCT VIEW

One patron, one useful history.

Profile, access, check-in, and recent visits in the current Wayside product, shown at Everfield Club & Grounds, the demo venue.

Wayside patron relationships view: patrons needing attention beside one patron's record with an active event inquiry, membership health, recent visits, and grants
DEMO VENUE Everfield Club & Grounds
IN THE PRODUCT
The layout, states, and check-in action.
ON THE RECORD
Names, dates, visits, and membership balances.
WHY IT HELPS
The team can see what is known, and when a source is missing.
ARRIVAL + RECORD PATH
01Parking arrival
02Check-in
03Range + activity
04Food + drink
05Future return

Registry fields

What belongs on the arrival record?

A field earns its place when staff need it at the desk and can see where it came from.

  • Identity across desks

    The same patron appears at arrival, activity, membership, and checkout without being re-keyed.

  • Source-aware history

    Every joined activity keeps its provider, timestamp, and authority visible.

  • Household dependencies

    Guardian, dependent, shared visit, and access relationships stay distinct on the record.

Record assembly

Test the registry at a single arrival: source event, identity match, staff view, and unresolved exception.

  1. 01SOURCE The booking arrives

    The provider, venue account, timestamp, and approved fields travel with it.

  2. 02MATCH Identity resolves or stays open

    Avery’s booking joins the registry; an uncertain match stays visible for review.

  3. 03ASSEMBLE The desk record is built

    Membership, household, access, and recent visits appear in the order staff need them.

  4. 04READ Staff recognize Avery on arrival

    The record answers the arrival question before staff ask the patron to repeat it.

PROVIDER AUTHORITY

Source systems keep authority.

The booking platform owns the booking. Clover owns the transaction. Select Pi owns range activity. Wayside records where each piece came from and when it changed.

WAYSIDE

Wayside assembles the registry.

Identity, last visit, active access, and household dependencies appear together with their source and timestamp.

OPERATOR DECISION

The operator decides which fields appear at each desk, which roles can read them, and how unresolved matches are handled.

WHAT IS LIVE

The shared patron record is live. Matching rules and data scope are configured to the venue.

IN PRACTICE

What it does, and how we set it up.

WHAT IT DOES

One patron view brings profile, membership or access, check-ins, and recent visits together for the venue.

HOW WE SET IT UP

We agree on which staff can see this view and which activity from your existing tools should appear in it.

PREVIOUS Venue modules

All product areas

Product overview
NEXT Today