Tock Integration with vinSUITE

Overview

When Tock is connected to your vinSUITE account, every booking made through Tock automatically creates a matching Reservation-type order in vinSUITE, and the guest is matched (or created) as a customer record. No manual entry is required on your end.

Each reservation order gets a friendly sequential order number.

The order is tied to the matched guest, with their name, company, address, phone, and email copied onto the order's billing details.

Tock is connected on our side, not through a setting in your account. Contact support if you'd like it connected or disconnected for your winery.

This article documents exactly which Tock fields map to which fields in vinSUITE, so you know what to expect on the customer profile and the order.

Requirements

Before this integration can be connected, your winery needs:

A Tock Premium plan
The integration is not available on Tock's standard tier. Confirm the winery's plan before starting any of the steps below.
Tock API access granted to vinSUITE
You must reach out to Tock directly to request the webhooks and API key for the integration. Tock generates the key and sends it back in their reply — we don't generate it ourselves. The request should also explicitly ask for the winery's Business Group and Business IDs, since Tock needs both to set up auth for the winery in their database.

Once both are in place, contact vinSUITE support to have the connection set up.

Guest → Customer field mapping

Tock field	vinSUITE field	Notes
Email	Member email	Used as the match key with vinSUITE's member database
First name, last name, phone, zip code	Member name, phone, zip code	Only overwritten when Tock sends a non-blank value. Tock will not erase existing data
Company	Member company	Same non-blank-only rule
Address (line 1, line 2, city, state, zip)	Member address	Same non-blank-only rule
Birthday	Member birth date
Verified guest flag	Member "Confirmed" status	Will always set to confirmed, never reverted
Opt-in status (purchase / waitlist / newsletter / imported vs. no opt-in / opted out)	Member type: Subscriber or Unsubscriber	Requires member types to be exact match between Tock and vinSUITE
Tags	Member type, matched by name	A tag with no matching member type doesn't fail. It is added as a note on the customer instead
Notes	Member notes	Timestamped, attributed to whoever made the update in Tock

Reservation → Order field mapping

Tock field	vinSUITE field	Notes
Experience, options, fees, custom charges, tax, service charge, gratuity, event fee	Itemized line items on the order
Cancellation	Order status → Cancelled	Automatic, no action needed
Payment collected in Tock	Amount paid
Total price	Order total
Discounts and comps	Order's discount amount	Field mapping for this is actively being refined
Refunds	Line item on the order once Tock reports it	vinSUITE reflects the refund; it doesn't process it

Refunds and payment changes

vinSUITE reflects what happened in Tock. If the payment was processed in Tock, refunds have to happen in Tock (or wherever the card was originally charged). vinSUITE will pick up the refund automatically once Tock reports it. Editing amounts directly on the vinSUITE order will not refund the guest.

Timing

Updates from Tock usually appear immediately. If something hasn't shown up after a few minutes, contact support rather than assuming it will catch up on its own.

FAQ:

Can I edit a Tock order's line items directly in vinSUITE? We don't recommend it. The order is meant to reflect what happened in Tock. Edits made in vinSUITE will not sync back to Tock and can make the order difficult to reconcile.

Why is a tag from Tock isn't showing up as a member type? The tag name has to exactly match a member type name already set up in vinSUITE. If it doesn't, you'll see a note on the customer's profile listing the unmatched tag instead.