Food Costing With Square: What Actually Works

August 10, 2026 · 3 min read

Square gives you sales data and an item catalog but does not do full recipe costing with yield adjustment or supplier price tracking. The practical setup is to keep Square as the till and sales source, cost recipes outside it, and push approved price changes back to the catalog rather than retyping them.

What Square does natively

Where the line falls
Task	Square	Notes
Item catalog and pricing	Yes	The system of record for what you charge
Sales and item mix reporting	Yes	This is your PMIX — export it
Modifiers and variations	Yes	Costing them is the hard part
Basic inventory counts	Partly	Varies by plan tier
Recipe costing with yields	No	Nothing native does EP cost
Supplier invoice tracking	No	—
Alerting when a dish crosses a margin target	No	—

The workflow that works

Keep Square as the source of truth for prices. One catalog, one place a price lives. Costing tools should push to it, not compete with it.
Export item sales monthly. That's the PMIX for menu engineering — you need units sold per item over four weeks.
Cost recipes outside Square, with yield adjustment. This is the part nothing native does.
Bring supplier prices in from invoices, not by hand. This is where the workflow lives or dies — see the data-entry tax.
Push approved price changes back to the catalog. Retyping is where errors and drift enter.

Costing modifiers, which is the genuinely fiddly part

Square modifiers are where Square-based costing gets hard, because a modifier has a price but no cost.

Worked example · An add-on that isn't earning what it looks like

Bacon add-on price: $2.00
Two slices raw, at $6.56/lb: $0.66
Cook loss ~55% — so the raw weight is what you buy: included
Attach rate: 210/week
Weekly contribution: $281 at a 67% margin

Healthy — but the same add-on priced at $1.50 with a three-slice portion contributes $176 at 56%. Modifiers are frequently priced once at launch and never revisited, and they're pure margin when they're right.

Cost your top five modifiers explicitly — the recipe cost calculator handles a modifier the same way it handles a plate, because that is what one is. They're usually a meaningful share of contribution and almost never appear in anyone's costing exercise.

What Marji does with Square specifically

Being precise, because vague integration claims are the norm in this category and they're not useful:

Works today: OAuth connection, linking Marji dishes to Square catalog items, and pushing an approved price change to a linked item (early access). Disconnecting keeps the links.
Doesn't work yet: pulling sales data for menu mix, and syncing modifiers or variations. You'd export the PMIX from Square yourself.
Never automatic: no price moves without you approving it. That's a product rule, not a limitation we intend to remove.

The full state, kept honest, is on the Square integration page.

Can I do this with Square's own tools only?

For a very short menu with stable prices, roughly — you'd maintain costs in a spreadsheet and read sales from Square. It stops working when supplier prices move faster than you'll re-enter them, which is the usual failure. See software vs. a spreadsheet.

Not into Marji — photographing your printed menu builds the costed dish list. Linking those dishes to Square catalog items is then a matching step rather than a data-entry one.

What about Toast, Clover or Lightspeed?

No integration exists for any of them today, and we say so on each integration page rather than showing a logo wall. The costing work is identical regardless — you'd apply approved price changes in the POS yourself.

Connect Square, cost the menu, push the fix.

Photograph your menu, link your Square catalog, and approved price changes go back to Square instead of being retyped. Free tier, no card.

Try it free →