For the fastest useful answer: send the application, target market, expected quantities, power architecture, sensing or control behaviour, physical format, customisation, required documents and five tests the sample must pass. TUODI can then match and quote one exact build instead of replying with a generic catalogue link. Copy the RFQ template →
1. Product fit and evidence
A product link rarely identifies the full build. Fix the model, revision, dimensions, included parts and sample evidence before comparing prices.
| Question to settle | What a useful answer should contain |
|---|---|
| Which current model fits the application? | Active model code, configuration suffix, application boundary and the current alternative if the linked item is run-out or discontinued. |
| Can I see the complete catalogue? | The relevant product-family pages first, then a dated catalogue or shortlist rather than an undifferentiated archive. |
| Can you send a complete datasheet? | One revision naming dimensions, power, sensing, controls, environment, accessories, packing and document scope. |
| Can I see real photos and a working video? | Current-build media showing the front, back, mounting, ports, controls and the requested function. Marketing artwork is not a substitute for a sample test. |
| What sizes, finishes and mounting formats exist? | Nominal and complete assembled dimensions, colour/finish, housing material and every included mounting part. |
| Is the hook, stand, case, sensor or battery part sold separately? | Exact spare-part number, compatible revisions, separate-sale status, pack quantity and continuity commitment. |
| Can I buy one or two units before a bulk order? | Sample configuration, cost, dispatch basis, freight, build time and whether a production-order credit is agreed on the quotation. |
| Is this an existing platform or a new development? | What is already tooled and tested, what changes by configuration, and what requires engineering, tooling or a new document route. |
2. Sensing and electrical architecture
Specify sensing behaviour, supply voltage and output switching separately. That prevents an apparently suitable sensor from arriving with the wrong range, wiring or load interface.
| Question to settle | What to freeze in the sample or quotation |
|---|---|
| PIR, microwave radar, hand-wave, photocell, door contact or presence? | The sensing principle and whether the product detects motion, close-range gestures, daylight or low-movement presence. |
| What are the range, angle and blind zones? | Horizontal and vertical coverage, mounting height, target speed/size, sensitivity setting and test-room conditions. |
| Can it cover a full room or reach roughly 5–8 m? | A model-specific detection diagram and an on-site sample test; “long range” is not an acceptance criterion. |
| Are time, lux and sensitivity adjustable? | Actual steps or ranges, control method, default settings and restart behaviour after power loss. |
| What voltage powers the sensor? | Input range, frequency, AC/DC polarity and whether the sensing module has an internal regulated supply. |
| What does the output provide? | Switched mains, low-voltage output, relay contact, dry contact, open collector, coil drive or data signal—plus wiring diagram. |
| What load can it really switch? | Lamp/driver/contactor type, steady current, inrush, inductive/capacitive derating, relay rating, conductor size and protection. |
| Does a timer switch the neutral? | Line/neutral topology, single- or double-pole isolation, switchable-neutral requirement and whether an external contactor is needed. |
| Is there manual override? | Override logic, duration, priority relative to the sensor and the state after an outage or manual reset. |
| Can it be hardwired at 12 V or 24 V? | Supply tolerance, output interface, cable/connector, maximum run, polarity protection and the exact receiver or driver it controls. |
| Can several lights share one plug or controller? | Maximum units and watts, connector topology, cable limits, simultaneous start/inrush and approved expansion parts. |
| Will it work in hot, humid, outdoor or splash-prone locations? | Operating-temperature/humidity basis and a named ingress test report. An IP number on a housing is not third-party proof. |
3. Rechargeable cabinet-light configuration
| Question to settle | What to record |
|---|---|
| Which complete lengths are available? | Complete assembled length and separate light-section/battery-module lengths so component dimensions are not mistaken for the finished product. |
| Can a short bar use a 3000 mAh battery? | Cell chemistry, rated and measured capacity, cell/pack dimensions, protection board, available internal volume, weight and heat—not a label-only upgrade. |
| What protects the battery? | Overcharge, over-discharge, short-circuit and temperature protection; cell and pack report mapping; and the approved charger/input. |
| USB-C, Micro-USB or a removable battery card? | Physical connector, input rating, cable supplied, charge indicator, replacement path and whether connector changes alter documents. |
| Can the light operate while connected to power? | Pass-through behaviour, charging priority, heat, battery-cycle impact and whether the intended use is continuous or occasional. |
| How long does charging and runtime take? | Brightness, mode, trigger frequency, ambient conditions, ageing factor, cut-off point and test log. “Days per charge” without a use pattern is incomplete. |
| What output and colour quality will I receive? | Lumens, CCT steps, CRI, LED count by length, dimming range/method, diffusion and unit-to-unit tolerance. |
| How is it mounted? | Magnet/plate/clip design, adhesive brand or grade, target surface preparation, pull/shear test, removal access and replacement parts. |
| Can it be black, waterproof or a special wavelength? | Finish and optical target as separate changes; for waterproofing or a wavelength such as 670 nm, require an engineering sample and measurement evidence. |
| Can it be individually hardwired under cabinets? | Whether the offered platform is rechargeable, removable low-voltage or fixed wired; do not infer hardwiring from the appearance of a light bar. |
4. Connected lighting and hotel-room control
| Question to settle | What must be demonstrated |
|---|---|
| Can one external sensor switch several light bars together? | Protocol/frequency, pairing procedure, maximum receivers, latency, synchronisation, range and recovery after power loss. |
| Can PIR, hand-wave and door sensors use the same receiver? | Compatible part numbers, pairing/interchange rules, priority logic and a video or sample using the exact requested combination. |
| Does it support Matter, Zigbee, Z-Wave, Wi-Fi or another RF system? | Exact protocol/version, radio module, certification path, hub compatibility and what is implemented today versus proposed. |
| Can it integrate with our hub or application? | API/SDK, data model, command and event list, authentication, cloud dependency, firmware ownership and update route. |
| Can it report when mains power failed and for how long? | Event source, timestamp source, offline clock/buffer, upload behaviour after reconnection, accuracy and data-retention limits. |
| Can a hotel room combine door contact and presence sensing? | Occupied/vacant state logic, delay, sleeping/low-movement test, false-off containment, override and commissioning procedure. |
| Can the controller drive an external DIN-rail contactor? | Dry-contact/coil output, fail-safe state, coil voltage/current, isolation, enclosure and who supplies the contactor. |
| Does one key-card switch read both 125 kHz and 13.56 MHz cards? | A same-unit demonstration with both credentials, supported technologies, card whitelist logic and clear distinction from two separate variants. |
| Can it connect to BMS or hotel controls? | Required interface—dry contact, RS-485/Modbus or another defined protocol—register/event map, isolation and commissioning responsibility. |
| What happens after power or network loss? | Output state, retained pairings/settings, clock behaviour, reconnection sequence and a repeatable recovery test. |
If your project needs Matter, Zigbee, Z-Wave, outage-duration logging, same-unit dual-frequency key-card reading or a switchable-neutral timer: include it as a development requirement. TUODI's published catalogue does not present these as standard functions, so feasibility and an exact-build demonstration come before a production promise.
5. White-noise, audio and nursery-product projects
| Question to settle | What to verify |
|---|---|
| Which sounds and how many are included? | Dated file list, category, length, encoding, loop point and the exact model/firmware configuration. |
| Is the noise mechanical or speaker-generated? | Sound-generation architecture and an acoustic sample; do not infer “real fan” from the word white noise. |
| Can our own audio library be loaded? | Number/size/format of files, storage method, naming/order, looping, programming ownership and production test. |
| Is audio loaded by TF/SD card or flashed to memory? | User-removable versus factory-programmed storage, update route, content security and whether a hardware/firmware revision is required. |
| Will a track loop continuously without an audible gap? | A full-duration listening test using the final encoded file and timer behaviour at the loop boundary. |
| Bluetooth, app-connected or fully offline? | Radio/version and app requirements—or explicit confirmation that no Wi-Fi, Bluetooth, app or cloud function is present. |
| Can the display numbers or lights be turned off? | Night-mode controls, minimum brightness, retained settings and whether indicator LEDs remain visible. |
| What are the timer, volume and sound-pressure ranges? | Actual steps/ranges and a dB measurement distance/setting, not an unreferenced “quiet” claim. |
| What are charge time and battery runtime? | Battery configuration, local/Bluetooth/light mode, volume/brightness, cut-off and test basis. |
| Can the housing, strap, PCB, app or controls be redesigned? | Existing-platform limits versus new industrial design, tooling, electronics and software work; prototype plan; ownership; cost; MOQ and schedule. |
Nursery briefs should specify materials, small-part/strap risks, temperature, charging and destination-market requirements. This site makes no medical, sleep-treatment or infant-safety claim.
6. OEM, ODM and configuration control
| Question to settle | What belongs in the project record |
|---|---|
| Can you sign an NDA before receiving our drawings? | Named parties, covered information, permitted use, term, governing terms and the files released after signature. |
| Which changes fit an existing model? | Logo, finish, packaging and firmware/content changes separated from battery, PCB, radio, sensor, housing and tooling changes. |
| What is the prototype path? | Feasibility review, engineering input, prototype type, sample quantity, test plan, revision loop and approval gate. |
| What are tooling and development charges? | Tool/item list, ownership, storage/maintenance, modification rights, refund/credit conditions and what deliverables the fee buys. |
| What is the MOQ for logo, packaging and a functional redesign? | Three separate thresholds. Printing minimums, component purchase lots and new-tooling economics are different constraints. |
| Can the logo be printed or laser engraved? | Position, size, artwork format, colour/finish, sample approval and permanence/abrasion check. |
| Can packaging and manuals be customised? | Dieline, dimensions, materials, print finish, languages, marks/labels, accessory map and responsibility for legal/importer fields. |
| Can you match a reference product without copying protected branding or design? | Translate the reference into a neutral performance, interface and acceptance brief; identify protected branding, appearance and IP boundaries; and do not call the result “equivalent” without agreed comparative testing. |
| Can we supply our own PCB or app and buy only the housing or mechanical assembly? | Interface and control drawings, incoming inspection, assembly/integration responsibility, warranty boundary, document holder, IP ownership, MOQ and packing for the component-only scope. |
| Is this model or platform already exclusive to another buyer in my country or sales channel? | The exact model, tooling and design rights; territory and channel; exclusivity term and performance conditions; pre-existing rights; and which custom elements, if any, can actually be reserved. |
| Who owns firmware, app, source files and tooling? | Pre-existing IP, project deliverables, source-code/SDK access, account ownership, maintenance and exit/transfer terms. |
| How is the approved build protected from drift? | Golden sample, BOM/revision, approved substitutions, change-notice period and re-sample/document triggers. |
7. Certification, test reports and destination markets
| Question to settle | What a document check should show |
|---|---|
| Which document covers this exact model? | Issued record number, model list, product description, applicant/holder, manufacturer, laboratory/body, date, standard and market. |
| Is it a grant, certificate, attestation, report, declaration or marking? | The document type stated accurately; a logo or factory claim is not promoted to an approval. |
| Does the report cover the offered revision and component change? | Exact suffix/build, sameness basis and whether battery, radio, power or housing changes require review or re-testing. |
| Can you provide a declaration of conformity? | Correct legal manufacturer/responsible party, model, applicable legislation/standards, signature/date and supporting technical records. |
| What is needed for the EU, Great Britain, Northern Ireland, US, Canada or another market? | A model-and-destination document map. Do not treat CE, UKCA, FCC or another acronym as universally interchangeable. |
| Does an ingress claim have a test report? | Report number, tested configuration, method, result and current relevance—or a clear statement that the number is only the manufacturer's own marking. |
| What battery transport documents are current? | Cell/pack mapping, UN 38.3 summary, MSDS and carrier/mode-specific current acceptance documents. |
| What packaging and importer data must the factory supply? | Materials, weights, label fields, carton data and technical records separated from the buyer/importer/responsible-operator obligations in the destination. |
| What is the HS code? | A proposed classification tied to the exact product and destination review; the importer or broker remains responsible for final classification. |
| How long is each document valid? | Expiry or continuing-validity basis, surveillance/renewal status and a pre-shipment recheck where carrier or market rules change. |
8. Samples, price, payment, packing, delivery and after-sales
| Question to settle | What the quotation should state |
|---|---|
| Can I start with one unit, a pilot or a mixed-model trial? | Allowed quantity/configuration, sample or stock status and which assumptions change for production. |
| What are prices at several quantity levels? | Exact SKU/configuration, quantity, currency, tax status, Incoterm, included packaging/accessories and quotation validity. |
| What payment methods, deposit and balance milestones are available? | Seller and payee legal entity, currency, bank or platform route, deposit, inspection and shipment-release milestones, fees, refund conditions and whether any buyer-protection service actually applies. |
| What does the sample cost include? | Product, custom work, freight, duty/tax basis and any production-order credit agreed before shipment. |
| What are sample and production lead times? | Preparation/build time, approval dependencies, materials/packaging critical path, start-of-clock event and dated dispatch estimate. |
| Is the exact variant in stock? | SKU, quantity, location, revision, packaging state, document status and reservation/dispatch terms. |
| EXW, FOB, DAP or DDP? | Named place, included charges, freight mode, customs/duty/tax responsibility and any battery route restriction. |
| What are unit-box and master-carton data? | Box dimensions/weight, units per carton, carton dimensions, gross/net weights and pallet assumptions where relevant. |
| Can you ship directly to customers? | Supported products/destinations, one-order minimum, processing time, tracking, returns, neutral-pack requirements and system/API capability. |
| Can packaging omit invoices and supplier branding? | Exactly which marks/documents remain for legal, customs and safety reasons, and what can be neutralised by agreement. |
| Can you share a non-confidential customer or market reference? | Only a reference the customer has authorised, with the product, period and supply scope stated narrowly. If confidentiality prevents names, ask for other verifiable evidence rather than an unattributed logo list. |
| What are warranty, DOA and remedy terms? | Period, covered defect, evidence, notice window, allowance, replacement/credit/repair, freight allocation and excluded misuse. |
| What happens after a successful sample? | Production approval, final PI, golden sample/BOM, inspection plan, change control, packing sign-off and shipment release. |
| Can a repeat buyer reorder the same build? | Revision and availability recheck, approved-substitution control, current lead time and any re-sample/document trigger. |
Advanced requirements to confirm before sampling
These projects can involve new electronics, firmware, tooling, documents or logistics. Keep the requirement in your brief, then ask for feasibility, the exact proposed build and a sample demonstration before budgeting around it:
- One sensor synchronising several bars across interchangeable PIR, hand-wave and door-sensor inputs.
- Matter, Zigbee or Z-Wave integration with a buyer-owned hub and application.
- Mains-outage events, offline timestamps and duration logging.
- A same-unit 125 kHz and 13.56 MHz hotel key-card reader.
- Presence plus door-contact hotel logic with a dry-contact or contactor output.
- A two-hour hot-water timer with switchable neutral.
- 12 V radar/presence sensing with relay or dry-contact output.
- Custom audio libraries, removable storage, gapless looping, buyer-designed PCB/app or full new housing.
- IP67 or outdoor use, custom optical wavelengths, and exact North American or destination-specific approvals.
- Year-round stock, per-order dropshipping, blind packaging and API integration.
Copy-and-paste RFQ structure
Application: installation, user behaviour and failure that must be avoided.
Product/configuration: preferred model or format, dimensions, materials, finish and accessories.
Power and control: input, output/load, sensing, timing, connectivity and recovery after power/network loss.
Market and documents: destination, sales channel, required document types and packaging/label responsibilities.
Commercial path: sample, pilot and expected repeat quantities; required Incoterm and destination.
Acceptance: five sample tests, evidence format and the points that must be written into the quotation/PI.
Ready for a model recommendation and sample quote? Send only the sections that apply. TUODI's international team will map the request to a current platform, flag anything that needs development and return the questions needed to price the right sample. Send the RFQ on WhatsApp →
Where these buyer questions came from
TUODI management supplied a 210-row export of questions received through its Alibaba inbox. Every row was reviewed and the useful requirement patterns were reorganised into this checklist. Names, companies, countries, contact details and original message wording are not published.
The source also contains duplicates, greetings, declines, spam, out-of-range requests and post-order notes. It is therefore not presented as a market-share or demand-frequency study. A requested function is a buyer requirement, not proof that the function already exists; where TUODI's current catalogue does not establish a capability, this guide tells you to confirm it for the project.