Skip to content
English
Visit Our Main Site
  • There are no suggestions because the search field is empty.

Adding Group Classes in Gingr

Staff reference for setting up a group class series in Gingr, from reservation type through pet enrollment.

Purpose

If this is your first time building a group class in Gingr, work through this in order: two reservation types, a package, the class itself, and then pet enrollment. Skip a step or do them out of sequence and the class either won't calculate a rate correctly or won't show up where a customer expects to book it.

At a Glance

  • Every class level needs two reservation types: one customer-facing, one backend-only for rate math.
  • Once a level's reservation type and package exist, you reuse them for every future term of that same class. You only rebuild them if the class format itself changes.
  • Order matters: reservation types, then package, then the class itself, then pet enrollment.

Steps

  1. Create the customer-facing reservation type. Go to Reservation Types and add a new type for the class level you're building. Give it a name and description, set it as a single-day reservation, choose a distinct color, and select "charge by night" for the charge option. Set "show on customer side" to yes so it appears where customers book.
  2. Create the matching backend reservation type. Build a second reservation type for the same class level, this one with "show on customer side" set to no. This backend type exists only so Gingr can calculate an even per-class rate: enter the base rate, location, and partner as a location-and-partner-specific rate. The per-class rate is the package's current total price divided by the number of classes in the term. Confirm the current package price with your manager or the pricing sheet before entering anything; don't reuse a rate from a prior term without checking it first.
  3. Build the package. Go to Reservations, then Packages, then Add a Package. Choose the location, select the backend reservation type from step 2, and set the quantity to the number of classes in the term. Enter the current package price, leave tax off, disable purchases through the customer portal for this package, and set the email reminder count to 1. Once this package exists for a class level, you don't need to rebuild it for the next term unless the format changes.
  4. Create the class itself. Go to Reservations, then Group Classes, then New Group Class. Name it to match the reservation type from step 1, set the size cap, location, assigned instructor, reservation type, and package type. Enter the start date and time in 24-hour format. The class schedules weekly until every session in the package has been used.
  5. Check the generated schedule. After saving, open the class back up and check every session date against your actual calendar. If a date needs to be skipped, Gingr can auto-correct the remaining sessions from the start date, but always confirm the result by eye. An auto-corrected run can land a session on a day you didn't intend.
  6. Fix mistakes before the class fills. Instructor, class name, and level can all be edited after creation, and a class can be deleted or disabled if it was set up wrong. Only the customer-facing level shows up under Reservations, Group Classes, Upcoming, where a customer or a business administrator can book into it; the backend level never appears there, but staff can still enroll a pet into either one manually.
  7. Enroll pets. Confirm the pet already has a profile in the system before enrolling. Search for the pet, select it, and click Enroll. Gingr calculates the total automatically, applying any valid coupon or package credit, then check out like any other reservation.

Edge Cases / Troubleshooting

  • Auto-corrected schedule lands on a closed day. If the system's auto-correction skips a holiday or lands a session on a day the location is closed, manually edit that single session's date rather than leaving it as generated.
  • A class was set up wrong. Instructor, class name, and level can all be edited after creation, and the class itself can be deleted or disabled if it needs to start over.
  • Pricing sheet has changed since a reservation type or package was last built. Update the base rate and package price before creating a new term. A stale rate is still an easy mistake to make since the reservation type and package don't warn you when the price behind them is out of date.
  • Reservation-type naming doesn't match current class naming. Class and grade naming can change over time. If the level names you see in Reservation Types don't match what's currently being sold, check with your manager before creating a new class off an outdated type.

Why does a class need two reservation types instead of one

One is customer-facing and is what shows up where a family books. The other is backend-only and exists so Gingr can hold the per-class base rate the package price divides down to; that one is deliberately hidden from the customer side.

Vendor Reference

The screens behind steps 1 through 3 are documented generically by Gingr here:

Who to Ask

The two-reservation-type pattern and the build-once-reuse-every-term shortcut are the parts of this SOP that are easy to forget between terms. If you're unsure about pricing, class naming, or instructor assignment, check with your manager before you save anything that will show up on a customer's invoice.