The short answer
Read a dash cam spec sheet by splitting it into five groups: image (sensor, lens, resolution), processing (chipset, codec, frame rate), power (buffer, voltage, temperature range), storage and connectivity (card, WiFi, GPS), and compliance (certifications and reports). For each group, ask whether the sheet names a specific component or only a marketing phrase. Named components can be verified and held to the sample; phrases cannot. The most useful habit is to mark every line as confirmed, vague or missing, and send the vague and missing lines back to the supplier in a single written list before approving a sample. The sheet also tells you how a supplier works: a company that answers vague lines quickly and precisely is usually easier to work with than one that resends the same marketing PDF, so the document doubles as an early test of the relationship.
Line by line
| Line on the sheet | What it should say | Red flag |
|---|---|---|
| Resolution | Recorded size and frame rate per channel | Only 4K with no sensor named |
| Image sensor | Part number, such as IMX415, and native MP | Ultra HD sensor with no model |
| Chipset | SoC name, such as NT96670 class | Missing or high-performance chip |
| Lens | Glass elements, aperture, angle and how it is measured | Angle only, no construction |
| Codec and bitrate | H.264 or H.265, default bitrate | Codec without bitrate |
| Night and dynamic range | WDR or HDR behavior, IR for cabin cameras | Night vision with no sensor info |
| Power buffer | Supercapacitor or battery | Not stated |
| Operating temperature | Range and whether tested | Range with no basis |
| Storage | Max card size, card type, speed class | Compatible with all cards |
| Connectivity | WiFi band, GPS type, app name | App with no localization info |
| Certification | FCC, CE, RoHS, E-mark as applicable, with report numbers | Logos only, no numbers |
| Warranty and after-sales | What the program covers and how replacements work | Missing entirely |
| MOQ and lead time | Typical reference range per route, confirmed in writing | Fixed promises without program terms |
Treat the sheet as a quote-comparison tool as well. When two factories quote the same kind of model, sheets with the same line items turn the comparison into a column exercise instead of a conversation, and gaps show up as gaps rather than as surprises after the sample arrives. Add the rows that matter to your program before you send the sheet out, so both suppliers answer the same questions.
Image and processing lines
Start with the sensor and chipset, because they set the ceiling. The sensor model reveals native resolution: an 8MP Sony IMX415 can capture native 4K, while a 5MP IMX335 is often upscaled when sold as 4K. Rear cameras often use a 2MP 1080P part such as the GalaxyCore GC2053. Then check the chipset against the claimed mode: 2160P at 30fps is within the range of Novatek NT96670 class platforms, while a claim of 4K at high frame rates on a modest chip should prompt a question. The deeper explanations are in image sensors and chipsets. A useful discipline is to demand the recorded mode table rather than a single headline: which resolutions, frame rates and bitrates the firmware actually offers, per channel, with the factory default marked. Marketing sheets compress this into one number; program sheets expand it, and the expanded version is what inspection will check against.
Power, heat and endurance lines
The power buffer decides what happens when the car turns off and how the camera behaves in the heat. A supercapacitor tolerates heat better than a lithium battery and avoids battery shipping restrictions; battery models raise heat and shipping-regulation issues. Operating temperature ranges on a sheet are only as good as the test behind them, so ask whether they were tested and under what program. The reasoning is explained in supercapacitor vs battery. A camera with a screen, WiFi and 4K encoding in a parked car is the hard case, so request footage after a long continuous run. Ask what the stated temperature range rests on: some ranges are design targets, some are sampling results, and a few are tested commitments, and the difference appears in the first summer. It is cheaper to learn that from the supplier's answer than from returns.
Storage and connectivity lines
Look for a maximum supported card size, whether a high-endurance card is bundled or recommended, and the speed class ratings of the supplied card. Loop recording makes cards fail, so a sheet that says compatible with all microSD cards is shifting risk to the buyer. For a seller, a bundled 64GB or 128GB high-endurance card is a clear value point worth stating in your own listing, together with who supplies the card, which grade it is, and whether the pairing of card and recorder was tested together, because card and recorder failures are hard to tell apart from a support desk and easy to prevent at specification time. For connectivity, ask which WiFi band is used, whether the app is available for both phone platforms, and who maintains it. App branding and localization are separate programs to agree, not defaults that arrive with the sample.
Compliance lines
Certification logos on a sheet prove nothing by themselves. What matters is a report or certificate number tied to the exact model, which can be verified with the issuing lab. WiFi models need radio certification (FCC ID in the US, RED in the EU), non-WiFi models follow the unintentional-radiator route in the US, and commercial-vehicle programs often look for E-mark under UNECE R10. Roadtrace holds no certificates itself; reports come from the producing factory or lab and are checked by number for each program. The certifications page gives the map and the test report note explains how to read them. Keep the report numbers in the program record with the sheet, so any future component change triggers a fresh look at whether the documents still describe the product.
Hidden gaps and a practical workflow
- Two different models sharing one spec sheet, with options mixed together.
- Marketing terms replacing numbers: pro-grade, ultra clear, enhanced night vision.
- Sample specifications that differ from the production specification.
- No mention of firmware version, update method or default settings.
- No statement on what is included in the box, such as mount, cable and card.
Two gaps deserve special attention because they cause the most disputes: component substitutions that arrive unannounced, and lead-time promises made without program terms. Both are handled the same way - by freezing the corrected sheet and treating changes as written exceptions. The workflow that catches the rest:
- Print or copy the sheet and mark each line confirmed, vague or missing.
- Send the vague and missing lines to the supplier as one written question list.
- Receive answers and a sample; compare the sample with the corrected sheet.
- Freeze the corrected sheet as the approved specification for the program.
- Check production units against it at inspection.
This is the routine Roadtrace follows with partner factories, supported by the sample checklist; typical MOQ and lead-time reference ranges per route are set out on the MOQ and lead time page. To have a sheet reviewed against your requirements, use the quote form.