Square's built-in inventory tracks the things you sell, counted in the units you sell them. It does not break a latte into milk, espresso, and a cup. For a shop that resells bottled drinks and bought-in pastries, that is often enough. For a cafe that makes drinks, it stops at the ingredient line, and that is where food cost actually lives.
I run Stella Coffee on Square, so I have read this from the owner's side of the counter as well as the software side. Here is how I'd work out whether Square alone does the job for you.
What Square tracks by itself
Square's inventory is item-based. You create a catalog item, give it variations (a 12 oz and a 16 oz, a bag of beans in two sizes), and Square keeps a stock count per variation. Sales decrement the count. You can set a low-stock alert so a number crossing a threshold nags you.
That model is a good match for anything that goes from vendor to customer in one piece:
- Bottled water, canned cold brew, kombucha
- Bags of whole bean coffee
- Pastries you buy in and sell whole
- Merch: mugs, tumblers, t-shirts
Square's plans and pricing change, and so does which inventory features sit on which plan (purchase orders and vendor management in particular). I have not frozen a plan-by-plan table here because it would be stale within a quarter. Before you decide anything, open Square's own pricing page for your plan and check the inventory features it lists. Treat what I describe here as the shape of the feature and Square's page as the source for the details.
Where it stops for ingredients
Now look at what a cafe actually sells. A 16 oz oat latte is not one item with one stock number. It consumes:
- About 11 oz of oat milk
- Two shots of espresso, which is a dose of beans
- One 16 oz cup, one lid, and maybe a sleeve
- Pumps of syrup if it is a flavored version
Square's item stock counts finished goods. The catalog item "Latte, 16 oz" can carry a count, but nobody buys a pre-made latte from a vendor, so a count of lattes means nothing. What you need decremented is the oat milk, the beans, and the cup.
Square does have recipe and ingredient features in its restaurant products; check Square's own page for what they cover today. Whether they deduct for modifiers, such as the oat swap that changes which milk gets used, is something to test rather than assume. Here is the test I'd run on any tool, including mine: ring up a 16 oz latte with oat milk and an extra shot, then look at what got decremented. If the whole milk went down, or the extra shot never showed up, the tool is tracking the menu item and not the drink.
Three other things cafes hit quickly:
- Sizes. A 12 oz and a 16 oz latte use different amounts. Per-size ingredient quantities need to live somewhere.
- House-made items. A vanilla syrup you cook from sugar, water, and vanilla is an ingredient made out of ingredients. Costing it means a prep recipe nested inside the drink recipe.
- Pack sizes versus usage. You buy oat milk by the case of 12 cartons and use it by the ounce. Something has to convert between the two, with a cost per ounce that follows the invoice price.
That last one is where the money leaks. Say a case of oat milk goes from $38.40 to $41.76. A case is 12 cartons at 32 oz, so 384 oz. Cost per ounce moves from $0.100 to $0.109. On an 11 oz pour, the milk in one latte goes from $1.10 to $1.20, a dime. At 300 oat lattes a week that is about $29 a week, or roughly $1,500 a year, from one price change on one item. A tool that never sees the invoice never notices.
The MarketMan add-on inside Square
In April 2026, Square and MarketMan launched Square Restaurant Inventory by MarketMan. It is a partnership and product integration, not an acquisition, and it is an add-on billed through Square for restaurants. (Source: Square's press page on the Square Restaurant Inventory by MarketMan launch, squareup.com/us/en/press/square-restaurant-inventory-marketman, accessed 2026-08-26.) MarketMan has been in restaurant inventory for a long time, and the add-on is built for restaurants with large ingredient lists.
I am deliberately not quoting a price. Check Square's page for the current price and terms, then decide whether a restaurant-grade inventory system is sized for a counter-service cafe with thirty ingredients that matter.
If you want my full read on the vendor itself, the ShelfCount versus MarketMan comparison lays it out. It is a capable system and the right tool for some operations. The questions I'd ask are what it costs a month all-in, how long setup takes with your real menu, and whether the person who closes on a Sunday will actually use it. Software nobody opens produces numbers nobody trusts.
What an add-on should do for a cafe
Whatever you pick, whether that is the add-on, ShelfCount, or a spreadsheet, here is the checklist I'd hold it to. Each item is something I run into at Stella.
Cost recipes down to the ingredient, with modifiers. Oat swap, extra shot, and sizes must change the ingredients used. In ShelfCount you map each Square variation to a recipe once, and modifiers carry real ingredient effects, so an oat latte with an extra shot is costed as exactly that. The walkthrough is in mapping your menu to recipes.
Read the invoice. When the price of oat milk changes, the cost of every drink that contains it should change too. ShelfCount takes receipts by phone camera, email, or file, and every line goes through a review step before it touches your costs. Nothing commits on its own. The details are in receipts and invoice scanning.
Turn counts into orders. A count that sits in an app does nothing. The count should produce a suggested order against your par levels, rounded to whole packs, in the vendor's preferred line order, drafted as a purchase order, and emailed for vendors you've set up for email. See vendors and purchase orders.
Compare what you should have used with what you used. This is usage variance. Sales say 20 gallons of milk should have gone through the machines this week. Your counts say 23. That gap is waste, over-pouring, or theft, and you cannot see it without both numbers. The usage variance report lays it out per item.
Work on your POS. A Square-only tool is fine until you move, add a second concept, or buy a shop that runs something else. ShelfCount reads Square, Toast, and Clover. Today you paste in an access token you create in Square. Square doesn't scope that token to read-only; ShelfCount only calls the read endpoints (locations, catalog, orders, refunds) and never writes to Square. Read-only OAuth is on the roadmap, and I'll update this post when it ships. Clover connects with a dashboard API token, and Clover App Market approval is still pending. Toast support is built and waiting on Toast's partner approval, so I won't tell you it is live. The Square integration guide shows exactly what syncs.
Price. ShelfCount is $50 a month, flat, with unlimited team members and storage areas. No annual plan and no per-seat charge. There is a 14-day free trial, and you can try the live demo first. The pricing page has the whole thing on one screen. Multi-unit enterprise reporting is not something we have yet, so a chain that needs consolidated roll-ups across dozens of stores should look elsewhere.
When Square alone is enough
Plenty of shops should stop reading here and keep what they have.
Square alone is probably enough if:
- You sell mostly bought-in items: bottled drinks, packaged snacks, bakery pastries, retail beans
- Your drink menu is short and your ingredient cost is a small share of sales
- You can already say what a latte costs you to the penny, and your food cost has not moved in months
- Nobody is asking where the milk goes
A quick test: take a week of invoices for the things you make drinks from and add them up. Divide by a week of drink sales. If that percentage matches what you think it is, and matches last month, you do not have a tracking problem.
You probably want more than Square if:
- Your milk, espresso, and syrup bills keep climbing and you cannot say which drinks changed
- You offer several milks, sizes, and add-ons
- You make syrups, sauces, or batters in house
- You order from several vendors by phone, text, or a clipboard
- More than one person counts and the numbers disagree
If you are in the second group, the cafe inventory guide covers how I count, and the par level post covers how I decide what to order. ShelfCount for coffee shops shows how the pieces fit together for a counter-service cafe.
Test your setup on five drinks
Pick the five drinks that make most of your money. Write out, ounce by ounce, what goes into each at each size. Price those ingredients from your last real invoice. That is a recipe cost, and you can do it today with a pencil or with the free recipe cost calculator.
Then ask whether your current setup can produce that number on its own, update it when an invoice changes, and tell you at the end of the week how much you should have used. If it can, you are done. If it cannot, you have just defined exactly what you would be buying, which makes every demo you sit through a lot shorter.