Managing Grantee Authorization Letters and Change in Identification Filings

Title

White-label hardware integration relies on transferring regulatory authority over a certified radio module without throwing out its original test data. Federal Communications Commission rules cover this process under Title 47 of the Code of Federal Regulations, specifically Section 2.933. A Change in Identification filing allows an applicant ~ the new grantee ~ to set up a new FCC Identifier for an existing equipment design without re-running radiated and conducted RF performance tests.

The entire transfer hinges on the Grantee Authorization Letter. Signed by an authorized representative of the original grantee, this document gives the Federal Communications Commission and the Telecommunication Certification Body explicit permission to reference the original compliance test reports, circuit diagrams, internal photos, and technical operational descriptions already on file for the original FCC ID.

Who controls the regulatory file determines how a host integrator works with a module manufacturer. When a host vendor buys an off-the-shelf Wi-Fi 6E or Bluetooth Low Energy module, they have two options. They can integrate the module under the original grantee’s FCC ID ~ using the original grantee code and model number on the external label ~ as long as they follow the Grantee’s Modular Integration Instructions under KDB 996369.

Or, they can submit a Section 2.933 Change in Identification filing to secure their own Grantee Code and Product Code. Having a dedicated FCC ID frees the host vendor from marketing dependencies, protects supply chain relationships, and lets the integrator handle subsequent Class II Permissive Changes on their own schedule if authorized.

1. Grantee Code Registration requires the applicant to register with the Commission’s Commission Registration System to get a unique three-character or five-character alphanumeric Grantee Code before starting the filing.
2. Grantee Authorization Execution requires a formal letter on the original grantee’s letterhead, citing the original FCC ID, the grant’s original issuance date, and explicit permission for the new applicant to apply for a Change in ID under Section 2.933.
3. Filing Construction involves submitting an application through a Telecommunication Certification Body with new external photos, label artwork showing the new FCC ID location, and a formal declaration that the equipment design, circuitry, and RF performance are identical to the certified device.
4. Grant Issuance produces a separate Grant of Equipment Authorization listing the new grantee name, new FCC ID, and original test report references, creating independent regulatory standing.

The Grantee Authorization Letter operates as a limited regulatory power of attorney for the scope outlined in its text. Unless it is signed by the registered Corporate Interface Contact listed in the FCC database, a Telecommunication Certification Body cannot legally reference the original test dossier. The letter requires specific wording: it must state the original FCC ID, give the exact date the original grant was issued, confirm that the equipment in the new application is electrically and structurally identical to the original, and explicitly authorize the Commission to access confidential exhibits from the original filing for the new applicant.

The Grantee Authorization Letter acts as a selective regulatory key, transferring reliance on underlying compliance reports while leaving legal liability for manufacturing compliance with the new grantee.

There are strict limits to what a Change in Identification accomplishes. While the filing issues a new Grant of Equipment Authorization with a new FCC ID, it does not change the physical or technical characteristics of the device. If the original module received full modular approval, the new grantee gets those exact grant conditions.

But if the original grant was a limited modular approval ~ tied to specific host designs or requiring external shielding ~ the new grantee is bound by those same restrictions. The new ID gives no right to modify transmitter circuitry, alter PCB trace layouts, or tweak firmware settings that control spectral compliance.

Friction often occurs when a module vendor refuses to sign a Grantee Authorization Letter or tries to tie their signature to exclusive purchase terms. If the relationship sours, a host integrator stuck with a custom enclosure built for that module cannot force a Change in ID through without the original grantee’s consent. That leaves two costly paths: keep printing the original vendor’s FCC ID on the product label under a standard OEM arrangement, or send the hardware to an accredited test lab for a full, ground-up certification under 47 CFR Section 2.911.

That second option means running a complete suite of radiated emissions, occupied bandwidth, phase noise, and peak power tests, plus submitting brand-new schematics and block diagrams.

Procurement contracts for radio modules should explicitly obligate the supplier to provide these letters, specifying that “The Grantee of Record shall deliver an executed, unconditional Grantee Authorization Letter matching FCC Section 2.933 requirements within ten business days of written notice from the Buyer.”

Foil

Dropping an approved module into a host enclosure changes the electromagnetic environment, which can undermine the assumptions behind the original grant. A successful Change in ID transfers the FCC ID on paper, but the hardware still has to comply with strict EMC limits. The stamped metal shield ~ often thin nickel-silver alloy or stainless steel over the RF front end ~ is what keeps internal high-frequency synthesizers from coupling with host circuitry.

Removing, altering, or replacing that foil shield during rebranding immediately voids the test reports referenced in the Section 2.933 filing.

When rebranding a module, product teams are often tempted to tweak the housing or mount an uncased board directly onto a main PCB. Under KDB 996369 D01, changing the RF shielding, onboard trace antennas, or power amplifier decoupling pushes the project out of simple administrative updates and into mandatory re-evaluation. Adding metallic paint, internal conductive foil, or thermal pads touching the module shield alters near-field coupling significantly.

In test chambers, a conductive ground path near an inverted-F trace antenna often pulls the resonant frequency off by several hundred megahertz, pushing harmonic emissions right past 47 CFR Section 15.247 or Section 15.407 limits.

What Physical Host Modifications Render a Change in Identification Filing Invalid?

Anything that alters the physical layout of the RF path, expands host ground plane dimensions beyond original test parameters, or swaps out external antennas invalidates the administrative Change in ID process. Certification bodies demand a formal statement certifying that the physical design hasn’t changed at all. Swapping a single resistor in the matching network or changing PCB substrate from FR4 to high-frequency PTFE means the device is no longer electrically identical.

At that point, a Section 2.933 filing isn’t enough; you are looking at a Class II Permissive Change under 47 CFR Section 2.1043 or an entirely new grant, depending on how extensive the changes are.

Host manufacturers should run spot-check pre-scans in a semi-anechoic chamber before committing to a Change in ID strategy. A basic pre-scan checks radiated spurious emissions across primary harmonic bands while running the module on its worst-case duty cycle firmware build. The table below outlines common host integration variables, how they affect RF compliance, and the regulatory path required if deviations occur.

Firmware configuration is just as critical as hardware in maintaining filing validity. The original grant was issued against specific software settings locked during testing. If a host vendor files a Change in ID while loading custom firmware that boosts transmitter power, enables extra channels, or alters duty cycles, the original test report no longer applies.

Under KDB 594280, software controls must lock out end-users or host software from driving the radio past certified limits. Changing drive levels beyond those bounds violates FCC regulations, even with a fresh Grantee Code and Product ID in hand.

During an integration project involving an industrial gateway enclosure lined with aluminum shielding foil, preliminary chamber scans revealed a 4.2 dB spike in second-harmonic spurious emissions at 4.88 GHz. Adjusting board positioning added an unplanned two-week delay for re-testing before the filing paperwork could be finalized.

Evidence

Building a compliance dossier for a Change in Identification filing comes down to documentation rather than laboratory work. The Telecommunication Certification Body won’t re-test RF parameters, but it will scrutinize the chain of custody between the original grant and the new filing. The cornerstone is the Grantee Authorization Letter.

It must be printed on the original grantee’s corporate letterhead and signed by the official corporate contact registered in the FCC database. If the signature doesn’t match the designated contact on the FCC Equipment Authorization System portal, the application gets rejected immediately.

Along with the authorization letter, the applicant must supply exhibits that reflect standard grant requirements while documenting the transfer details. This includes formal cover letters, external photos of the host or module enclosure, label artwork displaying the new FCC ID, and a diagram showing where the label sits on the product. The applicant must also upload a signed Declaration of Equivalence, explicitly confirming that the technical specs, internal circuitry, layout, and operational parameters match the original hardware without modification.

• Audit of Grantee Status confirms the original grantee code is active in the FCC database, with no open enforcement actions or unpaid fees.
• Verification of Contact Authority verifies that the signature on the Grantee Authorization Letter matches the official contact listed on the FCC portal.
• Cross-Reference Validation checks that the original FCC ID and grant date in the letter match public FCC database entries down to letter casing and hyphens.
• Label Compliance Review ensures the new label layout meets 47 CFR Section 15.19 requirements, including standard two-part compliance text or e-label access under the E-LABEL Act.

Leveraging an original grant for international distribution brings extra jurisdictional rules into play. While the US uses FCC Section 2.933, Innovation, Science and Economic Development Canada (ISED) handles equivalent transfers under RSP-100 Section 11.5, known as a Multiple Listing or Transfer of Certification. Intent is similar, but ISED requires a Canadian-specific authorization letter alongside a signed Canadian Representative Agreement.

The named agent must reside in Canada and take formal responsibility as regulatory liaison. Mismatches between Canadian Multiple Listings and US Change in ID filings routinely tie up shipments at the border.

The documentary integrity of a Change in Identification filing depends entirely on verbatim alignment between the original FCC ID records and the newly submitted declarations of identity.

Markets in Asia and South America take very different approaches to transfers based on foreign test data. In Japan, under Radio Law Article 38-24 administered by the Ministry of Internal Affairs and Communications (MIC), changing a Type Certification requires an application through a Registered Certification Body. If the construction design certification stays identical, you can file an administrative update, but local documentation requirements are rigorous.

In South Korea, the National Radio Research Agency (RRA) permits administrative changes under the Radio Waves Act, provided the certificate holder maintains a local presence or appoints a registered Korean representative. The table below compares these mechanisms across key jurisdictions.

A frequent bottleneck occurs when integrators assume standard marketing authorization emails allow a certification body to pull confidential schematics directly from the Commission’s public access portal. Certification bodies cannot access confidential exhibits on informal authorization. The TCB requires an official, signed Grantee Authorization Letter uploaded to the portal, specifically referencing the original filing’s confidential exhibit files to grant cross-referencing rights under 47 CFR Section 0.459.

To protect access down the road, contracts should stipulate that “The original grantee shall maintain all underlying compliance test data and confidential technical exhibits for a minimum of five years following the termination of production and shall grant regulatory access permissions to designated certification bodies upon written request.”

Transit

Market entry timelines swing wildly depending on how target regions treat foreign test data. A US Change in Identification filing processed through a Telecommunication Certification Body is quick, often wrapping up in five to ten business days. But taking that rebranded module into international markets means working through local acceptance rules, testing exemptions, and mutual recognition agreements.

Integrators who assume global approvals move at US administrative speed end up with shipments sitting stranded in customs.

The European Union handles market access under the Radio Equipment Directive (RED 2014/53/EU), which has no administrative Change in ID mechanism like FCC Section 2.933. European compliance hinges on the manufacturer’s Declaration of Conformity. Under RED Article 10, the company putting the host product on the EU market assumes direct legal responsibility.

You can reference the module maker’s ETSI EN 300 328 or ETSI EN 301 489 test reports inside your technical documentation file, but you must issue an EU Declaration of Conformity under your own company name, address, and CE mark. There is no central agency filing; legal liability simply lands on the importer or host manufacturer.

China’s State Radio Regulatory Commission (SRRC) requires local type approval for radio transmitters. The SRRC does not accept administrative transfers based on foreign authorization letters. Rebranding an imported radio module means submitting physical hardware samples to an accredited Chinese lab for testing against national standards ~ unless the module vendor holds an SRRC certificate through their own Chinese entity and agrees to add the host model to their filing.

Going through full local lab testing adds eight to twelve weeks to shipment schedules.

Managing global inventory gets tricky when a single hardware build targets multiple countries. Every target market demands its own label markings, but compact industrial sensors and IoT gateways quickly run out of physical surface area. Electronic labeling under FCC KDB 784748 D02 and ISED Notice 2014-DRS09 helps by shifting regulatory IDs onto an integrated display screen.

But e-labeling requires users to access compliance screens without special passcodes or external hardware ~ a condition headless or displayless IoT devices cannot meet.

What documentation satisfies international regulators during an equivalent Multiple Listing?

International regulators look for an unbroken paper trail when evaluating rebranded radio equipment. Under Mutual Recognition Agreements ~ like those between the US and Japan or the US and the EU ~ certification bodies accept test reports from accredited foreign labs. But you still need to provide the complete documentation set: original lab reports, the Grantee Authorization Letter, a formal statement of identity from the module vendor, and localized user manuals with regional compliance statements.

A discrepancy anywhere in model names, factory addresses, or operating frequencies will prompt destination authorities to hold shipments at customs.

Complications also crop up when a module manufacturer updates underlying silicon or moves production facilities while integrators rely on an earlier Change in Identification. Transferring manufacturing to a new plant overseas can require administrative updates or factory audits depending on regional rules. If the original grantee doesn’t inform downstream integrators who hold Section 2.933 grants, those integrators end up selling hardware whose regulatory records no longer match actual factory origins, leaving shipments exposed during border audits.

Default

Relying on a third-party Grantee Authorization Letter creates ongoing operational exposure across a product’s lifecycle. A Section 2.933 grant gives you a new FCC ID, but its validity remains tied to the underlying original grant. If the FCC suspends the original vendor’s Grantee Code over unpaid fees under the RAYBAUM’S Act, or revokes the grant following market surveillance, your downstream filing is left compromised.

You own an independent FCC ID, but the test data backing it sits on an invalidated grant.

Problems multiply if the module vendor goes out of business, files for bankruptcy, or gets acquired by a competitor who kills off the product line. If a certification body selects the rebranded module for routine audit testing under 47 CFR Section 2.945, you have thirty days to submit sample units and technical records. If the original supplier is gone and docs are missing, or if they refuse to help pull production samples, the FCC can revoke your authorization on the spot ~ making further sales or distribution illegal in the US.

• Grant Status Surveillance setup quarterly automated checks on the FCC database to verify the original grantee code stays active and clear of enforcement actions.
• Escrow of Technical Exhibits insert contract clauses requiring the vendor to deposit schematics, BOMs, block diagrams, and operational descriptions into a third-party escrow account.
• Permissive Change Authorization secure contractual authorization allowing the host vendor to execute Class II Permissive Changes if the module vendor becomes unresponsive.
• Surveillance Sample Allocation keep five factory-sealed production units set aside specifically to respond to FCC audit requests.

Ongoing product maintenance introduces similar hurdles. Component shortages frequently force board changes, like swapping an RF switch or updating a power management IC. For an original grant holder, these are handled via Class I or Class II Permissive Changes under 47 CFR Section 2.1043.

But a Change in ID grantee doesn’t own the underlying test data and cannot independently file a Class II Permissive Change on the original grant. You can only file a permissive change on your rebranded FCC ID if you have written authorization from the original grantee or if they file a concurrent change on the primary grant.

A practical rule of thumb in hardware risk management: any radio integration generating over one million dollars in annual revenue justifies securing an original equipment authorization rather than relying on a third-party Change in ID filing.

Indemnification terms in procurement agreements need to protect the host against supplier regulatory failures. A solid agreement shifts financial risk back to the module supplier if non-compliance invalidates the grant, using language like: “The Seller warrants that the certified radio equipment complies with all applicable regulatory requirements and agrees to indemnify, defend, and hold harmless the Buyer against any commercial losses, recall costs, or administrative fines arising from regulatory enforcement actions directed at the original Grant of Equipment Authorization.”

If an original grantee finds that a customer filed an unauthorized Change in ID using an invalid or forged letter, they can notify the FCC and the certification body. The TCB will start revocation proceedings under 47 CFR Section 2.939 immediately. Market access ends overnight, leaving inventory stranded in warehouses while contract and IP disputes play out in court.

Supplier policies often prohibit signing customized Grantee Authorization Letters, forcing integrators to accept standardized broad-scope agreements and handle any certification body objections on their own balance sheet.

Schedule

Budgeting for regulatory approval means weighing direct administrative expenses against schedule lead times. Executing a Change in Identification filing under 47 CFR Section 2.933 saves substantial capital compared to an original authorization campaign. A full original filing for a dual-band Wi-Fi and Bluetooth radio runs between twenty-five and forty-five thousand dollars in lab chamber fees alone, plus four to six weeks of testing and review.

A Change in ID filing reuses existing test data, skipping chamber testing entirely and cutting costs down to administrative TCB review fees and filing tariffs.

The true cost of a Change in ID strategy goes beyond the initial TCB invoice. You still have to account for Grantee Code registration fees, label redesign, technical document audits, and international filings. Expanding into Canada under RSP-100 adds fees for local representative representation and ISED listing services.

The table below compares financial outlays and lead times between original module certifications and administrative Change in ID filings across major jurisdictions.

Schedules need to reflect real administrative dependencies. The critical path starts with obtaining the signed Grantee Authorization Letter from the module vendor. Getting legal terms approved, verifying corporate contact entries, and receiving the signed letter routinely takes anywhere from two days to four weeks depending on vendor responsiveness.

Once you have the letter and an active Grantee Code, the TCB review moves quickly ~ application review, database indexing, and grant issuance usually wrap up in five to ten business days.

Timing can run into bottlenecks around regulatory transitions or holiday periods. Certification bodies see heavy application spikes right before new standards take effect ~ such as updates to ETSI harmonized standards or FCC spectrum allocation shifts. During peak periods, TCB turnaround times can swell from five days to three weeks.

Building no buffer into regulatory timelines risks missing launch dates or getting caught in customs on early shipments.

All in, a combined US Change in ID and Canadian Multiple Listing package runs between two thousand five hundred and five thousand dollars in administrative costs ~ a fraction of what full chamber testing demands. With clear tracking, solid contracts with module suppliers, and prompt administrative filings, product teams can turn regulatory compliance from a launch bottleneck into a routine supply chain task.