Product fit
Define the building, door count, indoor-unit requirement, cabling condition and environmental exposure. Confirm whether the proposed model is PoE, 2-wire retrofit or Wi-Fi.
B2B procurement guide
How to choose a video intercom or OEM manufacturer
A practical evaluation framework for distributors, system integrators, property teams and brands. Review the evidence behind product fit, integration, market documentation and commercial terms before you compare a quotation.
01 · PRODUCTBuilding type, entry topology and user flow
02 · INTERFACESIP, ONVIF, API and access-control handoff
03 · EVIDENCECertification, test reports and revision control
04 · COMMERCIALMOQ, timing, support and brand ownership
Selection framework
Six checks that separate a workable supply route from a catalogue promise.
Start with the project boundary. A capable manufacturer should be able to answer each question against a named model, target market and intended deployment—not a generic product family.
Protocol and integration
Ask for the SIP configuration guide, supported ONVIF profiles, API or SDK scope, and Wiegand / OSDP / RS-485 handoff. Test the actual firmware before approval.
Market documentation
Match the exact SKU and hardware revision to the destination. Request the Declaration of Conformity, lab reports and local approval route, not only a logo on a datasheet.
Commercial boundary
Separate standard supply, OEM branding and ODM scope. Confirm what is included in the quote: hardware, accessories, packaging, app route, testing and documentation.
Production and timing
Review sample approval, change control, production slot, inspection point and spare-parts route. Treat lead time as a planning range until the model and quantity are fixed.
Support and ownership
Clarify firmware updates, API access, warranty, RMA, documentation ownership and who handles first-line support after the distributor or integrator takes over.
Evidence before quotation
Turn every supplier claim into a document or a test.
The fastest way to reduce procurement risk is to ask for the same evidence from every shortlisted supplier.
| Claim to review | Evidence to request |
|---|---|
| “SIP compatible” | Firmware version, registration procedure, codec list, DTMF / relay behaviour and a test call with the planned SIP server. |
| “ONVIF supported” | Supported profile and conformance reference, plus a live test with the specified NVR or VMS. |
| “Certified for the market” | DoC, accredited laboratory report, exact model / revision and importer or responsible-person requirements. |
| “Fast delivery” | Stock position or production slot, sample approval dependency, packaging scope and the assumptions behind the date. |
| “PMS / platform integration” | Named PMS or platform, interface type, data flow, user provisioning and the functions included in the integration scope. |
Choose the right conversation
Different buyers need different evidence.
The next step should match your role. A distributor needs a repeatable product and support route; an integrator needs testable interfaces; an OEM buyer needs a clear brand and ownership boundary.
Distributor
Review product range, target-market documents, stock logic, packaging and the support material needed for repeat sales.
Review distributor routeDealer or integrator
Start with topology, SIP / ONVIF / access interfaces, commissioning ownership and a bench test against the intended system.
Review integrator routeOEM brand
Set the product line, brand assets, packaging, app route, certification responsibilities and MOQ before discussing deeper changes.
Review OEM & ODM routeProcurement FAQ
Questions to settle before you request a quote.
These answers are planning guidance. Confirm the selected SKU, destination and project scope before treating any figure or interface as a commitment.
Use 200 units as the current standard-supply planning point, 500 units for OEM branding and 1,000 units for ODM scope. The confirmed MOQ depends on the selected model, configuration, testing, packaging and destination. Request an itemized quote instead of comparing a headline MOQ alone.
For planning, standard stocked supply is typically reviewed in a 7–14 day range, OEM branding in a 21–30 day range and deeper ODM scope in a 60–90 day range. These are planning ranges, not delivery commitments; the final schedule follows model approval, documentation, quantity, packaging and production slot.
Ask for the documentation applicable to the exact SKU and target market: CE or RED where relevant, FCC for the United States, RoHS, applicable local approvals such as UKCA, UAE TDRA or Saudi CST or SASO routes, plus the Declaration of Conformity and underlying laboratory reports. ISO 9001 describes the factory quality system and does not replace product-level evidence.
Do not rely on the words SIP or ONVIF in a brochure. Request the device firmware version, SIP configuration guide, supported ONVIF profiles and conformance evidence, then bench-test registration, video, audio, door release and event behaviour with the planned PBX, NVR or VMS. Compatibility is model- and firmware-specific.
PMS integration must be defined by workflow and interface. Confirm whether the selected product exposes SIP, REST API, webhooks, SDK or a documented partner connector, and identify which PMS, user records, reservations, access events and door-release actions are in scope. Treat PMS compatibility as a project review, not a universal product claim.
Tuya and TTLock are platform choices that affect app workflow, device provisioning, cloud region, user administration, firmware ownership and integration boundaries. Confirm the exact lock family, app branding route, data location, API access, offline behaviour and platform fees before selecting one. Neither platform should be assumed to fit every property or market.
Have a model, market or integration in mind?
Send the building type, quantity, destination and required interfaces. The RFQ route can then be prepared around the actual project scope.