Running 10 stores means you can't just shut everything down for a full physical inventory count. You need a method that keeps operations running while keeping your counts accurate.
That's where cycle counting comes in — and it's a game-changer for multi-location operators.
This guide walks you through how to implement cycle counting across multiple locations, so you catch inventory errors early, reduce disruption, and keep your operations lean.
Cycle counting is the practice of counting a small portion of your inventory on a rotating schedule, rather than conducting one massive physical count once a year.
Instead of:
You:
Why this matters for multi-location businesses: You can rotate counts across stores so no single location is disrupted, and you get continuous visibility into inventory accuracy rather than one annual snapshot.
Here's what happens when you do one annual physical count across multiple locations:
Cycle counting eliminates these problems by distributing the count workload and catching issues early.
Not all inventory is created equal. High-value or fast-moving items need more frequent counts than slow-moving stock.
ABC Analysis breaks your inventory into three tiers:
Pro tip for multi-location operations: Your ABC categories might shift by location. A specific espresso blend might be Category A at a high-volume cafe but Category B at a gym location. Use your point-of-sale (POS) data to determine tiers per store.
Distribute counts so every location participates in a manageable rotation. Here's an example for a 10-location operation:
Result: Every location counts A items twice a month, B items once a month, C items once a quarter. No disruption. Minimal staff time.
For restaurants/cafes with tight labor constraints: Count during slow periods (early morning before rush, or mid-afternoon). Assign one manager + one crew member. Takes 20-30 minutes per count day.
Manual counts on paper are error-prone, especially across multiple locations. Use a system that:
What to look for: Barcode scanning tools, inventory apps with mobile count capabilities, or even a spreadsheet if you're just starting (though not scalable long-term).
This is where cycle counting pays for itself.
When a count doesn't match your system, investigate the same day:
By investigating on day one, you prevent the error from cascading across 10 locations' food costs and purchasing decisions.
Setup (one-time):
Ongoing (recurring):
Monthly review: Analyze trends — are certain locations showing higher shrinkage? Are certain products consistently off? This data drives purchasing and training decisions.
1. Early shrinkage detection: Instead of finding a $10,000 food cost overrun in month 12, you catch a $500 issue in week 2. Multiply that by 10 locations and the savings compound quickly.
2. Reduced operational disruption: One 30-minute count per location per week is far less disruptive than coordinating a full count across 10 stores. Staff morale improves.
3. Better purchasing accuracy: Real-time inventory data means you order based on actual usage, not guesswork. Less waste. Better margins.
4. Staff accountability: When counts are frequent and data is tied to individuals, shrinkage drops. People know their counts matter.
5. Reduced compliance risk: For food service operators, regular cycle counts demonstrate due diligence in food cost management. Auditors love this.
Challenge: "We don't have time for weekly counts."
Solution: Start with A items only (your top 20% of SKUs by value). That's just 5-10 items per location per week. Add B and C items later once the habit is established.
Challenge: "Our counts never match the system."
Solution: Your data is dirty. Dedicate one week to a full audit — recount everything, fix the system to match reality, then start cycle counting from a clean baseline. It's worth it.
Challenge: "We're getting different numbers from different locations."
Solution: This means your counting process isn't consistent. Create a written SOP: same time of day, same person if possible, same counting method (left to right, top to bottom). Train everyone the same way.
Challenge: "We're still finding massive discrepancies."
Solution: Investigate the discrepancy, not the count. If counts are consistently wrong by the same amount, something systematic is wrong: theft, receiving errors, POS voids not recorded, expired items not pulled. Find the root cause.
Cycle counting is the difference between knowing your inventory is accurate and guessing it is. For multi-location operators running on thin margins, that knowledge is worth thousands of dollars a month.
Start with A items. Start this week. Start at one location. By next month, you'll have real data showing you exactly where your shrinkage is — and that's when the real cost savings begin.