Procurement teams sourcing optical transceivers for AI data center fabrics regularly see the word "compliant" on a supplier's spec sheet or invoice. What that word means in practice depends on which FCC equipment-authorization procedure a given SKU actually went through — and the two most common paths, Supplier's Declaration of Conformity (SDoC) and Certification, are not interchangeable. Confusing them creates two different risks: over-asking a supplier for paperwork that doesn't exist for a self-declared device, or under-verifying a claim that should be backed by a public FCC grant. With optical-transceiver import rules also under active FCC review, buyers have good reason to understand the underlying authorization framework now rather than after a deployment is already committed.
This explainer separates the two procedures, shows how to tell which one applies to a given module, and gives a short checklist for what to request from a supplier before an order ships.
Two authorization paths, one word: "compliant"
The FCC does not issue a single blanket "FCC compliant" status. Under its equipment-authorization rules, most electronic devices sold in the US reach the market through one of two procedures:
- Supplier's Declaration of Conformity (SDoC) — a self-declaration process for lower-risk devices, primarily unintentional radiators (equipment that emits RF energy only as a byproduct of digital circuitry, not by design).
- Certification — a third-party review process for higher-risk categories, run through an FCC-recognized Telecommunication Certification Body (TCB), ending in a public FCC grant and FCC ID.
Both are legitimate, FCC-recognized paths to market. Neither is "more compliant" than the other in the abstract — the procedure is determined by the device category and its RF risk profile, not by supplier preference. The practical difference for a buyer is what evidence exists to verify the claim, and who is responsible for keeping it on file.
What SDoC actually requires
Under SDoC, the responsible party — typically the manufacturer or importer — has the device tested at an accredited lab against the applicable Part 15 limits, then self-declares conformity based on that test report. No application is filed with the FCC or a TCB, no FCC ID is issued, and the device does not appear in any FCC database.
That does not mean the process is undocumented. The responsible party is required to:
- Retain the test report and supporting technical documentation for as long as the product is marketed, plus a defined retention period after.
- Ensure the device carries the required compliance labeling and, where applicable, a statement identifying the responsible party.
- Produce that documentation on request if the FCC opens an inquiry.
Most pluggable optical modules — 400G, 800G, and 1.6T transceivers included — are digital devices whose RF emissions are an unintentional byproduct of high-speed switching circuitry, not a designed radio function. That places the large majority of the industry's optical modules under Part 15 Subpart B as unintentional radiators, which is where SDoC applies. This is the normal, expected authorization path for most transceiver SKUs — its absence from an FCC database is not itself a red flag.
When Certification applies instead
Certification is reserved for equipment the FCC treats as higher-risk for interference — most commonly intentional radiators (devices designed to transmit RF, such as wireless radios) and a smaller set of other regulated categories. The process runs through a TCB, which reviews test data and application materials before the FCC issues a formal grant of equipment authorization tied to a specific FCC ID. Because that grant is filed with the Commission, it is independently verifiable: any buyer can look up an FCC ID in the FCC's public equipment-authorization database and confirm the grant, the grantee, and the authorized configuration.
For a supplier claim to carry an FCC ID, the underlying device has to actually be in a certified category — an optical transceiver module by itself, with no wireless function, would not typically be expected to carry one. A certification claim attached to a plain optical module is worth a direct question, not an assumption.
SDoC vs. Certification at a glance
| SDoC | Certification | |
|---|---|---|
| Who reviews it | Responsible party self-declares | FCC-recognized TCB, then FCC grant |
| Public record | None — no FCC database listing | Public grant, searchable by FCC ID |
| Evidence a buyer can request | Test report + responsible-party statement | FCC ID + grant lookup |
| Typical device category | Unintentional radiators (most digital/networking gear, including most optical transceivers) | Intentional radiators and other higher-risk categories |
| Where documentation lives | Held by responsible party, produced on request | Filed with the FCC / TCB, publicly searchable |
What to request from a transceiver supplier
Because SDoC devices are not centrally listed, the burden of verification shifts to direct documentation requests rather than a database lookup. A practical pre-order checklist:
- Identify the authorization procedure per SKU. Ask the supplier directly whether a given transceiver model relies on SDoC or Certification — do not assume based on the product category alone.
- For SDoC devices, request the test report. Confirm it references the specific model or a documented family/variance covering it, from an accredited test lab.
- For Certification claims, verify the FCC ID. Look the ID up directly in the FCC's public database rather than accepting a certificate image at face value.
- Check labeling consistency. The compliance label and any responsible-party statement on the device or packaging should match the authorization path claimed in the documentation.
- Confirm document retention. Ask whether the supplier can reproduce this documentation on request for the life of the deployment, not just at time of sale.
This is a subset of the broader documentation set worth collecting per SKU — RoHS declarations, laser safety classification, and test reports among them — which we cover in more detail in our compliance documentation checklist for transceiver suppliers.
Why this matters more with rulemaking in progress
The FCC's equipment-authorization framework — the same Certification and SDoC procedures described here — is also the mechanism referenced in the FCC's pending rulemaking on new-model transceiver imports, which we analyzed in our earlier look at the proposed rules. That rulemaking is still in draft form and separate from the day-to-day authorization question covered here, but it is a reminder that equipment-authorization status is not paperwork buyers can treat as static. A model's authorization path and documentation should be revisited whenever a new SKU is qualified, not only at initial vendor onboarding.
Next step
Authorization procedure is one line item in a larger documentation set that infrastructure buyers should standardize across every optical transceiver SKU in a deployment. PhoScale maintains compliance documentation, including test reports and authorization details, available on request for its 400G, 800G, and 1.6T product lines, backed by tier-one manufacturing resources across Asia and US-warehouse stocking described on our supply assurance page. To request documentation for a specific SKU or start a sourcing conversation, use our RFQ form.
This article is general information about FCC equipment-authorization procedures, not legal advice. Authorization requirements can vary by device configuration and are subject to change as FCC rules are updated; confirm specifics with qualified compliance counsel or an accredited test lab before relying on them for a deployment decision.