A China electronics supplier may send a test report, product specification, circuit description, factory address, label draft, RF test summary, product photograph, or email when a buyer asks for FCC-related information. Those files may help a buyer trace what the supplier says about an item. They do not, by themselves, constitute a Supplier’s Declaration of Conformity, a responsible-party decision, an equipment authorization, or an approval to market or release a shipment.
China supplier FCC SDoC evidence is buyer-side evidence that links a buyer item/version, product description, supplier legal entity/site, stated RF functions, supplier-provided test information, sample/product association, source record/date, U.S. responsible-party context, label/contact information supplied, shipment association, and buyer owner. It does not establish that equipment is subject to SDoC or certification, complies with standards, has adequate testing, has an appropriate responsible party, is correctly labeled, has a valid authorization, may be marketed, or may be released.
The record should preserve supplier facts and their boundaries. Decisions about equipment-authorization scope, RF-function classification, responsible-party role, test sufficiency, labeling, certification, market access, product disposition, and release remain with qualified responsible functions.
Keep the U.S. responsible-party role separate from supplier records
FCC describes Supplier’s Declaration of Conformity as a procedure under which the responsible party ensures that equipment complies with appropriate technical standards. FCC says that the responsible party, or another party marketing the equipment, must provide a test report and other information demonstrating compliance when the Commission requests it.1
Under 47 CFR 2.906, SDoC is a procedure where the responsible party makes measurements or completes other procedures accepted by the Commission to ensure the equipment meets appropriate technical standards and other requirements.2 The rule also describes the relationship to subsequently marketed items that are identical to the sample tested and found acceptable under the stated provision.2 A China supplier test file may help identify product and sample information. It does not make the supplier the responsible party or establish the SDoC outcome.
47 CFR 2.909 identifies the responsible party for imported equipment subject to SDoC as the importer in the stated scenario and requires the responsible party to be located in the United States.3 A supplier located in China can provide production and testing facts. The buyer record must keep that supplier role distinct from the responsible-party determination.
Set the evidence boundary before collecting FCC documents
A supplier report can identify an item, sample, test, laboratory, label, or RF-function statement. It can help qualified personnel locate supplier-provided evidence. It does not decide what authorization path applies, whether a sample represents the marketed item, whether a test is adequate, or whether a responsible party has made an SDoC.
| Buyer review subject | A supplier record can identify | A supplier record cannot establish |
|---|---|---|
| Buyer item/version | Buyer-stated commercial scope | Applicable authorization procedure |
| Supplier legal entity/site | Stated source of information | U.S. responsible-party role |
| Product/RF description | Supplier-stated technical/commercial detail | RF-function classification |
| Test record | Supplier-provided report or summary | Test adequacy or compliance |
| Sample association | Supplier-stated sample/product relationship | Identity of all marketed equipment |
| Label/contact record | Supplier-provided artwork or contact detail | Labeling sufficiency |
| Shipment association | Stated product/transaction link | Marketing or release approval |
Use factual wording. “Supplier supplied report RF-12 for buyer model E-08” is a record entry. “Model E-08 has an FCC SDoC” is a conclusion that needs the responsible party and appropriate review process.
Define item, version, RF function, sample, and source scope
Start with the buyer item or SKU, current version, product description, and current specification/reference. Add the supplier legal entity and manufacturing site that supplied the record. Then capture the supplier-stated RF functions, test information, sample/product association, source record/date, U.S. responsible-party context if supplied, label/contact information, shipment association, and buyer owner.
A supplier report may use a factory model, while the buyer uses a retail SKU or a revised product name. A test sample may be identified by an internal code. Do not assume those names describe the same product/version. Preserve the association stated by the supplier and record an open condition where the relationship remains unclear.
| Scope field | Buyer record purpose |
|---|---|
| Buyer item/SKU and version | Identifies buyer-stated product scope |
| Buyer specification/reference | Identifies buyer baseline |
| Supplier legal entity/site | Identifies information source |
| Product/RF function description | Identifies supplier-provided equipment detail |
| Test record | Identifies supplied evidence object |
| Sample/product association | Identifies supplier-stated relationship |
| U.S. responsible-party context | Identifies supplied role information |
| Label/contact record | Identifies supplier-provided communication detail |
| Shipment association | Identifies stated transaction link |
| Buyer owner | Identifies responsible follow-up route |
Ask for facts, not an SDoC decision
A buyer can ask a China supplier to identify the product/version, legal entity and site, product and RF-function description, available test files, sample/model association, test date/source information, label/contact material it can provide, shipment association, and a follow-up contact. It can ask which records the supplier does not maintain or cannot share.
The request should not tell the supplier to decide whether the equipment is subject to SDoC or certification, whether a U.S. party is responsible, whether a test is adequate, whether a label is sufficient, whether an SDoC should be issued, or whether the equipment may be marketed or released. FCC’s procedure description assigns responsibility to the party responsible for compliance, not to every supplier who provides a document.1
| Supplier-stated evidence | Buyer question | Review limit |
|---|---|---|
| Product/model identity | Which product/version does the supplier identify? | It does not decide authorization scope |
| Supplier/site identity | Which entity and site supplied the record? | It does not identify responsible party |
| RF function description | What function does the supplier describe? | It does not classify equipment |
| Test record | What report or source information is supplied? | It does not establish test adequacy |
| Sample association | Which sample/model does the supplier link? | It does not prove market-item identity |
| Label/contact record | What details or artwork are supplied? | It does not approve labeling |
| Shipment association | Which item/shipment is linked? | It does not authorize marketing or release |
Keep related records separate
Supplier evidence, responsible-party SDoC, equipment-authorization assessment, RF-function classification, test assessment, label/contact review, certification application, marketing/import/release action, legal review, supplier status, product disposition, and shipment release are separate records. They may concern the same equipment, but they do not have the same owner or conclusion.
FCC explains that SDoC equipment is not listed in a Commission database and that the responsible party or another marketing party must provide a test report and other information when requested.1 This is a reason to preserve source records and product associations. It is not a reason to call a supplier report the SDoC itself.
| Evidence object | Factual relationship to capture |
|---|---|
| Supplier product record | Supplier-stated item/version and source file |
| Supplier RF/test record | Supplier-provided function/test detail |
| Sample/product record | Supplier-stated sample/model relationship |
| Label/contact record | Supplier-provided artwork or contact detail |
| Responsible-party SDoC | Separate responsible-party action |
| Authorization assessment | Separate qualified scope review |
| Test/label assessment | Separate qualified review record |
| Marketing/release record | Separate controlled decision or action |
Map evidence to the exact equipment version
Place the buyer item and version at the center of the evidence map. Link supplier legal entity/site, product/RF function, test source, sample/product association, label/contact material, source record/date, shipment association, and buyer owner. This allows another reviewer to see what the supplier supplied and whether it concerns the current equipment version.
China supplier FCC SDoC evidence becomes useful when it separates a supplier fact from an equipment-authorization conclusion. A report may identify a model, but a qualified function still needs to determine what that model relationship means. A label draft may identify contact text, but it does not make a responsible-party determination.
FCC states that certification and SDoC are different procedures and that the applicable procedure depends on the relevant FCC rule parts and RF functions.1 A buyer evidence record should therefore preserve the supplier’s stated product/RF information without choosing the procedure or declaring compliance.
Preserve gaps without making authorization conclusions
An unclear product/version, absent test record, test/sample mismatch, unclear RF function, supplier/site mismatch, missing U.S. responsible-party context, absent shipment association, unknown status, or unassigned owner needs a neutral record entry. The entry should preserve what was supplied and what remains unresolved.
| Record condition | Neutral buyer statement | It does not mean |
|---|---|---|
| Product/version is unclear | Supplier record does not identify a clear buyer version | Equipment is unauthorized |
| Test source is missing | Supplier did not provide requested test record | Testing never occurred |
| Test/sample link is unclear | Report does not identify a clear buyer product link | Report is invalid |
| RF function is unclear | Supplier record lacks a clear function description | SDoC or certification applies |
| Supplier/site differs | Records need source identity clarification | Supplier is unapproved |
| Responsible-party context is absent | Supplier did not identify U.S. role information | No responsible party exists |
| Shipment link is absent | Supplier file is not linked to a stated shipment | Equipment can or cannot be released |
| Owner is unassigned | Follow-up route is not recorded | Marketing or release is authorized |
| ## Use a restrained buyer review sequence |
Start with the buyer’s current equipment baseline. Record the buyer SKU, version, specification, and product description. Identify the supplier legal entity and site that supplied each record. This avoids treating an old report or a record from another factory site as evidence for the current equipment.
Capture the supplier’s statements as supplied. Record the product/model, RF-function description, test record, sample/model association, source file/date, label/contact information, and shipment link. Retain the original file when a report or test summary is in Chinese. A working translation may help route a question, but it does not turn a supplier statement into an SDoC or an equipment-authorization determination.
Then name the owner of the next question. The owner may need to compare the equipment version to a test sample, review the applicable authorization path, establish the responsible-party relationship, assess label information, or request additional supplier records. The evidence log should state that route instead of using a broad “FCC approved” status.
| Review step | Buyer action | Boundary kept intact |
|---|---|---|
| Establish baseline | Identify item, version, and buyer reference | Does not select authorization procedure |
| Identify source | Record supplier entity, site, file, and date | Does not name responsible party |
| Capture statement | Preserve supplied RF/test information | Does not establish compliance |
| Map association | Link record to sample, item, or shipment | Does not issue SDoC |
| Surface gap | Log unclear or absent relationship | Does not decide market eligibility |
| Assign route | Name responsible owner and question | Does not authorize release |
This sequence prevents a familiar sourcing shortcut: treating a test report as the final authorization record. A report may be useful supplier evidence. An SDoC is a responsible-party procedure, and it has a separate role, standard, and equipment relationship to consider.
Build a compact China supplier FCC SDoC evidence record sheet
A compact evidence sheet should make supplier information retrievable without becoming a hidden approval form. It should identify the buyer item, source file, stated relationship, and open condition. It should not label a product as SDoC-issued, FCC-authorized, market-ready, or released unless an appropriate controlled process has separately made that action or decision.
| Field | Example factual entry |
|---|---|
| Buyer item/version | Buyer SKU and version reference |
| Buyer specification | Current specification/drawing reference |
| Supplier source | Supplier-stated legal entity and site |
| Equipment/RF function | Supplier-provided product/function statement |
| Test record | Supplier-provided report or summary |
| Sample/product link | Supplier-stated model/sample relationship |
| Label/contact record | Supplier-provided artwork/contact information |
| Source record | File name, date, and supplier contact |
| Shipment association | Supplier-stated product/shipment link |
| Open condition | Missing detail, mismatch, or unclear link |
| Buyer owner | Function responsible for follow-up |
47 CFR 2.906 describes the SDoC procedure in terms of a responsible party, technical standards, and subsequent items identical to a sample tested and found acceptable in the stated rule.2 A buyer evidence sheet can preserve the supplier’s sample/model association and test files. It does not decide whether a later item is identical for the rule’s purpose or whether the requirements have been met.
Keep test reports and the SDoC as different records
FCC says that equipment under the SDoC procedure is not listed in a Commission database, while the responsible party or a marketing party must make test reports and other compliance information available upon request.1 This makes product/version, test-source, and responsible-party relationships important for records. It does not make a laboratory report into a Supplier’s Declaration of Conformity.
The responsible-party rule also identifies the importer as the responsible party in the specified imported-equipment situation subject to SDoC, and requires the responsible party to be located in the United States.3 A China supplier may be the manufacturing evidence source. It should not be assumed to be the U.S. responsible party because a report bears its name or because it produced the device.
China supplier FCC SDoC evidence should therefore preserve the exact product/version and sample association for each supplier file. A test report that names a similar model, a label draft with an old contact, or a supplier declaration with no link to the buyer’s equipment remains a record. The proper response is to make the gap visible, not to call the current item authorized.
Make handoffs readable for qualified owners
A useful handoff names the product and asks the actual question. A technical or RF function may need the supplier description and test records. A responsible-party function may need the product/version and controlled role information. Legal or regulatory reviewers may need the source documents, a record of gaps, and a clear question without an assumed answer. Supplier-management personnel may need to confirm the entity/site and document version.
| Owner route | Question a buyer record can present |
|---|---|
| Equipment-authorization function | What scope question remains for the identified equipment? |
| RF/function review | What supplier-stated function and sample details are available? |
| Responsible-party function | What separate SDoC role/action is required, if any? |
| Test/label review | What supplier records are available for the current version? |
| Certification function | Does a separate certification process need relevant source records? |
| Legal/regulatory function | What factual records and open questions need review? |
| Quality/supplier management | Which supplier entity/site and file apply to this item? |
| Disposition/release authority | Is a separate controlled decision recorded for the equipment state? |
The supplier can be asked to clarify its own production and test records without being asked to take the buyer’s U.S. responsible-party role. That makes the request more accurate and preserves the decision boundary FCC describes.
Avoid predictable record-control failures
Do not rely on a document title. A China supplier file called “FCC certificate” may be a laboratory report, product declaration, draft artwork, or commercial file. Record its origin, date/version, model, test/sample relationship, and stated purpose. If the record does not identify its connection to the buyer item, preserve that gap.
Do not use a factory address as responsible-party proof. The FCC responsible-party rule has a separate role framework for equipment subject to SDoC.3 A supplier site can identify the source of manufacturing or record information. It does not alone resolve the U.S. responsible-party question.
Do not assume that all electronic equipment shares the same authorization path. FCC describes SDoC and certification as different procedures and explains that applicable treatment depends on relevant rules and RF functions.1 A buyer record should capture supplier-provided function details and route the authorization question rather than make an assumption based on product type or a supplier label.
Do not merge supplier status with FCC authorization status. A supplier may be accepted in a buyer’s vendor process while a particular equipment version has unresolved records. A test file can be available while the product/sample relation needs clarification. Keep supplier evaluation, authorization assessment, labeling, marketing, and release as separate records.
Frequently asked questions
Does a China supplier test report count as an FCC SDoC?
No. A test report can be a supplier-provided evidence record. FCC describes SDoC as a responsible-party procedure and says the responsible party ensures equipment complies with applicable technical standards.1 A supplier report does not replace that responsible-party action.
Who is responsible for imported equipment subject to SDoC?
47 CFR 2.909 identifies the importer as the responsible party in the stated imported-equipment circumstance, and says the responsible party must be located in the United States.3 A supplier evidence record should remain separate from the responsible-party determination.
What can a buyer request from a China electronics supplier?
Request product/version identity, supplier entity/site, product and RF-function descriptions, available test records, sample/model associations, source dates, supplied label/contact materials, stated shipment association, and a follow-up contact. Do not ask the supplier to decide the authorization path or issue an SDoC outside its role.
Does a matching model name prove that a report covers the current product version?
No. Product identity needs a traceable relationship. Preserve the buyer version, supplier model, sample details, source date, and any stated association. If the relationship is unclear, route it to the qualified owner rather than assuming the report covers the item.
Does supplier evidence authorize marketing or shipment release?
No. Supplier evidence can help a qualified process locate product and test information. It does not establish an SDoC, an authorization outcome, marketing permission, product disposition, or shipment release. Keep those as separate controlled actions and decisions.
Keep supplier facts and responsible-party actions distinct
A useful China supplier FCC SDoC evidence record identifies the buyer item/version, supplier/site, equipment and RF description, source test/sample/label information, source record/date, shipment association, open conditions, and owner. It makes supplier information retrievable without calling the file an SDoC or a release authorization.
That boundary makes later review clearer. A qualified reviewer can see what the supplier supplied, which equipment version it concerns, and what remains unresolved. The responsible party can retain control of the role and action that FCC rules describe.
Supplier Ally can help buyers organize supplier communications, product specifications, electronics test records, label drafts, shipment references, and evidence requests across China sourcing projects. Decisions on FCC scope, RF classification, SDoC responsibility, testing, labeling, certification, legal interpretation, product disposition, and release should remain with the buyer’s qualified responsible functions.
ES 
EN 