Finding a Reliable LED Therapy Supplier in China: Supply-Continuity Questions to Ask
Supply continuity is not about finding a supplier where nothing ever changes. It is about whether changes are controlled, communicated and verified before they reach a delivered product. That distinction turns a vague question — “is this supplier reliable?” — into six specific ones about component substitution, traceability, escalation, spares and notification[1].
Table of Contents
- 1. Continuity Is a Change-Control Problem
- 2. How the Bill of Materials Is Controlled
- 3. Six Disruptions, and the Question Each One Becomes
- 4. Traceability, Escalation and Life After the First Order
- 5. What Goes in the Agreement
- 6. Capacity and Continuity: What Our Figure Does Not Tell You
- 7. How We Handle Continuity
- 8. References & External Links
1. Continuity Is a Change-Control Problem
Buying teams tend to assess reliability as a character trait: is this supplier dependable? It is a fair question and a poor one, because it cannot be answered with a document. In practice, every supplier in this industry will change something during your product’s life — a component, a supplier, a process, a firmware version, a model.
What differs is whether those changes are approved, recorded, communicated and re-verified before they affect what arrives at your warehouse. That is a property of a system, not of a personality, and it can be inspected.
So the aim is not to demand that nothing changes. It is to know, in advance, which changes you will be told about, which ones require your approval, and what happens to stock already in the field when something turns out to be wrong.
2. How the Bill of Materials Is Controlled
Start by identifying the components that would matter if they changed — the emitters, the driver, the optics, anything in prolonged skin contact, the battery. Then ask five questions about how those specific parts are governed.
- How are approved suppliers for each critical part maintained? Not “do you have approved suppliers”, but where the list lives and who can add to it.
- Does a substitution require written customer approval? If yes, in what form, and what happens if production needs the part before approval arrives.
- What evidence of equivalence is required? A comparable bin and wavelength is an argument; a measurement on the finished assembly is evidence.
- Does a component change trigger new testing or revised documentation? Which tests, and does the instruction for use get reviewed alongside them.
- Who owns the change record, and can you see one? A single real example from the last year tells you whether the process is used[2].
One line is worth memorising for the meeting: a verbal assurance that an alternative part is “the same” is not a control, it is a hope. The point of the question is not to catch anyone out — it is to establish who decides, because at some point someone will have to.
3. Six Disruptions, and the Question Each One Becomes
The scenarios below are illustrative rather than drawn from any named supplier’s history. Each one is common enough in this industry to be worth planning for, and each turns into a specific question you can put in writing today.
| Disruption | What It Exposes | The Question to Settle in Advance |
|---|---|---|
| A critical LED bin is discontinued | Whether substitution is a controlled decision or an improvisation. | Who approves a substitute, what equivalence evidence is required, and which tests are repeated. |
| A driver IC goes on allocation | Whether your production slot was ever guaranteed, or only discussed. | What happens to your allocation when supply is short — in writing, before it happens. |
| A subcontractor changes a process | Whether your control reaches past the factory wall. | Who audits sub-suppliers, who approves their changes, and who is obliged to tell you. |
| A firmware fault appears in the field | Whether affected stock can be identified and contained. | How batches are linked to firmware versions, and what you are told, in what timeframe. |
| A revision ships without notice | Whether change notification is a rule or a habit. | Which change types trigger notification, to whom, and within how many days. |
| The model reaches end of life | Whether spares and records were ever planned for. | How long parts and technical records stay available, agreed in the contract rather than assumed. |
4. Traceability, Escalation and Life After the First Order
Traceability is only worth what it enables. The question is not whether records exist, but what they let you do on the day something is wrong: identify which units are affected, stop the rest, and explain it to a customer.
- What connects a unit or batch to its components, revisions and test results? If the chain stops at the carton, a field problem becomes an investigation across your whole inventory.
- Who notifies you when a risk emerges, and how quickly? An escalation clause with no named role is a clause nobody performs.
- How is affected stock contained? Including stock in transit, in your warehouse and already with a distributor. This is the step most often discovered to be missing.
- What is the spare-part and repair position? Which parts are stocked, for how long, at what price, and whether the product can be repaired rather than replaced.
- How does end-of-life get communicated? A date, a notice period, and a final-order opportunity — or a message that arrives after the parts have gone.
- How long do records remain available? Because the answer to a question in year four depends on a file written in year one.
One caution here: do not assume a supplier can promise indefinite parts support. Nobody can, and a supplier who agrees to it readily has probably not thought about what it costs. What you can ask for is a documented arrangement — a period, a notice obligation, a last-time-buy opportunity — which is a promise someone can actually keep.
5. What Goes in the Agreement
Continuity only becomes real when it is written into the quality or supply agreement, because that is the document someone reads when the account manager has changed and the schedule is under pressure.
| Item | What the Agreement Must State | Why a Verbal Answer Is Not Enough |
|---|---|---|
| Change notification | Which change types trigger notice, to whom, and within how many days. | “We always tell customers” has no trigger and no deadline, so it is unfalsifiable. |
| Substitution approval | That critical components require written approval, and what evidence must accompany a request. | Approval given in a chat message is hard to find, and impossible to rely on later. |
| Traceability scope | What each unit or batch can be linked to: components, revisions, inspections, test results. | Traceability cannot be added retrospectively to stock that has already shipped. |
| Escalation contacts | Named roles on both sides, with response expectations for a quality issue. | A sales contact is not an escalation path at 11pm on a Friday. |
| Spares and end of life | Availability period, notice obligation, last-time-buy opportunity and record retention. | “We will support it” is not a period, and cannot be planned against. |
| Recovery plan | What happens to your order when a line stops, and who decides the sequence of recovery. | The plan is only useful if it exists before the disruption, not during it. |
6. Capacity and Continuity: What Our Figure Does Not Tell You
Rainbowdo states a monthly production capacity of 100,000 units and a starting MOQ of 500 units. Neither figure answers a continuity question on its own, and it is worth being precise about why.
- Capacity available for your configuration and window. A monthly total is not a slot. The relevant figure is what can be allocated to your model, in your packaging, in the month you need it.
- The component supply plan behind it. Capacity without parts is a building. Ask what the plan is for the critical components identified in section 2.
- The inspection and release sequence. How long between the last unit coming off the line and a shipment being released, and what could hold it.
- The contingency arrangement. What happens to your order if a line stops — the recovery plan in the table above, tested against a real answer.
- Whether the MOQ is per model, per configuration or per order. The written quotation should say which, because the three answers imply very different minimum commitments.
None of this is a criticism of a headline figure. It is simply that a headline figure is the beginning of a continuity conversation rather than the end of one — and a supplier who can talk comfortably about allocation, component plans and recovery sequences is telling you something a number cannot.
Planning continuity terms into a supply agreement? Visit our
Custom Light Therapy Manufacturing Page.
7. How We Handle Continuity
Rainbow Technology runs ODM and OEM programmes from our Shenzhen facility. These are the continuity conversations we expect, and the answers we would rather give before you ask:
- A named change-notification rule, with the change types that trigger it and the timeframe you should expect.
- Written approval for critical substitutions, accompanied by measurement evidence on the finished assembly rather than a claim of equivalence.
- Traceability that reaches the components, so a field issue can be bounded rather than estimated.
- A spare-part and end-of-life position stated as a period, with notice and a last-time-buy opportunity, rather than an open-ended assurance.
- 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
[1] International Organization for Standardization.
ISO 13485:2016 Medical devices — Quality management systems — Requirements for regulatory purposes. The source of the change-control, traceability and record-retention 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 basis for deciding how much traceability and control a given product risk actually warrants, rather than applying the same regime to every part.
