Skip to main content
AI InventoryComponent Map3D PrintingCircuit Breaker
Back to Blog
Component Map 5 min read 23 May 2026

Deciding What Spare Components to Keep vs. Pass On

The calculus of hoarding vs. contributing — and why it's simpler than it looks

Deciding What Spare Components to Keep vs. Pass On
Maker sorting through bins of spare electronic components deciding what to keep

Most makers I know have a component hoarding problem. Not a serious one — not the kind you'd write home about — but a consistent tendency to keep more than they need on the basis that it might be useful someday.

The justification is usually reasonable. Components are cheap. Storage is relatively easy. And the friction of not having something when you need it is real enough that keeping extras feels like sensible insurance.

But there's a cost to hoarding that accumulates slowly: the organisation overhead of tracking large inventories, the space taken up by components you haven't touched in two years, and the cognitive load of knowing you have stuff that hasn't been used and probably won't be.

More practically, every component sitting in your overflow bin is a component that could be useful to another maker right now, and isn't.

The keep threshold

The question I've started asking about spare components is simple: is there a realistic scenario in the next twelve months where I need this, and would it be annoying to not have it?

If yes to both: keep it. That's your working stock.

If no to either: the case for passing it on is strong. Either you're unlikely to need it, or the need is low enough urgency that ordering when the time comes would be fine.

The twelve-month window is more useful than "might need it someday," which is effectively infinite and keeps everything. A year is long enough to include most project cycles but short enough to exclude components that have been gathering dust for ages.

Categories that usually go

Project-specific components — parts purchased for a specific build that you've finished and won't revisit — usually shouldn't be held onto in large quantities. If you built three of something and have ten spare transistors from that design, you probably need two for repair/rework purposes. You don't need eight.

Superseded parts — components you used to use but have moved away from in favour of something better — are worth clearing out. You have a lingering attachment because you bought them, but that's sunk cost. If you wouldn't buy them again, there's no reason to hold them.

Parts you have far more of than you'll ever use — a hundred 1k resistors when you've established that you use maybe fifteen a year — are candidates for sharing. Keep what you'll realistically use. Pass the rest on.

What to keep no matter what

Common passives in standard values: resistors, capacitors, LEDs in the colours you use, small ceramic capacitors. These get used in almost every project. Keeping a good stock is genuinely worthwhile.

Basic semiconductor types that you reach for constantly: transistors like the 2N2222 or BC547, common MOSFETs, rectifier diodes. Small and cheap, but annoying to be without.

Any tools or specialised components for safety-critical aspects of your builds: fuses, TVS diodes, protective components. These are cheap, critical, and annoying to wait for if you don't have them.

Everything else: it's judgment. But when in doubt, it's often more useful to pass something on to someone who needs it now than to keep it on the basis that you might need it in three years.

List spare components on the RoboDIB Component Map — clear your bench and make your spares useful to other makers nearby.

List spare components

RoboDIB

Solve these problems yourself

AI inventory, component map, 3D printing, and circuit design tools — all built for India's maker community.