Assessing a Chinese LED Beauty-Device Supplier: Due Diligence Beyond the Website

Table of Contents

• 1. What “Beyond the Website” Actually Means
• 2. Five Names That Must Match
• 3. Audit the Operating System, Not the Brochure
• 4. Test the Relationship Before Scaling
• 5. Keep a Written Risk Register
• 6. A Note on the Country in the Title
• 7. What We Will Answer Without Being Asked
• 8. References & External Links

---

1. What “Beyond the Website” Actually Means

“Beyond the website” is usually read as “visit the factory”. A visit is useful, and it is not the first thing to do. The first thing to do is arithmetic on names, because the most expensive supplier problems are not manufacturing failures — they are mismatches between the entity you contracted, the site that produced, the party that invoiced and the party that holds the records.

Those four can all be different, and each combination has a different consequence when something goes wrong. None of it is visible on a website, and most of it is visible in documents you already have: the quotation, the proforma invoice, the certificate, the payment instruction.

The effort should be proportionate. A low-value accessory order and a regulated device launch do not warrant the same diligence, and pretending otherwise wastes the budget that should have gone into the second one. What the five checks below have in common is that they cost almost nothing and are worth doing at every scale.

---

2. Five Names That Must Match

Lay the documents side by side and check that the names agree. Where they do not, the question is not whether the supplier is dishonest — it is who is accountable for what, and whether you can enforce a claim against that party.

The Name	Where It Appears	What a Mismatch Means
Contracting entity	Quotation, contract, proforma invoice.	You may be contracting a trading company with no production authority and no ability to correct a design fault.
Production site	Certificate scope, audit report, shipping documents.	The site that was audited may not be the site that makes your order — and the records belong to neither if a third one does.
Invoice entity	Commercial invoice, customs declaration.	Payment and import records point at a party outside the contract, which complicates both a claim and a recall.
Bank beneficiary	Payment instruction.	A beneficiary unrelated to the contract is a fraud indicator. It is always worth one phone call to a number you did not receive by email.
Holder of technical records	Technical file, test reports, the source of the instructions for use.	If a trader holds them, the factory may be unable to update them — and you inherit a file nobody can maintain[1].

A trading intermediary is not automatically unsuitable — many are competent and add real value in coordination. What cannot be acceptable is not knowing that an intermediary is in the chain. Ask directly which processes are performed by the contracting entity, which are subcontracted, and who signs off production release.

---

3. Audit the Operating System, Not the Brochure

The brochure describes the best week the factory ever had. The operating system describes what happens on an ordinary Tuesday, which is what your order will experience. Seven things are worth asking for, in this order.

• Incoming inspection. What is checked on arrival, against what criteria, and whether a rejected lot is ever accepted under pressure. The last part is rarely written down and always worth asking aloud.
• Traceability from unit to lot. Whether a finished device can be tied to the components inside it. Without it, investigating a complaint becomes guesswork across an entire production run.
• Nonconformity handling. Where problems are recorded, who reviews them, and whether the log contains anything. An empty log across a long history is a finding rather than a compliment.
• Corrective action. Not just that a defect was fixed, but whether the cause was addressed and whether anything changed as a result.
• Change approval. Who signs a design or component change, and what re-testing it triggers. This is the point where a good product quietly becomes a different one.
• Production against the approved sample. Ask to see the comparison being made, not the description of it. One look at the fixture and the checklist answers more than a paragraph of process narrative.
• Component substitution and end-of-life parts. What happens when an LED bin is discontinued or a driver is replaced. A supplier with no answer here will improvise at the worst moment, and may not tell you.

Where it is permitted, inspect one record rather than a folder — a single incoming inspection sheet, a single nonconformity, a single change approval. One real record tells you whether the system is used; a bound folder of templates tells you it exists.

---

4. Test the Relationship Before Scaling

A sample evaluates a product. A pilot order evaluates a relationship — and the relationship is what you are actually buying at volume. Define the sample plan and its acceptance criteria in writing before anything ships, then use the sample stage to observe how the supplier behaves when something is wrong.

• Log the defects and the response. What was wrong, how quickly it was acknowledged, what corrective action was proposed, and whether it was delivered.
• Time the replies. Response speed at sample stage is a reasonable predictor of response speed at complaint stage, when the stakes are higher for you and lower for them.
• Use a pilot gate for higher-risk projects. A modest order with agreed inspection and release conditions, before volume. It costs a little and it converts a judgement about people into evidence about a process.
• Do not let a good sample substitute for the rest. A device that looks acceptable does not validate production control, and it certainly does not validate the market documentation you will need at the border.

---

5. Keep a Written Risk Register

Most sourcing teams already hold this information — in an email thread, a chat history and one person’s memory. Writing it down converts it into something that survives a staff change and can be escalated without re-litigating the history.

Column	What It Records
Risk	One sentence, in plain language, describing what could go wrong.
Evidence	What you actually saw or received, with the document reference — not what you were told.
Likelihood and impact	A simple high, medium or low for each. False precision here produces a spreadsheet nobody updates.
Owner	A named person on your side. A risk owned by a department is a risk owned by nobody.
Mitigation	The control you have put in place, or will put in place before the next milestone.
Open question	What is still unanswered. This column is why the register is useful in a meeting rather than decorative.

Revisit the register at four moments: after a supplier change, after a late delivery, after a failed test, and after a quality complaint. Those are the moments when new information arrives, and the only ones where the register earns its maintenance^[2].

---

6. A Note on the Country in the Title

The title of this page names a country because that is how buyers search. It is not a risk category, and it should not appear as one in your register. A supplier’s location does not predict its conduct; a site’s records do. Everything above applies equally to a supplier in Shenzhen, in Eastern Europe or in your own country, and a checklist that scores nationality instead of evidence has simply replaced one form of guessing with another.

What cross-border sourcing genuinely changes is the cost of verification, and it changes it in three specific ways worth planning for. Distance makes a site visit expensive, so verification has to be scheduled and budgeted rather than assumed. Language differences make document scope easy to misread, which is why written confirmation of scope matters more than conversational fluency. And payment routes add a step in the chain, which is why the bank beneficiary in the table above deserves a phone call rather than a glance.

Applied to us, the same discipline gives a short list. Rainbowdo reports a monthly production capacity of 100,000 units and a starting MOQ of 500 units — company-provided baseline figures, not a promise that any model or order size is immediately available. A serious enquiry should therefore ask for the current capacity definition, the production site and process scope, a configuration-specific quotation, and the schedule assumptions behind any delivery date. And for any product-market claim, verify the exact model against its own records rather than treating every product from one supplier as interchangeable.

Running due diligence on a new LED supplier? Visit our
Custom Light Therapy Manufacturing Page.

---

7. What We Will Answer Without Being Asked

Rainbow Technology runs ODM and OEM programmes from our Shenzhen facility. The five names, the seven records and the risk register are all reasonable requests, and these are the answers we would rather volunteer than be chased for:

• The contracting entity, the production site and who holds the technical file, stated together, so the chain can be checked rather than inferred.
• Which processes are in-house and which are subcontracted, including who signs production release for your configuration.
• A real record on request — one incoming inspection sheet, one nonconformity, one change approval — rather than a folder of blank templates.
• A pilot gate with agreed inspection and release conditions before you commit to volume.
• 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.

---

8. References & External Links