Sourcing a camera manufacturer starts with a shortlist of companies that all look the same on a website: factory photos, product grids, and a promise of OEM and ODM support. The differences that decide whether your product launches on schedule or stalls in a customs warehouse are invisible at that stage. They sit in who owns the firmware, who owns the tooling, who answers when a unit fails in month fourteen, and who holds the certification documents.
This guide lists ten checks worth running before you place a production order. None of them require special tools — most require a specific question and the willingness to wait for a documented answer.
1. What do they actually manufacture in-house?
The first question separates manufacturers from traders, and it is the one most likely to be answered loosely. Ask which production steps happen on their premises: board assembly, lens and sensor assembly, housing and mechanical work, final assembly, testing, and packing. Then ask for the address of each step.
A supplier that outsources several steps is not automatically a bad choice — many credible manufacturers do. What matters is knowing which steps they control, because that determines how they handle quality issues, how fast they can change a design, and how much of your margin is paying for an intermediary layer.
If you can, visit. A factory tour answers in an hour what a supplier questionnaire takes weeks to settle. If travel is not possible, ask for a live video walkthrough of the specific production line that will build your product.
2. Who owns the firmware?
Firmware ownership is the most consequential question in this list and the one most often skipped. Ask directly:
- Is the firmware developed in-house or sourced from a chipset vendor or a third party?
- Can the product be branded with your identity in the interface, mobile app, and cloud service?
- Who releases security patches, and how are they distributed to you?
- If the commercial relationship ends, what happens to the firmware?
What you are testing for is whether you will be dependent on the manufacturer for every future change, and whether a security issue can be patched without their cooperation. Get the answer in writing.
3. Where do the analytics come from?
Camera analytics — people counting, intrusion detection, plate recognition — are usually the hardest part of a product to build from scratch. Ask who supplies the models and the inference engine, whether the licence permits your branding and your volume, and what the per-unit or per-shipment cost looks like.
If analytics are licensed from a third party, ask what happens if that relationship changes. If they are in-house, ask how models are trained and updated, and whether updates reach devices already in the field.
4. Which certifications, and can they show the reports?
Do not accept a badge on a webpage. Ask for the actual test reports and certificates relevant to the markets you are selling into — electrical safety, EMC, radio for wireless products, and any local requirements for your destination country.
Two details matter as much as the certificate itself: whether it is issued in your company's name or the manufacturer's, and whether it covers the exact model you are buying rather than a similar one. Certificates tied to a parent model with a different housing or radio module are a frequent source of customs problems.
If a supplier cannot produce a report for the specific configuration, treat the certification as pending and plan accordingly.
5. What does their quality process look like?
Ask for the process, not the slogan:
- Incoming inspection of components and boards
- In-circuit or functional testing during assembly
- Optical alignment and image quality checks for camera modules
- Environmental or aging testing before packing, and for how long
- Ingress protection testing for outdoor models
- Outgoing quality audit sampling, and the acceptance criteria used
Request a sample test report. A manufacturer with a real process has documents it can share; a trading intermediary usually has a template.
6. Tooling, minimum order quantity, and non-recurring engineering
Customisation costs money before it produces a single sellable unit. Understand the structure even if you do not accept the first quote:
- Tooling. Whether injection moulds, dies, and fixtures are charged separately, and who owns them afterwards.
- Non-recurring engineering. Design, firmware, and certification work billed once.
- Minimum order quantity. Usually set per model, and sometimes per colour or per configuration.
- Sample and pilot costs. Whether pilot units are charged at production price or at a premium.
These are the levers that turn a unit price into a project price. Ask for them itemised, and ask what changes the total if volume triples or if you commit to a longer forecast.
7. What will they change, and what will they not?
Every manufacturer has a boundary between "we can customise this" and "we would rather not touch that." Find the boundary before you design around something unavailable. Typical customisation that is usually feasible: branding, packaging, mounting accessories, firmware defaults, enclosure colour, and interface language. Typical customisation that is harder or impossible: core sensor or chipset changes, a redesign of the optical path, or a major change to the analytics behaviour.
Ask for a written statement of what is in scope and what is excluded, with cost and lead-time implications for each option.
8. How does the product integrate?
If your customers use a VMS, an access-control platform, or your own software, integration decides whether the product is sellable. Confirm ONVIF profiles supported, RTSP availability, whether there is an SDK or documented API, and whether the manufacturer will support your integration work with engineering time.
Ask for a reference integration: a partner or customer who has connected the product to a third-party platform. A manufacturer with a real integration story can name the protocols and the process.
9. Support model, RMA, and spares
The purchase order is the beginning of the relationship. Establish:
- Who provides technical support, in which time zone and language, and through which channel.
- The RMA process, who pays return freight, and the typical turnaround.
- The defect rate threshold at which a batch is treated as a quality event rather than individual failures.
- Availability of spare parts and accessories, and for how long after the product is discontinued.
- Whether firmware support continues after a model is superseded.
A supplier that answers these crisply has dealt with them before. A supplier that answers vaguely has not.
10. Intellectual property, exclusivity, and exit
Finally, the commercial and legal layer:
- Who owns the design, tooling, firmware, and packaging artwork you paid for?
- Will the manufacturer sell the same product with a different logo to your competitor?
- Is there an exclusivity arrangement, in which markets, and for how long?
- What are the confidentiality terms around your specifications and volumes?
- On termination, what happens to tooling, stock, firmware access, and warranty obligations?
Put these in the contract, not in an email thread. If a manufacturer resists documenting IP ownership or exclusivity, that resistance is itself information.
How to run the evaluation
A practical sequence, in order: desk screening of candidate suppliers against checks 1 to 4; a live factory walkthrough or audit; a sample order for hands-on testing; a small pilot production run; then a production contract with the IP terms settled. Do not compress the pilot stage to save time — it is the cheapest place to discover a problem.
Red flags worth taking seriously
- No answer on firmware ownership, or an answer that changes between conversations.
- Certificates and test reports that cannot be produced for the exact model.
- Reluctance to let you see the production line, in any form.
- A price that is below the component cost of the specification being quoted.
- No named reference customers or integration partners.
- Pressure to pay in full before production starts.
- Specification sheets that cannot be traced to a datasheet or a measurement.
FAQ
What is the difference between an OEM and an ODM manufacturer?
An OEM arrangement typically means the factory builds to your specification and your brand, with you owning the design and often the tooling. An ODM arrangement means the factory offers a product it designed itself, which you can brand and configure. Most real projects sit between the two, so the useful question is not which label applies but which specific elements — design, tooling, firmware, certification — each side controls.
How do I verify a supplier is a factory and not a trading company?
Ask which production steps occur on-site, request a live video walkthrough of the line, and check that certification documents name the manufacturing entity. Trading companies can still be useful partners, but the price, lead time, and issue-resolution path are different.
Should I pay for tooling separately?
Usually yes, if you want to own the resulting mould and protect your design. Confirm in writing who holds the tool after production ends and what it takes to move it.
How long should a pilot run be?
Long enough to see failures. A short sample order tests whether the product works on arrival; a pilot placed in the field for a few weeks tests whether it works after installation. Budget for both stages.
What should be in the manufacturing agreement?
Ownership of design, tooling, and firmware; exclusivity and territory; confidentiality; quality thresholds and remedies; warranty terms; and the exit conditions including tooling handover and firmware access. Have it reviewed by a lawyer familiar with cross-border manufacturing.
---
The about page describes how HooViz works with brand owners and integrators on custom camera programmes, and the product center shows the current camera families available for OEM and ODM projects. If you have a specification or a target market in mind, send us the details and we will tell you plainly what we can and cannot do.