Coffee Shop Inventory Management: A Square Shop Workflow
A weekly coffee shop inventory management workflow for Square shops: count units, pars, waste logs, receiving and reorders, plus where Square's item tracking stops.
By Jared · 2026-11-09 · 9 min read
Coffee shop inventory management on Square works best as a weekly routine built on ingredients, not menu items: set one count unit per product, set a par for each, count the same way every week, log waste, and reorder from the gap between par and what is on the shelf. Square tracks the items you sell. It does not know how much milk is left in the walk-in.
That gap is where most independent shops lose money, quietly. A lost case of oat milk or a drifting bean order never shows up as a line on a report. This post lays out the workflow we run across three Kinos Coffee shops. It works with a clipboard, a spreadsheet or software, and it's written for owners and general managers on Square with one to five locations.
Why Square item inventory isn't ingredient inventory
Basic inventory alone is described as tracking finished goods, though Square now offers ingredient-level tracking and recipe-based ingredient cost tracking through Square Recipes, a beta feature for Square for Restaurants Plus or Premium subscribers. When a customer orders a 12 oz oat latte, Square records one sale of one item. It does not subtract 10 oz of oat milk, a shot of espresso, a cup, a lid and a sleeve.
So ingredient-level tracking is a separate layer. Square's own answer is Restaurant Inventory by MarketMan, an add-on for Square Plus or Premium listed at $99 per location per month in the US. It maps POS sales to estimated ingredient usage through recipes. Square also offers Square Recipes for ingredient cost tracking. Check that your plan and region support them before you commit.
The workflow below doesn't depend on any one tool. Whatever you use, you need ingredient-level counts, pars and waste. Square tells you what you sold. You still have to tell it, or your spreadsheet, what you used.
Set count units for milk, beans, syrups and cups
Pick one count unit per ingredient and never change it. Two people counting the same shelf must land on the same number, and that only happens when the unit is obvious.
We use these:
Milk: gallons or half-gallons, with opened containers counted as tenths (0.3 of a gallon). Oat and other alternatives get the same treatment, by carton.
Beans: pounds, by blend. Count the open bag on the bar as a partial bag and the backstock as whole bags.
Syrups: bottles, with the bottle in use counted as a fraction.
Cups, lids and sleeves: sleeves of cups, not individual cups. A sleeve of 50 is one count.
Write the unit on the count sheet next to the item name. Group items by where they live (walk-in, dry storage, bar) so the counter walks the shop once, not three times. When the count unit matches how you order from the vendor, reordering gets much faster, because the number you counted is the number you buy.
Build par levels from real usage and delivery days
A par level is the amount you want on hand right after a delivery lands, and you set it from usage between deliveries, not from a hunch. The formula is simple: expected use until the next delivery, plus a modest buffer for a busy weekend or a late truck.
Take whole milk. If you use about 14 gallons across a Monday to Thursday stretch and your next delivery is Friday, your par is those 14 gallons plus a buffer, say 3 gallons. Order the difference between par and usable stock on hand, minus anything already on the way.
Two rules keep pars honest:
Build them from two or three weeks of actual counts, not from one slow week.
Revisit them when something changes: a new menu item, a season shift, a new delivery schedule or a new wholesale account.
Fast movers like milk need tight pars because they spoil. Dry goods like cups can carry a wider buffer. Beans sit in between: track them by blend and roast date, and don't order more than you can use while the coffee is at its best.
Run a weekly count that two people would do the same way
A weekly count is repeatable when it happens on the same day, at the same time, in the same order, with the same units. We count before opening, when nothing is moving and the shelves are as full as they will be.
A count routine that holds up:
Same day, same time. Pick the day before your biggest delivery so the count feeds the order directly.
Same walk. Number the count sheet in the order you move through the shop.
Count opened containers as partials. Never round an open milk jug up to one or down to zero.
Different frequency by item. Milk daily or near daily, beans at least weekly, dry goods weekly.
One counter, one checker for the first month. A second person spot-checks five items. If they disagree, the unit definition is the problem, not the person.
The test is simple. If the opener and the closer would count the same shelf and write down different numbers, tighten the unit until they match.
Log waste and check milk usage against sales
Waste logging only works if it takes ten seconds, so log it when it happens: item, quantity, reason. Milk poured out at close, steamed milk left over, bean dial-in and purge shots, spills and remade drinks all count.
Review the log weekly and look for repeats. If the same two reasons keep showing up, that's a process fix, not a counting problem. A shop that dumps a gallon of oat milk every Sunday has a par that's too high or a prep habit that's too generous.
Then run the check that catches the rest: compare expected milk use against actual use. Expected use comes from drinks sold and your recipe sizes. Actual use is opening stock plus deliveries minus closing stock. A small gap is normal. A persistent gap points to over-pouring, spoilage or drinks rung in wrong.
Do this for milk first. It's your highest-volume, shortest-life ingredient, and the number is the easiest one to trust. Once you believe the milk number, extend the same check to beans. If you cost drinks from these usage numbers, our post on recipe costing software for Square coffee shops covers the next step.
Receive orders and make the reorder decision
Receiving is where inventory either stays accurate or quietly drifts. Check every delivery against the order before the driver leaves: items, quantities, damage and dates. Anything short or damaged gets noted on the spot, not discovered on Thursday.
Then update your on-hand counts with what arrived, so the next count starts from the right place.
The reorder decision follows from the count: par minus usable stock on hand, minus anything already on order, rounded to the vendor's case size. Two judgment calls matter:
Case rounding. If the math says 2.4 cases, decide whether to round to 2 and risk a short week or to 3 and carry more. Perishables round down, shelf-stable items round up.
Upcoming changes. A farmers market weekend, a holiday or a new menu drink should push the order above the formula.
The reorder should take minutes if your count units match your vendor's units. If it takes an hour, the units are wrong.
Keeping inventory consistent across multiple shops (and where StoreSync fits)
The hard part of a second and third shop isn't the workflow. It's keeping three shops on the same units, the same pars logic and the same item names. Three managers will drift into three versions of the count sheet within a quarter.
StoreSync is operations software for Square coffee and restaurant shops: inventory, recipe costing, scheduling, checklists, labor reporting and kitchen display in one login. We built it inside Kinos Coffee, our own three-shop business, which runs it daily with about 25 employees, 147 core menu items and 367 recipe variations. It syncs with Square, the only POS it supports today.
Pricing is $146 a month for one shop, billed annually, with $50 a month for each extra shop, two months free on annual and setup included. You can see what's in it on the features page.
Here's how it compares to the options Square owners usually weigh:
| Option | Ingredient-level tracking | Where it fits |
|---|---|---|
| Square item inventory | No, finished items only | Retail beans, bottled drinks |
| Restaurant Inventory by MarketMan (Square add-on) | Yes, via recipes | Shops that want inventory add-on inside Square; $99/location/month on Plus or Premium |
| Spreadsheet | Whatever you build | One shop, one careful counter |
| StoreSync | Inventory with recipe costing, scheduling and checklists in one login | 1 to 5 Square shops that want one system |
For the wider picture, see our posts on coffee shop management software and food cost management software. Choose on one criterion first: does it keep three shops on the same units and the same item list?
FAQ: Square coffee shop inventory questions
These are the questions owners ask most. The short version: Square counts what you sell, you count what you use, and the weekly routine in this post connects the two.
Does Square track ingredients like milk and beans?
Not in its basic inventory, which tracks finished items. For ingredient-level tracking with recipes and par alerts, Square points to Restaurant Inventory by MarketMan, an add-on for Square Plus or Premium.
What are coffee shop inventory management best practices?
Use one count unit per ingredient, set pars from real usage and delivery days, count on the same day each week, log waste as it happens, and compare expected milk use against actual use. Count perishables more often than dry goods.
How do I reduce waste in a coffee shop?
Log every discard with item, quantity and reason, then review the log weekly for repeats. Tighten pars on perishables, count milk daily, and check milk usage against sales to catch over-pouring.
Start with milk and one weekly count, then put it in one system
You don't need a perfect system to start. Pick your count units this week, set pars for milk and beans, and count on the same day for a month. The numbers will tell you where the waste is. When you're ready to run that routine across inventory, recipe costing and the rest of the shop in one login, book a demo with StoreSync at getstoresync.com/demo and we'll walk through it with your Square setup.
Common questions
How do I manage ingredient inventory for a Square coffee shop?
Square's basic inventory tracks finished items, so ingredient inventory needs its own routine: one count unit per ingredient, pars based on usage between deliveries, a weekly count, a waste log and a milk usage check. StoreSync is operations software for Square shops that includes inventory and recipe costing in one login.
How do I set par levels for milk, beans and syrups?
Estimate use until your next delivery, then add a modest buffer for busy days or late trucks. Order the gap between par and usable stock, minus anything already on order. Build pars from two or three weeks of real counts and revisit them when your menu, season or delivery days change.
How often should a coffee shop count inventory?
Count milk daily or near daily, beans at least weekly, and do a full count weekly on the same day, before opening. Use the same units every time and count opened containers as partial quantities so two people get the same result.
What does StoreSync cost for a Square coffee shop?
One shop is $146 a month billed annually, and each extra shop adds $50 a month. Annual billing includes two months free and setup. StoreSync syncs with Square, which is the only POS it supports today.