A LEGO inventory cycle count is a scheduled, partial recount of your stock, broken up by bin, shelf, or category, that lets you catch missing minifigures, mislabeled parts, or pricing mistakes before they quietly eat your margin. Instead of shutting your whole operation down once a year for a giant count, you recount a slice of your inventory on a rotating schedule so problems surface in weeks, not months.
I started running cycle counts after I noticed my sold totals on eBay and Whatnot weren't lining up with what I thought I still had sitting in bins. In my experience, that gap almost never shows up as one dramatic loss. It shows up as five or six small ones: a figure that got bagged with the wrong torso, a part that got tossed in the wrong drawer, a listing that never got marked sold. A cycle count is how you catch that drift before it becomes a real dollar problem.
- A cycle count is a rotating partial recount, not a full annual inventory shutdown.
- Shrinkage in a LEGO reselling business is usually death by a thousand small mistakes, not one theft.
- Count your fastest-moving, highest-value inventory (loose minifigures, CMF, sealed sets) more often than slow-moving bulk parts.
- A simple spreadsheet or a scanning tool like brick'em can turn a count that used to take a weekend into an afternoon.
What Is a LEGO Inventory Cycle Count?
A LEGO inventory cycle count is a recurring, partial physical count of a portion of your inventory, done on a set rotation so that every bin, shelf, or category gets recounted several times a year without ever closing your whole shop down at once. It's the retail and warehousing version of doing a little maintenance constantly instead of one huge overhaul annually.
For a reseller, that usually means picking one section of your inventory (say, your loose Star Wars minifigures, or last month's bulk lot) and counting it against what your spreadsheet or app says should be there. When I sort through a new bulk lot, I count it into the system once as it comes in, then recount that same bin again a few weeks later. If the numbers match, great. If they don't, I've found a problem while it's still small and traceable.
Why Does LEGO Inventory Shrinkage Happen?
Shrinkage happens for a mix of ordinary reasons: mis-picks during packing, parts that get separated from the wrong minifigure during sorting, listings that go unmarked after a sale, breakage in shipping, and the occasional item that walks off at a live event or a shared workspace. It's rarely one big theft and much more often a pile of small process gaps.
In my experience, the biggest source of shrinkage in a home-based LEGO business isn't dishonesty, it's speed. When you're trying to photograph, list, and ship fast enough to keep up with eBay and Whatnot sales, it's easy to grab the wrong bag off a shelf or forget to deduct a part from your count. A seller I know runs a small operation out of a spare bedroom and told me most of what he "lost" over a year turned out to be misfiled inventory, not missing inventory, once he actually went looking bin by bin.
How Often Should You Run a Cycle Count?
Most resellers should count their highest-value, fastest-moving inventory (loose minifigures, sealed sets, and Collectible Minifigures) monthly, mid-value bulk-sorted inventory quarterly, and slow-moving raw bulk lots once or twice a year. The exact cadence matters less than actually sticking to a schedule instead of only counting when something feels off.
I personally count my minifigure shelves every month because that's where the dollar value per square inch is highest and where a small mistake (say, ten missing figures at ten to twenty dollars each) adds up fast. Bulk parts sitting in flat-rate boxes waiting to be sorted get a lighter touch since the per-piece value is low and a small count discrepancy there barely moves the needle.
| Inventory Type | Suggested Count Frequency | What to Check |
|---|---|---|
| Loose minifigures & CMF | Monthly | Quantity, completeness, correct listing status |
| Sealed sets | Monthly | Box condition, correct location, matched to catalog |
| Sorted bulk parts (by color/category) | Quarterly | Bin labels, spot-check quantity vs. spreadsheet |
| Raw, unsorted bulk lots | 1-2x per year | Total lot count vs. purchase record |
| Manuals, boxes, accessories | Quarterly | Matched to correct set, condition noted |
Setting Up a Cycle Count System for Bulk LEGO Inventory
A workable cycle count system needs three things: a way to identify what's actually in a bin, a running record of what should be there, and a fixed date to compare the two. Without all three, you're just guessing whenever something feels wrong instead of catching it on schedule.
I use a simple rotation: every bin or shelf gets a number, and I assign roughly a quarter of my bins to be recounted each week so the whole inventory cycles through about once a month. When I first started, I tried to do this from memory and a notebook, and it fell apart within a few weeks. What actually stuck was cataloging everything as it came in with a tool built for this, since identifying and logging minifigures by hand is where most sellers give up on counting altogether. This is exactly the kind of workflow brick'em's free scanning and cataloging tools were built to speed up, so a count that used to take a weekend can take an afternoon instead.
How Do You Cycle Count Minifigures, Sealed Sets, and Bulk Parts Differently?
Minifigures need the most careful counting because they're the most valuable per square inch of shelf space and the easiest to accidentally mismatch (a body from one figure with the head from another). Sealed sets need a location and condition check more than a piece count. Bulk parts mostly need a weight or volume spot-check rather than counting every single piece.
For minifigures, I recommend counting by checking each figure against its listing, not just eyeballing a shelf and guessing a number. A minifigure database helps here too. If you're not sure whether a torso or accessory actually belongs with a given figure, cross-referencing against a minifigure database before you recount saves you from "fixing" a mismatch that was correct all along. For sealed sets, I check that the box is still sealed, undamaged, and sitting in the location my spreadsheet says it should be. For bulk, I weigh a sample bag against my expected count-to-weight ratio rather than counting every brick by hand.
What Should a LEGO Reseller Do When a Cycle Count Turns Up a Discrepancy?
When your count doesn't match your records, the first step is to recount that specific bin or category before assuming anything is actually missing, since simple counting or data-entry errors cause most discrepancies. If the second count confirms a gap, check your recent sales, shipping, and listing records for that item before writing it off as shrinkage.
I've seen plenty of "missing" minifigures turn out to be sold-and-shipped items that never got marked as sold in the spreadsheet, or a figure that got moved to a different bin during a reorganization. Only after you've ruled out a records error should you log it as genuine shrinkage. Once you do, write down what happened and when, because a pattern of discrepancies in the same bin or category over several counts is usually pointing at a real process problem, like a packing station that's too close to a similar-looking bin.
What Does Shrinkage Actually Cost a LEGO Resale Business?
Shrinkage costs more than the value of the missing item itself, because it also costs you the time you already spent sourcing, identifying, cleaning, and listing that piece before it disappeared. On higher-value minifigures priced anywhere from $10 to $20 each, a handful of missing figures a month can add up to real money over a year, which is exactly why catching shrinkage early through counting is cheaper than absorbing it silently.
It also helps to think about shrinkage next to what you're already paying in selling fees. I've sold over $100,000 worth of LEGO on eBay over the years, and once promoted listings are factored in, my total take rate on some of those sales has crept close to 25 percent. On BrickLink, whole-store acquisitions between resellers often trade for somewhere around 30 percent to 50 percent of market value. Against numbers like that, losing even a small slice of inventory to sloppy counting is an expensive way to give margin back that you already worked hard for.
Heads up: This is not financial or legal advice. We're sharing what we've learned from the LEGO reselling community.
If you want a rough sense of how much your current inventory is worth so you can see what a percentage of shrinkage actually costs you in dollars, running your collection through a collection value calculator before and after a count cycle is a useful gut check. It won't replace an actual physical count, but it puts a number on what's at stake.
How Does Cycle Counting Fit Into a Bulk Lot Reselling Workflow?
Cycle counting fits into a bulk lot workflow right at intake: you count and log the lot once when it arrives, sort and reprice it, then schedule that same bin for a recount a few weeks later once it's been picked over for sales. This catches sorting mistakes early, while the lot is still fresh in your memory and easy to trace back to its source.
Bulk lots are where I see the most opportunity for shrinkage to hide, simply because there's so much volume moving through at once. When I sort a new lot, I log the total piece count and rough category breakdown before I ever put anything up for sale, using something like brick'em's haul calculator to get a fast read on what a lot is actually worth so I know what I'm supposed to end up with after sorting. That starting number becomes the baseline my first cycle count gets checked against.
Frequently Asked Questions
What's the difference between a cycle count and a full inventory count?
A full inventory count means stopping and counting every single item you own at once, usually once a year. A cycle count breaks that same work into smaller recurring chunks, counting a portion of your inventory on rotation so the whole thing gets recounted regularly without ever shutting down your entire operation at once.
How long should a LEGO cycle count take?
A single cycle count session, covering one bin, shelf, or category, should take anywhere from twenty minutes to a couple of hours depending on how much inventory is in that section and whether you're counting by hand or using a scanning tool. In my experience, scanning tools cut that time significantly compared to manual counting and spreadsheet entry.
Can cycle counts help with pricing, not just shrinkage?
Yes. While you're recounting a bin, you're also looking directly at condition and completeness, which is a natural moment to check whether your listed price still matches current demand on BrickLink or eBay. Many sellers I know fold a quick price review into their cycle count instead of treating pricing as a separate task.
Do I need special software to run cycle counts?
No, a basic spreadsheet with bin numbers, expected quantities, and count dates is enough to start. That said, identifying and logging minifigures by hand is the slowest part of the process, which is why a lot of sellers eventually move to a scanning and cataloging tool once their inventory grows past a few hundred items.
What should I do after finding repeated shrinkage in the same bin?
Treat repeated shrinkage in one bin as a process signal, not bad luck. Look at what's physically near that bin, who has access to it, and whether it sits close to a similar-looking bin that could cause mix-ups. Fixing the layout or labeling around that spot usually solves it faster than trying to police the symptom.
.png)
