Skip to main content

Integrations · Who owns what

Name the provider. Define the boundary.

Clover owns the order and payment. Select Pi owns range activity. Wayside reads approved fields, names their source, and reports whether the venue connection is healthy. Nothing is ripped out.

Bring us your stack → See the connection board ↘
YOUR CURRENT STACK · CONNECTED BY WAYSIDE
Illustration of how Wayside adds to an existing tool stack

Connection board

Six connections, and the rest of your stack.

CARD-PRESENT COMMERCEClover

Clover owns the order, the tender, and the register. Wayside places the order beside the visit on the patron record.

RANGE ACTIVITYSelect Pi

Select Pi owns the bay session and the gameplay record. Wayside joins the session to the patron and the visit.

CATALOG AND COMMERCESquare

Catalog, orders, and payments read as approved fields; Square keeps the register and the tender.

PAYMENTS AND SUBSCRIPTIONSStripe

Memberships, deposits, and stored value settle in Stripe; the patron record shows what was paid and when.

MAIL AND CALENDARGoogle Workspace

Gmail threads and calendar holds sit beside the inquiry they belong to, so an event conversation is never only in an inbox.

EMAIL AUDIENCESMailchimp

Audiences and sends stay in Mailchimp; consent and delivery status come back to the patron record.

THE REST OF YOUR STACK Run something that isn’t on this board? Bring it.

Every other provider connects the same way: venue-approved access, a clear list of allowed fields, and a test on your property.

  • Toast
  • Rock Gym Pro
  • Smartwaiver
  • CourtReserve
  • + yours
Bring us your stack →

Ownership map

Every connection has an owner.

When Avery buys lunch, Clover keeps the order. Wayside can place the approved purchase fields beside Saturday’s visit. The operator still decides what happens next.

  1. 01
    Booking OWNER · BOOKING TOOL

    Reservation matched to a patron on arrival

  2. 02
    Range bay OWNER · SELECT PI

    Session joined to the same visit

  3. 03
    F&B counter OWNER · CLOVER

    Order placed beside the visit

  4. 04
    Patron record OWNER · WAYSIDE

    One chronology, sources visible

  5. 05
    Operator review OWNER · OWNER OR SHIFT LEAD

    Decides what happens next

Stack review

Bring the systems you already pay for.

The working session names each provider’s owner, the fields worth joining, and the first connection to make.

Map your venue →