Medical Device Kitting

Medical Device Kitting is the controlled assembly of specified components, packaging, labels, and instructions into a defined kit configuration. In manufacturing practice, the work includes more than putting the right number of objects into a container. It establishes which component identities and revisions were permitted, which actual lots or serials were used where applicable, and what evidence supports disposition of the resulting kits.

A kit might contain several independently packaged items, components assembled into a functional arrangement, or accessories supplied with a device. Those configurations create different manufacturing and regulatory questions. Begin by describing the physical product and operations rather than assuming that everything called a kit has the same classification, traceability granularity, packaging process, or release pathway.

These activities can intersect without becoming interchangeable. A diagnostic kit can contain a reagent whose history belongs in reagent-lot traceability, while its assembly record also captures containers, closures, instructions, and quantities. Likewise, recording a UDI does not by itself establish the component genealogy or demonstrate that an exception was resolved.

The practical boundary is the manufacturing decision: can the organization explain what it intended to build, what it actually built, and why a stated quantity is eligible for release? The workflow examples below are implementation practices, not a universal regulatory checklist. They should be adapted to the device, manufacturing role, applicable requirements, and documented quality system. Ordinary shipping confirmation is not a substitute for that manufacturing evidence.

For U.S. operations, the FDA Quality Management System Regulation overview explains that the QMSR became effective on February 2, 2026, incorporating ISO 13485:2016 by reference. Kitting procedures should therefore be evaluated against the current framework rather than assuming that historical Part 820 section numbers remain the governing structure. Incorporation by reference does not make every suggested workflow in this article a regulatory requirement.

The legal starting point is 21 CFR 820.1. Its scope includes methods, facilities, and controls for manufacturing, packaging, labeling, storage, and other specified operations involving finished devices. It also states that a manufacturer performing only some covered operations need comply only with requirements applicable to those operations. The relevant question is what the organization does, not whether its department is named assembly, warehouse, or fulfillment.

The same regulation distinguishes component manufacturers from finished-device manufacturers. Section 820.3 defines a finished device as a device or accessory suitable for use or capable of functioning, whether or not packaged, labeled, or sterilized. Consequently, calling an item a component in an internal inventory system does not settle its regulatory status. The FDA overview specifically notes that some accessories are considered finished devices.

As an implementation practice, document the product boundary, manufacturing responsibilities, applicable markets, and operations performed internally or by contractors. Then map those operations to procedures and retained evidence. The FDA QMSR reference describes the current framework. Internal labels such as DHR, eDHR, or kit traveler can remain useful organizing terms, but the document title alone does not demonstrate that the applicable records are complete.

Identity answers what the material is; eligibility answers whether this particular inventory can be used for this kit now. A correct item number can still identify material on hold, an incompatible revision, an expired lot, or a damaged package. A practical kitting control checks both questions before consumption, using the approved configuration rather than an operator’s familiarity with similar-looking parts.

Useful identity fields include the internal item number, supplier identifier, supplier lot, internal lot reference, and revision where relevant. Record the relationship between identifiers rather than replacing the supplier lot with an unexplained internal code. Define units explicitly: one carton, one bag of 50 caps, and one cap are different quantities even when they share a purchasing description.

FEFO is a selection strategy, not proof of eligibility. The earliest-expiring lot might be unsuitable for the intended kit shelf life or subject to an unresolved hold. Similarly, a supplier certificate of conformity may support a receiving decision without replacing the manufacturer’s own acceptance process. Define which evidence is needed for each component category rather than requesting identical documents for everything.

Check status again when circumstances can change between staging and use. For example, a lot placed on hold after picking should trigger assessment of staged material and affected work in progress. Preserve what status was checked, when it was checked, and which inventory was involved. A current status field alone cannot explain an earlier assembly decision.

The bill of materials defines the intended configuration, but a useful kit definition also addresses quantities, units, allowed alternatives, packaging, label versions, instructions, and relevant assembly steps. Treat the released definition as a coordinated configuration. A correct component list paired with an obsolete instruction sheet or incompatible packaging specification can still produce the wrong kit.

As a practical example, kit K100 revision C contains one connector, two protective caps, one pouch, one label, and one instruction leaflet. Work order WO1042 authorizes 240 kits against that revision. The manufacturing record should retain the revision actually authorized for WO1042, even if revision D becomes effective before the order is finished or reviewed.

• Identify the kit revision and the effective-use rule applied to the order.
• Specify component quantities in consumption units, including packaging and printed materials.
• Distinguish approved alternates from unapproved look-alike substitutions.
• Link the applicable assembly instructions, inspection criteria, and label artwork revisions.
• Define how a revision change affects staged inventory, open orders, and completed but unreleased kits.
• Record the approval and scope of any order-specific configuration exception without silently changing the master definition.

Revision effectivity needs an explicit business rule. An organization might use order authorization date, a defined production boundary, or another approved criterion appropriate to its process. Merely displaying the newest revision is insufficient because it can obscure the configuration under which existing work was performed. Conversely, freezing an order does not justify ignoring a change that requires assessment of open production.

Use change control to connect the engineering decision with shop-floor consequences. If a replacement cap changes fit, handling, packaging, or labeling, evaluate those relationships before treating it as an interchangeable purchase. For controlled temporary alternatives, specify affected orders, quantities, expiration of the authorization, and required checks. Repeated temporary exceptions should prompt review of the underlying configuration or supply strategy rather than becoming an undocumented second BOM.

A practical execution sequence links physical activity to contemporaneous evidence. It should be clear when inventory is reserved, issued, incorporated, rejected, returned, or released. These are different events. Recording all issued material as consumed at order start can hide unused stock, damaged pieces, and partially assembled kits unless subsequent transactions explain what actually happened.

Before assembly, use line clearance appropriate to the operation to address leftovers from previous work, especially printed materials and visually similar parts. During assembly, record the actual lot change boundary rather than relying on a planned allocation to reconstruct usage later. A reservation shows intent; it is not necessarily evidence of incorporation.

At interruptions, identify the partially completed population and its completion state. A shift handover should distinguish untouched staged components from open kits and finished kits awaiting inspection. This makes restart decisions more precise and avoids treating everything on the bench as either unrestricted inventory or completed output.

Lot genealogy connects actual component usage to identifiable outputs. Design it to answer both directions: which components entered this kit population, and which kit populations received this component lot? The granularity should reflect applicable requirements and the information needed for investigations. Do not assume that every component needs an individual serial number simply because the finished product is a medical device.

For manufacturers subject to the provision, 21 CFR 820.35(c) requires the UDI to be recorded for each medical device or batch of medical devices. Keep that obligation distinct from the practical design of component-level genealogy. A UDI field is not an instruction to serialize every cap or leaflet.

For example, if a 240-kit batch uses connector lots A and B, recording both against the whole batch establishes a broad relationship. It does not prove which individual kits contain A. To support a narrower conclusion, preserve actual consumption boundaries and identifiable, segregated subgroups. Otherwise, describe the uncertainty rather than reconstructing unsupported precision.

Test retrieval in both directions, including removed components and replacement events. Preserve original usage and subsequent corrections so a reviewer can distinguish what was first assembled from what remained in the final configuration.

Consider the illustrative K100 revision C order for 240 kits. Each kit contains one connector, two caps, one pouch, one label, and one leaflet. All 240 kits are assembled. Inspection and disposition identify 232 accepted kits, five held kits, and three kits designated for scrap. There are no unfinished kits or unrecorded transfers in this example.

For each component, use: issued quantity = quantity incorporated in assembled kits + loose or process waste + unused quantity returned + unexplained difference. Incorporated quantities include components inside accepted, held, and scrap-designated kits. This prevents counting those components again as loose waste.

The cap balance is 500 = 480 + 4 + 16 + 0 pieces. Within the 480 incorporated caps, 464 are in accepted kits, 10 in held kits, and six in scrap-designated kits: 232 × 2 + 5 × 2 + 3 × 2 = 480. Those six caps are not also included in the four loose damaged caps.

The output balance is separately 240 = 232 + 5 + 3 kits. The accepted fraction at this decision point is 232 ÷ 240 × 100 = 96.67%; held output is 2.08%, and scrap-designated output is 1.25%. Do not label the accepted fraction first-pass yield unless the records establish that definition, including how rework is treated.

The 15 wasted labels comprise 12 setup labels and three spoiled labels in this example. Their disposition is separate from labels attached to the three scrap-designated kits. Maintain supporting counts by item and relevant lot rather than adding unlike material units into one grand total.

If only 15 unused caps were physically returned, the unexplained difference would be one cap. Investigate that discrepancy; do not automatically post it as scrap. Even zero unexplained differences establish only a balanced account, not acceptable identity, packaging, or release evidence. Yield reconciliation supports disposition but does not replace it.

Exceptions should identify the affected population, not merely describe a problem. A record saying wrong cap found is less useful than one identifying the order, cap item and lot, time window, bench or station, and potentially affected output groups. As a practical containment step, separate confirmed affected kits from other populations while assessing whether the evidence supports a narrower boundary.

Common scenarios require different responses. A shortage may leave work incomplete without making the available components defective. A wrong-lot selection raises genealogy and eligibility questions. A damaged pouch concerns packaging condition. An unauthorized substitute raises configuration questions even if the physical count balances. Route each issue through the applicable nonconformance or deviation process rather than using a generic inventory adjustment to close it.

• Define what is held: component inventory, open kits, completed output, or several populations.
• Record the reason, discovery time, responsible decision-maker, and affected quantities.
• Distinguish correction of a recording error from physical replacement or reassembly.
• Authorize the disposition and identify the instructions and checks needed to execute it.
• Verify the resulting configuration, update genealogy, and reconcile removed and replacement materials.
• Document the final quantity and status without overwriting the original event history.

For physical replacement, preserve the original consumption event, the removal event, and the new incorporation event. If a component is removed from a kit, assess its disposition rather than automatically returning it to unrestricted stock. Package opening, handling, identity loss, or exposure may affect whether reuse is appropriate. Rework can also change which inspections or packaging operations need to be repeated.

An audit trail or controlled correction history should explain who changed the record and why. Backdating a replacement to make the original build appear correct destroys the distinction between initial assembly and final configuration. Repeated exceptions may justify a broader investigation or CAPA, but not every isolated discrepancy needs an identical escalation pathway. Use the quality system’s criteria to assess recurrence, significance, and the adequacy of the correction.

For covered manufacturers, 21 CFR 820.45 requires documented procedures addressing labeling and packaging activities. It requires examination for accuracy before release or storage where applicable, including identification, expiration date, storage, handling, and additional processing instructions. It also requires operations to prevent mixups and documented labeling inspection results. These are regulatory obligations, not merely suggested reconciliation practices.

Practical implementation connects the approved artwork and packaging configuration to the order actually executed. Inspecting a printed label against yesterday’s reference does not establish conformance to today’s authorized configuration. Likewise, counting 240 pouches does not demonstrate that all 240 packages meet their specified acceptance criteria. Separate printed-material accountability from content accuracy and packaging condition.

Sterility adds another boundary. The FDA’s guidance on sterility information in 510(k) submissions contains nonbinding recommendations and addresses devices labeled sterile that undergo industrial terminal sterilization based on microbial inactivation. It is not a general kitting procedure or proof that assembling separately sterile items establishes the sterility of the overall kit.

The FDA recognition entry for ISO 11607-2 describes a scope covering development and validation of packaging processes for terminally sterilized devices, including forming, sealing, and assembly. That process-validation subject is different from documenting that a particular assembly order used the correct parts. Both questions may matter, but their evidence is not interchangeable.

Shelf-life reasoning also needs care. The FDA recognition entry for ASTM F1980-21 describes accelerated-aging information that may support sterile-barrier-system expiration claims; its scope does not address device-material interaction compatibility. As a practice, assess component limits, packaging evidence, processing effects, storage conditions, and the supported finished-kit claim together. Selecting the earliest component date can be a conservative screening rule, but it does not establish a shelf life for an unassessed kit configuration. Link the relevant packaging validation evidence rather than treating assembly completion as proof of packaging performance.

Release review should answer a defined question: which identified kit population, in what quantity, is being authorized for the next permitted use or distribution step? As an implementation practice, separate assembly completion, inspection acceptance, quality disposition, and inventory availability. A single complete checkbox can otherwise conceal whether required evidence is missing or whether part of the order remains held.

The evidence may reside in several controlled records rather than one large attachment. What matters operationally is that the reviewer can navigate the relationships and identify the applicable versions and results. A device history record or electronic release record can serve as an organizing structure, provided it does not substitute a summary status for the underlying evidence.

FDA’s QMSR frequently asked questions explain that investigators may review QMS records created before February 2, 2026. As a practical consequence for record organization, retain the ability to interpret historical configurations and transactions. Migrating to a new record format should not sever the links needed to understand an earlier kit build.

In the worked example, a review could authorize 232 identified kits while the five held kits remain unavailable, if the organization’s applicable process supports that scoped decision. Record the segregation and scope explicitly. Do not let an order-level released status inadvertently make the held quantity selectable for dispatch.

Start with one representative kit family and map its physical material movements before designing screens or forms. Include ordinary assembly, lot changes, interrupted work, shortages, damaged packaging, and rework. Assign ownership of kit definitions, inventory disposition, production records, and release decisions. The following implementation checklist is a practical starting point, not a universal software specification or regulatory mandate.

1. Define the product and process boundary, including which operations occur at suppliers or contractors.
2. Approve the kit structure, units of measure, revision effectivity, and alternate-component rules.
3. Specify eligibility checks and when a changed material status requires reassessment of staged or consumed stock.
4. Choose justified lot or serial granularity and define identifiable output groups for traceability.
5. Separate reservations, issues, actual incorporation, removals, returns, scrap, and completed-kit quantities.
6. Establish interruption, exception, rework, and correction workflows that preserve original events.
7. Define labeling and packaging checks, applicable processing evidence, and release authority.
8. Challenge the process with wrong items, held lots, duplicate entries, missing quantities, and partial release.
9. Verify bidirectional trace retrieval and record interpretation before expanding to more kit families.

Software evaluation should ask demonstrable questions. What happens when a staged lot is put on hold? Can a revision change be assessed without rewriting the history of open orders? How are removed components distinguished from record corrections? Can the reviewer identify the precise quantity released while another quantity remains held? Use controlled test scenarios with expected results rather than accepting a dashboard or barcode demonstration as sufficient evidence.

S.G. Systems sells software, not kitting fulfillment. A medical-device manufacturing software evaluation should therefore examine the intended workflow and evidence responsibilities, not assume outsourced assembly or shipping services. Define system boundaries between inventory, execution, quality, and other records, including who owns corrections when interfaces disagree. Implementation acceptance should address the configured intended use; a product demonstration alone does not establish that an organization’s process or system is validated. Track unresolved test findings and their disposition before operational acceptance.