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.
Global wholesale buying guide
How to source video intercom and smart locks for distribution
A practical framework for distributors comparing supply, installation, support and ownership costs—not just the quoted unit price. It also covers product range, samples, connection evidence, market documents, quotation scope, timing and after-sales ownership before the first order.
01 · SUPPLYQuoted scope, accessories, MOQ and inventory exposure
02 · INSTALLATIONBuilding fit, wiring, commissioning and installer effort
03 · EVIDENCECertification, test reports and revision control
04 · SUPPORTReturns, spare parts, training and ownership after handover
Selection framework
Six checks that separate a workable supply route from a catalogue promise.
Start with the project boundary and compare the full cost of supply, installation, support and ownership. 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 connection review
Ask for the SIP configuration guide, documented ONVIF connection scope, API or SDK boundary, 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. |
| “Property-management platform connection” | Named platform, interface type, data flow, user provisioning and the functions included in the connection 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 and certification responsibilities before discussing deeper changes.
Review OEM & ODM routeChannel evidence cluster
Use five pages to close one distributor decision.
The distributor programme is the commercial hub. The supporting pages separate wholesale scope, factory evidence, after-sales ownership and model-specific compliance.
01 / HUBDistributor ProgramMarket, role, range and launch review.
02 / BUYWholesale GuideProduct, samples, quote and supply scope.
03 / AUDITFactory AuditProduction and control evidence.
04 / SUPPORTAfter-SalesWarranty, RMA and field ownership.
05 / VERIFYCertificationsModel and market document route.
Procurement 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.
Standard supply starts at 200 units. OEM and private-label programmes start at 500 units. ODM development starts at 1,000 units. Final scope, lead time and documentation are confirmed for the selected configuration, destination and written quotation.
Lead time is confirmed after the model, quantity, sample approval, documentation, packaging and available production slot are known. Ask the supplier to separate sample availability, engineering or artwork approval and mass-production timing rather than publishing one date for every order type.
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 and documented ONVIF connection scope, then bench-test registration, video, audio, door release and event behaviour with the planned PBX, NVR or VMS. Connection capability is model- and firmware-specific.
Property-management platform connection 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 the platform, user records, access events and door-release actions in scope. Treat 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 connection 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 connection review in mind?
Send the building type, quantity, destination and required interfaces. The RFQ route can then be prepared around the actual project scope.