What Should You Do When One Week of Inventory Usage Is Abnormally High?

The Answer Up Front

Do not change your system based on one unusual week. One high-usage week is a signal to investigate, not a signal to raise your PAR levels, increase your standing order, or panic. Look for the specific cause: a one-time event, a delivery timing issue, a counting error, waste, or a transfer that was not logged. Fix the cause if there is one. Then let your rolling average absorb the outlier.

Investigate Before You React

The first step is always to figure out why the number is high. A usage number is just math: starting count plus received minus ending count. If any of those three inputs is wrong, the usage number is wrong. Start there.

Check your starting count. Was last week's count accurate? If someone undercounted last week, this week's usage looks artificially high. Recount if you have any doubt.

Check what you received. Did you receive a delivery that got logged twice? Did you receive a larger order than usual and forget to account for it? Receiving errors are a common cause of distorted usage.

Check your ending count. Did someone miscount this week? Did they miss a storage location? A low ending count inflates usage.

Look for Real Causes

If your counts and receiving records are accurate, the high usage is real. Now figure out what caused it.

• One-time event: A catering order, a private party, a local festival, or a promotional special can spike usage for a single week.
• Delivery timing: If your previous delivery was late, you might have drawn down extra stock last week to cover the gap. This week's usage reflects the catch-up, not a new trend.
• Waste or damage: A spill, a broken case, or expired product that got thrown out shows up as usage even though it was not sold or served.
• Unlogged transfer: Product moved to another location without being recorded. The sending location shows high usage. The receiving location shows low usage.
• Weather or business interruption: A snow day that closed you for two days followed by a packed weekend can compress a week's worth of usage into fewer days.

Do Not Raise Your PAR

The most damaging reaction to one high week is raising your PAR level. If the high week was a one-time event, your new PAR will be too high for every normal week going forward. You will over-order for months before you realize the mistake.

Wait for at least two consecutive weeks of elevated usage before you consider raising a PAR. Even then, raise it gradually. A 10% to 20% bump is usually enough. You can always raise it again if the trend continues.

Do Not Increase Your Standing Order

If you have a standing order with a supplier, do not increase it because of one high week. Standing orders are built on patterns, not outliers. If you need extra product for a specific event, place a one-time supplemental order. Do not change your recurring order until the pattern is clear.

Document the Outlier

Write down what happened. "Catering order for 200 people on Thursday" is enough. Next year, when you are reviewing seasonal patterns, you will see that week and understand why the number was high. Without documentation, the outlier becomes a mystery that distorts your averages forever.

How TrackItWeekly Helps You Handle Outliers

TrackItWeekly calculates a rolling three-week usage average, which naturally smooths out single-week spikes. When you look at a suggested order, you see the average, not just last week's number. This prevents you from overreacting to one unusual week.

Your count history is stored permanently, so you can look back and see exactly when the outlier happened. If you document the cause in your notes, that context stays with the data. Next year, you will remember why that week was different.

The app does not automatically flag outliers or prevent you from ordering more. It gives you the data to make an informed decision. The judgment call is still yours, but you are working from a rolling average instead of a single distorted number.

Frequently Asked Questions