Multi-location GoTab venues in Patch

How it works

When you Connect GoTab, you choose which locations Patch may use.
One location can live on a single Patch account (no mapping step).
Multiple locations use a parent + child setup: one Patch child account per GoTab location.
Scheduled sync runs from the parent; purchases and products land on the child that owns that location.

Unassigned locations import nothing. If a whole venue is empty in Patch, it’s usually mapping: not a missing guest.

You do	Patch does
Connect GoTab and grant the right locations	Create child accounts and assign each location
Tell your rep which location is which	Turn on inter-account contact lookups when needed
	Activate and run the first sync

Don’t rematch locations yourself unless your onboarding rep asks you to: a wrong assignment moves that location’s data.

Build most GoTab automations on the location (child) account that owns that venue’s purchases.
Searching for a guest? Use the Patch account for the location where they closed their tab.

What this covers: How locations map to Patch accounts, without asking you to DIY the wiring.