Answer
What is convenience store inventory shrink?
Definition.
Inventory shrink is computed at the SKU level: expected on-hand = previous on-hand + receipts − sales. The difference between expected and actual (counted) on-hand is shrink. Aggregated to the category or store level, shrink expresses as a percentage of gross sales. The shrink number is universally tracked; the shift-level attribution is what separates well-run operators from the rest.
Step by step.
Receive vendor invoices at the SKU level.
Distributor or DSD invoice records SKU, quantity, unit cost, line total. OCR ingestion or hand-keying, the result must be SKU-level on-hand updates.
POS sales decrement on-hand per transaction.
Where POS is integrated, item-level sales decrement inventory continuously. Where not, batch update at EOD.
Run mobile cycle counts on a rolling cadence.
30–50 SKUs per day across high-velocity categories (tobacco, beverages, snacks). The system suggests which to count; clerk scans and enters the count.
Compare counted vs. expected on-hand.
Variance flags per SKU. Tobacco variances over the configured threshold escalate immediately; lower-velocity SKU variances aggregate.
Attribute variance to shift patterns.
A 2% velocity drop on a tobacco SKU correlated with the same overnight shift, with corresponding void burst, that's a flagged shrink pattern.
Investigate categories and patterns, not individual events.
One missing Marlboro pack is noise. Six missing Marlboro packs in 30 days on the same shift is a pattern. Investigate patterns; ignore singletons.
A concrete example.
Store buys 50 cartons of Marlboro Box (200 packs total) from McLane on Monday. POS records 142 packs sold by Friday close. Expected on-hand: 58 packs. Cycle count Friday night: 51 packs. Variance: 7 packs × ~$11/pack = $77 shrink. Cross-reference: 5 of the 7 packs disappeared during overnight shifts run by the same clerk over the week. Pattern flagged for owner review.
Checklist.
- Vendor invoice ingested at SKU level
- On-hand inventory updated per invoice
- POS sales decrement on-hand (live or daily)
- Cycle counts run rolling 30–50 SKUs/day
- Variance computed per SKU
- Tobacco / high-shrink categories prioritized
- Variance attributed to shift patterns
- Patterns investigated; singletons noted
- Vendor short-shipments flagged on receiving
Common mistakes.
Tracking inventory at the category level instead of SKU.
Category-level tracking hides the per-SKU patterns. The Marlboro Box shrink hides inside "tobacco." SKU-level is the actionable layer.
Running quarterly full counts and skipping cycle counts.
Full counts at quarter-end create a number that's too aggregated to attribute. Rolling cycle counts surface variance while attribution is still possible.
Investigating every variance as if it's theft.
Most variance is process, vendor short-shipment, mis-rang sale, count error. Investigate patterns, not individual events. Theft is a small minority of total shrink.
Not separating tobacco shrink from snack shrink.
They have totally different patterns. Tobacco shrink is targeted (high-value pockets); snack shrink is opportunistic (clerk grabs a Coke). Reporting and investigation should reflect the difference.
How StationPro fits in
The StationPro angle.
FAQs.
What's a normal shrink rate at a c-store?
1.5–2.5% of gross sales is the national average per NACS. Well-run independents can get to under 1%; high-shrink stores routinely run 3–4%. The variance between the best and the worst is roughly 4×, and the difference is process, not luck.
Where does most shrink come from?
Tobacco is the biggest single category. Beverages and snacks are second tier. Within tobacco, soft-pack pocketing is the most common pattern. Vendor short-shipments are a meaningful but often-undetected source for stores without invoice OCR.
How do mobile cycle counts work?
The system suggests 30–50 SKUs per day to count on a rolling basis. A clerk scans the SKU on a phone, enters the count, and moves on. Variance against expected on-hand flags for review. Full rotation across all SKUs takes about 30 days without a "big count" night.
Can shrink be measured without POS integration?
Yes, but lagged. Without POS, sales decrement happens at EOD (one bulk update per day) instead of per-transaction. Shrink detection still works; the time-to-detection shifts from minutes to hours.
See where your station is leaking money.
A 30-minute call. We build the demo around your stations, not a generic deck.