One booking form.
Every location.

Offer sessions at several venues through one form. This record-driven recipe adapts the idea from Eden’s multi-venue platform; it is a simpler architecture, not a reproduction of every part of that build.

Pixie parties 3 sites
Saturday, May 9Places per session
Riverside 11:00 AM 4 available
Kingsmead 11:00 AM 0 full
Eastgate 2:00 PM 12 available

Choosing a venue narrows its sessions, prices, and extras.

One venue fills up. The others stay open.

Illustrative experience

  • Sessions held as records, not choices
  • Capacity counted per site
  • Prices and extras set per site

The finished experience

Add a site without adding a form.

Choosing the venue narrows what follows, so a visitor only sees sessions and extras that site can deliver.

A good fit for
Anyone running one service at several sites: play centres, studios, clinics.

  1. 1

    Keep each site’s sessions as records

    In this suggested setup, keep each venue’s published dates, times, prices, extras and capacity as Gravity Forms entries. Adding a venue means adding records to that list.

    GP Populate Anything

  2. 2

    Let the venue narrow the rest

    The session list, the extras and the prices are filtered by the chosen venue, so a site that does not trade on Mondays has no Monday to offer.

    GP Populate Anything

  3. 3

    Cap every session where it sits

    Each session’s places come from its own record, so when the 11:00 party at one centre fills it drops off that centre’s list and the others are untouched.

    GP Inventory

  4. 4

    Total the party, fee and all

    A subtotal adds up the head count and the extras, and a conditional discount takes the table fee back off when paying children come — no product field for every combination.

    GP eCommerce Fields

What you’ll need.

Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.

Taking it further

Add these optional plugins when your project calls for more.

Before you start

  • Session records holding a stable session ID, venue, date, time, prices and capacity.
  • Configure Populate Anything’s filters and Inventory’s record-based limits so each published session has its own stock. A paid booking also needs a payment integration and tested inventory/payment-status settings.

Get this built.

A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.

Required

  • GP Populate AnythingPerks

  • GP InventoryPerks

  • GP eCommerce FieldsPerks

Optional

Gravity Perks Advanced $169 /year

3 perks need Advanced or above — on up to 3 sites.

Gravity Perks Pro $299 /year Taking all 2 optional perks too makes it 5 in all, which needs Pro.

See plans for this solution

Every plan renews at the same price, and you can upgrade any time for the difference.

Make it fit
your project.

Should this use Inventory or Bookings?

Inventory suits fixed sessions you publish as records. For rolling availability, GP Bookings offers services, resources, opening hours and capacity. Treat that as a separate design to prototype: check venue capacity, age rules and package pricing before replacing an existing booking form.

How many sites can one form hold?

As many as you keep records for. The form reads the list, so opening a site is a few new entries rather than another form to maintain, and one site can charge differently or offer something the others do not.

  • Clay, CTO
  • Dan, Content Sorcerer
  • Dani, Product Manager
  • David, Founder & CEO
  • Matt, Senior Support Wizard
  • Roxy, Support Wizard

Not quite your build?

Tell us what you are making and we will work out which pieces it takes — or tell you straight if this is not something we can do.

Ask the wizards