Skip to main content

Inline Waiver Signing

Every operator that runs an experience where safety matters — paragliding, diving, white-water — has the same problem: customers book, pay, arrive, and then you scramble to get their waiver signed at the desk. Inline waiver signing fixes that. The waiver is signed as a step inside the widget checkout — before payment. Every booking arrives already-signed.

How It Works​

  1. Customer adds an experience or rental to their cart.
  2. In checkout, after entering their details, they see a Sign your waiver step.
  3. Each participant's waiver is shown in sequence — full name, date of birth, any custom fields you've set up, and a signature canvas.
  4. Once everyone has signed, the customer enters payment details and confirms the booking.

The signed waiver is recorded as a normal form response, just like the existing post-booking email flow — you don't have to change how you view or audit waivers.

Enabling Inline Signing on a Waiver​

Inline signing uses the waivers you already have in Waivers & Forms. No new configuration needed on the waiver itself.

  1. Go to Waivers & Forms.
  2. Open or create a waiver.
  3. Make sure it's assigned to the products, experiences, or categories where you want it signed inline. See Assigning forms.
  4. Save.

Any waiver assigned to an experience / rental / category now renders inline when that item is in a customer's cart.

By default the booker signs each applicable waiver — no extra details are collected. To have every renter sign, turn on Require participant details — shop-wide in Settings → Rentals, or per product (Shop default / On / Off); then each participant gives their details and signs their own copy. For multi-person gear (a 2-person kayak, a tandem bike) also set Participants per item so checkout lets the customer add up to that many participants (only the booker is required, the rest are optional). See Creating a Product.

What Gets Recorded​

Each signed response is saved as a FormResponse with:

  • Source: widget_inline (so you can distinguish it from email-signed responses on reports).
  • IP address and signed-at timestamp — for legal defensibility.
  • Per-participant link — each participant gets their own response, tied to the booking participant record.
  • Signature image — saved as a PNG in your waivers folder.

You can view all responses under the Responses tab of any waiver.

Falling Back to Email​

If something prevents inline signing (waiver isn't assigned, customer is on a very old browser, etc.), the old post-booking email flow still kicks in — the customer gets an email with a signing link. Nobody is ever left without a path to sign.

Store Items Don't Trigger Waivers​

Waivers only apply to experiences and rentals. A customer buying a t-shirt from your store won't be asked to sign anything — store checkout skips the waiver step entirely.

Tips​

  • Require email on each participant. If email is hidden or optional, signed waivers don't have a counter-party email to send a copy to.
  • Keep waivers short on mobile. Every extra field on the waiver drops conversion 1–2% on mobile.
  • Use headings and sub-headings in your waiver body to break it up. Customers skim-read on phones.

Where You See the Status​

  • Booking detail — each participant row shows a Waiver signed chip once the inline response is recorded.
  • Manifest — the signed-waiver status is a column on every day-sheet export.
  • Waivers → Responses — filter by Source = widget_inline to see only inline-signed responses.