GoTab Orders & refunds: which trigger to use

GoTab activity shows up in Patch primarily as orders. There are no GoTab check-ins, reservations, or memberships in this connection.

At a glance

What happened in GoTab…	Use this in Patch
Closed, settled tab with identified owner	Order Finished
Payment refunded on that tab	Order Refunded
Guest first appears from a tab	Contact Created
Guest details update on a later tab	Contact Updated

Timing tip: Patch syncs from GoTab about every 6 hours. Webhooks can land sooner. Use quiet hours and short delays on “thanks for your order” journeys.

Purchase amounts in Patch exclude tips.

Orders (settled tabs)

Best for: Spend: receipt follow-ups, reviews, offers based on what they ordered or how much they spent (after Patch consent).

Includes: Line items, totals (ex-tips), location, refunds when applicable.
Does not include: Creating GoTab promo codes from Patch; order-ready SMS (that stays in GoTab).

Good examples

Thank-you / review after a settled tab (only if opted in in Patch)
Buyers of a specific menu item
Win-back for guests who haven’t ordered since X date

Not ideal for: “They ordered today” when the tab never had an owner email/phone: those tabs usually never sync.

Refunds

Best for: Stopping or adjusting journeys when money was returned.

Use Order Refunded (or suppress on refund) so someone who got a refund doesn’t keep getting “thanks for your order” offers.

Contacts

Best for: Welcome journeys when someone first becomes a contact from an identifiable tab.

Remember: GoTab does not send SMS/email marketing consent into Patch. Confirm opt-in in Patch before messaging. GoTab’s own order-update SMS opt-in is separate.

Simple decision guide

Message about money spent? → Order Finished
Message about a refund? → Order Refunded
Message about first time we saw them? → Contact Created
Looking for check-ins, reservations, or memberships? → Not available from this GoTab connection (use your other Patch integration if you have one)