OEM LED Face Mask RFQ: The Technical Brief Buyers Should Send to a Manufacturer
An RFQ is useful when it describes the intended product and separates mandatory requirements from preferences. A product photo and a competitor link force the supplier to guess about materials, performance, testing, packaging and target market — and guesses are what make quotations impossible to compare[2]. Ten sections and one tagging rule are enough to fix most of it.
Table of Contents
- 1. Why a Photo-Based RFQ Fails
- 2. The Ten Sections
- 3. Must, Preferred, or Supplier to Propose
- 4. The Compliance Matrix — and What It Cannot Decide
- 5. Two Figures to Confirm, Not Assume
- 6. Sending It to Us
- 7. References & External Links
1. Why a Photo-Based RFQ Fails
The most common OEM enquiry is a picture of a competitor’s mask, a target price, and a request to “make something like this”. It feels efficient. In practice it hands the supplier a series of decisions the buyer is better placed to make, and returns a quote built on assumptions that were never written down.
The damage shows up later as a comparison problem. Three quotations arrive at very different prices, and nobody can tell whether the difference is the LED count, the material, the packaging, the certification scope or the supplier’s margin. Every one of those is a line the buyer never specified, so every supplier filled it differently.
An RFQ is not a longer email. It is the document that makes quotations comparable, and its value is measured by whether two responses can be read side by side.
2. The Ten Sections
Ten sections cover a mask brief. The third column is what a supplier has to invent when a section is missing — which is the most practical way to decide whether a section is worth including.
| Section | What It Must Contain | What Gets Guessed Without It |
|---|---|---|
| 1. Intended use and users | Who uses it, on which body area, for what purpose, and who should not use it. | The entire design brief — output, geometry, warnings and the market-access route. |
| 2. Markets and channels | Countries, channel type, label languages and any known market-specific requirement. | Plug type, label set, packaging format and the compliance scope the quote should cover. |
| 3. Form factor and fit | Mask or panel, coverage, adjustment range, and a mass ceiling if one matters. | Housing dimensions, material thickness and the tooling investment behind the price. |
| 4. Optical and electrical | Wavelength, irradiance at a stated distance, mode definitions, input power, runtime — with measurement conditions where you know them. | The performance target itself, plus the LED, driver and battery choice. |
| 5. Materials and cleaning | Skin-contact materials, colour references, and the cleaning agent you intend to recommend. | Material grade and therefore the cost tier, plus whether the finish survives its own cleaning instructions. |
| 6. Controls and timers | Button logic, timer behaviour, shut-off, charging arrangement and error states. | Firmware scope and a bill of materials that changes after quotation. |
| 7. Packaging and labels | Retail or e-commerce pack, artwork ownership, languages, and what must appear on the box. | Packaging cost and the MOQ per variant — two figures that move the total significantly. |
| 8. Testing and documentation | Which reports you require, against which standards, and what acceptance means. | Test scope and therefore test cost — the line most often excluded from a quotation without comment. |
| 9. First order and forecast | First-lot quantity, a twelve-month range, and any seasonality you already expect. | MOQ, material purchasing and capacity planning across your whole range. |
| 10. Milestones | Target dates for sample, pilot run and production, plus your own approval steps. | Lead time quoted against nothing, which is why the number rarely survives contact with the calendar. |
3. Must, Preferred, or Supplier to Propose
Tag every line in the RFQ with one of three labels. It takes an extra column and removes most of the ambiguity from the responses.
- Must. A constraint the product cannot ship without. A deviation means the offer is non-compliant, and that has to be visible rather than negotiated quietly in a meeting.
- Preferred. A target you would trade against cost or schedule, stated as such. Marking a preference as a must is how a project acquires a requirement nobody can justify later.
- Supplier to propose. A line where you genuinely do not know the right value. Ask what options exist and what evidence is available for each, rather than inserting an arbitrary target that then becomes the specification.
That third label is the one teams under-use. Writing “irradiance: 40 mW/cm²” because it looks reasonable creates a requirement you now have to meet, test and support — when what you actually needed was a conversation about what the device can deliver and how it would be measured. An invented number is not neutral; it becomes the spec.
4. The Compliance Matrix — and What It Cannot Decide
Ask every supplier to return a completed compliance matrix rather than a narrative email: one row per RFQ line, with the columns below. The third column is why the format is worth insisting on.
| Column | What It Captures | Why It Changes the Comparison |
|---|---|---|
| Requirement, quoted | Your line, reproduced with its number and tag. | Keeps answers aligned to your numbering, so two suppliers can be read side by side. |
| Proposed response | What they will actually deliver, in the same units you asked in. | Exposes the supplier who answers a different question more impressively. |
| Deviation | Where their offer differs from your line, stated rather than implied. | The most informative column in the matrix, and where cost differences usually hide. |
| Supporting document | The file that evidences the response, with model and revision identifiers. | Turns a claim into something checkable, and makes “we can do that” auditable. |
| One-time and recurring cost | Tooling, NRE, artwork and certification separated from unit price. | Stops a low unit price with a large tooling charge from looking like the cheap option. |
| MOQ assumption | Stated per model and per variant, not per product family. | The figure that decides whether a colour or packaging variant is viable at all. |
| Lead-time dependency | What the quoted lead time assumes about materials, capacity and your own approvals. | A date without dependencies is not a commitment, and will not survive the first delay. |
| Outsourced steps and exclusions | What they do not perform themselves, and what the quotation does not cover. | Tells you where your risk actually sits, and what will arrive later as a change order. |
What the matrix cannot do is make the decision for you. A supplier can advise on manufacturability, cost drivers and what is difficult — that advice is valuable and should be sought. But four things stay with the brand, and they should be settled before anyone authorises irreversible spend: who owns the intellectual property, what constitutes sample acceptance, how tooling is owned and paid for, and how changes are approved after the design is frozen[1].
5. Two Figures to Confirm, Not Assume
Rainbowdo reports a starting MOQ of 500 units and a monthly production capacity of 100,000 units. Both belong in an RFQ as points to be confirmed rather than as blanket assumptions — which is exactly how a buyer should treat any supplier’s headline numbers, ours included.
- Ask for MOQ per configuration. The starting figure, the figure with a logo or packaging variant, the figure if you request an engineering change, and the minimum for a first production lot. Four numbers, not one.
- Ask for capacity available in your delivery window. Total monthly capacity is not allocation. A capacity figure becomes meaningful only when it is attached to the SKU, the configuration and the month you need it.
- Ask whether the number is nominal, planned or currently available. Three different claims hide inside one adjective-free sentence, and the answer changes what you can promise your own customers.
Nothing about a total monthly figure guarantees a specific lead time. A supplier running at capacity can still hold a production slot for you; a supplier with spare capacity can still be waiting on a component. The RFQ line that resolves this is not the capacity number — it is the lead-time dependency column in the compliance matrix.
Preparing an LED mask RFQ? Visit our
Custom Light Therapy Manufacturing Page.
6. Sending It to Us
Rainbow Technology runs ODM and OEM programmes from our Shenzhen facility. Send the RFQ in your own numbering and we will return it in the same rows, with the columns above completed:
- A completed compliance matrix, including the deviations rather than only the compliant rows.
- Separated one-time and recurring costs, so tooling, NRE and certification are visible next to unit price.
- MOQ stated per configuration and capacity confirmed for the delivery window you name, with the assumptions written down.
- Model and revision identifiers on every technical document, so each response can be traced to a build.
- Sample and small-batch production from 500 units, with a stated capacity of 100,000 units per month; both figures depend on model, configuration, packaging and schedule, and are confirmed in a formal quotation.
- Compliance documentation matched to the exact model for your target market. Where a model holds a 510(k) record we provide the K-number so you can check its scope in the FDA’s public database; clearance is not the same as FDA approval, and the scope differs from model to model.
7. References & External Links
[1] International Organization for Standardization.
ISO 14971:2019 Medical devices — Application of risk management to medical devices. The reason intended use, foreseeable use and change control have to be defined before irreversible work is authorised.
[2] International Organization for Standardization.
ISO 20417:2026 Medical devices — Information to be supplied by the manufacturer. Second edition, published March 2026, replacing ISO 20417:2021; it sets the general requirements for labelling, packaging and accompanying documentation — the content that has to be agreed in the RFQ rather than after tooling.
