Can Square Track Coffee Shop Ingredient Inventory?

The question Square's own forums keep asking

In Square's Seller Community, a cafe owner asks how to track raw materials in inventory. Another, running a coffee shop on Square with a third-party inventory tool, explains the wall she keeps hitting: a latte can have different milks, espresso types, and modifiers, and her tool cannot follow the variations. The replies are workarounds. Make every variation its own item. Wire up an alert with a third-party automation. Update stock by hand.

The question is the right one. It just never gets a straight answer, so here is one, from an owner who runs a cafe on this exact stack.

Your POS counts what sold. Your shelves lose what you used.

A register has one job: record the sale. "Iced matcha latte, oat milk, $6.75." That line is perfect sales data and zero inventory data, because what left your shelves was not an iced matcha latte. It was a scoop of matcha, a pour of oat milk, a cup, a lid, and a straw.

No POS knows that by default. Not Square, not Toast, not Clover. A point of sale tracks finished goods, the sellable items in the catalog. Square says this itself: its basic inventory "only tracks finished goods" (Square's own product page, July 2026). Finished-goods tracking works when what you sell is what sits on the shelf: bags of beans, bottled drinks, merch. A cafe sells assemblies. The gap between the receipt and the shelf is where the guessing lives.

Why a latte breaks item-level tracking

The workaround every owner tries first: make each variation its own catalog item. Do the arithmetic before you commit. Two sizes, four milks, hot or iced, here or to go. That is 32 items for one drink, and your baristas now hunt through 32 buttons during the rush. The owner in that community thread ran the same math and abandoned the idea for exactly this reason.

The deeper problem is that the interesting information lives in the modifiers. At my shop, 47 iced matcha lattes sold means 94 g of matcha, 564 oz of oat milk, and 47 cups used. Swap twelve of those to whole milk and the oat number changes while the receipt total does not. An extra shot changes what left the grinder, not what the item was called. If the tracking layer cannot read the modifier on each ticket, its numbers drift a little every day, and by Friday the count on paper and the count in the fridge are strangers. This is why recipe costing starts with the recipe, not the price.

What Square actually offers today

Three options exist inside the Square ecosystem, as of July 2026. Each has an honest fit.

Built-in inventory, free. Item-level counts and daily low-stock alerts on finished goods (Square inventory features, July 2026). Right answer for the retail side of a cafe: whole-bean bags, cold brew cans, mugs. It has no concept of ingredients, so it cannot see your milk.

Square Recipes, in beta. For Square for Restaurants Plus and Premium, at no listed extra cost: build ingredients, attach recipes to items, deplete stock on each sale. The limits are in Square's own documentation: no batch recipes, and recipes "cannot be applied to modifiers or multi-variation items." For a drink menu where the money moves through milk swaps and extra shots, that limitation is the whole game.

Square Restaurant Inventory by MarketMan. Launched globally on April 2, 2026: a full back-of-house suite with purchase orders, invoice scanning, and vendor management, sold inside the Square dashboard. It costs $99 per month per location as an add-on that requires Square Plus at $49 or Premium at $149, so the realistic floor is $148 a month, and the published price applies to sellers new to MarketMan only (Square's product page, July 2026). Activation goes through a Square account manager, not self-serve signup. The launch showcase is a six-location biscuit group, and that is the honest tell: this is restaurant-grade machinery, built for invoice volume and multi-site visibility. If you run several locations or drown in invoices, it deserves your shortlist.

What none of the three gives a single cafe is modifier-accurate ingredient tracking at single-cafe price and setup effort.

The same map on any POS

This is not a Square problem. Toast's answer is xtraCHEF, an invoice-first add-on that only works inside Toast and publishes no price. Clover's answer is a marketplace of third-party bolt-ons. Every POS draws the same picture: a register that counts sales, plus a separate layer that turns sales into ingredient math. So the useful question is not "which POS tracks ingredients," because at cafe grain none of them do natively. The question is what the layer on top has to do.

What the ingredient layer needs to do for a cafe

Hold any tool, mine included, against this list:

• Read every ticket with its modifiers, and map each drink to a recipe. A milk swap is a replacement at the same volume; an extra shot is an addition.
• Accept a physical count from a phone as ground truth, and run sales-based depletion between counts instead of pretending the count never ages.
• Turn the gap between projected stock and the next delivery into an order, timed to each supplier's window, so the answer arrives before the deadline does.
• Keep cost per drink current as invoice prices move, so pricing decisions use this month's milk price, not last spring's.

Everything that happens after the connection is made, the live consumption picture, the data-driven orders, the real drink costs, is covered in what changes when you connect your POS to inventory.

The one-question test

When you evaluate anything for this job, ask it one question: we sold 47 iced matcha lattes this morning, so how much oat milk is left? A register answers with revenue. An ingredient layer answers in ounces. If the demo cannot answer in ounces, whatever it is tracking, it is not your shelves.