How to Plan Refurbishment Capacity and Bottlenecks

Refurbishment stops being a side bench and becomes a factory the moment volume arrives. This guide covers mapping the stages, measuring capacity in phones per week, finding the bottleneck, and scheduling around it so work in progress never piles up.

Refurbishment is a factory problem, not a bench problem

A single technician can work phone-by-phone and stop whenever the tray is empty. A refurbishment line cannot — it has intake, grading, repair, reassembly, testing, and packaging all flowing at different speeds. The moment the line starts, the slowest stage governs the whole operation. Refurbishers who think of themselves as "a few technicians" instead of "a small factory" end up with a pile of half-finished phones and no idea why nothing is shipping. The distinction between refurbished and used stock matters here, because refurbished units carry a much higher expectation of a fully working, disclosed result.

Map the stages and measure each one

Write down every stage a phone passes through, from intake and triage to cosmetic repair, part replacement, testing, and final QC. Then measure, over a real week, how many phones each stage completes per day — not per technician, but per stage. Measuring is the step most lines skip, and it is why bottlenecks are usually guessed instead of found. The number you want is phones per week per stage, because that is the unit that lets stages be compared directly.

Find the bottleneck, then schedule around it

The bottleneck is the stage with the lowest phones-per-week throughput. It is almost never the stage people assume — repair technicians are visible, but a slow testing bench or a parts-constrained replacement stage is quieter. Once you find it, the rule is simple: feed the bottleneck, protect the bottleneck, and never let it starve or overfill. Schedule everything else to the bottleneck's pace, because producing more upstream than the bottleneck can absorb only builds a bigger pile of work in progress. This is the same pacing logic that applies when you set up a grading line at scale.

Capacity in phones per week, not hours of effort

Measure capacity in completed phones per week, never in technician-hours. Hours measure effort; phones measure output, and only output pays the bills. Capacity planning means asking one question every week: how many phones per week can each stage complete, and what is the whole line's true output. When intake is planned against the line's measured output rather than its ambition, promises to buyers stop being guesses.

When to add capacity vs. slow down intake

When the bottleneck is a machine or a parts supply, add capacity at that stage — a second tester or a reordered parts buffer often unlocks the whole line. When the bottleneck is a person, adding more people downstream does nothing until the person's stage catches up. The cheapest lever is often the opposite of what a busy shop tries first: slow down intake so the bottleneck clears, rather than pushing more phones into a line that cannot absorb them. Intake control is capacity planning, not lost sales.

Scheduling rules that keep work in progress from piling up

• Cap work in progress per stage. A hard limit stops upstream stages from burying the bottleneck.
• Batch by repair type. Running similar repairs together cuts setup time and speeds the whole line.
• Schedule to the bottleneck's pace. Release new work only as fast as the slowest stage completes it.
• Review weekly, not monthly. A bottleneck can move from one stage to another as the mix of phones changes.

These rules tie directly into the per-phone resell vs. refurbish decision — a phone should only enter the refurbishment line when the incremental margin justifies the capacity it consumes.

Frequently asked questions