Product Configuration
Product Configuration for Global Certification
Define the product, variants, power supply, radio, and accessories that the test report and certificate will actually cover, before a sample is booked.
Product Configuration
The certificate only covers the configuration you name.
A market does not approve a product family in the abstract. It approves a defined configuration: the model, the power supply, the battery, the radio module, the firmware, and the accessories in the box. If the report describes a different unit, the certificate does not cover what you ship.
ORBIS reads the configuration with your engineers before testing starts. We lock the boundary of the product, the variants that can share evidence, and the parts a substitution would break. That decision is what keeps a later model change from reopening the whole file.
How ORBIS scopes it
What decides the file
The unit you ship
The sample, the label, and the instructions have to describe the same product. We write that boundary before the lab builds a fixture.
What can change later
Some options can be added by a family listing. Others require a new file. We say which is which before you commit the design.
Records in one place
The agreed configuration lives with the project in ORBIS Intelligent Compliance, so the next market starts from the same product.
Questions
Before you start
We have six SKUs. Do we test all of them?
+
Not always. We group the SKUs that are electrically and mechanically the same and name the ones that need their own evidence.
Can we change a power supply after the grant?
+
Only if the certificate allows that substitution. If it does not, the change is a new configuration and we scope what has to be repeated.
Bring the product and the markets.
We will tell you which of this work applies, which evidence you already have, and what still has to be done before the product ships.
Book a Discussion