Batch Ordering vs. Ordering As You Go — The Real Tradeoffs

I've tried both extremes and they both have serious problems.

The batch-ordering approach: every few months, I'd go through a list of components I'd been running low on, add a bunch of "probably useful soon" stuff, and place a large order. This was efficient in a narrow sense — one delivery event, one set of shipping fees, some volume discounts. But it consistently resulted in me having too much of things I used occasionally and running out of things I needed urgently, because my predictions about what I'd use were reliably wrong in specific ways.

The just-in-time approach: order exactly what you need for the project you're about to start. No inventory accumulation. Everything fresh. The problem was constant small orders, shipping fees adding up, delays that blocked builds, and the particular frustration of needing one component and paying ₹60 shipping on a ₹15 part.

Most makers I know have migrated to something between these — not by design, but through accumulated experience with both extremes. The question is where the middle should actually be.

What inventory actually costs you

Before deciding how much to stock, it helps to be honest about what carrying inventory actually costs.

Storage space is the obvious one — physical space that could be used for something else. For most makers in Indian cities, bench space is genuinely constrained.

Capital is less obvious but real. Components you've bought and aren't using are money sitting idle. ₹500 in components you might use next year is money that could have been invested or spent on something you need now.

Organisation overhead is the hidden cost. Every component you stock is a component you need to track, find space for, remember you have, and keep from getting lost. The component that's easy to order when you need it might not be worth stocking, because the management cost exceeds the convenience of having it on hand.

Against these costs, the benefits of inventory are: no shipping delays when you need something, no shipping fees on individual components, and the ability to prototype freely without ordering first.

What's worth stocking vs. what isn't

The components worth stocking heavily: things you use across multiple projects, that come in standard values or types, and that are cheap relative to shipping costs. Resistors, capacitors, common transistors, LEDs, hookup wire, standard connectors. You'll always need these. Bulk buys of passives make obvious sense.

The components not worth stocking: things you use once per project type, that are specific to a particular design, or that cost enough that carrying spare inventory is meaningful capital tied up. Microcontrollers, specific sensors, motor drivers — these are worth having a small buffer of (maybe two or three) but not a large surplus.

The components that look worth stocking but aren't: anything where your usage is hard to predict. If you've never built with a certain type of component before, buying ten of them "because they might be useful" is usually a mistake. Buy two. See if you use them. Reorder when you have a reason.

The reorder trigger problem

The practical challenge in any ordering strategy is the reorder trigger: how do you know when you're running low on something before you're actually out in the middle of a build?

Manual inspection doesn't scale. You can't check all your component levels before every project. It's the kind of thing that sounds like it should take five minutes and actually takes forty.

What works: a minimum quantity threshold in the inventory system, checked when you're about to start a new project rather than continuously. The threshold doesn't need to be precise — "I'm below the level where I feel comfortable starting this build without checking if I need to order" is enough signal.

The pattern that prevents most mid-build blocking: when you finish a project and do the cleanup, check the inventory for components you used heavily. If they're below a comfortable level, add them to the next order. The cleanup moment is the right time — you have fresh information about what you just used, and you're not in the middle of anything.

This isn't fancy. It's just consistent. The difference between "I always have what I need" and "I'm always running out" is usually just this habit, applied consistently for long enough that the stock level stabilises.