Square POS food cost integration

If you're running Square

Square kitchens tend to be small and quick to change: a café adding a seasonal drink, a bakery repricing by the tray, a truck rewriting the board on Friday. When the catalog is the menu, a price you approve in one place and retype in another is a second list to keep in sync, and second lists drift. That is why the write-back was built here first rather than anywhere else.

How to use Marji with Square today

Costing works without any POS connection: photograph the menu and Marji reads the dishes and prices straight off it, which is the same data a catalog sync would give us. When a price changes you retype it in Square yourself, once. What each plan includes is published.

What a POS integration buys you, precisely: it saves you retyping an approved price. Costing, watching supplier prices and naming the dish that drifted all run off photographs, whatever till you use.

Why Squareisn't built yet

This one is further along than the rest: the OAuth flow, the dish-to-catalog linking screen and the approved price write-back are written and deployed. What is missing is the production Square application credential, so the connect button is inactive and nobody has linked a catalog. We would rather say that plainly than let a page imply a connection you can't make. If Square write-back is the reason you're here, tell us — it moves the queue.