Ask five factories to price the same 200 units and you will get five numbers that differ by more than the products do. That is not market opacity. A per-unit price is not a property of the microscope — it is the sum of two different bills, divided by a quantity you choose. Once you can see the split, the quotes stop being mysterious and start being comparable.
The first bill is non-recurring engineering (NRE): costs you pay once, whatever the volume. The second is per-unit cost: what it takes to make and ship one more microscope. Suppliers rarely label them, so the single number you receive hides a decision about which costs sit where.
Typically one-off: tooling and fixtures, enclosure artwork and print plates, firmware and app customisation, ISP tuning sessions, certification testing, packaging design, and the test plan written around your configuration.
Typically per unit: sensor and lens module, illumination, housing and mechanical parts, PCBA, assembly and test labour, cable and accessories that go in the box, packaging consumed, and freight.
This is why a low unit price is not automatically a better price. If the NRE was folded into the unit number, you are prepaying engineering across your first order — and if you never order again, you paid the whole bill for a fraction of the work.
When a buyer says "the other factory is cheaper", the difference is almost always on one of these lines rather than in the margin:
Four forces push the per-unit price up as volume falls, and none of them are anyone being punished for ordering small:
The practical consequence: treat the gap between your pilot price and your repeat price as tuition, not as a discount you are owed. A pilot batch buys tooling, tuning and a validated build — assets that make the second order cheaper. Buyers who negotiate the pilot down to the repeat price usually discover the difference reappears as a setup charge, a shorter warranty, or a supplier who declines the second order.
There is a reverse warning too: a factory quoting the same unit price at 200 and at 2,000 has either hidden the NRE, plans to renegotiate later, or has not costed the changeover at all.
The real question is what you are buying with the NRE: identity, or difference. Both are legitimate; they cost differently and they defend differently.
Expecting ODM outcomes on an OEM budget. It is the most common way a small-batch project dies: the brief asks for a new enclosure, custom software and a modified optical path, the quote comes back at platform-rebrand money, and six weeks later the project is re-scoped. Decide how much difference your market actually pays for before the first call — our OEM/ODM briefing guide walks through that decision.
Normalise first, then compare. Nine lines decide whether two numbers mean the same thing:
A quote that lands materially lower is almost always different on one of these lines. Ask which one before you ask for a discount.
Suppliers quote ranges when a variable is missing. Five inputs close most of the gap: volume (pilot and annual, separately), target market and certifications, the customisation list, software scope (who builds the app, who owns it), and your date. Tell us what you will not change, too — stability is worth money, because it removes re-work.
We show the split, because hiding it costs both sides time later:
If you are still choosing between a rebrand and a variant, the briefing guide is the better starting point. If you already know what you want to build, send the five inputs and we will quote the split — on a real configuration, not a catalogue position.
Because four fixed-cost forces are spread over fewer units: component pack minimums, tooling amortisation, production setup time, and certification that attaches to a configuration rather than a quantity. The unit itself did not change; the number of units carrying the fixed bill did.
There is no single figure — it falls out of the configuration. Component pack sizes and tooling set a practical floor, and software customisation sets a different one. We quote a pilot quantity and a repeat quantity together so you can see what the floor actually costs before committing.
You can ask for it amortised into the unit price, and some suppliers will do that. The risk is that you prepay engineering across the first order without owning the tooling or designs. Ask for the split anyway — even if you choose the bundled number, you should know what you are buying.
If the first batch exists to test whether the market wants the product at all, rebrand an existing platform and keep the one-off cost low. If your differentiation is the device itself — ergonomics, illumination, software workflow — budget for a variant. Buying ODM outcomes on an OEM budget is the classic way these projects stall.
Per configuration, plus maintenance. Reports attach to a tested build: change the radio module or the sensor and an existing report may no longer cover the product, which means re-testing. That is why certification belongs on the one-off side of the quote, and why late BOM changes are expensive.
What to specify, what to leave to the factory, and the details that decide whether a custom build ships on schedule.
Read the article →What the extra megapixels actually buy you, where they stop paying, and how optics and lighting quietly outrank both.
Read the article →