Connect Square and ShelfCount learns what you sell. Map each menu item to a recipe once, and every sale is costed down to the ingredient, with the modifiers that were on it. That is what powers your theoretical food cost, your usage variance and your menu margins.
Cafes and restaurants that ring up sales in Square and want to know what each sale cost in milk, beans, cups and food. If you have a Square catalog with sizes and modifier lists, ShelfCount reads them as they are.
One ShelfCount account is one business, at $50 a month. It can watch several Square locations of that business, and you choose which. There is no combined report across separate businesses.
Square connects with an access token you create; ShelfCount reads sales, catalog, and locations and never writes to Square. Read-only OAuth is on the roadmap.
What it reads
Never writes anything to Square.
Square connects with an access token you create; ShelfCount reads sales, catalog, and locations and never writes to Square. Read-only OAuth is on the roadmap.
ShelfCount only reads from your POS. It never changes an item, a price or a sale there. A purchase order goes to a vendor only when you send it, or when you have switched on auto-send for that vendor.
That list is the whole of it. A test fails if the code that talks to Square starts making a call that is not on it.
In Square, an item has variations (a Latte in 12 oz and 16 oz) and modifier lists (Milk: whole, oat; Extras: extra shot). A sale is costed through the variation that was sold, so each variation points at a recipe, or straight at an inventory item for simple retail products like a bottled drink.
Example: a customer buys a 16 oz Latte with oat milk and an extra shot. The 16 oz Latte variation points at a recipe that uses whole milk and two shots. The oat milk modifier replaces the whole milk with oat milk, and the extra shot modifier adds a third shot. That sale is costed as exactly that drink, not as a plain latte. Each modifier shows its net cost impact, so you can check your upcharges.
When something changes in Square, such as a renamed drink or a new size, the affected mappings are flagged for review instead of being guessed.
Each modifier gets one or more of five effects, applied in order. You set them once, and every sale after that is costed with them.
Sales are pulled about every 15 minutes. Square can also send webhooks, if you add a webhook signature key in settings, which nudge a fresh pull when something changes. The webhook only says that something happened; ShelfCount pulls the real orders and catalog from Square's API. A Sync now button pulls on demand.
No. It reads sales, catalog and locations. It never writes an item, a price or a sale to Square.
With an access token you generate in your Square account and paste into ShelfCount.
Yes. Each modifier can add, replace or change an ingredient, so a latte with oat milk and an extra shot is costed as exactly that.
Yes, if they belong to one business. One account is one business at $50 a month and can watch several Square locations; you choose which. Separate businesses are separate accounts, with no combined report across them.
Your recipes, counts and costs stay. You remap the menu items to the new POS's items.
Connect Square in the trial and see your first sales costed to the ingredient. Or look around the demo first.