UDI (Unique Device Identification): US Definition
A US-focused definition of device identity, labeler responsibility, label and package requirements, and the boundary between UDI, GUDID and traceability evidence.

On this page · 9 sections
- 1What Is UDI?
- 2US Scope and the Labeler
- 3DI, Conditional PI and the Two Label Forms
- 4Packages, Direct Marking and Stand-Alone Software
- 5How UDI Relates to GUDID and Submission Timing
- 6Worked Example: Identity to Label to Database Record
- 7Identifier Changes and Supporting Records
- 8Evidence Limits: What UDI Does Not Establish
- 9Questions for Evaluating UDI Support
How does UDI apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What Is UDI?
UDI (Unique Device Identification) is the US framework for identifying medical devices through identifiers on applicable labels and packages and related device-reference information. The identifier itself is a unique device identifier: a mandatory device identifier (DI), plus a conditional production identifier (PI). Under §830.3, the DI identifies the labeler and the specific version or model; the PI identifies specified production information when that information appears on the label.
UDI therefore does not necessarily mean a unique serial number for every physical unit. A model identity and a lot identity answer different questions from a unit serial number. Nor does the general labeling rule mean every device has identical obligations: §801.20 establishes the label-and-package requirement, while §801.30 provides important exceptions.
This definition covers selected US provisions of 21 CFR Part 801 Subpart B and Part 830 in the reviewed October 21, 2026 section texts. It is not a review of either entire Part or a device-specific applicability determination.
02US Scope and the Labeler
Start with the labeler, not the printer operator or the company name on a purchase order. Under §801.3, a labeler is a person who causes a label to be applied, replaced or modified with the intent that the device will be commercially distributed without subsequent label replacement or modification. Adding only a distributor’s name and contact information, without other label changes, does not count as modification for this definition.
As an internal review practice, identify who causes the final labeling arrangement and what subsequent changes are intended. A commercial title such as manufacturer or distributor should not replace that activity-based assessment.
| US Situation | Rule in the Selected Text | Boundary to Preserve |
|---|---|---|
| Medical-device label and device package | §801.20 generally requires a UDI on the device label and every device package. | Assess exceptions before concluding that the general rule applies. |
| Certain class I devices | §801.30(a)(2) excepts class I devices FDA has exempted by regulation from Part 820 good manufacturing practice requirements, apart from continuing §820.35 recordkeeping. | This is not an exception for every class I device. |
| Production identifiers on class I devices | §801.30(d) does not require a class I device’s UDI to include a PI. | A PI exception is different from an exception from UDI altogether. |
| Individual single-use devices in one package | §801.30(a)(3) provides a conditional exception for individuals of one version or model, stored in the package until use and not intended for individual commercial distribution. | Implantable devices cannot use this exception; the containing device package still requires a UDI. |
| Research, teaching or chemical-analysis devices | §801.30(a)(4) excepts devices used solely for those purposes and not intended for clinical use. | The nonclinical-use condition matters. |
| Custom or investigational devices | §801.30(a)(5)–(6) identifies exceptions using the referenced regulatory definitions. | This article does not assess whether a particular device satisfies those definitions. |
| Shipping containers | §801.30(c) does not require a UDI on a shipping container. | A shipping container is not the same defined object as a device package. |
This is a bounded scope map, not a complete exemption checklist. §801.30 contains additional categories and conditional provisions. Section 801.20 also references other exception and alternative routes that are not analyzed here. Record the actual basis for an applicability decision rather than inferring an exemption from a product description or a missing database result.
03DI, Conditional PI and the Two Label Forms
The DI is the fixed identity portion. The PI is conditional, not a requirement to populate every possible production field. The definition in §830.3 identifies these PI elements when included on the label:
- Lot or batch number.
- Serial number of a specific device.
- Expiration date.
- Manufacturing date.
- For an HCT/P regulated as a device, the distinct identification code required by §1271.290(c).
Section 801.40(b) connects label content to UDI content: when the label includes the specified production information, the UDI must convey it in a PI segment, subject to the class I PI exception in §801.30(d). This is why a lot-number field and a serial-number field should not be treated as interchangeable. For the detailed two-part comparison, see UDI-DI vs UDI-PI.
Plain Text and AIDC
Under §801.40(a), the general presentation rule requires both easily readable plain text and automatic identification and data capture (AIDC) technology. AIDC means technology that conveys the UDI or DI so it can enter an electronic patient record or another computer system automatically. It describes a capture capability, not one particular barcode design.
If the AIDC technology is not evident on visual examination, §801.40(c) requires the label or package to disclose its presence. Direct marking and stand-alone software have the specific presentation provisions discussed below; do not apply the general two-form rule to them without that further assessment.
Under §830.20(a), a UDI must be issued under a system operated by FDA or an FDA-accredited issuing agency. An internal stock code is not made into a UDI merely by printing or scanning it. This article does not teach issuer syntax, application identifiers, check digits or the referenced technical standards.
04Packages, Direct Marking and Stand-Alone Software
Device Package Versus Shipping Container
Section 801.3 defines a device package as a package containing a fixed quantity of a particular version or model. A shipping container is used during shipment or transportation and may have different contents from one shipment to another. The distinction concerns the defined object, not simply whether someone calls it a carton, box or case.
For example, in an internal packaging review, distinguish a fixed five-device package from a transport container assembled for a particular order. Assess each against the definitions: do not treat every outer carton as a shipping-container exception, or require a shipping container to carry a UDI merely because it travels through a warehouse.
When the Device Itself Needs a Mark
§801.45 requires a permanent UDI marking on the device itself when the device must bear a UDI on its label and is intended both for more than one use and for reprocessing before each use. Reusability alone is not the complete test.
The direct-mark UDI may match the label UDI or be different to distinguish the unpackaged device from its package. Unlike the general label presentation rule, the direct mark may use easily readable plain text, AIDC or an alternative technology providing the UDI on demand, or both forms described in §801.45(c).
The listed exceptions cover interference with safety or effectiveness, technological infeasibility, a single-use device undergoing additional processing and manufacturing for an additional single use, and a device previously marked under the rule. Small size is not a separately listed exception. A labeler relying on an exception must document its basis in the design and development files under §801.45(e).
The Stand-Alone Software Display Rule
Section 801.50(b) requires stand-alone software regulated as a medical device, whether packaged or not, to provide its UDI in easily readable plain text at startup, through a menu command, or both. It does not require both display routes. For software not distributed in packaged form, §801.50(a) deems the labeling requirements satisfied when that display provision is met and the version number is conveyed in the PI. Software distributed in both packaged and nonpackaged forms may use the same DI. These are stand-alone software provisions, not a general rule for every software component.
05How UDI Relates to GUDID and Submission Timing
The identifier and its reference record are different objects. Section 830.300(a) requires the labeler to provide the required device-identification information for each version or model required to bear a UDI. Selected information under §830.310 includes the labeler’s name, the DI, the labeled brand and model references, the types of PI appearing on the label, and the number of individual devices in the device package.
FDA’s GUDID overview, an explanatory web page rather than binding regulation, describes GUDID as an FDA-administered device-reference catalog. It explains that GUDID contains only the DI portion of the UDI, not PI values. PI flags indicate which production attributes are present.
Consequently, a flag saying that the UDI includes a lot number is not a stored lot number. The regulatory requirement in §830.310(b)(10) is to report the type of production identifiers appearing on the label. Keep that distinction intact when comparing a label with a reference record. The separate GUDID definition covers the database topic in more depth.
| Submission Event | Timing Under §830.330 |
|---|---|
| Initial required information | No later than the date the device label must bear a UDI under §801.20. |
| Changed required information appearing on the label | No later than the date a device is first labeled with the changed information. |
| Changed required information not appearing on the label | Within 10 business days of the change. |
Do not replace these distinct triggers with a general instruction to update before shipment or during a monthly refresh. As an internal control, identify the affected information, whether it appears on the label, and the relevant date before scheduling the submission work.
06Worked Example: Identity to Label to Database Record
Assume a fictional labeler, Training Device Company, supplies a fictional class II single-use device, Model TRAIN-A. For this example only, assume the device is subject to UDI labeling and device-information submission without an applicable exception. Each individual device is labeled, and a separate device package contains five such devices. The only production information on these fictional labels is a lot number; no serial number or production date is included.
| Step | Individual Device | Five-Device Package |
|---|---|---|
| Define the identity | Model TRAIN-A; one device. | A fixed package of five Model TRAIN-A devices. |
| Assign the training identity | DI-TRAINING-0001 | DI-TRAINING-PACK-0005 |
| Represent label content conceptually | DI-TRAINING-0001; PI: LOT=TRN-24A | DI-TRAINING-PACK-0005; PI: LOT=TRN-24A |
| Describe selected reference information | Training DI, labeler, model, quantity 1 and lot-number presence. | Training package DI, labeler, model, quantity 5 and lot-number presence. |
| Keep production values out of the reference record | TRN-24A is a label-side lot value, not the GUDID PI flag. | The same distinction applies to the package label. |
- Identity DecisionIdentify the labeler, Model TRAIN-A and the separate fixed five-device package.
- Label RepresentationAssociate each training DI with the applicable lot value. No usable barcode is supplied.
- Reference DescriptionAssociate the DI with descriptive attributes and a lot-number presence flag—not the lot value.
Now assume a second fictional lot, TRN-24B, with no change to the labeler, version, model, package or PI types. The label-side lot value changes. The reference description still says that a lot number is present; it does not acquire an inventory of the two lots. This illustrates the separation of objects, not a general exemption from assessing identifier changes.
The example intentionally stops before production genealogy. It does not establish which components went into a device, which customer received it, whether an individual was exposed, or whether product can be released. Those questions require separate evidence and decisions. It also omits many submission attributes: the table is a teaching comparison, not a complete GUDID record.
07Identifier Changes and Supporting Records
Under §830.50, a change to a device required to bear a UDI requires a new DI when the change results in a new version or model. Creating a new device package also requires a new DI. This is not a rule that every edit or every change in production information automatically creates a new DI.
Relabeling has a separate provision. Section 830.60 requires a person relabeling a device required to bear a UDI to assign a new DI and keep a record linking the previous DI to the new one. In an internal change review, assess the actual activity and applicable provision rather than treating model changes, package changes and relabeling as interchangeable events.
Section 830.360 requires labelers to retain records of the UDIs used for devices required to bear them and the version or model associated with each DI. Those records must be provided to FDA on specific request and retained for three years after the labeler ceases marketing that version or model. This period does not replace other FDA recordkeeping requirements.
Two selected QMSR provisions add useful context without turning this definition into a record-format guide. Section 820.35(c) requires recording the UDI for each medical device or batch of devices. Section 820.45(a) requires examination of labeling and packaging for accuracy before release or storage, where applicable, including the correct UDI, UPC or other device identification.
Do not infer a universal scan location, sampling plan or serial-allocation architecture from these statements. Those are process-design choices to justify against the applicable requirements and intended operation. For the separate production-record topic, see DHR.
08Evidence Limits: What UDI Does Not Establish
Use the following as an operational evidence test, not an additional regulatory checklist. Ask what the evidence actually demonstrates and what would still need investigation. An exact identifier match is useful, but it does not answer every question about the physical device.
| Evidence Object | Question It Helps Answer | Conclusion Not Established by That Object Alone |
|---|---|---|
| Identifier on a label | Which stated identity and production attributes are associated with this label? | That the label was applied to the correct physical device. |
| GUDID reference record | Which device-reference information corresponds to the DI? | Which individual units were manufactured, shipped or used. |
| Physical genealogy and distribution records | What recorded materials, processing and movements connect to particular devices? | That every relevant event was captured or every unlisted unit or patient is unaffected. |
| Release decision and supporting evidence | Who made the disposition decision and on what basis? | That a scan or database match can substitute for the required decision. |
For an internal review, distinguish a readable carrier from correct content, correct content from correct physical association, and a reference-record match from complete genealogy. If evidence is missing, record the limitation and the question it prevents you from answering. Do not silently convert an incomplete search into a safety conclusion.
Limits of This Definition’s Sources
The legal discussion uses the selected eCFR section texts dated October 21, 2026, not whole-Part review. The FDA material is a bounded GUDID web-page excerpt; the linked guidance document body was not reviewed. Issuer specifications, referenced standards and provisions outside these selected sections were not evaluated. This article therefore does not establish a usable identifier syntax, every exception, a complete submission schema or a device-specific compliance conclusion. Other jurisdictions have their own rules and are not covered here.
09Questions for Evaluating UDI Support
When evaluating a proposed labeling or record-management system, ask for evidence of the intended workflow rather than a general claim that it supports UDI. The questions below are evaluation practice, not prescribed software features or a universal implementation plan.
- Can a reviewer distinguish device, package and transport-container identities without relying on an ambiguous item description?
- Can the demonstration keep the DI, actual PI values and PI-presence flags separate?
- Can the reviewer identify which source revision supplied the label content and which supplied the reference-record attributes?
- How are a changed model, new device package and relabeling relationship presented for review?
- Can missing or conflicting evidence remain visible without a successful scan or database match being treated as release approval?
Define sampling, scan points and serial allocation for the actual process rather than presenting one design as a universal UDI requirement. Any proposed capability needs its own evidence; this definition makes no product, certification or performance claim. Continue with UDI and device traceability through production for the separate production-reconstruction topic.
Frequently asked questions
Q.Does UDI require a serial number for every device?+
Not as an inherent feature of UDI. Under §830.3, the DI identifies the labeler and version or model; PI elements are conditional on the specified information appearing on the label. A serial number is one possible PI element, not the only one. Section 801.30(d) also exempts class I UDIs from including a PI.
Q.Does a shipping carton need its own UDI?+
Determine what the carton is. A device package contains a fixed quantity of a particular version or model and falls under the general package rule. A shipping container is used for transportation and may have varying contents; §801.30(c) does not require a UDI on it. The everyday word carton does not resolve that distinction.
Q.Must a direct UDI mark include both plain text and AIDC?+
No. Section 801.45(c) permits either or both of its specified direct-mark forms. First establish applicability: the device must require a label UDI and be intended for more than one use and reprocessing before each use. The listed exceptions and the requirement to document reliance on an exception also matter.
Q.Must stand-alone medical-device software show its UDI every time it starts?+
Startup display is one permitted route, not the only route. Section 801.50(b) permits easily readable plain text at startup, through a menu command, or both. For nonpackaged software to use §801.50(a)’s labeling provision, it must also convey its version number in the PI. This is a stand-alone software rule.
Q.Does GUDID store the lot and serial numbers printed on devices?+
No. FDA’s GUDID web page explains that the database contains the DI portion of the UDI, not PI values, with flags indicating PI attributes. Section 830.310(b)(10) requires the type of production identifiers appearing on the label. A lot-number presence flag is not a record of a particular lot or its movements.
Q.Does every device change require a new DI?+
No blanket every-change rule appears in §830.50. It requires a new DI when a change results in a new version or model, and when a new device package is created. Relabeling is addressed separately by §830.60, which requires a new DI and a record linking the prior and replacement DIs.
Q.When must the labeler submit or update device-identification information?+
Under §830.330(a), initial information is due no later than the date the label must bear a UDI under §801.20. Under §830.330(b), changed information appearing on the label is due by the first labeling date with that changed information. Changes to information not appearing on the label are due within 10 business days.
Q.Does a successful UDI scan establish that a device can be released or excluded from an investigation?+
No. For operational decision-making, treat a scan as evidence about captured identifier content, not release authority or proof of complete genealogy. Traceability alone does not prove units or patients unaffected. Review physical associations, missing evidence and the applicable decision process separately; do not turn a successful scan into a disposition decision.
Primary sources
- 21 CFR 801.3 — Definitions
- 21 CFR 801.20 — Label and Device Package UDI Rule
- 21 CFR 801.30 — General Exceptions
- 21 CFR 801.40 — Form of a UDI
- 21 CFR 801.45 — Direct Marking
- 21 CFR 801.50 — Stand-Alone Software
- 21 CFR 830.3 — UDI, DI, PI and AIDC Definitions
- 21 CFR 830.20 — UDI Requirements
- 21 CFR 830.50 — Changes Requiring a New DI
- 21 CFR 830.60 — Relabeling
- 21 CFR 830.300 — Devices Subject to Data Submission
- 21 CFR 830.310 — Required Device-Identification Information
- 21 CFR 830.330 — Submission and Update Timing
- 21 CFR 830.360 — Labeler Records
- FDA — GUDID Overview
- 21 CFR 820.35 and 820.45 — Selected Records and Labeling Controls
Further reading
Explore this topic
UDI sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
GS1 identifiers, barcodes, ASNs and the rules that require lot-level traceability.
Device-specific rules, submissions and the standards that bind them.
Want to see how UDI could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
