TRACKITWEEKLY FIELD GUIDE
Why Am I Always Running Out of the Same Inventory Items?
Short answer: if you keep running out of the same items, the problem is almost never a careless team. It usually means one of three things. Your order-up-to levels were set once and never adjusted. Your real usage has crept above what your order guide assumes. Or product is leaving the building without being sold, portioned, or recorded. Stockouts that repeat on the same items are a data problem wearing a staffing disguise.
The good news is that all three causes are diagnosable with information you already have or can collect in one week. Let's walk through it.
What this problem looks like in real life
- The same five to ten items are gone by mid-week, every week, while shelves of other products sit untouched.
- Someone runs to a retail store or a competitor to buy substitutes at full price.
- Your system or count sheet says the item is in stock, but the shelf is empty.
- One location runs out constantly while another location of the same business never does.
- The item is always gone on the same day of the week, usually right before or right after delivery day.
If two or more of these sound familiar, keep reading. The pattern matters more than any single incident.
The likely root causes, and how to tell them apart
1. Your par level was set once and never revisited
Most small businesses set order quantities early on, often based on a supplier's suggestion or a gut feel from opening week. Then the business changes. A popular item gets promoted. A portion gets slightly bigger. A catering order gets added on Fridays. The order quantity stays frozen while reality moves on. If your order history shows the same quantity ordered for the same item week after week, regardless of what is actually on the shelf, this is probably your problem.
2. Usage has crept up, and your average can't keep up
Usage grows quietly. A menu change, a new regular who orders the same thing daily, seasonal traffic, or a neighboring business closing can all push demand up 10 to 20 percent over a quarter without anyone noticing. If you order off a fixed number rather than a rolling average of actual usage, you are always ordering for the business you had, not the business you have.
3. Your lead time assumption is wrong
If stockouts always happen right before delivery day, your buffer is too thin for the actual gap between order and shelf. Trucks run late. Suppliers short you and backorder. A holiday shifts a delivery. If you assumed a two-day lead time and reality is four, you will run out of fast movers every single week no matter how good your counts are.
4. Product is leaving without being recorded
Over-portioning, unlogged employee meals, spoilage tossed without a note, remakes, and sometimes theft all drain inventory without showing up in sales. The tell: your purchases keep rising, your sales are flat, and the item still runs out. That gap between what you bought and what you sold is going somewhere.
5. Your counts are wrong, so the shelf looks fuller than it is
Counting cases as units, counting a case as twelve when the supplier switched to eight, or counting from memory instead of the shelf will all make your on-hand number look healthy while the shelf sits empty. If your counts bounce around a lot week to week on the same item, distrust the count before you distrust anything else.
6. A repeating demand spike your baseline ignores
Some spikes are predictable: a local event, a seasonal weekend rush, a school schedule. If the item runs out the same week every month or every season, your baseline quantity is built on calm weeks and cannot survive busy ones.
How to figure out which cause applies to your operation
Spend thirty minutes on these checks. You do not need software for any of them.
- Pull up the last eight weeks of orders for the problem items. Are the quantities nearly identical every week? That points to cause one or two. Do the quantities swing with no pattern? Look at cause five or six.
- Write down the day and time each stockout happened. Always right before delivery day points to cause three. Always after a busy weekend points to cause two or six.
- Recount one problem item right now, carefully, in units not cases. Compare it to what your sheet said. A gap of more than a few percent points to cause five.
- Compare purchases to sales for one month. If you bought 20 percent more of the item than sales justify and you are not building any stock, cause four is in play.
- Ask the person who uses the item most. "Has anything changed about how we use this?" Operators on the floor almost always know before the office does.
Practical corrective actions
- Raise the order level on proven movers, and do it deliberately. Add enough to cover real usage plus a buffer for lead time, then watch for two weeks. Adjust again if needed. One thoughtful change beats ten panicked ones.
- Order from usage, not habit. A rolling average of the last three weeks of actual usage, plus a look at the upcoming calendar, is a solid ordering baseline for most small operations. This is exactly the kind of number a weekly count workflow produces almost as a side effect.
- Fix the count before you fix the order. If the count is wrong, every order built on it inherits the error. Count in the same unit the supplier sells in, and count the shelf, not the memory.
- Investigate the gap between purchases and sales. Watch portioning for a day. Check whether employee meals and remakes get recorded. Spoilage should leave a paper trail, even a simple one.
- Adjust for known spikes in advance. If the third week of every month is heavy, plan the order before the week arrives, not after you run out.
Where TrackItWeekly fits: this is the exact problem its weekly workflow is built around. Counts feed a rolling three-week usage average, low-stock alerts flag problem items before the shelf empties, and PAR multipliers (1x, 1.5x, 2x) let you raise order levels for seasonal weeks without rebuilding your whole setup. Where it does not fit: it will not by itself catch theft or portion drift. Those need eyes on the floor and clear rules, with TrackItWeekly surfacing the numbers that tell you where to look.
What to track going forward
- Weekly usage per item, from an actual count, not an estimate.
- On-hand quantity at count time, in the same unit you order in.
- A simple stockout log: item, day it ran out, day the next delivery lands.
- Days of supply on hand for your top movers, calculated as on-hand divided by weekly usage.
What not to do
- Do not bulk up everything. Blanket over-ordering ties up cash, fills your storeroom with slow movers, and hides the actual problem item behind a pile of stuff you did not need.
- Do not set a bigger number and walk away for a year. That is how you got here. Levels need a regular look, even a quick one.
- Do not accuse the team before you check the numbers. Running out of the same item is almost always a system issue first. Jumping to blame burns trust and fixes nothing.
- Do not rely on the supplier to catch it. Sales reps see order history, not your shelf. Only you know the item runs out every Thursday.
FAQ
How much buffer stock should I carry for my fastest movers?
Enough to cover usage during your longest realistic lead time, plus one busy day. If you use ten units a day and your worst-case restock gap is four days, carry around fifty, then verify against reality after two weeks. Fine-tuning from real data beats any rule of thumb.
What if only one location runs out?
That usually means that location's counts are off, its usage genuinely differs, or product is walking out there. Compare its order history and counts against a stable location before changing anything company-wide.
Is a rolling three-week average enough, or do I need forecasting software?
For most single and small multi-location operations, a rolling three-week average plus your own knowledge of upcoming events beats a complex forecast you will not maintain. Forecasting software earns its keep at larger scale, with more locations and more volatile demand.
My counts seem fine but we still run out. Now what?
Then the loss is happening between the count and the sale: portioning, unrecorded meals, spoilage, or theft. Spend a shift watching how the item actually gets used. The answer is usually visible within an hour.
Should I just order more from my main supplier to be safe?
Order more of the specific items that prove they run out, not everything. Carry the buffer where the risk is, and keep the rest lean.
Conclusion
Running out of the same items every week feels like bad luck. It is not. It is one of a handful of fixable causes: frozen order levels, drifting usage, a lead time you never verified, unrecorded loss, or counts you cannot trust. Pick the problem items, spend one week gathering the evidence, and fix the specific cause. A consistent weekly count and order rhythm is what keeps the fix in place, because it surfaces drift while it is still small enough to correct over coffee instead of during a Friday night rush.