[Home](/)/[Resources](/resources)/FCC SDoC Deep Dive USFCCDeep dive # FCC SDoC Deep Dive: Responsible Party Obligations, Record Audits, and the Part 15 Gray Zone Most SDoC guidance stops at eligibility: which devices qualify, what the declaration must contain. The harder questions come later — when one product has both SDoC-eligible and Certification-required components, when a design change lands in the ambiguous space of "might affect emissions," or when the FCC actually asks for records with 72 hours on the clock. This deep dive covers those operational realities and compares SDoC directly to its closest EU equivalent, Module A self-declaration. Copy Link[Share on WhatsApp](https://wa.me/?text=https%3A%2F%2Fkrono-labs.com%2Fguides%2Ffcc-sdoc-supplier-declaration-deep-dive) At a glance Record retention 2 years post-manufacture Production deadline 72 hours on request FCC filing required None Mixed-mode devices Common — SDoC + Certification FAQs 6 On this page * [1\. Mixed-mode devices: when one product has both SDoC and Certification parts](#mixed-mode-devices) * [2\. Responsible party obligations beyond the basics](#responsible-party-deep) * [3\. What the 72-hour record request actually looks like](#72-hour-reality) * [4\. Class A versus Class B: a decision that changes your label and your buyer](#class-a-vs-b) * [5\. What design changes actually require a new SDoC](#design-change-triggers) * [6\. SDoC compared to CE self-declaration under Module A](#sdoc-vs-module-a) * [7\. The importer's role when the manufacturer is overseas](#importer-role) * [8\. Building a record-retention system that survives staff turnover](#record-retention-practice) ## 1\. Mixed-mode devices: when one product has both SDoC and Certification parts The [base guide on FCC SDoC](/guides/fcc-sdoc-supplier-declaration) draws a clean line: unintentional radiators can generally use SDoC, intentional radiators need Certification. In practice, the large majority of modern connected products are not purely one or the other — they combine an unintentional-radiator digital core with one or more intentional-radiator transmitters, and the two parts of the same physical product follow two different authorization paths at once. This is not a contradiction in the rules; it is the normal outcome of how Part 15 is structured. A laptop's motherboard, clock circuitry, and general digital switching are evaluated as an unintentional radiator under Subpart B, typically via SDoC. The Wi-Fi and Bluetooth radio inside that same laptop is an intentional radiator under Subpart C and needs Certification — frequently satisfied by using a radio module that the module manufacturer already certified separately, letting the laptop integrator inherit that existing grant rather than re-certifying the radio from scratch. The mistake to avoid is treating the device's primary function as the deciding factor. A smart thermostat is not exempt from Certification for its Zigbee radio just because its main job is temperature control rather than communication — every intentional radiator inside a product needs its own Certification-track evaluation, regardless of how central that radio is to what the product is marketed as doing. ## 2\. Responsible party obligations beyond the basics Four common mixed-mode scenarios illustrate how SDoC and Certification actually split across a single product, and where the common oversight tends to occur. Device Unintentional-radiator part Intentional-radiator part Note Laptop computer with integrated Wi-Fi/Bluetooth module SDoC — for the digital device baseband, clock circuits, and general digital emissions Certification — for the Wi-Fi/Bluetooth radio module (often pre-certified as a modular transmitter by the module vendor) The host device integrator typically relies on the radio module's existing FCC ID grant, while still needing an SDoC for the unintentional-radiator aspects of the host itself. Smart thermostat with Zigbee radio SDoC — for the digital control circuitry Certification — for the Zigbee transmitter A common oversight is treating the whole device as SDoC-eligible because the host's core function isn't radio-related — the transmitter still requires Certification regardless of the device's primary purpose. USB peripheral (external hard drive, USB hub) with no radio SDoC — standard unintentional radiator route Not applicable — no radio present The straightforward case: no intentional radiator means the entire device qualifies for SDoC treatment as a Subpart B unintentional radiator. Switching power supply / USB charger SDoC — switching supplies are common Subpart B unintentional radiators Not applicable, unless the supply incorporates wireless charging communication features A wireless-charging-capable power supply with any signaling radio component needs to be re-evaluated — the added radio function can move it toward Certification for that element. ## 3\. What the 72-hour record request actually looks like The base guide notes that SDoC records must be producible within 72 hours of an FCC request. The number sounds manageable in the abstract, but 72 hours is not enough time to locate a lab report that was never filed consistently, track down a designated responsible-party contact who has since left the company, or reconstruct which specific product revision a given set of test results actually covers. What actually needs to be retrievable on short notice is the full package: the accredited lab's test report, the specific product configuration and revision it corresponds to, the SDoC statement itself, and a clear internal record of who currently holds the responsible-party role for that product. A records system that only stores the final SDoC document, without the underlying test evidence and configuration mapping, technically satisfies the letter of "retain records" but fails the practical test of being able to produce them coherently within the 72-hour window. Treat the 72-hour requirement as a design constraint on your record-keeping system, not just a compliance fact to note — a system that would take a week to assemble a complete response is a system that has not actually been built to meet the requirement. ## 4\. Class A versus Class B: a decision that changes your label and your buyer SDoC devices are classified as either Class A (marketed for commercial, industrial, or business use, distributed through commercial channels) or Class B (marketed for use in a residential environment). This is not a minor labeling footnote — the two classes carry meaningfully different emission limits, with Class B held to a stricter standard because residential environments have less RF-noise tolerance and more sensitive nearby equipment than typical commercial or industrial settings. A product tested and labeled as Class A that later gets sold or marketed into residential channels — through a consumer-facing retailer, for instance — creates a genuine compliance gap, since the device was never actually verified against the tighter Class B limits its new market exposes it to. The classification decision needs to be made based on the product's actual intended distribution channel, and revisited if that channel changes materially after launch. ## 5\. What design changes actually require a new SDoC The base guide flags treating SDoC as perpetual as a common mistake, but the harder judgment call is deciding which specific changes actually trigger a new evaluation. Not every design revision does — the test is whether the change could plausibly affect the device's RF emissions characteristics, not whether the product changed at all. A change to the enclosure's cosmetic color, a user-interface software update unrelated to timing-critical operations, or a firmware change that only touches application-layer features are generally not emissions-relevant. A change to the clock crystal frequency, the switching power supply's topology, the PCB layout in a way that affects trace routing near high-speed signals, or firmware that alters processor clock speeds or switching frequencies are the kinds of changes that plausibly do affect emissions and warrant a fresh look — potentially new testing and a new SDoC. When genuinely uncertain whether a specific change crosses that line, the safer operational default is treating it as emissions-relevant and re-verifying, rather than assuming the original test evidence still applies — the cost of an unnecessary re-test is far smaller than the cost of an enforcement action premised on shipping a materially changed but never re-verified device under stale SDoC documentation. ## 6\. SDoC compared to CE self-declaration under Module A Companies certifying for both the US and EU markets often assume their self-declaration processes can be unified, since both SDoC and CE Module A share the basic shape of manufacturer-driven self-certification with no third-party filing. The details diverge enough that treating them as one process is a mistake. For the EU side of this comparison in full, see [the CE conformity assessment modules deep dive](/guides/ce-conformity-assessment-modules-deep-dive). Aspect FCC SDoC CE Module A Who performs the assessment Responsible party, based on testing at an accredited lab Manufacturer, based on internal testing against harmonised standards (or accredited lab testing, depending on product) Third-party filing None — no submission to the FCC None — no submission to an EU authority Public database entry No FCC ID, no database listing No equivalent public registry entry Record retention Test records retained by responsible party for two years after last manufacture/import; producible within 72 hours on request Technical file retained by manufacturer, typically for ten years after the last product is placed on the market, producible to market surveillance authorities on request Scope of eligible products Most Part 15 Subpart B unintentional radiators; excludes essentially all intentional radiators Most products under RED, EMC, LVD where harmonised standards fully apply; excludes higher-risk categories under other directives Underlying philosophy Narrow: self-certification reserved for lower-risk RF emission categories Broader: self-declaration is the default route across many directives when standards are available and followed The practical implication: a shared internal compliance checklist across US and EU self-certification is a reasonable starting point, but the specific eligibility rules, retention periods, and response-time expectations need to be tracked and satisfied separately for each market. ## 7\. The importer's role when the manufacturer is overseas For a foreign manufacturer without a US presence, a US-based importer or designated representative has to act as the responsible party — but that role is a distinct legal designation from being the customs importer of record, even though the same company frequently holds both. A customs relationship alone does not automatically confer FCC responsible-party status; the acceptance of that specific compliance role — including the obligation to retain and produce records — should be documented explicitly between the foreign manufacturer and the US entity. This distinction matters most when something goes wrong. If an enforcement inquiry arrives and the US entity assumed its customs role was the extent of its involvement, discovering mid-inquiry that it was also the undocumented FCC responsible party is a considerably worse position than having that role clearly assigned and prepared for in advance. ## 8\. Building a record-retention system that survives staff turnover The two-year retention period and 72-hour production requirement are frequently satisfied on paper by a policy document, while the actual records live in an individual employee's inbox or personal file structure. That arrangement works fine until the person who owns it leaves the company, at which point the records can become effectively unretrievable even though they technically still exist somewhere. A durable system ties each SDoC-authorized product to a centrally stored, clearly indexed record set — test report, product configuration and revision identifier, the SDoC statement, and the current responsible-party designation — that does not depend on any single person's continued employment or institutional memory to locate. Building this once, before it is needed, is considerably cheaper than reconstructing it under a 72-hour deadline after the fact. ## Frequently asked questions ### Can a single device use SDoC for part of it and Certification for another part? Yes, and this is the normal situation for most connected devices today. A device with an unintentional-radiator digital core and a separate intentional-radiator transmitter — like a laptop's motherboard plus its Wi-Fi module — typically needs SDoC treatment for the unintentional-radiator aspects and relies on Certification (often via a pre-certified modular transmitter) for the radio. The device as a whole is not simply 'an SDoC device' just because its primary function isn't wireless. ### What actually happens when the FCC requests records within 72 hours? The FCC or an authorized agent can request test records and supporting documentation for an SDoC-authorized device, and the responsible party must produce them within 72 hours. In practice this means the records need to be organized, current, and retrievable well before any request arrives — not assembled reactively once a request lands, since 72 hours does not leave meaningful time to track down a lab report that was never properly filed or a designee who has since left the company. ### Does a minor firmware update require a new SDoC? It depends on whether the change could affect the device's RF emissions characteristics. A firmware update that only changes user-interface behavior or unrelated software features generally does not require new testing or a new SDoC. A firmware change that alters clock timing, switching frequencies, or any parameter that was part of the original emissions testing does require re-evaluation, and potentially new testing and a new SDoC, because the original test evidence no longer represents the device as currently shipped. ### How does FCC SDoC compare to CE Module A self-declaration in the EU? Both are self-certification routes with no third-party filing, but they differ in scope and retention expectations. SDoC is narrowly available — mostly for Part 15 Subpart B unintentional radiators — and record retention runs two years past last manufacture with a 72-hour production requirement. Module A is broader in the range of product categories it covers across multiple EU directives, and EU technical file retention periods are typically longer, commonly cited around ten years after the last unit is placed on the market. A company selling into both the US and EU needs two separate self-certification programs, not one unified process, because the eligibility rules and retention obligations do not map onto each other. ### If a foreign manufacturer already has a US importer of record for customs purposes, does that importer automatically become the FCC responsible party? Not automatically — customs importer-of-record status and FCC responsible-party status are separate legal roles, even though the same US entity often ends up holding both. The FCC responsible party specifically has to accept the compliance obligations tied to record retention and production, and this should be documented explicitly rather than assumed to follow from a customs relationship alone. ### What happens if the responsible party goes out of business or the product line is discontinued? The record retention obligation is tied to the product having been manufactured or imported, not to the continued existence of the original responsible party's business in its original form. Where a company is acquired, restructured, or discontinues a product line, the compliance records should be preserved and the responsible-party designation updated or transferred as part of that transition — losing SDoC records in an acquisition or wind-down is a foreseeable risk that a compliance handover process should explicitly address. **Disclaimer:** This page is an educational resource only and does not constitute legal advice. FCC Part 15 requirements are product- and rule-part-specific, and enforcement practice can vary — verify current requirements for your exact device category and consult qualified counsel before issuing an SDoC or relying on a third party's authorization. 🇺🇸 US roadmap for your product Every standard, document, and test that applies — free, no account required. See your free roadmap[ Want an expert to take your product through 🇺🇸 US compliance for you? One consultant from Krono's compliance team takes your product from requirements to legal sale, with a fixed quote before any work starts. See compliance services](/services) Learn this properly In-depth course that teaches the full process, not just this one answer. [Start the course — $149](/courses/02-fcc-authorization-for-hardware-startups)[Prefer to read? Get the book — $24.99](/books/02-fcc-authorization-for-hardware-startups) Related guides * [FCC SDoC (Supplier's Declaration of Conformity)FCC SDoC explained: which devices qualify, required content, responsible party obligations, record-keeping, and when Certificat…](/guides/fcc-sdoc-supplier-declaration) * [ANSI Standards in the US MarketANSI (American National Standards Institute) accredits organizations to develop American National Standards.](/guides/ansi-standards-us-market) * [CE DoC Common Mistakes Deep DiveA deep dive into building a defensible EU Declaration of Conformity: multi-directive and multi-standard structure, version control across product revisions, translation obligations, common market surveillance findings, and DoC versus DoP distinctions.](/guides/ce-doc-common-mistakes-deep-dive) * [US Wearables Compliance Deep DiveA deeper look at US wearables compliance: how the medical-device classification decision actually gets made, FCC authorization routes by device type, CPSC certification differences for adult vs. children's products, battery safety.](/guides/us-wearables-compliance-deep-dive)