What Should Buyers Include In An IP Camera RFQ For OEM Production?

A useful request for quotation (RFQ) does more than name a camera type and ask for a unit price. It gives manufacturers enough information to quote the same product, identify assumptions, and explain any differences between your requirements and their proposals.

For an original equipment manufacturer (OEM) project, a complete RFQ should cover the cameras intended use, measurable technical requirements, software and security expectations, branding, compliance, sample approval, quality acceptance, and commercial terms. The goal is to make requirements clear enough to compare quotations and later verify the delivered product.

Describe the Project and Intended Use

Start with the use case. A camera designed for a sheltered indoor corridor may not suit an exposed roadside installation, even if both are described as outdoor cameras.

Include:

• Intended application and installation location
• Indoor, outdoor, or harsh-environment use
• Typical viewing distance and area to be covered
• Whether identification, detection, or general observation is the priority
• Expected lighting conditions, including backlighting and nighttime use
• Target sales markets and relevant environmental conditions
• Estimated annual demand, initial order quantity, and forecast period

If the product will be sold under your brand, state whether the project involves a new design, a modification of an existing model, or a private-label product. The project type can affect engineering work, tooling, testing, cost, and lead time.

Define Camera and Image Requirements

Camera type and installation

Specify the camera format, such as dome, turret, bullet, box, or pan-tilt-zoom (PTZ), and describe installation constraints. Note requirements for wall, ceiling, pole, or pendant mounting, as well as cable-entry direction, connector access, and tamper resistance.

For a PTZ camera, specify the required pan and tilt ranges, optical zoom, preset positions, and control interface. Avoid relying on terms such as long range or wide coverage without defining the required field of view or viewing distance.

Resolution, frame rate, and image performance

State the minimum resolution and the frame rate required at that resolution. Include image-processing features that matter to the application, such as:

• Wide dynamic range (WDR), including the conditions in which it must work
• Backlight compensation or highlight suppression
• Image rotation or corridor mode
• Noise reduction
• Privacy masking
• Day/night switching and a removable IR-cut filter

Resolution alone does not guarantee useful detail. For facial or vehicle identification, describe the scene and required resultfor example, target distance, mounting height, lighting, and whether the subject is moving. Where possible, request sample footage from a comparable setup.

Lens and field of view

Define the lens type and field of view needed at the installation distance. Include:

• Fixed or motorized varifocal lens
• Focal-length range, if known
• Horizontal and vertical field-of-view targets
• Focus method: fixed, manual, or motorized
• Required focus performance across the intended temperature range

If you do not know the focal length, provide a site layout or desired coverage area and ask the manufacturer to propose a lens. Require the supplier to state the proposed focal length and field of view in its quotation.

Low-light performance and night vision

Describe the expected nighttime scene rather than simply requesting good night vision. Specify whether the camera needs:

• Infrared (IR) illumination, white-light illumination, or both
• A required usable distance under defined scene conditions
• Monochrome or color nighttime images
• Adjustable IR intensity or smart illumination

IR range claims can vary with the scene, lens, target reflectivity, and ambient conditions. Ask the supplier to describe its test conditions and provide sample images or footage. Do not treat a stated illumination range as a guaranteed identification distance.

Specify Network, Recording, and Interoperability

Network interface and power

State whether the camera must use wired Ethernet, Wi-Fi, cellular connectivity, or more than one option. For Ethernet, identify whether Power over Ethernet (PoE) is required and specify the applicable power standard or class, if known. Confirm the cameras maximum power consumption, including IR illumination, heaters, and other accessories.

For wireless models, identify supported bands and security requirements, and describe expected distance or network conditions. Wireless performance depends on the installation environment, so a nominal range should not be treated as a guaranteed operating distance.

Protocols and system compatibility

List required protocols and integrations, such as RTSP or ONVIF. If ONVIF interoperability is required, name the relevant profile or functions and ask the supplier to identify the exact models and firmware versions covered by its conformance claim. The phrase ONVIF compatible alone may not clarify which functions are supported. See ONVIFs profiles and specifications for profile information.

Provide details of the intended video management system (VMS), network video recorder (NVR), or other software. Where possible, request a compatibility test using the system and firmware versions planned for deployment.

Video, storage, and audio

Specify the required video codecs, number of streams, and stream configuration. Include the expected resolution and frame rate for each stream if they differ. Also state whether the camera needs:

• A microSD card slot and supported card capacity
• Local or event-based recording
• Audio input or output
• Alarm inputs or outputs
• Time synchronization and event logging

Storage and bandwidth depend on scene movement, image settings, codec, and recording schedule. Provide an expected operating profile and ask the manufacturer to estimate storage and bandwidth using stated assumptions.

Set Environmental and Mechanical Requirements

Ingress protection and impact resistance

For outdoor cameras, specify the required ingress protection (IP) rating and, where relevant, the test basis. IP codes defined by IEC 60529 describe protection against solid objects and water under specified test conditions; they do not by themselves guarantee resistance to every weather condition or installation environment. For example, IP66 and IP67 describe different water-exposure tests and should not be treated as interchangeable. See the IEC overview of IP ratings.

If impact resistance matters, specify an IK rating separately. Also state any requirements for corrosion resistance, UV exposure, salt spray, vibration, or vandal resistance. These may require tests beyond an IP rating.

Operating conditions

Provide required operating and storage temperature ranges, humidity conditions, and any relevant altitude or condensation concerns. Ask the manufacturer to state whether its temperature specification applies during startup as well as operation, and whether it includes accessories such as heaters.

For demanding environments, identify the test method and acceptance criteria rather than relying on a general claim such as all-weather.

Dimensions and mounting

Include maximum dimensions or weight, mounting-hole patterns, materials, cable lengths, connectors, and required mounting accessories. Request drawings or a 3D model if the camera must fit an existing enclosure or installation.

Include Software, Cybersecurity, and Maintenance Requirements

For network-connected products, include software and cybersecurity expectations in the RFQ. Requirements may cover:

• Unique credentials and secure first-time setup
• Password-change policies and user-role permissions
• Encrypted management and video connections, where required
• Secure firmware updates and a documented update process
• Firmware support period and vulnerability-reporting process
• Logging, time synchronization, and configuration backup
• Data retention, privacy controls, and account management
• A software bill of materials (SBOM), if required by your organization

Identify who controls the firmware, cloud services, mobile application, and update-signing keys. Clarify whether the camera must operate without a vendor cloud service and whether telemetry or remote access is permitted. Validate the cameras network features against your organizations security policy rather than assuming they meet it.

State Branding, Packaging, and Documentation Needs

Describe OEM customization requirements, including:

• Logo placement, colors, labels, and product markings
• Custom model numbers and serial-number format
• Packaging dimensions, materials, language, and labeling
• Barcodes, QR codes, and regional product identifiers
• Accessories included in the retail or installation package

Identify the required documentation and languages, such as installation guides, quick-start instructions, datasheets, firmware release notes, and compliance documents. If the manufacturer is expected to create artwork or packaging, state who approves it and whether design or tooling charges apply.

Identify Market-Specific Compliance Requirements

List the intended destination markets and ask the manufacturer to identify applicable requirements for the exact product configuration. Depending on the product and market, requirements may relate to radio equipment, electrical safety, electromagnetic compatibility, environmental restrictions, or cybersecurity.

Examples include CE marking for applicable European Union legislation, FCC requirements for relevant products marketed in the United States, and RoHS substance restrictions where applicable. A declaration or certification for one model, component, or market does not automatically establish compliance for every configuration or destination.

For each applicable requirement, identify the evidence you expect, such as a declaration, test report, certificate, or listing. Confirm that the evidence matches the quoted model and accessories, and verify current requirements for the target market and product category before placing an order. Reference information is available from the European Commissions CE marking guidance and the FCCs Equipment Authorization program.

Document Sample Approval and Quality Acceptance

Agree on sample approval and acceptance criteria before authorizing mass production.

Sample approval

Specify:

• Number and configuration of samples
• Sample delivery date and shipping responsibility
• Tests to be performed by the buyer and by the manufacturer
• Approval period and how approval will be recorded
• Whether a design change requires a new sample
• Whether the approved sample will be retained as a reference, or golden, sample

The approved sample should match the production configuration, including hardware revision, firmware, lens, accessories, labels, and packaging.

Production quality checks

Define measurable inspection and test requirements. A practical plan may include:

• Visual and dimensional inspection
• Power-on and network-connection checks
• Image, focus, and stream verification
• Required protocol and VMS integration checks
• IR, audio, alarm, or storage tests, where applicable
• Label, accessory, and packaging checks
• Environmental or reliability tests, where required by the application

State the sampling plan, inspection level, defect classifications, and acceptance criteria. If using an AQL-based plan, identify the standard and sampling parameters by agreement rather than simply writing AQL inspection. For critical functions, consider requiring a test on every unit or on a clearly defined production sample.

Document test results, nonconformities, corrective actions, and approval before shipment. Specify how rework, replacement, retesting, and rejection will be handled.

Provide Commercial Details for a Comparable Quote

Manufacturers need more than technical specifications to price an OEM project accurately. Include:

• Initial order quantity and forecast volumes
• Target order schedule and delivery location
• Requested Incoterm and named place, if applicable
• Tooling, engineering, sample, and certification cost treatment
• Minimum order quantity and price breaks
• Quote validity, currency, and payment terms
• Sample and production lead times, plus shipping method
• Warranty duration, coverage, and exclusions
• Repair, replacement, and return process
• Spare-parts availability and firmware-support period
• Ownership of custom designs, tooling, firmware changes, and artwork

Ask suppliers to itemize one-time costs separately from unit prices. Require them to list assumptions, exclusions, and proposed substitutions so quotations can be compared on the same basis.

Separate Mandatory Requirements from Options

Mark each requirement as one of the following:

• Mandatory: The product must meet this requirement to be considered.
• Preferred: The requirement is desirable but can be discussed.
• Optional: The supplier should quote it as a separately priced option.

This helps manufacturers identify gaps and propose alternatives without silently changing a critical requirement. Ask each supplier to complete a compliance matrix showing whether it meets, partially meets, or does not meet each item, with evidence or comments.

Supplier response matrix template

Add a row for every technical, quality, compliance, and commercial requirement in the RFQ. Ask suppliers to explain all partial compliance, exclusions, and proposed alternatives.

Use a Final RFQ Checklist

Before sending the RFQ, confirm that it covers:

• Application, installation environment, and target market
• Camera type, dimensions, and mounting requirements
• Resolution, frame rate, image functions, and field of view
• Lens and focus requirements
• Night-vision type and defined performance conditions
• Network interface, power, protocols, and VMS/NVR compatibility
• Codecs, streams, storage, audio, and alarm functions
• IP and IK ratings, operating conditions, and other environmental tests
• Software, cybersecurity, cloud, and firmware-support requirements
• Branding, packaging, accessories, and documentation
• Market-specific compliance evidence
• Sample approval process and production acceptance criteria
• Initial quantity, forecast, delivery, and commercial terms
• Warranty, support, and ownership of custom work
• Mandatory, preferred, and optional requirements
• Supplier response matrix and required supporting evidence

A well-prepared RFQ makes it easier to compare suppliers, uncover hidden assumptions, and reduce revisions after sampling. Be specific where the requirement is known. Where it is not, provide the use case and ask the manufacturer to state its proposal and test basis. This gives both parties a clearer path from quotation to an approved production camera.