Certification support — compliance files prepared and kept valid
CE, FCC, UKCA, RoHS and REACH documentation prepared per market, issued under your name where required, and maintained as products and regulations change. This page sets out what we hold, what we prepare, the sequence from gap analysis to declaration, and what happens when a rule changes.
To importers, brand owners and distributors who carry the compliance risk,
Tittron — the B2B division of FlykanTech — invites you to put the compliance file on our side of the relationship. Every model we build carries CE, FCC, UKCA, RoHS and REACH documentation, and for programmes sold under your brand those files can be issued with your company as the applicant. When a marketplace, a retailer or a customs authority asks for the declaration, it exists — dated, signed and matched to the units you bought.
Certification is not a one-time exercise. Components are replaced, regulations are revised and ranges are extended; a file prepared once and forgotten is a file that fails an audit two years later. We maintain the documentation for the models you buy and tell you when something in it changes.
Send us the markets you sell into and the models you buy. We will return the list of files we hold for them, any gap that has to be closed, and the cost and lead time of closing it.
The Tittron teamB2B division of FlykanTech · www.tittron.com
What the service actually solves
Certification support means two things: the file exists, and the file is true. The first is paperwork — declarations, test reports, material declarations and labelling. The second is harder: the documents describe the units actually shipped, including the current hardware revision, the components inside them and the markets they are declared for.
Because the hardware, the firmware and the documentation are produced in one organisation, that second part is achievable. When a component changes, the Bill of Materials changes with it and the file is updated; when a firmware change touches EMC-relevant behaviour, it is assessed against the certified build rather than assumed to be harmless.
For private label and distribution programmes, the declaration can be issued with your company as applicant. That is usually what makes the difference between selling into a channel and being asked for documents nobody can produce in time.
From market list to maintained file
-
01
Market and model list
Give us the markets you sell into and the models you buy. We return the compliance files we already hold for each combination, and flag any gap.
- CE and UKCA for the EU and UK, FCC for the US, plus RoHS and REACH material declarations
- Market-specific extras identified — for example local labelling or importer details
- Gaps listed per model rather than as a generic statement
-
02
Gap analysis
For anything not already covered, we state what has to be done: a test, a new declaration, an updated material declaration or a labelling change — with cost and lead time attached.
- Written gap analysis per market
- Testing quoted separately from documentation work
- We say plainly when a gap cannot be closed on a given model
-
03
Testing where required
Where a test is needed, units are submitted to an accredited laboratory against the relevant standard, and we manage the submission and the report rather than handing you a contact.
- EMC, safety, radio and environmental testing as the market requires
- Test samples taken from the production build, not from a prototype
- Reports issued to your company where you are the applicant
-
04
File assembly
Declarations, test reports, material declarations, labelling artwork and the technical file are assembled into one set per model and market.
- Declaration of conformity dated and signed
- RoHS and REACH material declarations matched to the current Bill of Materials
- Labelling artwork checked against the market requirements
-
05
Issue under your name
Where the market or the channel requires it, the file is issued with your company as applicant or importer, so the documents you present are yours.
- Applicant and importer details set to your company
- Private label programmes issued under your brand as standard
- Documentation language matched to the market
-
06
Maintenance
Files are reviewed when a regulation changes, when a component changes or when the standard is revised — and you are told, rather than finding out from a channel audit.
- Component and hardware revision changes trigger a file review
- Regulatory revisions tracked per market
- Updated files issued to you and uploaded to your Cloud Disk
The numbers, at a glance
| Markets covered | EU (CE), UK (UKCA), US (FCC), plus RoHS and REACH declarations |
|---|---|
| File set | Declaration of conformity, test reports, material declarations, labelling artwork, technical file |
| Applicant | Tittron as standard; your company where the market or channel requires it |
| Gap analysis | Within five working days of the market and model list |
| Documentation only | 1–2 weeks where the test reports already exist |
| With new testing | 4–8 weeks depending on the standard and laboratory schedule |
| Maintenance | Reviewed on regulation changes and on component or hardware revision changes |
| Delivery | Files delivered as PDF and stored on your Cloud Disk |
The figures below are typical values. The quotation states the exact minimums, lead time and commercial terms for your specific programme.
What we actually do
Declarations per market
Declarations of conformity prepared for CE, UKCA and FCC as applicable, dated, signed and matched to the hardware revision you are buying — not to a discontinued build.
Material declarations
RoHS and REACH declarations produced from the current Bill of Materials, so the substances listed are the substances in the units shipped.
Files under your name
Declarations and test reports issued with your company as applicant or importer, which is what most retail and marketplace channels actually require.
Maintenance and change control
Files reviewed when a regulation, a component or a hardware revision changes, with updated documents issued to you instead of a silent change.
Three ways programmes usually start
Files we already hold
The standard set for the markets you named, delivered as PDF and stored on your Cloud Disk. No cost for the models you buy from us.
Files under your brand
Declarations and reports issued with your company as applicant or importer, prepared for private label and distribution programmes.
Gap-closing programme
Where a market you sell into is not covered by the existing file: testing managed at an accredited laboratory, then a complete file issued under your name.
Who this invitation is for
Importers and regional distributors
Businesses that carry the compliance obligation in their own market and need files issued to their company, not to a supplier abroad.
Private label brand owners
Brands selling into retail and marketplace channels where the declaration has to name the brand owner.
Retailers and marketplace sellers
Sellers who are asked for a declaration during listing or audit and need it the same day, in the right language.
Corporate and public-sector buyers
Procurement processes where the compliance file is part of the tender and has to match the delivered units exactly.
The resources behind it
These sit inside the same organisation — that is why the work can be quoted, built and shipped as one programme.
Certification library
A maintained library of test reports, component certifications and declarations covering the models in production, which is why most programmes start with the files already held.
Testing on the production build
Samples submitted from the production build rather than a prototype, so the report describes what you receive rather than what was intended.
Change control in-house
Component and firmware changes route through the same organisation that maintains the file, so a change cannot reach production without the documentation being assessed.
Cloud Disk delivery
Every file delivered as PDF and stored on your Cloud Disk with its version, so the latest declaration is the one your team sends.
Commercial terms
| Existing files | Supplied at no charge for models you buy from us |
|---|---|
| Files under your name | Quoted per model and market; reusable for reorders |
| New testing | Quoted separately at laboratory cost, with the standard and scope stated in advance |
| Lead time | 1–2 weeks for documentation; 4–8 weeks where new testing is required |
| Validity | Tied to the hardware revision; reissued when that revision changes |
| Confidentiality | NDA on request; your company details used only for your files |
| Maintenance | Regulatory and component changes tracked; updated files issued at no charge |
| Delivery | PDF delivery plus Cloud Disk storage for the current version |
Standard terms for a first programme. Framework agreements, payment terms and exclusivity are open to discussion from the second order onwards.
What buyers ask first
Can the declaration name our company?
Yes. For private label and distribution programmes the declaration of conformity is issued with your company as applicant or importer for the markets you name. The underlying test reports remain valid because the hardware is unchanged — only the applicant and the labelling change.
What if a market we sell into is not covered?
We run a gap analysis and tell you exactly what is missing: usually a test against a specific standard, sometimes only a labelling or documentation change. Testing is quoted at laboratory cost with the standard stated in advance, and managed by us rather than handed to you as a contact.
How long does a file stay valid?
As long as the hardware revision it was issued against is what you are buying, and as long as the standard has not been revised. We track both, and when either changes you receive the updated file rather than discovering the gap during an audit.
Does a firmware change affect certification?
Usually not, but it is assessed rather than assumed. Changes that touch EMC-relevant timing, radio behaviour or safety functions are reviewed against the certified build and re-tested where necessary — and the scope note for the firmware work tells you which category your change falls into.
Do you cover markets beyond the EU, UK and US?
Those are the ones covered by the standard file set. Other markets are handled case by case: some accept CE documentation with local labelling, others require their own approval. The gap analysis tells you which situation applies before you commit to the market.
Know exactly what your compliance file contains
Send the markets and models. You will receive the file list we hold, any gap, and the cost and lead time of closing it.