What connects, and what actually syncs
Three ways data gets into GriddleMath, described precisely — plus an honest list of what doesn't connect yet, so you can rule us out in a minute instead of after a sales call.
Where your numbers come from
Square
LiveA direct OAuth connection. Sales arrive by webhook as orders are paid, and you can also pull on demand for a date range.
- Authorize through Square's own OAuth screen — no API keys to copy, and you can disconnect from Settings at any time.
- Map each Square location to a GriddleMath truck, so multi-truck operators get sales in the right place automatically.
- Square catalog items are matched to your menu items; anything unmatched is queued for review rather than silently dropped.
- Imported orders attach to the booking they belong to, which is what pre-fills sold quantities on your closeout.
CSV sales import — any POS
LiveNot on Square? Export sales from whatever you run and upload the file. The importer is POS-agnostic.
- Map your file's columns to item, quantity, price and date once — the mapping is saved as a preset and reused on the next upload.
- Duplicate rows are detected across imports, so re-uploading an overlapping export doesn't double-count revenue.
- Unmapped item names surface with suggested matches instead of being discarded.
- Imports attach to a truck and a booking exactly like a Square sync, so everything downstream works the same way.
Supplier invoices by photo
LivePhotograph a supplier invoice and GriddleMath reads the line items, so ingredient costs stay current without retyping.
- Line items and prices are extracted from the image and proposed as draft ingredient cost updates.
- Drafts are reviewed before they apply — nothing changes your recipe costs until you accept it.
- Accepted updates re-cost every recipe that uses the ingredient, which moves the margins on your reports.
What GriddleMath does not do
Every integrations page on the internet lists wins. Here is the other half, because finding this out three weeks in is worse for both of us.
Toast and Clover
Not yetNo direct connection yet. Both export sales as CSV, and the CSV importer handles those files today — you upload rather than sync.
QuickBooks, Xero and accounting
Not yetNot connected. GriddleMath is a margin layer, not a bookkeeping system; it does not post journal entries or replace your accountant.
Live inventory and purchasing
Not yetNot supported. GriddleMath tracks what a booking consumed, not perpetual stock on hand or purchase orders.
Payroll and labor cost
Not yetNot supported. Margins here are food-cost margins — labor is deliberately out of scope for now.
Read your sales, write nothing back to your POS
GriddleMath reads orders and catalog data from Square. It does not modify your catalog, change your prices, issue refunds, or take payments — the connection is one-way by design, so the worst case for your POS is that we read something we didn't need.
You authorize through Square's own OAuth screen and can revoke from either side. See the privacy policy for how the data is stored and retained.
Integrations FAQ
Do I need Square to use GriddleMath?
No. Square is the deepest integration and the one that requires the least work from you, but the CSV sales importer accepts an export from any POS. Everything downstream — recipe costing, closeout, waste-adjusted margin, recommendations — works identically either way.
How often do Square sales sync?
Orders arrive by webhook as they're paid, so a normal service populates itself while you're working. You can also trigger a sync for a date range from Settings when you want to backfill or re-pull.
What happens if a POS item doesn't match a menu item?
It surfaces on the POS mapping screen with a suggested match rather than being dropped. Revenue you haven't mapped is visible as unmapped instead of quietly missing from your margins.
Can I disconnect Square?
Yes, from Settings, at any time. Sales already imported stay in your account; nothing new arrives after you disconnect.