Compliance research

ANSI UL 122-2019 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 12-177 to 12-375 and state declaration-acceptance date(s) for the replaced recognition: recognition 12-177: 2028-07-02. Compare the exact edition and recognition limitations with your reports before agreeing the submission evidence or further work.

Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.

Exact FDA recognition records

Compare the edition and the recognized portion

Read these columns together. A complete recognition is not a device-specific testing instruction. The limitations are the FDA’s public metadata; the licensed standard itself is not reproduced.

Recognition / editionPublic recognition limitationsDeclaration transition context
FDA 12-177
UL 122-2007 (R2011)

Standard for Photographic Equipment - Ed. 5.0

Complete

Complete standard

[2] [4]
Exported transition expiration: 07/02/2028
FDA 12-375
ANSI UL 122-2019

Standard for Safety Photographic Equipment - Ed. 5.0 [Including revisions through October 15 2019]

Complete

Complete standard

[3] [6]
No expiration date is stated in this acquired export row. That is not a guarantee of indefinite recognition.

What FDA’s transition statement says

Recognition 12-177 → 12-375

FDA recognition of UL 122-2007 (R2011) [Rec# 12-177] will be superseded by recognition of UL 122-2019 [Rec# 12-375]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 12-177] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 12-177] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [1] [5]

FDA public recognition metadata describes use of declarations of conformity in support of premarket submissions. A recognition transition is not a universal retesting deadline, a product ban, or proof that this standard applies to your device. The technical differences between licensed editions, adequacy of existing reports, buyer-specific route and final test scope remain incomplete. The comparison below does not reproduce the standard or establish FDA approval.

Method: Exact directed old-to-new statements are reconciled across both acquired sheets and the old export date. No name-similarity mapping or technical-clause inference.

Build your edition-to-report handoff matrix

Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.

  1. Which edition is actually in your evidence?

    Reconcile each report and declaration against ANSI UL 122-2019 and the replaced designation(s) UL 122-2007 (R2011). Record amendments and the exact report/device revision. A similar standard number is not an edition match.

    Useful evidence: Report cover, method/edition references, amendments, declarations and device/configuration revision.

  2. Does the declaration cover the recognized portion?

    Use the complete FDA public limitation text in the comparison table. Map each listed exclusion, where present, to the relevant report sections and obtain a reasoned evidence assessment. Complete recognition still does not determine device applicability.

    Useful evidence: Recognition-to-report coverage matrix, excluded-clause assessment and the licensed edition used by your specialist.

  3. How does the recorded transition affect your submission plan?

    Record planned declaration/submission dates against the FDA sheet’s acceptance date(s): recognition 12-177: 2028-07-02. This concerns declarations supporting premarket submissions to the replaced recognition; do not treat it as a blanket deadline to retest or stop selling.

    Useful evidence: Submission plan, intended declaration references, dated recognition-sheet check and rationale for the chosen evidence route.

  4. What changed beyond the designation?

    Ask the specialist to assess the actual licensed edition/amendment differences for your design, materials, software and use environment. Separate a documented evidence gap from a changed title. This metadata comparison does not establish which tests changed or must be repeated.

    Useful evidence: Edition gap assessment tied to the device and existing evidence, with a bridging rationale and unresolved inputs.

  5. What should the quote include?

    Request a report/recognition reconciliation and a justified gap assessment first. Separate any proposed additional evaluation or testing, samples, methods, deliverables and exclusions; agree them only after applicability and existing evidence are assessed.

    Useful evidence: A scoped evidence-assessment quote; separately identified conditional work and report ownership.

Work packages and dependencies

Questions for providers

Sources and data dates

Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.

FDA — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot c126a86139363c6e1ad3b044f93b4930bc77d6ad5c1ec977277f0f10107dcf67

  • [1] HTML tr 22 / Transition Period / nested table · record 10a39542744deca8a4efd2e459b862533d90e2e0224991d1d288e1bc0c1cc34a
  • [4] HTML tr 18 / Extent of Recognition / nested table · record 46c0bc914af1f321f2d4e85f138ee53901943099388eb698d5eb5dc3e282cd26

FDA — recognition metadata exported through the official search form ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 94ccf56dc846c7f6d78d6ad77dc6e87d1803ac3612af01d6894949e34c4a78d8

  • [2] CSV row 1831 · record 204adae64e57bc03c247989820444ac56dce7f400b57407dd4bdc828a3e55fe5
  • [3] CSV row 262 · record 2c7ead2cf60644ac3c431fffc603dba79f7db821c7f2ec656e6a27f11a1ca322

FDA — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 005d517417bb5dd079d3e6c730196647e6412e2ce84724bd32c985ff1cf861c8

  • [5] HTML tr 22 / Transition Period / nested table · record c669857a72aabd19105902c6ecd19afb03d2f6233695f1958f04b6c4b70152ca
  • [6] HTML tr 18 / Extent of Recognition / nested table · record d6f23cd697c85bd357d79ac856a50f2e7ed3c5d9818fd5b04af7ed482351a9e3

Prepare an editable project brief

Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.

Choose work packages to discuss

Compare FDA 510(k) Submission Services