MedDeviceGuide: Tracing Mixed-Lot Consumables During a Recall

When an urgent medical consumable recall notification reaches a hospital materials management desk or medical supply distributor dock, inventory managers face an immediate operational dilemma: How should a hospital buyer or distributor reconcile an actual consumables recall notice against mixed lots, multiple packaging levels, and issue or return records without mistaking a Unique Device Identifier Device Identifier (UDI-DI) match for proof that every unit is affected or recovered?

Under 21 CFR 7.49(c)(1)(ii), a recall communication should clearly identify the product, size, lot number(s), code(s) or serial number(s), and any other pertinent descriptive information to enable accurate and immediate identification of the product. 21 CFR 7.49(c)(1)(v) says it should also provide a ready means for the recipient to report whether it has any of the product. Scope for this worksheet is that notice text—not a catalog family. Hospital ERP systems, supply modules, and distributor catalogs often aggregate consumables by catalog number or primary UDI-DI, which is a weaker match than the lots and codes the notice named.

21 CFR 801.3 divides a UDI into two components: the mandatory Device Identifier (DI), a fixed portion that identifies the specific version or model and the labeler, and the conditional Production Identifier (PI), which identifies, when included on the label, the lot or batch, serial number, expiration date, manufacturing date, and, for an HCT/P regulated as a device, the distinct identification code. FDA UDI Basics and FDA's GUDID page state that GUDID contains only the DI portion of the UDI, which serves as the key to obtain device information. GUDID does not include production identifiers. It contains PI flags to indicate which PI attributes appear on the UDI; those flags are not the lot values for units on a hospital shelf. AccessGUDID can confirm brand, model, labeler, and packaging-level DIs. It cannot list lots, prove a unit is affected, prove recovery, or prove clearance or approval.

When materials personnel query AccessGUDID or scan a barcode at receiving, a DI match can confirm brand, model, labeler, and registered packaging configurations. It does not say whether the box in hand was made in an affected lot. Treating a UDI-DI match as proof of scope or recovery creates two failures: lots that the notice did not name may be pulled as if they were in scope, or one matching-DI carton may be counted as if it closed the file while other units with the same DI remain uncounted.

Related reading from another VayoMed publication: For adjacent background on how labelers assign device identifiers and packaging-level GTINs, and on how AccessGUDID displays DI records, see MedDeviceGuide's medical device labeling and UDI system guide. That publication is manufacturer and labeler background. It is not a regulator, a lot database, a tester, or proof of clearance or approval, and it cannot reconcile the mixed carton on this dock.

21 CFR 7.40 describes recall as a voluntary action by manufacturers and distributors to protect the public from products that present a risk of injury or deception or are otherwise defective. That section and §§ 7.41 through 7.59 provide guidance so responsible firms can discharge recall responsibilities and so FDA can monitor recalls. Treat the word should in those sections as guidance. The operational text for the reader is the recall notice in hand plus responsible quality personnel. eCFR is unofficial; the Title 21 display used for these checks was current as of 8 September 2026.

Under 21 CFR 7.49(a), the recalling firm is responsible for promptly notifying each of its affected direct accounts. The stated purpose of that communication is fourfold: (1) that the product is subject to a recall; (2) that further distribution or use of remaining product should cease immediately; (3) where appropriate, that the direct account should notify customers who received the product; and (4) instructions on what to do with the product. Under 21 CFR 7.3(n), a consignee is anyone who received, purchased, or used the product being recalled. 21 CFR 7.49(d) says consignees that receive a recall communication should immediately carry out the instructions set forth by the recalling firm and, where necessary, extend the recall to their own consignees.

Distinguish a recall from adjacent actions defined in 21 CFR 7.3. A recall under 21 CFR 7.3(g) is a firm's removal or correction of a marketed product that FDA considers to be in violation of the laws it administers and against which the agency would initiate legal action, e.g., seizure. Recall does not include a market withdrawal or a stock recovery. A correction under 21 CFR 7.3(h) means repair, modification, adjustment, relabeling, destruction, or inspection without physical removal to another location. 21 CFR 7.3(j) defines a market withdrawal as a removal or correction involving a minor violation that would not be subject to FDA legal action, or involving no violation, for example normal stock rotation practices. Do not treat a market withdrawal, stock rotation, or a same-catalog SKU as automatically in recall scope.

21 CFR 7.42(b)(1) says recall depth may be consumer or user level (including intermediate wholesale or retail), retail level, or wholesale level. A hospital materials desk or distributor is typically a user-level or wholesale-level consignee, not the party that writes the recall strategy. FDA's Initiation of Voluntary Recalls guidance states that a notified consignee should implement its own recall-initiation procedures to extend the recall promptly to its direct accounts that may have received affected product, in accordance with the recalling firm's instructions (21 CFR 7.49(d)), and that product coding may allow consignees to separate violative lots from unaffected lots. Do not invent local hold, release, destruction, or clinical stop-use rules, and do not treat a completed worksheet as recall closure or as authorization for patient care.

Reconciling consumable quantities requires navigating the physical hierarchies of packaging found on medical docks. Under 21 CFR 801.3, FDA establishes a clear technical distinction between a device package and a shipping container. A device package is defined as a package that contains a fixed quantity of a particular version or model of a device. A shipping container is defined as a container used during shipment or transportation of devices whose contents may vary from one shipment to another.

21 CFR 801.20(a) requires the label of every medical device and every device package to bear a UDI unless an exception or alternative applies. 21 CFR 801.40(a) requires that UDI in easily readable plain-text and in AIDC form; 21 CFR 801.40(b) requires a device-identifier segment and, whenever the label includes a lot or batch number, serial number, manufacturing date, expiration date, or HCT/P distinct identification code, a production-identifier segment that conveys that information. FDA GUDID guidance states that Primary DI identifies the lowest packaging level that contains a full UDI (the base package) and that Device Count is the number of devices in that base package. Package DI is the DI for a particular package configuration and does not include shipping containers. Package records include Contains DI Package (the lower-level DI inside) and Quantity per Package (how many of those lower-level packages are inside). A pouch, an inner box of 10 pouches, and a case of 50 pouches can therefore have different DIs and different device counts. Convert quantities to one unit of measure from the labeled count on the package in hand.

Because Package DI excludes shipping containers, a received carton can mix in-scope and out-of-scope lots under one outer shipper. Scanning the shipper does not identify those lots. Open the shipping container far enough to read each inner device package. A case-level DI match does not identify the lots inside a mixed shipping carton.

Convert master cases, inner boxes, and single pouches to one unit of measure from the labeled count. Labeled storage and transport conditions for remaining stock are a different published job from this quantity worksheet; see labeled storage and transport for medical consumables.

A common error is to treat this recipient worksheet as manufacturer or importer reporting under 21 CFR Part 806. Under 21 CFR 806.10(a)–(b), each device manufacturer or importer shall submit a written report to FDA within 10 working days of initiating a correction or removal to reduce a risk to health or to remedy a violation of the act that may present a risk to health, unless an exception applies. FDA's Recalls, Corrections and Removals (Devices) page states that only the person who initiates the correction or removal is required to report, and that reports may be submitted by email or FDA Electronic Submission Software (eSubmitter).

Under 21 CFR 806.10(c)(5) and 806.10(c)(11), that manufacturer or importer report includes the UDI that appears on the device label or package, or the device identifier, UPC, model, catalog, or code number and the manufacturing lot or serial number or other identification number, plus names, addresses, and telephone numbers of consignees and the dates and number of devices distributed to each. Those fields explain why a recalling firm asks consignees for quantities. They do not make a hospital or distributor that merely received a notice into an 806 reporter. The consignee job is to carry out the notice, count remaining product, and reply to the recalling firm—including when none is on hand.

Contractual notification windows, customer communication protocols, and liaison responsibilities between distributors and original equipment manufacturers (OEMs) are formally governed by quality agreements rather than dockside worksheets. For comprehensive guidance on structuring change notification and recall liaison clauses in supplier contracts, refer to our companion guide on quality agreements for consumable suppliers.

21 CFR 7.53(a)–(b) request that the recalling firm submit periodic recall status reports to the appropriate FDA district office, generally every 2 to 4 weeks unless otherwise specified, including the number of consignees responding and the quantity of products on hand when the communication was received, the number of products returned or corrected by each consignee contacted, and the quantity of products accounted for. FDA Regulatory Procedures Manual Chapter 7 states that recall communications to direct accounts and sub-accounts should include an arrangement for the consignee to report the amount of the product available and its disposition, should direct the consignee to submit a report regardless of whether any of the products are on hand, and should stress prompt return of that report. Those are recalling-firm and FDA monitoring tools. They justify a balancing worksheet. They do not make a hospital a 7.53 reporter to FDA.

To give the recalling firm accountable numbers, record six inventory states in one unit of measure:

• Opening Quantity (O): The total units in warehouse stock, central stores, and departmental supply rooms at the timestamp the recall notice was logged.

• Received Quantity (R): Units received after that snapshot, including deliveries that arrived before a vendor hold took effect.

• Issued Quantity (I): Units issued to points of use or shipped downstream, as the facility's issue records show after the opening snapshot.

• Returned Quantity (Ret): Units returned from points of use or from downstream accounts after the notice, still lot-identified.

• On-Hand Lot-Identified Quantity (H): On-hand units whose packaging still bears a readable lot that matches the notice, converted to the same unit of measure.

• Unknown / Unresolved Quantity (U): Units that are present or possibly present but not lot-identified after opening, including open bins where a DI may match and the PI is missing.

The fundamental reconciliation identity that governs the inventory worksheet is:

The table below is a labeled hypothetical. It is not a real recall, not FDA incidence, and not a named manufacturer's notice. In the example, a hospital receives notice REC-2026-088 from a fictitious firm for sterile gravity IV infusion tubing, catalog IV-200. The notice names only Lots 26A14 and 26A15. Lot 26A16 shares the same catalog number and the same hypothetical case DI but is not named on the notice, so it is out of this notice's lot scope.

All quantities are converted to individual sterile pouches (eaches). Master cases contain 50 eaches; dispenser boxes contain 10 eaches. Lot 26A15 inner boxes arrived in a mixed shipping carton whose outer shipper is not a Package DI. Inventory sits in central stores, receiving, emergency-department bins, and floor carts. The rows below balance, and the unidentified open-bin quantity stays unknown.

An examination of each row confirms mathematical integrity:

• Row 1 (Lot 26A14): Opening 200 + Received 0 + Returned 0 = 200 eaches. Issued 50 + On-Hand 150 + Unknown 0 = 200 eaches. The 50 issued units are one case issued to an ICU storeroom before the notice snapshot; they remain in the issued column until returned or otherwise accounted for.

• Row 2 (Lot 26A15): Opening 80 + Received 20 + Returned 10 = 110 eaches. Issued 40 + On-Hand 70 + Unknown 0 = 110 eaches. The received 20 eaches are two dispenser boxes taken from a mixed shipping carton; one unopened dispenser box (10 eaches) was returned from an emergency-department clean-utility shelf.

• Row 3 (Unverified Loose Stock): Opening 25 + Received 0 + Returned 15 = 40 eaches. Issued 0 + On-Hand 0 + Unknown 40 = 40 eaches. These 40 loose units came from open bins after dispenser cartons were discarded. Because pouch printing cannot confirm Lot 26A14, 26A15, or 26A16, they stay Unknown. Do not relabel them to close the gap.

• Row 4 (Unaffected Lot 26A16): Opening 100 + Received 50 + Returned 0 = 150 eaches. Issued 50 + On-Hand 100 + Unknown 0 = 150 eaches. This row is the point of the article: the same hypothetical case DI as Row 1 does not put Lot 26A16 in scope. The notice did not name that lot. Do not treat that row as worksheet authorization for patient care.

The diagram below is an identification and quantity-balance path for this hypothetical. It is not a hospital quarantine SOP and not a 21 CFR 7.53 filing path.

graph TD
    A["Recall notice received (21 CFR 7.49)"] --> B["Copy product, size, lot, code, or serial from the notice"]
    B --> C["Record opening quantity at that snapshot"]
    C --> D{"What is in hand?"}
    D -->|"Sealed device package or case"| E["Read the labeled lot next to the UDI"]
    D -->|"Shipping container"| F["Inspect inner device packages; shipper is not a Package DI"]
    F --> E
    D -->|"Open-bin pouch or missing PI"| G["Do not relabel; log unknown quantity"]
    E --> H{"Does the labeled lot match the notice?"}
    H -->|"Yes"| I["Convert to eaches; follow the notice instructions"]
    H -->|"No"| J["Out of this notice's lot scope; a DI match is not scope"]
    G --> K["Keep unknown unresolved"]
    I --> L["Balance: opening + received + returned = issued + on-hand + unknown"]
    J --> L
    K --> L
    L --> M["Report quantities to the recalling firm, including when none is on hand"]

Once quantities balance and a reconciliation owner timestamps the rows, send the on-hand, returned, and unknown counts back to the recalling firm in the form the notice requested. 21 CFR 7.53 is the recalling firm's status report to FDA, not a hospital filing. If this consignee further distributed the product, 21 CFR 7.49(d) says the consignee should carry out the recalling firm's instructions and, where necessary, extend the recall to its own consignees using the same identification.

A completed worksheet does not close a recall. 21 CFR 7.53(c) says recall status reports are discontinued when the recall is terminated by FDA; that termination is between FDA and the recalling firm. Until the recalling firm's instructions say otherwise, do not invent return, destruction, or release rules from this table. Follow the notice and responsible quality personnel. Contract fields for who notifies whom of a correction or removal belong in the published quality-agreement article, not in this dock worksheet.