GoTab - Integration Set up

GoTab is the POS layer Rex pushes deposits and on-premise tabs into. This article covers everything from the initial integration setup to every workflow and behavior toggle.

What to ask your GoTab rep to create

Rex needs a few specific items configured in your GoTab POS before the integration can work end-to-end. Copy the template below and send it to your GoTab rep so they can set everything up at once.

Request template

Copy and paste the message below into an email or chat to your GoTab rep.

Hi [GoTab rep] — we're setting up the Rex GoTab integration and need the following configured in our GoTab POS.

1. Deposit Product
Name: Reservation Deposit (or similar).
Configure as a liability item (non-revenue). Reservation deposits sit on this item until the guest checks in, when the deposit is applied to the check-in tab and revenue is recognized.
Open Price (flexible pricing) so it can accept any deposit amount.

2. Fallback Product
Name: Fallback Product (or similar).
Used by Rex any time a specific package or resource doesn't have its own product mapping.
Configure as a revenue item with Open Price (flexible pricing).

3. Rex Reservations Spot
A single spot we'll use for both the Deposit Spot and the Fallback Spot in Rex.

4. Additional products mapped from individual packages (we'll send the list separately)
All of these should be Open Price (flexible pricing) — package totals vary by guest count, duration, taxes, fees, and discounts, so the items need to accept any amount.

Once these are created, please also send us our location's UUID so we can paste it into Rex.

Thanks!

Setup

This walkthrough enables GoTab on your account, connects a specific venue to your GoTab location, and maps the products and spots Rex needs to create tabs. Plan on roughly 10 minutes, plus whatever time your GoTab rep needs to create a few items in your POS.

Workflow: Reservation Deposit vs Paid in Full

The Workflow setting controls when and how Rex creates tabs in GoTab. It's the single most consequential decision in the integration setup, and it has real accounting implications.

Venue-level behavior settings

After Setup is complete, configure how Rex behaves when creating and managing tabs in GoTab. These toggles live on the GoTab card under your venue's General settings.

Map a resource to a GoTab spot

By default, every tab Rex creates for a venue uses the venue's Deposit Spot (and Fallback Spot). You can override this per-resource — for example, if Lane 1 should route to one spot in GoTab and Lane 2 routes to another. Per-resource mappings take priority over package and venue defaults.

Map a package to a GoTab product and spot

Mapping every package to a GoTab product is effectively required — without a per-package mapping, Rex falls back to the venue's Fallback Product, which means every package posts to the same generic line item in GoTab. For clean reporting and reconciliation, map each package to its own product. The per-package settings also let you override the spot and customize tab names per package.

Map an add-on to a GoTab product

Each add-on can be mapped to its own GoTab product, on a per-package basis. This is what controls whether the add-on shows up as a line item on the GoTab tab — and which line item it shows up as. The same add-on can post to different GoTab products depending on which package it's attached to (e.g. a Pizza add-on might map to one GoTab item on a kids' party package and a different one on a corporate event package).

Customize deposit and check-in tab names

Packages can define custom tab names for both the deposit tab and the check-in tab. These names support placeholder fields:

If no custom name is set, Rex defaults to: `[Reservation Number] - [Guest Name]` for the tab name.

Reference

Operational details and edge-case behavior — useful when troubleshooting or understanding what's happening behind the scenes.

What Rex sends to GoTab at each stage

Here's what actually happens in GoTab as a reservation moves from booking to check-in. This is the customer-facing flow as Rex sees it.

When a guest books online

Rex creates a tab in GoTab containing:

• The reservation details as line-item notes — date, time, guest name, package, reservation number.
• The product and spot mapped for this package (or the venue's defaults if the package isn't mapped).

For the Reservation Deposit workflow, the tab amount is the deposit only. For Paid in Full, it's the full reservation total.

If Schedule Tab is enabled, the tab is created with a scheduled start time matching the reservation start.

When a host checks the guest in

From the host app, when a host checks in the guest:

• Rex creates a new open tab (if you're using Reservation Deposit and Create Open Tab on Check-In is enabled — otherwise the deposit tab is reused).
• The check-in tab includes line items for the main reservation (quantity based on the pricing model — see the table below), each add-on that has a GoTab product mapping, and each additional activity with its own line items.
• Resource bay IDs are attached as notes on the tab.
• If Auto-apply Deposit to Check-In Tab is enabled, Rex applies the deposit as a payment on the new tab using the stored payment method, so the balance reflects what the guest still owes.

How spots & products resolve

When Rex needs to pick a GoTab spot or product for a tab, it walks this priority order:

1. Resource mapping — if the assigned resource (lane, bay, court) has a GoTab spot, Rex uses it.

2. Package mapping — if the package has a GoTab spot, Rex uses it.

3. Fallback Spot — if the venue has a Fallback Spot set, Rex uses it.

4. Venue default — the Deposit Spot set in the venue's GoTab settings.

Products follow the same priority: resource-level → package-level → fallback → venue default.

How the check-in tab quantity is calculated

On the check-in tab, Rex sets the line-item quantity based on the package's pricing model:

Any amount already paid (the deposit) is subtracted from the check-in tab's unit price.

What happens when a reservation changes

When a reservation is modified, cancelled, or extended after it's been booked, Rex syncs the change to the GoTab tab:

Tripleseat + GoTab check-in

When both Tripleseat and GoTab are enabled and the "Enable Tripleseat GoTab Check In" toggle is on, a Tripleseat event check-in automatically creates a GoTab tab. Conversely, un-checking the Tripleseat event cancels the GoTab tab. The new tab follows the same product/spot priority as a normal Rex check-in.

Rex also writes the GoTab tab ID back to a Tripleseat custom field on the event, so your team can jump from a Tripleseat event to the matching GoTab tab without searching.