---
title: "Set up your karting products for maximum impact"
slug: "set-up-your-karting-products-for-maximum-impact"
description: "Optimize your karting venue setup with our guide on track structures, scheduling, and resource management to enhance guest experiences and avoid overbooking."
updated: 2026-09-01T23:22:31Z
published: 2026-09-01T23:22:31Z
canonical: "mysupport.roller.software/set-up-your-karting-products-for-maximum-impact"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://mysupport.roller.software/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up your karting products for maximum impact

## What this guide covers

Karting venues have more setup decisions than most attractions: how your track is structured, how races are scheduled, and how resources are layered to manage capacity correctly. This guide walks through the recommended setup patterns so your products behave the way guests expect and your track doesn't get overbooked.

> [!NOTE]
> Your ROLLER Training and Implementations team sets all of this up during onboarding, guiding you through these options to get your venue ready to open and start selling. Keep this guide for reference, to understand why your venue is set up the way it is, and for later, when you need to set up a new product, add a track, or revisit how something's configured.

This guide assumes you already know the basics of creating products, resources, and schedules in ROLLER, see [Get started with products, resources and schedules](/v1/docs/get-started-with-products-resources-and-schedules) if you need a refresher. This guide covers which pattern to choose for karting specifically.

To get your karting products set up, you'll work through:

- Your operational model
- Resources
- Core product types
- Licensing
- League setup

## Operational models

Karting venues typically fall into one of two track structures, each with its own scheduling approach.

### Single-track venues

If all your race types run on one shared track, choose between two scheduling approaches, described below.

**Fixed schedule:** race sessions are set at defined times. Each race type is its own product, with its own specific time slots that don't change based on demand. With 10-minute heats, a typical alternating schedule might look like this:

| Time | Race type |
| --- | --- |
| :00 | Adult |
| :10 | Adult |
| :20 | Junior |
| :30 | Adult |
| :40 | Adult |
| :50 | Junior |

- Provides predictable scheduling and clear separation between race types.
- Multi-race packs need a gap built into the schedule between races (for example, Race 1 at :00, Race 2 at :30).
- Cross-attraction bundles (for example, Karting plus VR) are only possible on a fixed schedule.

> [!WARNING]
> Only schedule one race type into a given heat. Selling two different race types into the same slot causes conflicts, a fixed schedule avoids this by design, but it's still on staff to keep each race type's slots genuinely separate when building the schedule.

**Floating schedule:** any race type can be booked into the same shared time slots, rather than each one having its own. This suits venues with variable demand.

- All race types need to live within a single product as ticket type variations, or as separate products competing for the same slots, this limits how many distinct products or ticket types you can offer.
- Multi-race packs are often unavailable, because if a later slot gets claimed by another race type, the pack shows as unavailable. There's no automatic logic to shift a race to the next open slot.
- Cross-attraction bundles aren't compatible with a floating schedule.

**Set the booking rule to match:** once you've picked fixed or floating, set the track resource's booking rule to match. You can do this via Venue Manager > **Settings** > **Resources**. With **Multiple bookings** selected (the right choice for almost every karting track, since it lets several guests share the track at once up to kart capacity), a second setting controls what happens if more than one product or ticket type is ever booked into the same time slot:

| Booking rule | What happens | Best for |
| --- | --- | --- |
| Multiple products (the default) | Guests booked under different products or ticket types in the same slot are pooled together and can share the resource concurrently, up to capacity. | A fixed schedule, since your race types are already scheduled into separate slots and never actually share one, so pooling never comes into play. |
| Single product | Race types are separate products, but when two are listed at the same time slot, whichever sells first claims that session exclusively; the rest of that session's capacity sells only that product. | A floating schedule built from separate race-type products. |
| Single ticket type | The same exclusive-locking behavior as Single product, but for ticket type variations within one product instead of separate products, for example Adult and Junior variations of a single Arrive and Drive race. This is the pattern [Map bookings to ROLLER Karting](/v1/docs/map-bookings-to-roller-karting) recommends for age splits, since each variation maps to its own run template. | A floating schedule built from one product with multiple ticket types. |

> [!WARNING]
> A floating schedule left on the default Multiple products rule won't stop two race types being sold into the same heat and mixed together. If you're running a floating schedule, deliberately switch the booking rule to Single product or Single ticket type. If you're on a fixed schedule instead, the default rule is fine, since your race types never actually share a slot.

**Single booking:** separately from all of the above, the track resource's top-level Booking rule can also be set to Single booking, reserving the whole resource for one booking at a time regardless of capacity. This doesn't suit day-to-day racing, but it's worth knowing about if you offer a full-track exclusive hire product (for example, a private buyout).

### Multi-track venues

If you run separate tracks for different race types (for example, an adult track and a junior track), setup is simpler: each track gets its own resource with its own booking rule, plus its own licensing requirements, race speeds, and resource controls. Party packages and group events can be configured per track without conflict.

## Resources

Resources control your track capacity and determine what data reaches the karting module. Understanding how they layer is worth doing before you build any products. See [Create resources](/v1/docs/create-your-resources) for how to create a resource and set its capacity and booking rule.

### Resource types

| Example resource | Purpose | When to use it |
| --- | --- | --- |
| Track | Sets the overall kart capacity on the track. The primary capacity control for every karting product. | All karting products |
| Single kart | Limits availability of single-seat karts, layered under the track resource. | Single kart products |
| Duo kart | Limits availability of two-seater karts, layered under the track resource. | Duo kart products |
| Extra driver | Captures a waiver and ticket for the second occupant of a duo kart at no charge. Doesn't consume kart capacity. | Duo kart products only |
| Overflow | Extends capacity beyond the track resource for bookings that exceed normal capacity. | Over-capacity group, event, and party packages |
| Driver | Maps the booking to the karting module. Sits on its own resource line. Only one resource can be mapped per product in the karting module. | Group, event, and over-capacity party packages |

*Name your own resources however makes sense for your venue, the names above are examples.*

### How resources layer

**Standard single or duo race products:** put your track resource and single kart resource on separate lines, so both are required on every booking: track manages your overall track capacity, and single kart manages how many single karts you have available (split into adult and junior sub-pools where relevant). For duo kart products, use the track resource and duo kart resource on separate lines for the same reason. You don't need a driver resource here, waiver capture is handled at the product level by ticket count.

**Group, event, and over-capacity party packages:** put your track resource and overflow resource on one line, and the driver resource on its own separate line, since that's what maps to the karting module.

### Overflow resource sizing

ROLLER fills the largest resource first. If an overflow resource's capacity equals or exceeds the track's capacity, ROLLER fills the overflow before the track, which creates an overbooking risk. Tier your overflow resources to cover only the gap above track capacity. For example, with a 10-kart track: an Overflow 10 to 20 resource with capacity 10 covers guests 11 to 20, and a separate Overflow 21 to 30 resource with capacity 10 covers guests 21 to 30.

> [!WARNING]
> If two different party packages share the same oversized overflow resource, ROLLER may route all guests into the overflow and leave the track open. Break overflow resources into tiers that match your package sizes. By default, ROLLER fills the track resource before spilling into the overflow, so a booking that spans both can end up with most guests on the track and only a few on the overflow. If you'd rather guests were split evenly across the track and overflow instead, that's available through [Split session bookings evenly across resources (on request)](/v1/docs/split-session-bookings-evenly-across-resources), contact your customer success manager or the ROLLER support team to enable it. It requires the track and overflow resources involved to have matching capacity.

## Core product types

### Single race

Configure a single race as a [session pass](/v1/docs/create-your-session-pass-products) with a defined session duration, typically 10 minutes. This is the simplest karting product and works for both online and in-venue sales.

- On a fixed schedule, each race type is its own product, so set up a schedule for each one, at defined times, with the track and single kart resources layered in the variation.
- On a floating schedule built from separate products, list each race type as its own product at the same time slots, and set your track resource's booking rule to Single product so whichever sells first claims that session.
- On a floating schedule built from one product, build your race types as ticket type variations of that product instead, and set the booking rule to Single ticket type so the same first-sold locking applies at the ticket type level.

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(21).png)

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(31).png)

**Step-by-step: set up a single race product**

**Fixed schedule (each race type is its own product, in its own time slots):**

1. In Venue Manager, go to **Settings** > **Resources** and confirm your track resource's Booking rule is set to Multiple bookings > Multiple products (the default). No change is needed here, since your race types never share a slot.
2. Go to **Products** > **Create product** > **Session pass**.
3. In **Content**, name the product for this race type (for example, "1 × 10 min Adult Karting").
4. Under the **Session pass details**, set the **Session duration** (for example, 10 minutes) and add the track resource and the single kart resource **on separate lines**, so both are required on every booking: the track resource controls your overall track capacity, and the single kart resource controls how many single karts are available.
5. Select **Save** and go to schedules.
6. Create a schedule, set **First session starts at** and **Last session ends at** to this race type's dedicated time window, and set **Session starts every** to your heat interval (for example, every 10 mins).
7. Repeat steps 2 to 6 for each additional race type, each as its own product with its own non-overlapping time slots.
8. Add each product to your online checkout and POS device menus.

**Floating schedule, built from separate products (race types share time slots, each is still its own product):**

1. In Venue Manager, go to **Settings** > **Resources**, select your track resource, and set Booking rule to Multiple bookings > Single product.
2. Go to **Products** > **Create product** > **Session pass**, and repeat this for each race type as its own product.
3. In each product's **Session pass details**, add the same track resource and single kart resource **on separate lines**.
4. Select **Save** and go to schedules for each product, and set up the same **First session starts at**, **Last session ends at**, and **Session starts every** values across all of them, so they share identical time slots.
5. Add each product to your online checkout and POS device menus.

**Floating schedule, built from one product (race types are ticket type variations of a single product):**

1. In Venue Manager, go to **Settings** > **Resources**, select your track resource, and set Booking rule to Multiple bookings > Single ticket type.
2. Go to **Products** > **Create product** > **Session pass**, and create one product (for example, "1 × 10 min Karting").
3. Add a ticket variation for each race type (for example, Adult, Junior).
4. Add the track resource and single kart resource to each variation, **on separate lines**, so both are required within each variation.
5. Select **Save** and go to schedules, and make sure every race-type variation is included in the same schedule and time slots.
6. Add the product to your online checkout and POS device menus.

### Multi-race packs

Let guests buy 2 or 3 races in a single transaction. We recommend building these as a [Multi-pass product](/v1/docs/create-your-multi-pass-products).

- Set the multi-pass up as a Multi-pass product type in Venue Manager, not a session pass. Quantity is set at the product level and can't be changed after saving. Link each variation to the relevant session pass product, set the valid period in availability (for example, 12 months from purchase), and note that the pass links to the guest's email address, so booking holder details need to be added at POS before it can apply.
- On a floating schedule, multi-race packs are often unavailable, because if a later slot gets claimed by another race type, the pack shows as unavailable. There's no automatic logic to shift a race to the next open slot.

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(22).png)

> [!NOTE]
> If a guest on a multi-race pack wants to move one race to a later time, add an internal-only, no-charge Individual Race product on the same track resource to their existing booking at the new time, then assign the waiver to the new ticket. Mark it internal-only so it isn't visible to guests online or at a self-serve kiosk.

**Step-by-step: set up a multi-race pack**

1. Set up the individual race session pass product(s) this pack will draw from first, if you haven't already (see **Single race** above). A multi-race pack must link to an existing session pass product.
2. In Venue Manager, go to **Products** > **Create product** > **Multi-pass**.
3. In **Content**, name the pack (for example, "3-Race Pack") and add a description and image.
4. Under **Multi-pass details**, set **Quantity** to the number of races included (for example, 3). This can't be changed after you save the product.
5. Edit the placeholder variation: give it a name, link it to the relevant session pass product's variation, and set its price.
6. Select **Create variation** to add another variation if you sell packs across more than one race type.
7. Under **Availability**, set when the pack is available to sell and how long it's valid for (for example, 365 days from purchase).
8. Select **Save**.
9. Add the pack to your online checkout and POS device menus.

Since a fixed schedule builds in a gap between each race in the pack (for example, Race 1 at :00, Race 2 at :30), make sure the individual race products' schedules already have that spacing before you link them into the pack.

### Duo Kart products

Duo Karts need extra resource setup to handle capacity and capture waivers for both occupants.

- Layer the Duo Kart resource with the track resource on separate lines, so both are required on every booking, consuming one kart slot per booking.
- Add a no-charge Extra Driver variation linked to the Extra Driver resource, and mark it compulsory if you need a waiver from the second occupant. The Extra Driver resource doesn't affect track capacity, it exists purely to generate a ticket and waiver for the second occupant.

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(24).png)

**Step-by-step: set up a Duo Kart product**

1. In Venue Manager, go to **Settings** > **Resources** and confirm your Duo Kart resource and Extra Driver resource both exist. Create them if they don't, each with the appropriate capacity and a Multiple bookings booking rule.
2. Go to **Products** > **Create product** > **Session pass.**
3. In the Duo Kart variation, add the track resource and the Duo Kart resource **on separate lines**, so one booking consumes one Duo Kart slot and the track resource.
4. Add a ticket variation named Extra Driver, set its price to $0, and link it to the Extra Driver resource. This is what keeps it from consuming track or Duo Kart capacity, it exists purely to generate a ticket and waiver.
5. Check the **Variation ratio** box and set it to require 1 Extra Driver variation for each Duo Kart variation.
6. Select **Save** and go to schedules to ensure it's set up correctly (the same as any other race product).
7. Add the product to your online checkout and POS device menus.

### Cross-attraction bundles

Bundles like Karting plus VR package two experiences into one product, and only work on a fixed schedule. Every session pass schedules its time slots at the variation level, so build the bundle as a single product with two resource lines in the same variation:

- The track and single kart resource, scheduled for the karting window (for example, 0 to 10 minutes)
- The second attraction's resource, scheduled for the next window (for example, 20 to 30 minutes), with the gap between them acting as a transition buffer

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(32).png)

If a fixed schedule isn't an option, offer the second attraction as an add-on experience on the karting booking instead. It's less seamless for the guest, but avoids the scheduling constraint.

**Step-by-step: set up a cross-attraction bundle**

1. In Venue Manager, go to **Products** > **Create product** > **Session pass**.
2. Under **Content**, name the bundle (for example, "Karting + VR").
3. Create a variation, add the track resource and single kart resource **on separate lines**, and set its scheduled window within the variation (for example, 0 to 10 minutes).
4. Add the second attraction's resource **on a third, separate line** in the same variation, and set its scheduled window to start after the first (for example, 20 to 50 minutes), leaving a gap as a transition buffer.
5. Select **Save** and go to schedules, and set the schedule's session times and interval to match your fixed slots.
6. Add the product to your online checkout and POS device menus.

### Party packages

[Party packages](/v1/docs/create-your-party-package-products) combine track, overflow, and driver resources to handle group bookings that may exceed normal track capacity.

- **Within track capacity:** configure it as a regular party package product using the track resource.
- **Over capacity:** add a tiered overflow resource sized to your pre-set party package sizes, on the same line as the track resource, with the driver resource on its own separate line. ROLLER fills the track resource first, then spills into the overflow.

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(26).png)

Party packages can't automatically add heats or time as guest counts grow, so set up pre-set party packages sized for your common group sizes rather than relying on the package to scale automatically.

**Step-by-step: set up a karting party package**

**Within track capacity:**

1. In Venue Manager, go to **Products** > **Create product** > **Party package**.
2. Complete **Content** (name, description, image) and set up the **Party program**. You can choose the flow of the party. For example, you can let the guests race before heading to the party room, or stagger it so that they race before and after their time in the party room.
3. Add a party package variation, name it, and choose **Per guest** or **Per party** pricing.
4. Select **Add item** and add any food, drink, or merchandise inclusions.
5. Select **Save**.
6. Add the party package to your online checkout.

**Over capacity (larger parties that may exceed track capacity):**

1. In Venue Manager, go to **Settings** > **Resources** and confirm your tiered overflow resources are set up to match your pre-set party sizes (see **Overflow resource sizing** above).
2. Go to **Products** > **Create product** > **Party package** (or open your existing party package to edit it).
3. In the **Party program**, add the track resource and the appropriately tiered overflow resource **on the same line**, so ROLLER fills the track first, then spills into the overflow.
4. Select **Save** and go to schedules, and confirm the variation is included.
5. Add the party package to your online checkout.

## Licensing

Whether you need a licence depends on your venue and race types, not every venue does. Casual arrive-and-drive racing usually doesn't need one, but if you run competitive or Pro races, set up a licence as a [membership product](/v1/docs/create-a-membership-product) valid for 12 months, with common licence types like Junior, Adult, and Pro. You can optionally include race credits or race discounts as membership entitlements.

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(27).png)

> [!WARNING]
> Speed tags and competency flags can be applied per driver in the karting module, but ROLLER POS can't enforce access restrictions based on them. Qualification checks happen in the karting module, not at the point of sale. There's also no automatic age-based licence upgrade or expiry, so plan to review and reissue licences manually as drivers move between categories. If you're including race credits as a membership entitlement, note that they're fixed once issued and can't be added or removed afterwards, if you want more flexibility to top up or adjust credits later, a [multi-pass](/v1/docs/create-your-multi-pass-products) is a better fit than a membership.

**Step-by-step: set up a licence**

1. In Venue Manager, go to **Products** > **Create product** > **Membership**.
2. Under **Content**, name the licence (for example, "Junior Licence") and add a description and image.
3. Under **Membership variations**, edit the existing variation to add a licence type (for example, "Adult Pro").
4. Add a price and select **One-off payment** from the payment frequency drop-down, since licences are typically a fixed-price membership rather than recurring.
5. Optionally, under **Membership discount**, add race credits or race discounts.
6. Save the variation. If required, repeat step 3 by selecting **Create variation** to add each additional licence type.
7. In **Availability**, set the validity period (usually 365 days from date of purchase), **Redemption dates** and **Online checkout sales period**.
8. Select **Save**.
9. Add each licence to your online checkout and POS device menus.

## League setup

We recommend building leagues as a [Standard Pass](/v1/docs/create-your-standard-pass-products), with set redemptions and an expiry date matching the league end, plus a no-charge League Race POS product for weekly check-ins. You'll need to manually block the track schedule for league times.

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(28).png)

![](https://cdn.us.document360.io/23700755-951c-4b69-8afe-ec8b33c6c689/Images/Documentation/image(30).png)

A membership-based league (a one-time payment granting a 100 percent discount on the League Race product) is possible, but it has no built-in sales cap, which carries an oversell risk. The Standard Pass approach avoids this and is the recommended path.

**Step-by-step: set up a league**

1. In Venue Manager, go to **Products** > **Create product** > **Standard pass**.
2. Under **Content**, name the pass (for example, "Saturday League") and add a description and image.
3. Under **Variations**, edit the placeholder, add a variation name and price, and set a sales cap via **Quantity**.
4. In **Sales availability**, select the days the pass can be used (match the league's start and end dates) and set an online sales period.
5. Check the box **There is a limit to how many times a pass can be used** and set the number to match how many sessions are in the league term (for example, 6 for a league that runs every Saturday for 6 weeks).
6. Select **Save**.
7. Add the pass to your online checkout and POS device menus.
8. Set up a $0 League Race product for weekly check-ins: go to **Products** > **Stock** > **All stock** > **Create stock**, name it (for example, "League Race Check-in"), and set its price to $0.
9. Add the League Race product to your POS device menus.
10. To block the track schedule for league times, go to **Bookings** > **Blocked capacity**, select **Block capacity**, choose your track resource, and set the date and time window for each league session.

## Keep in mind

- **Karting module and ROLLER sync one way:** changes made in the karting module don't sync back to ROLLER, and product changes to an existing booking don't automatically resend to the karting module. Treat ROLLER as the source of truth for bookings and products.
- **Guest sync depends on waivers:** venues that don't collect waivers can't sync guest names to the karting module, so leaderboards and cross-visit tracking won't be available.
- **Use a unique email per guest account:** reusing the same email address across different guests can cause ROLLER to treat them as the same customer profile, which affects your guest-to-race history. Capture a distinct email for each guest where possible.

## Related

- [Install ROLLER Karting](/install-roller-karting.md)
- [Map bookings to ROLLER Karting](/map-bookings-to-roller-karting.md)
- [Manage karts in ROLLER Karting](/manage-karts-in-roller-karting.md)
- [Get started with ROLLER Karting](/get-started-with-roller-karting.md)
- [Run a race in ROLLER Karting](/run-a-race-in-roller-karting.md)
- [Set up your race track in ROLLER Karting](/set-up-your-race-track-in-roller-karting.md)