US FCC / UL / Prop 65 Market Access Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: There is no single "US certificate" for electrical/electronic products. At least three layers matter: FCC regulates radio-frequency devices (federal mandatory; the product follows Certification/FCC ID or SDoC); UL/NRTL is the occupational/electrical-safety certification system (not mandatory for every product, but some workplace products, customers or local AHJs require it); California Prop 65 is a chemical-exposure warning law (not a product-safety certification). A US market-access page cannot say "FCC/UL certified" in one sentence; it should state the product/model, applicable rules, FCC route (Certification or SDoC), FCC ID/responsible party/test reports, UL/NRTL mark and standard scope, Prop 65 warning and chemical list, labels/manuals and customer documents. Information is current to 2026-11-05. This is a review of public rules and project practice, not legal, certification, testing or customs advice; specifics follow the FCC, OSHA, California OEHHA, applicable regulations and the customer contract.

This guide is for electronics/electrical, consumer electronics, appliances, lighting, power supplies, wireless/IoT, automotive electronics, medical electronics, tools and export manufacturers in Changzhou and nearby areas. It explains how to write and accept a US market-access/compliance page. US rules are not the EU CE set: CE does not cover the US, and FCC does not regulate all product safety; UL is not a federal "mandatory certification", and Prop 65 is not a "product certificate".

How does the US page relate to EU CE, UK UKCA and LVD/EMC pages?

The EU LVD/EMC page answers EU CE safety/EMC; the UK UKCA/CE page answers GB/NI market access; the US page answers FCC radio authorization, UL/NRTL electrical safety and California Prop 65. CE does not cover the US, and FCC is not CE EMC; a product may need CE (EU), UKCA/CE (UK), FCC (US), UL/NRTL (customer/workplace) and Prop 65 (California). Technical files/test reports may reuse some data, but the applicable standards, limits, labels, responsible party and declarations differ; do not rename a CE DoC into an FCC/UL document.

Common breakpoints: treating CE as a US passport; treating FCC as product-safety certification; treating UL as mandatory for all products; treating Prop 65 as a "product certificate"; mixing FCC ID and SDoC; test reports not covering all models; wrong responsible party/importer; labels/manuals missing compliance statements; the website says "FCC/UL certified" without an ID/certificate; giving only a CE DoC when the customer asks for US documents. Separate the three systems first; then sales, quality, regulatory and the customer share one playbook.

This page map is editorial; specific duties follow FCC/OSHA/OEHHA rules and the customer contract—not this article.

Which US requirements apply?

At least five: (1) FCC: radio-frequency devices must be authorized before marketing, through Certification (usually intentional radiators, FCC ID) or SDoC (usually unintentional radiators); (2) OSHA NRTL: some electrical products used in the workplace must be certified by an OSHA-recognized NRTL; UL is one NRTL, not the only one; (3) California Prop 65: provide a "clear and reasonable" warning for exposure to listed chemicals; it is not product-safety approval; (4) CPSC/federal product safety: consumer-product safety/recall/reporting as applicable; (5) customer/industry/state/local AHJ: UL/ETL, energy efficiency, state rules, building/fire codes. Do not merge them into "US certification"; list applicability by product.

Acceptance checks: product type; radio/digital circuitry; workplace use; California sales; customer/state/local requirements; CPSC/energy efficiency. Common gaps: FCC only; UL only; treating Prop 65 as federal; ignoring California; ignoring workplace NRTL; ignoring customer/state requirements; presenting a voluntary mark as mandatory.

This matrix is editorial; specific applicability follows FCC/OSHA/CPSC/state rules and the customer contract.

How should FCC Certification and SDoC be separated?

FCC equipment authorization has two main routes: Certification and SDoC. Generally, an intentional radiator (a device that intentionally emits radio frequency, such as Wi-Fi/Bluetooth/wireless modules) requires Certification: an FCC-recognized TCB reviews the application, an FCC ID is granted, and the product carries the FCC ID; an unintentional radiator (digital circuitry/incidental emissions, such as ordinary ITE or a monitor) usually uses SDoC: the responsible party declares conformity, keeps test reports/compliance information, does not file with the FCC/TCB, and is not listed in the FCC database. Some devices are exempt; the FCC rules and product functions decide. A product with both a wireless module and digital circuitry may involve both Certification and SDoC. Do not say "all products need an FCC ID", and do not say "SDoC has an FCC ID".

Acceptance checks: product function (radio/digital); applicable rules; Certification/SDoC/exemption; TCB/FCC ID; responsible party; test standards; model coverage; labels/manuals. Common gaps: a wireless product only does SDoC; ordinary ITE insists on an FCC ID; SDoC is described as having an FCC ID; FCC ID does not match the model; the test report covers only one model; the SDoC responsible party is not in the US; module/end-product authorization relationship is unclear.

FCC routes follow FCC equipment-authorization rules/pages; product functions decide the route, not a one-line "wireless or not" judgment.

What FCC documents, labels and manuals should be checked?

The Certification route normally needs an FCC ID, grant/authorization record, test reports, label/e-label and compliance information in the manual; the SDoC route normally needs test reports, a compliance-information statement and responsible-party information, with the compliance statement supplied with the product—no FCC ID. Both must show model/series coverage, test standards/versions, test lab/TCB, responsible party, label location and manual language. An FCC ID can be checked in the FCC database by grantee/product code; SDoC is not in the FCC database, so provide test reports/statement to the customer. Product changes/module/antenna changes may trigger re-evaluation; do not reuse an old report forever.

Acceptance checks: FCC ID/grants; test reports; model coverage; label/e-label; manual statement; responsible party; change assessment; database query. Common gaps: FCC ID not found; grant does not match the model; outdated standards; only one variant tested; label location/size non-compliant; manual lacks the compliance statement; module change not assessed; SDoC gives an FCC ID.

FCC documents/labels follow FCC rules and authorization conditions; specific test standards depend on product functions.

Is UL/NRTL mandatory?

UL is not a federal certification required for every electronic product entering the US. OSHA's NRTL program recognizes private organizations to certify certain products against OSHA electrical standards; each NRTL has a scope of recognized standards and uses its own registered certification mark. Some electrical products used in the workplace need NRTL certification; customers, procurement, local AHJs (building/fire/electrical inspectors) or insurers may also require a UL/ETL mark. UL is one NRTL, not the only one; UL marks include Listed/Recognized/Classified with different meanings. The website should say "confirm per product/customer/use whether NRTL is required, and which NRTL/standard scope", not "all products are UL certified".

Acceptance checks: workplace use; OSHA/customer/AHJ requirements; NRTL; standard scope; mark type; certificate/report; model coverage; factory inspections. Common gaps: all products say UL; UL treated as federal mandatory; mark types mixed; standard scope does not cover; expired certificate; failed factory inspection; customer wants ETL but only UL is available; UL treated as FCC.

NRTL/UL requirements follow the OSHA NRTL program and customer/AHJ requirements; UL mark meanings follow UL guidance.

How should UL mark types be distinguished?

A UL mark is not just "UL certified": UL Listed is generally for complete products/systems; UL Recognized Component is generally for components/parts evaluated as part of an end product; UL Classified generally indicates classification for specific properties/standards/hazards. Different marks have different scopes, standards and responsibilities; do not describe a Recognized component as a "UL Listed end product", or a Classified mark as full certification. When a customer asks for documents, provide the certificate/report for the matching model/scope, not just a logo. Specific mark meanings follow UL's mark guide/certificate.

Acceptance checks: mark type; product/component; standard; model; certificate/report; factory inspection; customer acceptance. Common gaps: component presented as end product; Classified presented as Listed; mark does not match the certificate; model not covered; customer wants an end-product certificate but gets a component certificate; UL mark treated as FCC/CE.

Mark meanings follow UL/NRTL certificates and mark guides; this table is editorial and does not replace UL rules.

How should California Prop 65 be described?

Prop 65 (the Safe Drinking Water and Toxic Enforcement Act of 1986) requires businesses to provide a "clear and reasonable" warning before exposing Californians to listed chemicals; the list is maintained by OEHHA (the list date in this article's source is 31 July 2026) and includes chemicals known to cause cancer/reproductive harm. A warning is not a "product-safety certification" and does not ban sales; it requires assessing exposure and providing a warning by product label/package/shelf/catalog/website as applicable under the regulations/OEHHA guidance. Safe-harbor levels (NSRL/MADL) can be used in assessment; missing warnings may attract private enforcement/demand letters. The US page should state California sales, products/chemicals, warning method and list version—not "Prop 65 certified".

Acceptance checks: California sales; chemicals/materials; exposure assessment; warning content; label/package/website; list version; safe harbor; supplier declarations; records. Common gaps: warning on every product; "no chemicals" without assessment; wrong wording/format; outdated list; website only, not product; missing supplier data; treating Prop 65 as federal; ignoring private enforcement.

Prop 65 requirements follow OEHHA regulations/guidance and the list; warning wording/location depend on the product/scenario—not legal advice.

How should the product-rule matrix be laid out?

The website can list a matrix by product line: product/model, radio?, digital circuitry?, workplace electrical?, California sales?, FCC route, NRTL/UL requirement, Prop 65 warning, other (CPSC/energy efficiency/state rules). For example: Wi-Fi modules/smart devices usually FCC Certification + FCC ID; ordinary power supplies/monitors may use SDoC; industrial equipment may have customer UL/ETL requirements; consumer electronics sold in California may need a Prop 65 assessment. The matrix is not a "legal conclusion"; it helps the customer see what has been done and what is still missing. Do not put all products in one row.

Acceptance checks: product/model; radio/digital; workplace; California; FCC route; NRTL; Prop 65; other; document status. Common gaps: one conclusion for all products; radio/non-radio mixed; workplace/consumer mixed; California ignored; matrix inconsistent with certificates/reports; no "to be confirmed" status.

This matrix is an editorial example; specific routes/requirements follow product functions, FCC/OSHA/California rules and the customer contract.

Which US compliance documents will customers ask for?

Common: FCC ID/grant or SDoC statement, test reports (standard/version/model), label/manual compliance information, US responsible party/importer, UL/NRTL certificate/report/mark photo, Prop 65 warning/assessment/supplier declaration, material/substance declarations, CPSC/energy-efficiency/state documents. Customers may also ask for FCC database screenshots, TCB information, factory inspection records and change records. Answers must be truthful, model-specific and versioned; if a document is missing, say "to be confirmed/planned", not use a CE DoC or a logo. Customer-specific documents are provided under NDA, not published on the website.

Acceptance checks: document list; model coverage; FCC route; responsible party; UL/NRTL; Prop 65; version/date; customer acceptance. Common gaps: only CE; FCC ID not found; SDoC has no report; UL scope not covered; no Prop 65 assessment; model/version mismatch; outdated documents; inconsistent questionnaire answers.

The document list is editorial; specifics follow the customer questionnaire, contract and applicable regulations.

How should the website US market/compliance page be written?

Suggested content: (1) applicable products/models/markets (US/California); (2) FCC route (Certification/FCC ID or SDoC) and test standards; (3) responsible party/importer; (4) whether UL/NRTL is required, body/standard/mark; (5) Prop 65 warning/assessment/list version; (6) labels/manuals/packaging; (7) customer document request/NDA; (8) change/version/module changes; (9) other CPSC/energy/state requirements; (10) contact/version/update date. The public page should state the rules, document types and an entry; FCC IDs/reports/certificates/customer questionnaires are provided per permission. The English page should use consistent terms (FCC ID, SDoC, NRTL, UL Listed/Recognized, Prop 65 warning) and state the check date.

Do not write "FCC/UL certified" as a one-line conclusion; write "this product follows FCC Certification/SDoC; whether UL/NRTL is required depends on customer/use; California sales require a Prop 65 assessment". Do not promise "customs clearance guaranteed/access guaranteed"; do not publish customer-specific documents; do not mix CE/UKCA marks into the US page.

This page structure is editorial; external statements must be truthful and verifiable, per the regulations and customer contract.

What must not be written?

High-risk claims: "FCC certified/FCC certificate" (FCC is equipment authorization; Certification gives an FCC ID, SDoC does not); "all products need UL/UL is federal mandatory" (no); "UL = FCC compliance" (no); "Prop 65 certified/passed Prop 65" (not a certification; it is a warning); "CE covers the US" (no); "SDoC has an FCC ID" (no); "FCC ID = product-safety certification" (FCC covers radio, not all safety); "UL means no FCC needed" (no); "one test report covers all models/versions" (depends on coverage/changes); "website says FCC/UL certified without an ID/certificate" (misleading); "customs clearance/access guaranteed" (cannot promise).

Safer wording: "This product follows FCC Certification (FCC ID: xxx) or SDoC; whether UL/NRTL is required depends on customer/use; California sales require a Prop 65 assessment/warning; specifics follow FCC/OSHA/OEHHA rules and the customer contract." External promotion must also comply with advertising/fair-competition law; customer documents/test data need authorisation/redaction.

These red lines are editorial; whether a claim is false advertising/non-compliant is determined by regulators and the contract—not this article.

Go-live acceptance checklist

Ten checks: products/markets, FCC route, FCC documents/labels, responsible party, UL/NRTL, Prop 65, labels/manuals, customer documents, change management, page wording/version. Each needs an owner, evidence and review date. The pass condition is not "the page says FCC/UL", but that a customer can find the applicable route, number/certificate, warning and documents for the product.

Before go-live, run one real product through: determine function (radio/digital/workplace/California) → determine FCC route → check FCC ID/report → determine UL/NRTL → do Prop 65 assessment → check labels/manual → prepare customer documents. Any step that fails is a gap in the page or compliance file.

This checklist is editorial; specific compliance requirements follow FCC/OSHA/OEHHA/CPSC and the customer contract.

Who should read this, who should not, and what decisions does it support?

It suits regulatory, quality, sales, procurement and website teams at electronics/electrical, consumer electronics, appliances, lighting, power supplies, wireless/IoT, automotive electronics, medical electronics, tools and export manufacturers in Changzhou and nearby areas; also companies supplying US customers/importers and receiving FCC/UL/Prop 65 questionnaires. It does not suit businesses that do not sell to the US, products entirely outside FCC/NRTL/Prop 65, or teams wanting one page to replace testing/certification/legal advice.

Read it if a US customer asks for an FCC ID/SDoC/UL certificate/Prop 65 statement; your product has radio/digital circuitry; it is used in the workplace; it is sold in California; or your website says "FCC/UL certified". Skip it if you treat FCC as safety certification, write UL for every product, or treat Prop 65 as certification. It supports self-review of the product/rule matrix, FCC route, documents/labels, UL/NRTL, Prop 65 and page wording.

FAQ

Are FCC certification and FCC ID the same thing?

Not exactly. FCC equipment authorization has Certification and SDoC routes; Certification through a TCB results in an FCC ID (grant), while SDoC is a responsible-party declaration with test reports/compliance information, no FCC/TCB filing, and no FCC ID. "FCC certified" is confusing; write "FCC Certification (FCC ID: xxx)" or "FCC SDoC".

Do all electronic products need UL?

No. UL is not a federal mandatory certification for every product entering the US; OSHA's NRTL program requires NRTL certification for certain electrical products used in the workplace, and customers/procurement/local AHJs/insurers may require UL/ETL. Whether it is required, which NRTL and which standard scope depend on the product/use/customer contract. UL is one NRTL, not the only one.

Does SDoC require an FCC filing?

No. Under SDoC, the responsible party (generally required to be in the US) ensures compliance, keeps test reports/compliance information, and supplies a compliance-information statement with the product; SDoC equipment is not listed in the FCC database. On FCC request, the responsible party or marketer must provide test reports and other evidence. Follow the FCC rules for responsible-party/statement requirements.

Where must a Prop 65 warning appear?

Prop 65 requires a "clear and reasonable" warning before exposure to listed chemicals; the method depends on the product/sales scenario (product label/package/shelf/catalog/website, etc.) and OEHHA regulations/guidance. Not every product needs a warning; first assess chemicals/exposure, then decide whether a warning is needed and its wording/location. Follow OEHHA guidance/legal advice.

How should we provide FCC/UL/Prop 65 documents to a US customer?

Use the customer questionnaire as a checklist: FCC ID/grant or SDoC/test reports, labels/manual, US responsible party, UL/NRTL certificate/report/mark, Prop 65 assessment/warning/supplier declaration. Documents must match the model and be versioned; customer-specific documents go under NDA, not on the public website. If a document is missing, state the plan/timeline honestly—do not substitute a CE DoC.

Can the website say "FCC/UL certified"?

Not as a one-line claim. Write "this product follows FCC Certification (FCC ID) or SDoC; whether UL/NRTL is required depends on customer/use; California sales require a Prop 65 assessment/warning", and state the check date. FCC is equipment authorization, UL is NRTL/electrical-safety certification, and Prop 65 is a warning—not the same "certification".

One-sentence takeaway

A Changzhou manufacturer's US market page is not about the phrase "FCC/UL certified". It should turn the product/rule matrix, FCC route (Certification/FCC ID or SDoC), responsible party, UL/NRTL, Prop 65, labels/manual and customer documents into a reviewable checklist—so a customer can find the applicable route and evidence for the product.

Method and limitations

This is a review of public rules and project practice, not an audit, certification, testing, customs or legal opinion on any company, product or compliance file. No undisclosed customer, product, test or certification data were used. The rule matrix, document list, labels and acceptance items are editorial suggestions, not legal/certification conclusions. Specific FCC routes, NRTL/UL requirements, Prop 65 assessment/warnings and customer documents depend on FCC/OSHA/OEHHA/CPSC rules, testing bodies and the customer contract; rules may change, so recheck before publication.

Sources and scope

Information is current to 2026-11-05. The following are US federal/California official pages; their rules, lists and guidance control.

1. FCC, Equipment Authorization: FCC. Equipment authorization, Certification/SDoC, responsible party, FCC ID, labels/documents.
2. FCC, Equipment Authorization Procedures: FCC. Intentional/unintentional radiators, Certification vs SDoC, US responsible party.
3. OSHA, Nationally Recognized Testing Laboratory (NRTL) Program: OSHA. NRTL recognition, standard scope, certification marks, workplace electrical products.
4. California OEHHA, Proposition 65: OEHHA. Prop 65 list (31 July 2026), warnings, safe harbor, regulations.
5. California OEHHA, Proposition 65 Warnings: p65warnings.ca.gov. Consumer/business warning guidance and methods.
6. eCFR, 47 CFR Part 2: eCFR. FCC equipment authorization/frequency allocation regulations.