Authenticate with 7shifts using OAuth 2.0 and obtain an access token and x-company-guid for the target restaurant company.
Pull current-day sales totals from your POS system API, aggregated by location and time interval (e.g., hourly or by daypart).
POST actual sales data to the 7shifts sales endpoint with the location_id, date, and sales figures; refer to the Sales Integration overview in the 7shifts developer docs for the exact payload schema.
Optionally POST projected sales using the Custom Sales Projections endpoint to seed 7shifts' labor forecast models with forward-looking POS projections.
Retrieve the Daily Sales and Labor report (GET /v2/reports/daily_sales_and_labor) to confirm that 7shifts has ingested the data and is generating updated labor recommendations.
Schedule recurring POS data pushes (e.g., every hour during operating hours) to keep the labor forecast current throughout the day.
Known gotchas
Sales data must be submitted per-location using the 7shifts location_id; sending aggregate multi-location data to a single location_id will skew that location's labor forecast.
7shifts uses its own internal sales projection model; custom projections you POST can be overridden if the account admin manually edits projections in the UI.
The API rate limit of 10 requests per second per access token can be hit quickly if you are syncing many locations simultaneously; implement per-location throttling.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp