Short answer: verifying a Chinese supplier is not something you receive, it is something you do. Documents can be bought, samples can be hand-picked and a factory tour can be arranged for a day. What separates a supplier you can build a product line with is whether the answers you get can be checked — and whether the same answers hold on the second and third order, not just the first.
This page is written for the buyer who has a shortlist and needs to know which items on it are real. It is also written to be used against us: the same questions appear below in the form we expect to be asked, along with what we can and cannot answer.
Five things you can verify before you pay anything
1. What kind of company you are actually talking to
There are three shapes in this market and they present almost identically: a factory that builds the product, a trading company that sources it, and a product development partner that coordinates design, specification and quality across factories it does not own. Each is legitimate. The problem is that a buyer who believes they are hiring one and is actually hiring another has mispriced their own risk.
The fastest test is not a question about identity but about capability: ask what they can change. A trading company can apply your logo to a finished product. A factory can change the product and owns the tooling to do it. A development partner can specify a change, hold the drawing and hold a factory to it. Ask for a specific example of each, and listen for whether the answer names parts or just activities.
2. Whether the equipment is owned or borrowed
"We test for that" and "we own the equipment we test that on" are different sentences. Ask which test equipment is on their own floor, and which tests are sent to a third-party laboratory. Then ask who pays for the third-party test and where the report goes. A supplier that cannot separate those two is describing an intention, not a capability.
3. Who holds the documents, and what they actually cover
Three documents circulate as if interchangeable, and they prove three different things:
- A product test report proves that one sample of one configuration passed the listed tests on a stated date. It does not prove that the units in your shipment were built to that configuration.
- A factory system certificate proves that a site's quality system was audited against a standard at a point in time. It says nothing about the performance of the product you are ordering.
- A battery test report proves that a cell or pack design passed defined abuse and transport testing. It does not prove that the cell inside your bill of materials is the one that was tested.
Ask which of the three you have been sent, read the scope page, and check the date. The question that matters is not "do you have certificates" but "does this document cover the configuration I am ordering?"
4. What happens when something goes wrong
Every supplier says quality is important. Far fewer can describe what they did the last time a batch failed. Ask for the most recent example, what the root cause was, and what changed afterwards. A supplier without a failure story is either new or not being straight with you.
Then ask the commercial version of the same question: if a pre-shipment inspection fails, who pays for the rework, and who pays for the delay. The answer should be in writing before the first order, not negotiated during the first crisis.
5. Whether your requirements are enforceable at all
Read your own specification back. Any requirement phrased as an outcome ("waterproof", "high quality", "durable") cannot be failed, which means it cannot be enforced. A requirement you can enforce names the test, the condition, the acceptance value and the record that proves it was met.
Three things that cannot be verified remotely
Being clear about the limits of remote verification is part of doing it properly.
- Batch consistency. A sample is one point in time. Whether the third batch matches the first is a property of the process, and the only way to know is to order a second batch and compare.
- Real spare capacity. A factory can look capable and still be fully committed to another customer's season. Ask what share of its lines your order would occupy, and what happens to your delivery date when a larger customer arrives.
- Yield. Nobody volunteers a first-pass yield figure they have not been asked for, and the number changes with product complexity. Ask for it against a comparable product.
What to put in writing before the first order
| Requirement | What to ask for | Why it decides something |
|---|---|---|
| Declared configuration | The revision, the approved vendor list and part numbers for the components that decide performance | Without it you have no baseline to compare a repeat order against |
| Substitution rule | A statement that listed components may not change without your written approval, plus the notification process | Substitution is usually a purchasing decision, not a plot — it needs a written gate |
| Test plan | The specific tests, the sample size, the method and the pass/fail thresholds for your order | An undefined test cannot be failed, so it cannot be enforced |
| First-article approval | Approval on each production batch, not only on the development sample | This is the only control that catches drift as it happens |
| Lot traceability | Lot codes recorded per component per batch, and the link from shipment cartons back to the batch | It is what lets a field failure be scoped to the units it affects |
| Change control | How a change is proposed, recorded, approved and communicated | Undocumented changes are how a good product quietly becomes a different one |
| Failure cost | Who pays for rework and delay if pre-shipment inspection fails | Better agreed before there is a shipment to argue about |
Red flags that survive a good presentation
- A price given before the specification is agreed.
- A capability claim with no example at the level being claimed.
- A certificate supplied as a cropped photograph with no scope page and no date.
- Reluctance to let you draw your own sample from production rather than from the sample room.
- No answer to "what may not be changed without my approval".
- A willingness to accept any target price without changing the specification.
How RYVO fits this, stated plainly
It would be inconsistent to write a verification page and then be vague about ourselves, so:
- We are not a factory. RYVO is a product development partner. We do not own a production line and we do not claim to. We specify, verify and coordinate, and we work with manufacturing partners we select, test and manage.
- What we hold is the specification, the verification work and the record of what was checked: over ten years of consumer electronics product development, and more than a hundred teardown and engineering analysis cases behind the way we specify things.
- What our partners hold is the production capability, the tooling and the line equipment, and those sit with them, not with us. When a project needs a certificate or an audit against a standard, that document names the site it belongs to — and we will tell you which site that is.
- What we will not do is send you someone else's certificate as if it were ours, publish indicative prices for a product we have not specified with you, or quote a number we cannot hold on a repeat order.
- What we ask of you is the same standard we apply to our own partners: a declared configuration, a test plan you are willing to enforce, and a written answer on who owns the tooling.
If your current supplier passes the checks on this page, you do not need us. If you cannot get the answers, that is usually the answer.
Frequently asked questions
Is RYVO a factory or a trading company?
Neither, strictly. RYVO is a product development partner: we hold the specification and the verification work, and production runs at manufacturing partners we select, test and manage. We do not own a production line, and we say so because a buyer who believes they are hiring one kind of company and is hiring another has mispriced their own risk. What we own is the specification, the drawing and the record of what was checked.
How do I check that a supplier is real before sending a deposit?
Check three things that cannot be bought quickly: what the company can actually change about a product, which test equipment is on its own floor rather than at a third-party laboratory, and a specific example of a batch that failed and what changed afterwards. Then ask for a certificate and read its scope page. None of these prove a company is honest, but a company that cannot answer them is not yet verifiable.
Can I rely on a certificate to confirm product quality?
Not on its own. A product test report is a statement about one sample of one configuration on one date, and a factory system certificate is a statement about a site's quality system rather than about your product. The useful question is whether the document covers the exact configuration you are ordering, which is why the scope page and the date matter more than the existence of the certificate.
What should I do if a supplier refuses a factory visit or an inspection?
Treat the refusal itself as information. A refusal to allow a randomly drawn sample from production, or to let an inspector see the line, is a stronger signal than any document. If a visit is genuinely impractical, the alternative is to require batch records and first-article approvals in writing, because those are checkable at a distance and a refusal to provide them has no innocent explanation.
How long does proper supplier verification take?
The document and sample review can be completed in a couple of weeks if you know what you are asking for. What cannot be compressed is the part that requires time rather than effort: seeing whether the same result holds on a second and a third batch. Any supplier claiming to prove consistency faster than that is describing a sample, not a process.
If you would rather work from a printed list, the same checks are available as a supplier verification checklist you can download and mark up by hand.