How to Evaluate a Red Light Therapy Device OEM/ODM Manufacturer
A manufacturing partner should be evaluated against the risks of your specific project, not against a checklist of claims. Four questions carry most of the decision: who actually makes the product, what the documents prove, whether production can repeat what the sample did, and who controls change after approval. Price and minimum order quantity belong after those four, because their value depends on the answers[2].
Table of Contents
- 1. Who Actually Makes It
- 2. Inspect Evidence, Not Badges
- 3. A Good Sample Is Not a Process
- 4. Compare the Commercial Model Last
- 5. What Our Own Numbers Do and Do Not Mean
- 6. What a Supplier Evaluation Pack Should Contain
- 7. References & External Links
1. Who Actually Makes It
Three different businesses answer the same enquiry: a factory that builds the product, an integrator that assembles and manages several suppliers, and a trading intermediary that passes the enquiry on. All three can be legitimate. What is not legitimate is not knowing which one you are speaking to until the first quality problem arrives.
The test is not whether everything is in-house — very few suppliers do every process internally, and insisting on it excludes competent partners. The test is whether the division of labour is transparent, and whether each responsibility has one named owner. Six responsibilities need a clear answer.
| Responsibility | The Question to Ask | If It Stays Ambiguous |
|---|---|---|
| Design and specification ownership | Who makes the design decisions, and whose name is on the drawing that production builds to? | No one can say who approved a change, so the approved configuration becomes whatever shipped last. |
| Regulatory documentation | Who holds and maintains the technical file, and who signs the submission in your market? | A document set exists but nobody owns its currency — the classic cause of a launch that stalls at the border. |
| Component selection and substitution | Who chooses parts, who may substitute them, and what triggers a re-test? | A different LED bin or driver arrives quietly and the optical report no longer describes the product. |
| Testing and measurement | Which tests are performed in-house, which are outsourced, and which laboratory signs the result? | You cannot tell whether a report describes the product or a predecessor of it. |
| Production release | Who authorises a batch to ship, against what criteria, and what happens when a criterion fails? | Release becomes a schedule decision made by whoever is under the most pressure that week. |
| Post-market and complaints | Who receives a complaint about the device, who investigates, and who decides whether to notify anyone? | Complaints are answered by the channel that happened to receive them, with no route back to the design. |
2. Inspect Evidence, Not Badges
Every supplier has logos. The question is what each document actually establishes, because three terms that sound interchangeable are not: registration is an administrative listing of an establishment or product; certification is a third-party attestation against a standard, with a scope; and product authorisation is a permission to market a specific device for a specific intended use. A supplier can hold the first, legitimately lack the third, and still describe itself as “FDA registered”.
| What to Request | What It Establishes | Where It Stops Being Enough |
|---|---|---|
| Quality-system certificate with its scope | That a management system was audited for a stated scope at a stated site. | The scope may exclude the process you are relying on, or the site you are buying from. |
| Sample test reports | That a specific configuration met specific criteria under specific conditions. | Reports for a sibling model, or dated before the current design, describe a different device. |
| Incoming and final inspection records | That inspection happens routinely, with criteria, and is recorded rather than assumed. | A record showing all-pass with no defined criteria is a form, not a control. |
| Nonconformity and corrective-action process | That problems are logged, investigated and prevented from recurring. | An empty log across a long production history suggests nothing is being captured. |
| Establishment registration or listing | That an entity or product appears in an administrative register. | It says nothing about review of safety or performance for your device. |
| Product authorisation for the model | That a specific model cleared or was approved for a stated intended use in a stated market. | The authorisation attaches to the model and scope listed — not to the brand, and not to the factory. |
Ask every document the same four questions before reading the conclusion: which entity, which site, which product, which configuration. A document that cannot answer all four is not wrong, but it is answering a different question than the one you asked[1].
3. A Good Sample Is Not a Process
A hand-built sample can meet every criterion and still tell you nothing about the third production lot. Repeatability is a capability, and it is demonstrated by records rather than by the sample on the table.
- How production units are held to the approved configuration. Which parameters are checked, how often, and against which drawing revision. “We follow the same process” is not an answer; a control plan is.
- How parts and suppliers are traced. Whether a finished unit can be tied to the component lots inside it — the difference between investigating a problem and guessing at one.
- How changes are approved. Who decides, what re-testing a change triggers, and how the decision propagates to labels, instructions and production records.
- How test failures are handled. The disposition, the retest, and whether the failure stays in the file. A supplier who shows you a failed test and what followed is more informative than one who shows a clean sheet.
- A documented sample-to-pilot-to-production path. With acceptance criteria and named responsibilities at each gate, so that “approved” means the same thing at every stage.
This is also the section where a site visit earns its cost. Not to inspect the showroom, but to watch one inspection being performed and ask who signs it off. Fifteen minutes on the line usually settles more than a week of correspondence.
4. Compare the Commercial Model Last
Once the technical and quality gates are passed, seven commercial terms decide between the survivors. Comparing them earlier is not wrong so much as premature: a low price on a scope that cannot be maintained is the most expensive option available.
- Minimum order quantity, stated per configuration rather than per product family, because the meaningful figure is the one for the version you intend to buy.
- Engineering and tooling charges, separated from unit price, with ownership of the tooling stated explicitly. Who owns a mould when the relationship ends is a question best answered before it begins.
- Unit price at your volume, with the assumptions behind it written down — configuration, packaging, Incoterm, payment terms.
- Lead time and its dependencies. A generic number is not a commitment. Ask what it assumes about material availability, production slot and your own approval timeline.
- Warranty terms, in writing, including who pays freight and what voids cover.
- Spare parts and service: what is stocked, for how long, and at what price.
- Support during launch, defined as deliverables rather than goodwill — who answers technical questions from your channel, and within what time.
Require every quotation to state its assumptions and exclusions. A quote without exclusions is not a quote; it is an opening position, and the exclusions will appear later as change orders.
5. What Our Own Numbers Do and Do Not Mean
It would be strange to describe this process and then present our own figures as though the rules did not apply. So here is the same standard applied to Rainbowdo: what we can state, and the limits on each statement.
Capacity and minimum order. We report a monthly production capacity of 100,000 units and a current starting minimum order of 500 units. Both are company-provided baseline figures, not a promise that any model, customisation or order size can be produced immediately. A quotation should identify the product family, configuration, packaging, production slot, material availability and schedule — and it is fair to ask whether a capacity figure is nominal, planned, or currently available for your order.
US product authorisations. Public FDA records identify two Traditional 510(k) clearances covering LED mask models. They are model- and scope-specific. They do not mean that every Rainbowdo product is cleared, and a clearance is not an approval.
| Record | Models Covered | Decision Date | Status |
|---|---|---|---|
| K243423 | RB-008, RB-030, RB-081, RB-008G, RB-008GB, RB-008J, RB-008JB | 28 January 2025 | Public record |
| K253712 | RB-051, RB-061, RB-071, RB-052, RB-062, RB-072, RB-053, RB-063, RB-073 | 23 January 2026 | Public record |
| K263313 | Red Light Therapy Hair Growth Cap — RB-009, RB-011, RB-012, RB-088, RB-089, RB-092 | Reported received 29 October 2026 | Company-reported; public record pending |
Two notes on how to read that table. For the two public records, check the K-number in the FDA’s own database rather than taking this page’s word for it — the model list and the indications for use are what matter, and both are visible there. For K263313, the company reports having received the SE letter, but the public record was not independently retrievable when this page was prepared; until it appears, the company-held letter is the document to verify against, and the model list and indication language should be read from it rather than inferred.
That is what “evidence, not badges” means in practice, including when the supplier is us: name the record, name the models, name the date, and say plainly which part has not yet been confirmed independently.
Building a supplier evaluation pack? Visit our
Custom Light Therapy Manufacturing Page.
6. What a Supplier Evaluation Pack Should Contain
Rainbow Technology runs ODM and OEM programmes from our Shenzhen facility, and we would rather be evaluated on documents than on a presentation. The pack we expect to answer covers:
- Scope and responsibility — which processes are in-house, which are subcontracted, and who owns design, testing, release and complaint handling for your configuration.
- Quality documentation with scope — certificate and its scope, inspection records, and the nonconformity and corrective-action process[3].
- Model-specific test reports, with the instrument, conditions and configuration identified, and stated limitations.
- A sample-to-pilot-to-production plan with acceptance criteria and named approvals at each gate.
- Commercial terms with assumptions and exclusions — MOQ per configuration, engineering charges, tooling ownership, lead-time dependencies, warranty and spares.
- 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 13485:2016 Medical devices — Quality management systems — Requirements for regulatory purposes. The source of the document-control, traceability and change-control expectations used throughout this page; incorporated by reference in the FDA Quality Management System Regulation that took effect on 2 February 2026.
[2] International Organization for Standardization.
ISO 14971:2019 Medical devices — Application of risk management to medical devices. The reason supplier evaluation should follow the risks of your specific project rather than a generic checklist of claims.
[3] U.S. Food and Drug Administration.
Overview of Device Regulation. Distinguishes establishment registration and device listing from Premarket Notification 510(k) and Premarket Approval — the terminology behind the “registration is not authorisation” point in section 2, and the database in which the K-numbers above should be verified.
