How to Prepare an RFQ for a Custom Remote Control Project

Prepared by RemoteControlCN Engineering Team. Compliance references checked on September 28, 2026.

A product photo, button count, target price, and frequency do not define a custom remote control project. The supplier still has to guess what the remote operates, how it communicates, which functions matter, and what the price includes. Those guesses often return as revised quotations or incompatible samples.

A useful RFQ gives each supplier the same technical and commercial baseline and becomes the first controlled project specification. If you are still selecting the control method or development route, start with the OEM lighting and fan remote-control buying guide. Otherwise, use the process below to prepare a quotation-ready package.

Key Takeaways

• Define the controlled product and receiver interface before discussing handset appearance.
• Quote the transmitter, receiver, firmware, tooling, testing, and packaging as separate scopes.
• State the destination market for radio compliance, and identify the product owner and design path for Bluetooth qualification.
• Ask every supplier to return pricing, assumptions, exclusions, and open questions in the same format.
• Approve samples against a revision-controlled specification and written test record.

What Should a Custom Remote Control RFQ Accomplish?

The RFQ should explain the control system, support a realistic development route, and expose assumptions that affect price. It must also let your team compare proposals without rebuilding them into a common format.

A supplier may adapt an existing platform, retain the housing while changing electronics or firmware, or develop new tooling, electronics, firmware, and a matched receiver. Describe the required result, then ask the supplier to state the route, limitations, and new work. The returned quotation should show inclusions, exclusions, assumptions, one-time charges, price tiers, sample scope, ownership, and open questions.

Step 1: Define the Controlled Product and Project Boundary

The first step is to describe the complete system, not just the handheld transmitter. By the end of this step, a supplier should be able to draw a simple block diagram showing the remote, communication link, receiver or device, power source, and controlled load.

State what the remote operates, how the product is powered, the load or logic interface, the installation environment, and the normal user scenario. Include relevant system details such as lighting channels and dimming, fan motor and speed control, or appliance modes and feedback.

Then mark the RFQ boundary. Does the supplier quote only the handset, or also the receiver, antenna, PCBA, wiring, enclosure, firmware, packaging, test fixture, and compliance support? Identify what already exists and who owns each input.

Use remote controller product families as visual references, but never treat similar appearance as proof of compatibility.

Verification: Someone who was not involved in the first discussion should be able to mark what is inside and outside the supplier's scope without asking what the word "remote" includes.

Step 2: Describe the Control Link and Compatibility Inputs

Name the intended control technology, or clearly mark it as undecided. IR, RF, and Bluetooth require different compatibility information, test conditions, and compliance planning. If your team is still deciding, review the practical differences between RF and IR control methods before requesting a final quotation.

For RF, provide destination markets, known frequency, protocol or coding data, pairing behavior, receiver and antenna configuration, interference environment, and range-test conditions. A distance is incomplete without the test environment, obstacles, mounting position, receiver, and antenna. Ask the supplier to identify missing data and propose a verification method. Wireless remote controller options can help identify the product type, not the final protocol.

For IR, provide the carrier and protocol if known, command data, working samples, receiver details, and line-of-sight conditions. For Bluetooth, specify required profiles or services, the company placing the product on the market under its own name, model naming, host integration, and the proposed qualification path. Relevant Bluetooth and voice remote options may help define the product class.

Frequency alone never proves compatibility. A supplier also needs the coding, command structure, pairing rules, timing, and receiver behavior, or physical samples that can be tested together.

Verification: The RFQ either contains enough data to reproduce the control link or lists the samples, measurements, and open questions required before compatibility can be confirmed.

Step 3: Build a Function Table Instead of a Button List

A button count describes the housing, not the behavior. Use one row per command and record short press, long press, repeat, combinations, feedback, and power-cycle behavior. Include pairing, timeouts, wake-up, and reset where relevant.

Add application-specific rows where needed. LED lighting projects may require dimming, CCT, scenes, zones, and memory. An air conditioner remote control project may require modes, limits, display states, timers, and synchronization. A fan remote control project may require speed, direction, timer, light, and shutdown behavior.

Assign the same revision identifier to the function table, key artwork, firmware, and receiver behavior. If the artwork says "Timer" but the function sheet calls the key "Delay," reviewers may approve different interpretations.

Verification: Every physical key and every automatic behavior has an expected response and a practical acceptance check.

Step 4: Specify the Handset, Receiver, and PCBA Separately

Separate the three scopes even when one supplier quotes all of them. A single line item can hide different handset, receiver, and control-board assumptions.

For the handset, specify dimensions, battery access, keys, indicator, display or backlight, legends, finish, environment, and sealing. Mark dimensions fixed by the product or packaging.

For the receiver, provide the supply input, load or logic interface, connector and pinout, relay or driver interface, antenna, mounting space, enclosure, standby behavior, and fault state.

For the PCBA, provide the outline, keep-outs, holes, connectors, programming access, firmware ownership, component restrictions, and test points. A lighting control board or another receiver PCBA also needs documented input, output, and load conditions. If one supplier designs both boards, ask how their revisions will be paired and traced.

Verification: The quotation shows which physical and electronic assemblies are included, who provides their input specifications, and which changes would trigger a new quotation.

Step 5: Provide Mechanical, Artwork, Branding, and Packaging Files

Supply controlled files wherever appearance or fit affects approval: dimensioned drawings, available 3D files, button artwork, vector logos, color references, finish samples, labels, dielines, manual languages, barcodes, and accessories.

A screenshot is a reference, not a controlled color or finish standard. Identify which drawing or physical sample governs approval. For an existing enclosure, ask what can change without new tooling, including the key layout, battery space, PCB outline, logo area, and surface treatment.

Artwork also needs revision control. Put the model, language, revision, and approval date in the filename or title block. When legal markings or manual statements depend on the destination market, keep them in the market-specific approval package instead of copying them across models without review.

Verification: The quotation identifies existing-tool limitations, artwork work, packaging work, and every item that would require new tooling or a separate approval.

Step 6: State the Destination Market and Compliance Responsibility

Do not ask whether the supplier is "certified." Ask for a model-specific compliance plan that names the product configuration, destination countries, responsible brand or importer, required documents, labels, manual statements, and responsibility split.

For the European Union, the Radio Equipment Directive addresses essential requirements for safety and health, electromagnetic compatibility, and efficient use of radio spectrum (European Commission, accessed September 28, 2026). The RFQ should define the final product and all intended configurations, then assign responsibility for determining the applicable conformity route and harmonised standards.

For the United States, an RF device generally cannot be marketed before the applicable equipment authorization has been obtained, subject to the conditions and exceptions in 47 CFR section 2.803. Import conditions and exceptions are addressed separately in 47 CFR section 2.1204. The RFQ should identify the responsible party, device configuration, proposed authorization path, and any test evidence the supplier will provide.

For Bluetooth products sold under your company's name, identify your company's qualification path in the RFQ. The Bluetooth SIG states that a supplier or another member cannot complete the qualification process on behalf of your company's product; the submission must be made under the member account of the company qualifying that product (Bluetooth SIG, accessed September 28, 2026). A reseller that distributes another company's qualified product without presenting it as its own should instead verify that the original company completed the qualification process.

One report should not be assumed to cover every model, hardware revision, firmware version, receiver combination, or market. If you need broader sourcing background before assigning responsibilities, review these common remote-control sourcing questions.

Verification: The supplier's response lists the proposed documents and tests, the exact model or revision they cover, and the party responsible for each action.

Step 7: Define the Sample and Approval Plan Before Requesting a Price

Define what each requested sample is meant to prove. Depending on the project, you may need a functional prototype, appearance sample, engineering validation sample, or pilot-production approval. Not every project needs every stage, but each stage used should have a written purpose.

State the requested quantity, included hardware, firmware revision, receiver revision, test setup, pass or fail criteria, approver, feedback format, and change-control method. Use one approval table so comments do not disappear across email, chat, annotated images, and spreadsheets.

If lot acceptance sampling will be used, name the current inspection standard, sampling plan, inspection level, lot definition, and acceptance criteria. Writing only "standard AQL" is incomplete because it does not identify the sampling parameters. ISO published the third edition, ISO 2859-1:2026, for sampling procedures for inspection by attributes, but the buyer still needs to select and document the applicable plan.

Verification: A reviewer who did not attend the development meetings can repeat the sample test and reach a recorded pass, fail, or open result.

Step 8: Require a Comparison-Ready Supplier Response

Give every supplier the same response table. Do not let unanswered fields disappear. Mark them "open," "not included," or "buyer input required" so they remain visible during commercial review.

The supplier should return the completed table with the technical proposal. If protocol data, drawings, or market requirements are missing, the response may be a budgetary quotation with stated assumptions. It should not be presented as a final production quotation.

Verification: Two proposals can be compared row by row without treating omitted work as included or relying on separate email explanations.

Copy-and-Paste Custom Remote Control RFQ Checklist

Copy this checklist into your RFQ and delete items that do not apply. Keep the revision number and attachment names at the top of the document.

1. Company and project details

• Buyer, brand owner, importer, and engineering contacts
• Project name, model name, RFQ revision, and response deadline
• Development route requested or marked open for supplier proposal

2. Controlled product and use environment

• Product being controlled and normal user scenario
• Power system, controlled load or interface, and installation environment
• Temperature, moisture, indoor or outdoor use, and other relevant conditions

3. Control technology and compatibility

• IR, RF, Bluetooth, or undecided route
• Frequency, protocol, coding, pairing, command data, or available samples
• Receiver, antenna, host, and operating-distance test conditions

4. Function table

• One row for every command and non-key behavior
• Short press, long press, repeat, combination, feedback, memory, and reset rules
• Acceptance check for each function

5. Handset, receiver, and PCBA specifications

• Handset dimensions, battery, keys, display, indicators, finish, and environment
• Receiver input, output, connector, antenna, mounting, standby, and fault state
• PCBA outline, keep-outs, holes, connectors, programming access, and test points

6. Mechanical, branding, and packaging files

• Drawings, 3D files, artwork, logo, color reference, and finish standard
• Packaging dieline, labels, manuals, languages, barcodes, and accessories
• Existing-tool constraints and requested new tooling identified

7. Target markets and compliance

• Destination countries and responsible brand or importer
• Required reports, declarations, labels, and manual statements
• Responsibility matrix tied to the exact model and revision

8. Samples and acceptance

• Sample type, quantity, included hardware, and firmware revision
• Test setup, expected results, evidence, approver, and feedback format
• Change-control process and any lot sampling plan

9. Commercial response fields

• Quantity tiers, MOQ basis, one-time charges, and sample charges
• Timing assumptions, packaging basis, freight basis, payment terms, and quotation validity
• Ownership of tooling, firmware, source files, artwork, and fixtures

10. Attachments and revision control

• Attachment index with filename, revision, date, and approval status
• Open-question list and named owner for each answer
• One approved specification package used for quotation and sample approval

Common RFQ Mistakes That Delay a Useful Quotation

Sending only a photo and target price. The supplier cannot see the protocol, receiver interface, functions, scope, or test conditions. Add a system description and mark unknowns instead of inviting guesses.

Giving a range without test conditions. Walls, interference, antenna location, receiver design, supply state, and mounting position affect the result. Define a repeatable test setup.

Treating the handset and receiver as independent. A remote that transmits does not automatically control a given receiver. Quote and test the link as a system.

Requesting "CE/FCC" as a generic line item. Name the destination market, model, configuration, responsible party, and expected evidence. The supplier can then propose the applicable work without implying that one document covers every variant.

Mixing revisions across channels. Consolidate comments into one approved specification, function table, artwork set, and test record before authorizing the next sample.

Frequently Asked Questions

Can a supplier quote before the protocol is known?

Yes, but the quotation should be labeled budgetary and list the protocol assumptions, excluded validation work, and information required for a final quotation. If an existing receiver must be matched, provide protocol and coding data or working samples for verification.

Is a new mold always required for a custom remote control?

No. An existing enclosure may work if it fits the dimensions, battery, key count, PCB space, branding area, and user-interface requirements. Ask the supplier to separate changes possible with existing tooling from changes that require new tooling.

Can a new handset be matched to an existing receiver?

Possibly. The supplier needs enough information to reproduce the communication link, such as frequency, protocol, coding, timing, and pairing behavior, or working samples that can be measured and tested. Appearance and frequency labels are not sufficient evidence of compatibility.

Who is responsible for Bluetooth qualification?

A company that sells the Bluetooth product under its own name should confirm and complete the applicable qualification path under its member account. A supplier cannot complete another company's product qualification on that company's behalf. If you only resell another company's qualified product without presenting it as your own, verify the original company's qualification record instead.

What makes a quotation final?

A final quotation should identify the agreed configuration, scope, assumptions, quantities, packaging basis, one-time charges, compliance responsibility, sample plan, commercial terms, and remaining deviations. If a material technical input is still open, the quotation should show how that uncertainty affects price or scope.

Turn the RFQ Into an Engineering Review Package

A good RFQ produces two useful outputs: quotations that can be compared on the same scope and samples that can be checked against written acceptance criteria. Keep the controlled-product description, function table, receiver information, artwork, compliance plan, supplier response, and sample record under one revision system.

To request an engineering review from a custom remote control manufacturer, send the controlled-product details, function table, receiver or working-sample information, target markets, estimated quantity tiers, and required project timing. Unknown items can remain open, but they should be visible so the supplier can respond with specific questions and assumptions.