What decides whether a new variant can ride on an existing report, and what it takes to put a second model name on a document that was issued for one.
Most of these cases arrive as an assumption rather than a question. The second colour is ready, or a distributor asks for a higher-capacity version of something that already has a report, and someone in the company says: it is the same product, the report covers it. Sometimes that is right. Sometimes it holds until a marketplace compliance team, an importer or a buyer's quality engineer opens page one of the report, reads the model list, and finds a model name that is not there.
Whether a model can be added to an existing test report depends on one thing: what actually differs between the two models, and whether that difference touches anything the laboratory measured. Everything else follows from that - the cost, the timeline, and whether the answer is a piece of paperwork or a bench booking.
A test report is a record of a measurement. It names the sample that was on the bench: its model designation, electrical ratings, mechanical construction, firmware version, the accessories used, and the radio modes that were exercised. When a report lists several model names, those are the variants that were declared before testing started and assessed as one family, usually with the most severe of them tested as the representative sample.
That is not the same as holding a certificate. The documents in this area do different jobs, and treating them as interchangeable is where most of these problems begin - the roles of a report, a declaration and a third-party certificate are set out in test report vs certificate. The point here is narrower: a report is not a licence that you extend by printing a new name on the carton. If the model is not in the list, the report does not cover it.
Nearly every "can we add a model" question is really one of two different cases.
Only the second case needs a decision, and that decision is a comparison, not a formality.
| What differs between the two models | Usual effect on the report |
|---|---|
| Brand or model name only - the hardware is identical | No bench work. The added model is documented and the report is amended to list it, provided the identical hardware is evidenced |
| Colour, paint, trim, packaging | Normally documentation only, with the more severe variant as the tested sample |
| Enclosure material or shape, internal layout | Reassessment. Shielding, creepage and clearance distances move with the construction |
| Output power, current or voltage rating | Retest of the affected items - ratings are measured values, not label text |
| Different battery cell, or a higher-capacity pack | The battery items are tied to the cell and the pack; the EMC and safety items depend on what else moved |
| Different supplied adapter or charger | The adapter is part of the tested configuration, so the configuration changes with it |
| An added radio mode, or a changed antenna | New radio testing. Radio behaviour is tested mode by mode |
| New firmware version, power table or band list | The tested firmware version is recorded, and RF behaviour can change with it |
The pattern is straightforward: names and cosmetics are cheap; anything electrical, mechanical or radio is not.
This is the logic that makes family coverage possible at all. A laboratory does not test every variant. It identifies the worst case in each direction - the variant most likely to produce the highest emissions, the one drawing the most current, the one with the tightest clearances - and tests that one. If every other variant in the range is the same or less severe in every measured respect, the result for the worst case covers them.
The catch is the word every. A second model can be less severe for emissions and more severe for temperature rise. Family coverage fails the moment one variant is worse in one parameter, because the tested sample is then no longer the worst case for that item. That is why a family assessment is a comparison table rather than a one-line statement that the models are similar, and why a laboratory will ask for both bills of materials before answering.
There are three possible routes, and which one applies follows from the table above.
Two things do not count as any of these. Editing the model list in your own copy of the report, and relabelling the product. Both leave you with a document that does not describe the product you ship, and it works right up until someone checks - by which point the goods are usually already on the water.
Buyers, importers, marketplaces and customs authorities do not read a report from cover to cover. They open it and look for four things: the model name that matches the shipping carton, the standards applied, the test dates, and the name of the responsible company. A model that is absent from the list fails the first of those checks no matter how similar the product is. It is also why the model list on the report, the model list on the declaration and the label have to agree with each other - the reasons they usually do not are covered in why the laboratory asks for your label and artwork.
If you want a firm answer instead of a provisional one, send these five things together:
A photograph of both units helps more than it sounds. A cosmetic-only change sometimes turns out to include a relocated connector once the two boards are placed side by side.
A private-label version for a distributor. The hardware comes from the same factory and only the brand name on the enclosure changes. This is the easy case, but it needs evidence rather than an email: a statement from the manufacturer plus matching bills of materials. Without that, no laboratory can put a second brand on the report.
A higher-capacity battery version. The instinct is that the case and the electronics are unchanged, so the report should still apply. It does not, because the battery-related items were measured on the smaller pack. Expect the battery tests to repeat and the EMC and safety items to be reviewed against the new pack.
Adding a plug variant for a second market. The electronics are identical and only the supplied cord set differs, yet the cord set is part of the tested configuration, so the configuration has changed. If you know from the start that the product ships with three plug types, declaring all three before testing removes the problem entirely.
A model that only adds a radio mode. Occasionally a new model turns out to switch on a second radio that was already on the board but never declared. Radio behaviour is tested mode by mode, so this is a new radio test - and the honest version of that story is much cheaper than the version a buyer's engineer discovers later.
If what changed instead is a part inside one product - a substitute capacitor, a second-source connector - that is a different question with a different answer, covered in does changing a component require retesting.
On our side, family coverage is normally settled at quoting time. We ask for the full list of models you intend to sell, not just the one you plan to ship first, and we build the test plan around the worst case in the range so the report lists the whole family from the beginning. When a model is added afterwards, the review is a comparison of the two configurations against the tested sample, and the outcome is one of three things: an amended report, a defined delta test, or a clear statement that the new variant is not covered. Whichever it is, the reasoning is written down with the file, so the family rationale still stands up if a buyer or an authority asks about it two years later. That documentation is also what an importer needs when a marketplace requests evidence, since those requests usually arrive with a deadline attached. If it is not obvious which category your case falls into, our testing and certification work covers the EMC, radio, safety and battery scope most of these ranges sit in, and the initial comparison is a short piece of work.
If you are preparing to launch a second variant, send the model list you intend to sell, a short note on what differs between the existing model and the new one, and the original report. We will tell you which of the three routes applies - an amended report, a delta test, or a new project - before anything is booked on the bench.
No. A report is issued by the laboratory that performed the testing and can only be amended by them. A model added to your own copy leaves you with a document that does not describe what was tested, and it fails the first check a buyer, importer or marketplace makes.
Usually not a new project, but not nothing either. The laboratory has to confirm the hardware is genuinely identical, normally from the manufacturer's statement plus the bills of materials, and then the report is amended to list the second model. There is no bench work, but there is a review and a re-issued document.
Normally no. Colour and cosmetic changes are handled as documentation, as long as the tested sample is the more severe variant - for example the darker housing where optical or thermal behaviour matters. If the colour change comes with a different material or a different moulding, it is reassessed like any construction change.
Usually only after retesting the affected items. Ratings and battery performance are measured values, so a larger pack or a higher output changes results that were recorded on the original sample. The rest of the scope often carries over, which makes it a delta test rather than a full project.
An amended report is normally a matter of days, because it depends on document review rather than bench time. A delta test depends on which items repeat and on when the bench is available, but it is always a fraction of the original project. Full retesting is the slow case and is rarely necessary.
That is a different question. Adding a model is about product coverage - which models a report describes. Whether the same report can serve several countries is about market coverage, and it depends on the standards listed in it and on what each destination market accepts.