How to Verify a Red Light Mask Manufacturer’s Claims: A Buyer Evidence Checklist
A manufacturer’s website is a starting point, not an audit record. The work is to turn each important sentence into a specific document request, then record one of five statuses against it — not to decide whether the supplier feels trustworthy. This protects the buyer from a smooth presentation and protects a serious manufacturer from being compared against vaguer claims than its own.
Table of Contents
- 1. A Website Is a Starting Point, Not an Audit Record
- 2. Six Claims, and the Request Each One Becomes
- 3. Record a Status, Not an Impression
- 4. When a Supplier Says No
- 5. The Checklist, Filled In for Our Own Claims
- 6. Requesting the Pack
- 7. References & External Links
1. A Website Is a Starting Point, Not an Audit Record
Procurement teams are usually handed a supplier’s homepage and asked for an opinion. The homepage is written for a different purpose: it compresses a factory into adjectives and a decade into a number. Reading it as evidence produces two failures at once — unwarranted confidence when the presentation is good, and unwarranted suspicion when it is not.
The reliable move is mechanical and slightly tedious: take each sentence that matters and convert it into a document request that could be answered yes or no. “Twenty years of experience” becomes “which legal entity, and what does the twenty years cover”. “FDA cleared” becomes “which K-number, which models, which indications”. The conversion is the whole method; everything else is administration.
It is worth naming why this benefits a good manufacturer as much as a buyer. A supplier with real records is currently competing against suppliers whose equivalent sentences are unverifiable in both directions. A checklist that demands documents rewards the one who has them.
2. Six Claims, and the Request Each One Becomes
Six statements appear on almost every manufacturer site in this category. Each one is convertible into a request with a specific answer, and each has a version of the answer that sounds complete without being it.
| The Claim as Written | The Request It Becomes | What Would Actually Settle It |
|---|---|---|
| “20 years of experience” | Which legal entity, registered where, and what period do the years cover? | A registration document for the entity you are contracting with — not a group, a brand or a predecessor. |
| “100,000 units per month” | Is this nominal, planned or currently available allocation? For which site, over what period, and for which product family? | A written definition of the metric plus the month it applies to. Capacity is not the same as allocation for your order. |
| “Patented design” | Which patent number, which jurisdiction, who holds it, and is it owned or licensed? | The register entry, checked at the source — plus an explanation of how that patent relates to the model you are buying. |
| “In-house testing laboratory” | Which tests, on which equipment, and can you share a redacted report showing the method and the instrument? | A report naming the instrument, the conditions and the model tested. A photograph of a lab bench is not a capability. |
| “ISO 13485 certified” | The certificate itself: holder, address, scope, issuing body, validity date and any exclusions. | The certificate, read against your product. A quality-system certificate is not authorisation for every product made under it. |
| “FDA cleared” | Which K-number, which model list, and which indications for use? | The public database entry for that number, matched to the exact model. Registration and listing are different things from clearance[1]. |
Two of these requests are usually answered well and four are usually answered vaguely, in our experience of being asked them. The pattern is not random: the two that get answered are the ones where the document already exists as a file someone can attach. The four that get answered vaguely are the ones that require someone to read a scope and write a sentence about what it excludes.
3. Record a Status, Not an Impression
Every line in the checklist gets one of five statuses, plus the source file and the date you reviewed it. The value of the discipline is that it makes an unfinished review look unfinished, which is the honest state of most supplier comparisons at the shortlist stage.
- Verified. You have seen the document and confirmed it covers the entity, site, product and configuration in question.
- Partially verified. The document exists but covers a sibling model, an earlier revision, or a wider scope than the one you need.
- Supplier-stated. Asserted in writing by the supplier, with no document you have been able to inspect. This is a legitimate status and should not be quietly upgraded.
- Expired or out of scope. A real document that no longer applies — a lapsed certificate, or one whose scope excludes your configuration.
- Not provided. Requested and not supplied. Distinct from supplier-stated, and worth recording separately, because a pattern of these is the finding.
One rule prevents most of the errors: do not mark a claim as true because it appears repeatedly. The same paragraph on the homepage, the brochure, three marketplace listings and a trade-show banner is one source quoted four times, not four sources agreeing. Repetition is a distribution fact, not corroboration[2].
4. When a Supplier Says No
A refusal is not automatically a red flag. Complete technical files contain commercially sensitive material, and a supplier who hands one to every enquirer is not being careful with the next customer’s information either. The useful question is not whether they will disclose, but whether they offer a route.
- A redacted version. Model names, client names and pricing removed, with the method, instrument and conclusion intact. Most refusals survive contact with this request.
- Third-party confirmation. A testing laboratory or certification body that will confirm the existence and scope of a report without releasing it.
- A controlled review. An NDA plus a scheduled session, in person or by screen share, where the document is read rather than sent.
- A written summary of scope and limits. The least attractive option, and still far better than a sentence with no document behind it.
A supplier who offers none of these four has told you something. Not that the product is bad — that the evidence cannot be examined, and that you will be making the decision on presentation. That is a legitimate basis for a decision only if it is written down as one.
5. The Checklist, Filled In for Our Own Claims
A checklist is only credible if the author is willing to run it on themselves. Below are Rainbowdo’s own headline claims, with the evidence we can point to and the status we would honestly assign at the time this page was written.
| Our Claim | Evidence We Can Point To | Status |
|---|---|---|
| Starting MOQ of 500 units | A configuration-specific quotation naming the model, packaging and schedule. | Supplier-stated until your quotation is issued; a starting MOQ is not a substitute for that quotation. |
| 100,000 units monthly capacity | A written definition of the metric, the site it applies to and the period. | Supplier-stated; the definition should be requested alongside it. |
| 510(k) K243423 — RB-008, RB-030, RB-081, RB-008G, RB-008GB, RB-008J, RB-008JB | The FDA’s own public record for that K-number. | Public record — verifiable independently, and worth checking yourself rather than taking this page’s word for it. |
| 510(k) K253712 — RB-051, RB-061, RB-071, RB-052, RB-062, RB-072, RB-053, RB-063, RB-073 | The FDA’s own public record for that K-number. | Public record — same caveat: the model list on the record is what governs, not the brand. |
| K263313 — Red Light Therapy Hair Growth Cap, models RB-009, RB-011, RB-012, RB-088, RB-089, RB-092 | The company-held SE letter. | Supplier-stated; the public database record was not independently retrievable when this page was written. |
| Quality-system documentation | Certificate and scope, inspection records and corrective-action process, shown under controlled review. | To be provided on request — and it should be requested, not assumed. |
Two rows say “public record” and three say something weaker. That distribution is normal, and it is what a real checklist looks like: not a page of ticks, but a page where the differences between rows are visible to the person reading it.
Building your supplier evidence checklist? Visit our
Custom Light Therapy Manufacturing Page.
6. Requesting the Pack
Rainbow Technology runs ODM and OEM programmes from our Shenzhen facility. If you send the checklist above, we will answer it in the same rows rather than sending a brochure:
- A row-by-row response with a status for each item, including the rows where the honest answer is “supplier-stated” or “not provided”.
- A definition for the capacity figure — nominal, planned or currently available — with the site and period it covers.
- K-numbers with their model lists, so each one can be checked in the FDA’s public database rather than accepted on trust.
- A redacted or controlled-review route for anything we would not send by email, offered at the point of refusal rather than after a second request.
- 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] U.S. Food and Drug Administration.
Overview of Device Regulation. Sets out establishment registration and device listing alongside Premarket Notification 510(k) and Premarket Approval, which is why “FDA registered”, “FDA cleared” and “FDA approved” cannot be used interchangeably.
[2] International Organization for Standardization.
ISO 13485:2016 Medical devices — Quality management systems — Requirements for regulatory purposes. The document-control and traceability expectations behind the status system in section 3; incorporated by reference in the FDA Quality Management System Regulation that took effect on 2 February 2026.