Square handles the transaction. Yes Chef handles food safety, due diligence, compliance evidence, corrective actions, and audit trail.
This guide is for sellers connecting Square to Yes Chef. Reviewers: see also Square reviewer instructions.
Before you start
- A Yes Chef organisation with an Owner (or admin) signed in.
- A Square seller account (Sandbox for testing; Production when live OAuth is enabled).
- At least one Yes Chef site created under Settings → Sites (or equivalent).
1. Connect Square
In Yes Chef open Settings → Integrations → Connect Square. Approve MERCHANT_PROFILE_READ on Square’s screen. You return to Integrations with a success banner when the connection is saved.
2. Map locations
For each Square location, choose a Yes Chef site and click Save. Mapping is explicit — Yes Chef does not auto-guess production sites without your confirmation.
3. Use Due Diligence
Open Due Diligence / Food Safety from the main navigation in the mapped site context. Complete checks, attach evidence, and use corrective actions per your package entitlements.
4. Disconnect
Settings → Integrations → Square → Disconnect. Yes Chef revokes the OAuth token when possible and marks the connection revoked. You can also revoke Yes Chef inside Square; Yes Chef processes Square’s revocation webhook.
What we read from Square
- Merchant id
- OAuth access + refresh tokens (stored encrypted)
- Location id / name for mapping
- Revocation notifications via webhook
We do not sync Square payments, orders, catalog, or inventory in this integration version.
Troubleshooting
- OAuth error banner → retry Connect Square while signed into the same organisation.
- No locations → confirm Square locations exist in the connected merchant.
- Still Connected after Square revoke → wait for webhook; refresh Integrations.
Permanent production webhook URL (owner configures in Square Console after deploy): https://<production-domain>/api/webhooks/square
Help: Support · hello@yeschefai.co.uk