Somewhere right now, a founder is sizing a production run like this: "The black hoodie sells well. Let's make 500." No velocity data, no lead-time math, no material check. Just a number that felt right on a Tuesday. Sometimes it works. Then one month it doesn't — the hero product sells out for three weeks while 400 units of a slow mover gather dust — and the founder learns that gut feel is a plan right up until it isn't.
Production planning for small manufacturers doesn't need an ERP consultant or a six-month MRP rollout. It needs a repeatable loop: read the demand signal, size the run, check materials, track work in progress, gate on quality, and release finished goods back to the store. This guide walks through each step with real numbers, and ends with a 6-step system you can run this week.
Key takeaways
- Gut-feel planning works until roughly 50 SKUs — after that, human memory can't track velocity, lead times, and material stock simultaneously.
- Size runs from arithmetic: (target cover − days remaining) × daily velocity, not round numbers like 500.
- Check materials before you commit machines. A run you can't feed is a promise you can't keep.
- QC belongs inside the process as a gate, not at the end as a surprise.
- The loop only closes when finished goods land back in your store's inventory — automatically, not via a Sunday-night CSV.
Why gut feel breaks past 50 SKUs
With 10 products, one person can genuinely hold the whole operation in their head. You know the bestseller, you know the fabric supplier takes two weeks, you know there's a roll of jersey in the back room. Planning by feel is not stupid at this stage — it's efficient.
The math changes as the catalog grows. Fifty SKUs with three materials each is 150 material positions, a dozen supplier lead times, and 50 different sales velocities that shift every month. No one holds that in memory. What actually happens is that attention concentrates on the five products the founder thinks about most, while the other 45 drift — some quietly stocking out, others quietly overstocking. The failure isn't dramatic. It's a slow leak: a few lost weeks of sales here, a pile of dead stock there, and a planning meeting that starts with "wait, how much do we even have?"
The fix is not more willpower. It's moving the plan out of one person's head and into a system that reads the numbers for you.
Start with the demand signal, not a hunch
Every production decision starts with one number: how fast is this product actually selling? Not "well" or "okay" — units per day, measured over the last 30 to 60 days.
Two corrections make this number honest. First, exclude stockout days. If a product sold 90 units in 30 days but was out of stock for 10 of them, its true velocity is 90 ÷ 20 = 4.5 units per day, not 3. Averaging over stockout days systematically understates demand for exactly the products you most need to reorder — your bestsellers, since they're the ones that run out. Second, convert velocity into a countdown: stock on hand ÷ daily velocity = days remaining. "120 units left" means nothing by itself; "27 days remaining on a 30-day lead time" is an alarm bell.
Days remaining is the single most useful planning metric a small manufacturer can adopt, because it puts every product — fast and slow — on the same scale. Sort your catalog by it every Monday and the plan writes itself. If you want the underlying math, our guide to calculating reorder points covers thresholds, and demand forecasting methods covers what to do when history alone isn't enough.
Size the run with arithmetic, not round numbers
Round numbers are the tell of gut-feel planning. Real run quantities come from three inputs: current runway, lead time, and how many days of cover you want after the run lands.
Notice what the formula surfaces: with 18 days of stock and a 30-day lead time, you are already 12 days late — you'll stock out before the run lands unless you expedite or accept the gap. That's the kind of truth a hunch never volunteers. Rounding to a pack size or a sensible MOQ at the end is fine; starting from a round number is not.
Materials before machines
A production order is only real if you can feed it. Before committing a run, explode it through the bill of materials: 350 hoodies × 1.4 m of fleece per unit (including a 5% waste allowance) = 490 m of fleece, plus zips, drawcords, labels, and polybags. Then compare each line against material stock on hand.
The gap between required and available is your shortfall list, and the shortfall list is your purchase order. This check takes minutes with a maintained bill of materials and is nearly impossible without one — which is why runs so often stall on day three waiting for a trim that nobody ordered. If your BOMs live in someone's head or a stale spreadsheet, fix that first; our guide to building a bill of materials shows how to structure variants and waste percentages properly.
Sequence matters too. Material lead times stack in front of production lead times: if fleece takes 10 days to arrive and stitching takes 20, your true lead time is 30 — and the fabric PO, not the work order, is the thing that has to go out today.
Track WIP through stages, not in your head
Once a run starts, the question changes from "should we make it?" to "where is it?" Cut, stitched, finished, packed — every batch is somewhere, and if that somewhere lives only in a WhatsApp thread with the production manager, you'll rediscover it during a crisis.
The discipline is simple: define your stages, and record quantity moving between them. Not to the minute — a daily update is plenty. The payoff is that "when will the hoodies be ready?" becomes a lookup instead of a phone call, and bottlenecks become visible as stages where quantity piles up. If 350 units have been sitting at "stitched" for six days, you don't have a stitching problem — you have a finishing problem, and now you can see it.
QC is a gate, not an afterthought
The most expensive place to find a defect is in a customer's unboxing video. The second most expensive is in the warehouse, after the full run is packed. Quality control works when it's a gate that WIP must pass through — inspect a sample when goods move from stitching to finishing, and again before anything is marked sellable.
Gating does two things a final-inspection habit doesn't. It catches systematic errors early, while only 50 units are affected instead of 350. And it creates a record: which runs failed, at which stage, for which reason. Three months of that log tells you more about a workshop's real quality than any factory visit.
Close the loop to the store
A run isn't finished when the boxes are taped. It's finished when the units are sellable — counted into inventory and live on your storefront, per size and per variant. This last step is where manual systems quietly bleed: goods sit received-but-not-listed for days because updating Shopify quantities is someone's Friday chore. Those are stockout days you already paid to prevent.
Automate this step ruthlessly. A two-way Shopify sync means finished goods appear in the store the moment they pass QC, and sales flow back to update velocity — which feeds the next planning cycle. The loop is only a loop if it closes.
A 6-step production planning system for small manufacturers
Put together, production planning for small manufacturers is six repeating steps. This maps one-to-one to Honey Shelf's 6-stage pipeline, but the logic holds whatever tool you run it in:
| Step | What you do | What replaces gut feel |
|---|---|---|
| 1. Check stock | Review days-remaining for every SKU | Velocity math instead of "feels low" |
| 2. Draft production orders | Size runs from the run-quantity formula | Arithmetic instead of round numbers |
| 3. Buy materials | Explode BOMs, order the shortfall | A shortfall list instead of a memory test |
| 4. Receive goods | Check deliveries in against POs | A record instead of a shelf mystery |
| 5. Produce | Move WIP through stages with QC gates | A status board instead of phone calls |
| 6. Release to store | Sync finished goods to your storefront | Same-day listing instead of a Friday chore |
Run the loop weekly and each pass gets easier: velocities are fresher, BOMs get corrected, supplier lead times turn from guesses into measured averages. Within a quarter, the planning meeting stops being an argument about facts and starts being a decision about trade-offs — which is what it should have been all along.
Frequently asked questions
Plan one full cycle ahead: your production lead time plus a safety buffer. If a run takes 30 days end to end, every product should have a plan covering at least the next 45 days of demand. Beyond that, forecast loosely — demand data goes stale fast for small catalogs.
Planning decides what to make, how much, and by when — driven by demand and lead times. Scheduling decides the exact sequence on the floor — which line, which day, which operator. Most small manufacturers fail at planning, not scheduling: the run starts too late long before the floor sequence matters.
Not full-blown MRP — that's built for factories with hundreds of routings. You need the core loop: demand signal, run sizing, material check, WIP tracking, QC, and stock release. Lightweight tools built for small brands cover that loop without the six-month implementation.
Use velocity from the matching period last year as your baseline, scaled by this year's growth, and start runs one full lead time before the season begins. During the season itself, shorten your review cycle — check days-remaining weekly instead of monthly, because a spike can compress a 60-day runway into 20.