What the standard build carries
GMS certification
Where a specification lists GMS certification, it applies to that standard build — the reason deployments that depend on Google Mobile Services need the platform and build stated together.
Fingerprint module approval
The capacitive fingerprint module carries Ministry of Public Security certification where it is used, which matters for identity deployments in regulated workflows.
Environmental ratings
Ingress protection figures published on a product page apply to that platform as built — and to that housing. Structural changes mean re-verification, not a carried-over rating.
Nothing beyond the above is assumed to carry over to a custom build. That is deliberate: a project that starts from "what does your market actually require" finishes on schedule more often than one that starts from a list of assumptions.
What is scoped for your destination market
| Route | When it applies |
|---|---|
| Radio and wireless approvals | When the device ships to a market with its own radio approval regime, or when the LTE band configuration is changed for local carriers |
| Conformity marks | Where your procurement or import process requires specific marks before goods are accepted |
| Sector-specific approval | Where a deployment sits inside a regulated workflow — identity programmes are the common case |
| Operator or enterprise policy | Where the buyer's own acceptance testing is the real gate, with its own document list |
Tell us which of these apply before the proposal is written. The answer can change the hardware, the enclosure or the test list, and it is much cheaper to settle at feasibility than at acceptance.
When certification work changes the plan
| Change | Likely effect |
|---|---|
| Structural or enclosure change | Ingress protection and mechanical testing re-verified on the new part — see industrial design |
| New or changed radio module | Radio approvals affected for the markets you ship to |
| New mainboard | EMC and safety work belongs to the new board, not the original platform |
| New modules in the build | Verify the module's own approvals and the SDK or integration requirement, as covered in software customization |
| Nothing structural changes | The test plan stays close to the standard build, which is usually the fastest route to a first order |
Where certification sits in the schedule
| Stage | What happens |
|---|---|
| Feasibility | Destination market, required marks, and whether the change affects existing approvals |
| Proposal | Test plan, documentation set and schedule stated in writing before tooling |
| Engineering sample | Units available for the tests your market requires, and for your own integration |
| Verification | Tests run and records collected; the image is frozen for production |
| Mass production | Production follows the verified configuration; later changes are raised as a revision with their own review |
The full six-stage project sequence is on the Custom Solutions page, and ordering terms are summarised on the OEM and ODM centre.
Certification questions
Which certifications does the standard build already carry?
Do you handle the conformity marks our market requires?
Does a custom enclosure change what has to be re-tested?
What documents come with a production order?
Tell us where the devices will ship
- Destination market, and any second market planned
- The marks or approvals your procurement requires
- Whether the department sits inside a regulated workflow
- Whether the project changes the enclosure, the board or the radio
- Your own acceptance testing, if the buyer runs one
- Quantity and target date
Discuss certification Chat on WhatsApp
Shenzhen Xinhong Smart Technology Co., Ltd. · WhatsApp and phone +86 185 9427 9341 · [email protected] · Mon–Sat, 9:00–18:30 (GMT+8). Back to the OEM and ODM centre · hardware customization · software customization · industrial design · Android OS customization.