> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/integrations-overview/setup-tablecheck.md). # How to Set Up TableCheck ### Before you begin (Prerequisites) * **Permissions**: You must be an **Administrator** or **Supervisor**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **TableCheck account** with API access enabled. * **Credentials from TableCheck**: API Key, Franchise ID, and Shop ID. Contact your TableCheck representative or check the [TableCheck API Documentation](https://tablecheck.atlassian.net/wiki/spaces/API/overview?homepageId=43909423) if you need help locating these. * **Membership programs configured in TableCheck** must match Peoplevine membership SKUs. Ask your TableCheck representative to set this up before connecting. > For full setup instructions including TableCheck-side configuration, scheduler options, and testing steps, see [Connect TableCheck and Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) in Peoplevine Connect. The steps below cover the Peoplevine Control Panel side. ### Instructions 1. Navigate to [**AUTOMATE > Integrated Platforms**](https://control.peoplevine.com/admin_authenticate.aspx). > **Note (Pro Dash):** Same path — **AUTOMATE > Integrated Platforms**. 2. In the **Reservations** section, select **TableCheck**. 3. In **Associate with Location**, select the Peoplevine directory location for this connection. 4. For the **URL**, select **Production** from the dropdown (or enter the TableCheck API URL for a custom environment). 5. Enter your **Authorization Header (API-KEY)** — this is the TableCheck API key provided at account creation. 6. Enter your **Shop ID** and **Franchise ID**. > **Note:** The Shop ID and Franchise ID can sometimes be the same value. Check with TableCheck Support if you are unsure. 7. Toggle **Enable Webhooks** to **On**. 8. Click **CONNECT**. 9. After connecting, the system generates a webhook URL. Copy this URL and provide it to your TableCheck representative to complete the webhook setup on the TableCheck side. > Contact your account manager or if the webhook URL does not generate. ### What Gets Synced | Data | Direction | Timing | | ------------------------------------ | ------------------------- | ----------------------------- | | Member profiles (name, email, phone) | Peoplevine --> TableCheck | On enrollment + updates | | Membership status changes | Peoplevine --> TableCheck | Real-time | | Membership tier + ID | Peoplevine --> TableCheck | On sync | | Reservations | Both directions | Real-time (requires webhooks) | | Real-time availability | TableCheck --> Peoplevine | On demand (Member Portal) | > **Not supported:** Attribute syncing, CRM sync from TableCheck to Peoplevine, arrival status syncing, reservation notes, and member photo display are not currently supported. ### Best Practice * **Match membership SKUs before connecting** — the membership program ID in TableCheck must match the membership SKU in Peoplevine. Mismatches prevent members from syncing to the correct location. * **Test with a single reservation first** — create a test booking via the Scheduler, then verify it appears in the TableCheck Manager dashboard under **Online > Unprocessed** before going live. * **Create a scheduler after connecting** — schedulers let members book TableCheck reservations from the Member Portal. Go to **Scheduler > New Scheduler > Make a Reservation > Dining Reservation**, then set **Pull Availability From** to your TableCheck location. See the Connect guide for full scheduler setup steps. * **Use the Sync option for existing members** — after the initial connection, use **Sync > Members ==> TableCheck** with a date range to push your existing member base. New members sync automatically going forward. ### Common Issues **Webhook URL not generated after clicking CONNECT:** Contact your account manager or . The webhook URL is required for TableCheck to send reservation data back to Peoplevine. **Members not syncing to the correct TableCheck location:** Verify that membership program IDs in TableCheck match the membership SKUs in Peoplevine. These must be set up by your TableCheck representative before connecting. **No availability showing in the Scheduler:** Ensure the scheduler's **Pull Availability From** dropdown is set to your TableCheck location. If using a Sync ID, verify the seating category name matches exactly. **Reservations from TableCheck not appearing in Peoplevine:** Webhooks must be enabled and configured. Confirm the webhook URL generated by Peoplevine was provided to your TableCheck representative. ### What Happens Next * Members synced to TableCheck are recognized when they make reservations — hosts see membership tier and Member ID * Members can check availability and book dining reservations through the Peoplevine Member Portal * Reservations created in either system sync to the other in real time (with webhooks enabled) * New members are automatically pushed to TableCheck upon enrollment *Last updated: 2026-05-24* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/integrations-overview/setup-tablecheck.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.