Toast and Omnivore POS

Restaurant POS connections link attributed website leads to guests and orders, sync menus and hours into your site, and support Order online links to hosted Toast or Olo checkout. Food-order card processing stays with Toast/Olo — NurtureSite Stripe is for table reservations and private-dining deposits only.

Prefer Toast Standard API credentials from Toast Web when available ($0 NurtureSite absorb). Toast Partner marketplace and Omnivore production access may require vendor location fees. Live connections still require restaurant authorization and, for Omnivore-class fees, pass-through consent.

What the integration does

• Matches a site CRM lead by email, phone, or email then phone through the NurtureSite factory broker (requires Toast guest.pi:read for guest PII).
• Syncs published menus (Menus API V2 until ordering-partner certification) and restaurant hours into site content / business_hours.
• Prefer Toast orders webhooks and Omnivore ticket webhooks for CRM order status; hourly poll as backup.
• Returns order lifecycle outcomes so CRM automations can enroll on pos_order_* and pos_guest_matched triggers.
• Ordering Phase A: synced menu + Order online CTA to a hosted Toast/Olo URL.
• Payments Phase A: guest pays on Toast/Olo hosted checkout (no NurtureSite PCI for food).
• Phase B (when partner write scopes are granted): POS order injection and Toast credit-cards partner / Olo Pay — not enabled by default.

Pricing and pass-through

• Toast Standard API: restaurant-owned credentials; NurtureSite does not add a Toast fee.
• Omnivore / Toast partner location fees: approximately $30/location/month vendor API middleware is an approved client pass-through when you enable the connection with disclosure. NurtureSite does not absorb these fees into the base plan.
• Card processing for food orders remains on the restaurant’s Toast/Olo merchant account. Reservation/deposit Stripe fees follow your Stripe Connect settings.

Data handling

• The restaurant must authorize the connection (and pass-through fee when applicable).
• POS credentials and connection metadata are application-encrypted in the NurtureSite factory.
• Factory MySQL retains only keyed-hash guest and order references plus order timing/status for 90 days.
• Raw POS identifiers and payment card data are not retained in NurtureSite.
• POS credentials and outcome records are never stored in the client-site database.

These controls reduce retained data. They do not by themselves constitute PCI certification, SOC 2 certification, or a security audit claim.

CRM automation behavior

Add a POS guest match node to a flow. The node calls the factory broker and continues to the next node.

Use POS guest matched, POS order placed / paid / completed / cancelled, and related triggers for follow-up flows.

Before a live connection

Complete authorization disclosure, store credentials only in the portal, test the connection, sync menus once, and verify a single attributed lead/order in sandbox or a controlled window. Do not send production secrets by email or support ticket.