2 posts tagged with "rentals"

This post is part of our Curling IO v3 sneak peek series, where we explore some of the new features available in the upcoming version.

Clubs often need to send purchase information to systems outside Curling IO. That might mean updating a spreadsheet, notifying staff, or starting a workflow in another service.

Rentals are one example. Someone may need to prepare the lounge, reserve tables, arrange catering, or add the booking to a staff spreadsheet.

Curling IO v3 webhooks can send that product purchase to Zapier, n8n, or another HTTPS endpoint when it is submitted, paid, cancelled, or rescheduled.

This post is part of our Curling IO v3 sneak peek series, where we explore some of the new features available in the upcoming version.

Curling clubs use rentals for practice ice, lounges, meeting rooms, and other bookable resources they define. A rental needs a product and price, but it also needs a schedule, one or more resources, public availability, and a booking record after checkout.

In Curling IO v3, an administrator defines the rental schedule and resources in the admin area. Available time slots appear on the public calendar, where curlers can add one to the cart and complete checkout. This post explains the rental options being added and how they fit into the calendar.