Certification guidance almost always stops at approval, as though the certificate were the destination. But the expensive failures happen later: a certificate lapses while stock is already in the channel, a regulator pulls an approved product off a shelf and tests it again, or a supplier substitutes a component and quietly invalidates approvals in six markets at once.
Post-approval obligations fall into four types, and every market you’re in imposes some combination of them. Expiry: certificates range from permanent to annual, and some markets issue a provisional certificate that must be converted before it lapses. Recurring documentation: several markets require a certificate or permit with every consignment, which is a logistics task rather than a compliance one. Surveillance: some regulators can select approved products at random and re-test a fresh sample, meaning what ships today must still match what was tested. Change triggers: a component substitution, layout revision or added radio module can require reassessment — and if you’re certified in several markets, in all of them simultaneously. The organising principle is that each obligation needs a named owner and a calendar entry, because the failure mode isn’t difficulty, it’s that nobody was watching. Certification maintenance is an operations function, not a project phase.
Build the calendar once, per product, per market. The four obligation types below are the columns; your markets are the rows. Most of the work is a single afternoon of populating dates and assigning names.
The thing that makes it work isn’t completeness — it’s a named owner per row. “Compliance handles it” is how certificates lapse.
§01The failure mode changes after approval
Getting certified is hard in a way that’s visible: there’s a project, a budget, a deadline, and someone is clearly responsible. Nobody forgets to do it, because you can’t ship without it.
Staying certified is hard in a way that’s invisible. There’s no launch date, no obvious owner, and no immediate consequence to letting something slide. The obligations are individually trivial — request a document, diarise a date, notify a body — and collectively they’re what stands between you and a border hold on a market you spent a year entering.
§02The four obligation types
FIG.01 — Four obligation types. No market imposes all four; most impose two or three. The value of the framework isn’t in the categories themselves but in forcing the question per market: which of these apply here, and who owns each one by name?
Validity varies enormously. Some approvals last the life of the product unless it changes. Others expire annually. Some markets issue a provisional certificate that must be converted to a permanent one within a defined window. And renewal is sometimes a form, sometimes a reassessment involving retesting — the difference matters for lead time.
WHERE IT BITES: Mexico’s provisional-to-definitive conversion · Saudi Arabia’s annual product certificate · Brazil’s category-dependent renewal with a grace period · Australia’s annual supplier registration renewalSeveral markets require a document per consignment rather than per product. This is the obligation most likely to fall between departments, because it isn’t a compliance task — it’s a shipping task that happens to be a compliance requirement. Whoever prepares your freight documentation needs to own it explicitly.
WHERE IT BITES: Saudi Arabia’s shipment certificate for every consignment · the UAE’s customs release permit matched to import purpose · Mexico’s certificate copy accompanying each shipment · India’s approval produced at customsA minority of markets reserve the right to select approved products at random and put a fresh sample back through testing. This is qualitatively different from a document audit: it tests the product as currently manufactured, not the paperwork. The implication is that production consistency becomes a regulatory matter, not just a quality one.
WHERE IT BITES: Mexico’s random surveillance including re-test · Korea’s follow-up factory inspections for the strictest safety tier · Brazil’s periodic retesting by categoryThe one that scales badly. A component substitution, board revision, antenna reposition, added radio module or housing change can require reassessment — and the more markets you’re certified in, the more places that reassessment lands. A single unannounced change by your supplier can put approvals in every market you sell in into question simultaneously.
WHERE IT BITES: everywhere. This is the only obligation type with no exceptions across any market covered in this series.§03Which obligations apply where
A mapping across the markets covered in this series. Use it to populate your own calendar, then verify each cell against your actual certificates rather than against this table.
→ scroll table horizontally
| Market | Expiry pattern | Per-shipment | Surveillance |
|---|---|---|---|
| UNITED STATES | Authorization persists; changes to the configuration are the trigger | No | Market surveillance possible |
| EUROPEAN UNION | Declaration stands while the technical file remains accurate | No | Market surveillance by authorities |
| GREAT BRITAIN | As EU, with a separate declaration | No | Market surveillance |
| AUSTRALIA | Annual supplier registration renewal; records retained for years | No | Compliance checks on evidence |
| CANADA | Certification persists; REL entry maintained | No | Possible |
| JAPAN | Approvals effectively persist; records retained | No | Possible |
| SOUTH KOREA | Permanent unless the design changes | No | Factory follow-up for the strictest safety tier |
| SAUDI ARABIA | Annual product certificate | Yes — shipment certificate each time | — |
| UAE | Around three years, renewable | Yes — customs release permit | — |
| BRAZIL | Category-dependent renewal; grace period then full re-certification | Homologation number active at customs | Periodic retesting by category |
| INDIA | Radio approval for the life of the product | Approval produced at customs | — |
| MEXICO | Provisional one year → definitive permanent | Yes — certificate copy per shipment | Random re-test of fresh samples |
| SOUTHEAST ASIA | Varies by market and scheme | Varies | Varies |
TABLE.01 — Obligation mapping. Simplified deliberately: exact patterns depend on scheme, product category and current regulation, and several cells would need footnotes to be complete. Treat this as a prompt for the right questions per market, not as an authority — and confirm each against your own certificates and qualified advice.
§04The calendar
Four recurring reviews. The frequencies matter less than the fact that each has a fixed slot and a named owner.
- Confirm every per-shipment document is in the pack for each destination — shipment certificate, customs permit, certificate copy, whichever applies.
- Verify the underlying approval is still valid on the date of shipment, not the date it was last checked.
- Confirm the goods match the certified configuration — same model number, same declared components.
- Review every certificate expiring within the next nine months — long enough ahead that reassessment-based renewals can be started.
- Check any provisional certificates approaching conversion deadlines.
- Confirm local representative and registration renewals — these lapse quietly and block filings.
- Verify each renewal has a named owner who has acknowledged it in writing.
- Assess whether the change affects RF behaviour, electrical safety or materials — the three things approvals rest on.
- List every market where the affected approval is held, because the impact is simultaneous.
- Determine per market whether reassessment is required, and whether existing stock is affected.
- Update the technical file so documents keep describing the product actually shipping.
- Re-run the document verification checks across every certificate you hold — see the 24-check list.
- Confirm the certified configuration still matches production, including any changes that were approved but never assessed for regulatory impact.
- Review which markets still justify their maintenance cost, since recurring local-representative fees accumulate quietly.
- Check for regulatory changes in each market — standards get revised, and grandfathering isn’t universal.
- Confirm surveillance readiness: if a regulator pulled a unit today, would it still pass?
§05Change control is the whole game
Of the four obligation types, three are calendar problems — solvable with a spreadsheet and a name. The fourth isn’t, because you don’t control when it happens. A supplier substitutes a component for cost or availability reasons, doesn’t consider it material, and doesn’t mention it.
In a market with documentation-only oversight, that might pass unnoticed for years. In a market with surveillance re-testing, it surfaces as a failed test on product already sold. And because you’re certified in several markets on the same technical basis, the exposure isn’t one market — it’s all of them at once.
Which is why written change control belongs in the purchase order, not in a relationship. The commitment is specific: no component, board layout, antenna or firmware change affecting RF behaviour without prior written notice. Suppliers who have been through multi-market certification understand why. Suppliers who resist are telling you something about how they’ve operated before.
This connects the maintenance question back to supplier selection, which is where it actually gets decided. The verification checklist treats change control as a disqualifying gate rather than a scored item for exactly this reason — a factory without it can cost you every market simultaneously, years after you chose them.
§06Who owns what
The assignment that makes the calendar function. Names, not departments.
§07Red flags
- No single document listing every certificate you hold with its market, expiry and owner. If it doesn’t exist, something has already slipped.
- Expiry dates in one person’s calendar rather than a shared system. People change roles.
- Per-shipment documents treated as a compliance task. They’re a shipping task, and they’ll be missed until they’re written into the shipping checklist.
- Renewal assumed to be a form. Where it’s a reassessment, starting late means a gap in approval.
- No written change control with your factory. The one obligation you can’t manage by calendar.
- Change notices going only to purchasing. A change accepted commercially before regulatory review is a change already in production.
- Local representative renewals unmonitored. A lapsed registration can block filings and, in some markets, undermine your compliance position entirely.
- “We got certified” spoken in the past tense about a market with annual obligations.
§08Frequently asked questions
What happens after a product is certified?
Four types of ongoing obligation, in some combination depending on the market. Expiry: certificates range from permanent to annual, and some markets issue a provisional certificate requiring conversion. Recurring documentation: several markets require a certificate or permit with every consignment. Surveillance: some regulators can select approved products at random and re-test a fresh sample. Change triggers: component substitutions or design revisions can require reassessment across every market simultaneously. Each needs a named owner and a calendar entry, because the failure mode is inattention rather than difficulty.
Do certifications expire?
It varies enormously by market. Some approvals persist for the life of the product unless the design changes — Korea’s radio certification and India’s WPC approval work this way. Others expire annually, such as Saudi Arabia’s product certificate and Australia’s supplier registration. Mexico issues a provisional certificate valid for one year before a definitive permanent one can be sought. Brazil’s renewal frequency depends on product category, with a grace period after which full re-certification becomes necessary. Read each certificate’s expiry rather than assuming a pattern.
Can a regulator re-test a product that’s already approved?
In some markets, yes. Mexico can select certified products at random for surveillance that includes re-testing a fresh sample. Korea’s strictest electrical safety tier includes follow-up factory inspections after initial certification. Brazil requires periodic retesting depending on product category. This is qualitatively different from a documentation audit because it tests the product as currently manufactured — which means production consistency becomes a regulatory matter, and a component substitution can surface as a failed test on product already in the channel.
What product changes require recertification?
Broadly, changes affecting the three things approvals rest on: RF behaviour, electrical safety, or restricted materials. In practice that includes component substitutions on the radio path, board layout revisions, antenna repositioning, adding a radio module, and sometimes housing changes that affect RF performance. Firmware updates that don’t affect RF parameters typically don’t trigger reassessment, though this varies. The consequential point is scope: if you’re certified in several markets on the same technical basis, one change puts approvals in all of them into question at once.
Who should own certification renewals?
One named person for the whole portfolio, with dates in a shared system rather than an individual’s calendar — portfolio-level ownership catches what per-market ownership drops. Per-shipment documents belong to whoever prepares freight documentation, written into their checklist rather than treated as a compliance task. Change notices belong to whoever manages the supplier relationship, with a standing instruction to route every notice to regulatory review before it’s accepted commercially. The common failure is assigning obligations to departments rather than people.
What happens if a certificate lapses?
Consequences vary but are rarely trivial, since in several markets the certificate is also part of your customs documentation — a lapse can mean shipments held at the border with no quick remedy. Some schemes provide a grace period during which products remain marketable, but letting that run out can force full re-certification including any in-country testing, which is the expensive outcome. The practical protection is starting renewal well ahead of expiry, particularly where renewal involves reassessment rather than a form.
How does True Bond support certification maintenance?
Written change control is the core of it: a commitment that no component, board layout, antenna or firmware change affecting RF behaviour happens without prior written notice, so approvals built across several markets aren’t invalidated silently. Beyond that, the technical file is kept current so documentation continues to describe the product actually shipping, updated test data is provided where a change requires reassessment, and expiry and renewal obligations per market are set out during project scoping rather than left to be discovered. Renewals themselves and local representative arrangements sit with the certificate holders in each market.
Change control is what protects everything else
Three of the four obligations are calendar problems you can solve. The fourth depends on your supplier telling you before they change something. Ours is written into the purchase order — because approvals across a dozen markets are too expensive to lose to a component swap nobody mentioned.
Talk about change control → info@truebondtech.com · WhatsApp +86 189 2846 4489 · View productsThe certification toolkit