Multi-component Kit Classification and Documentation

A modern diagnostic kit is no longer a single bottle of reagent: lyophilised components, reconstitution solutions, calibrators, control materials, microplates, magnetic particles, pipette tips and the software processing the data all come out of the same box. In some sets the components come from different manufacturers; in some the software lives in the cloud; in some the consumables are delivered as mandatory companions for the kit to run. This structure complicates two simple questions: is classification done over the whole or over the components, and is the declaration given as a set or line by line? A wrongly built set file produces confusion at customs and a scope dispute at inspection. This article explains the classification logic of multi-component kits, the documentation rules for multi-vendor components, the status of accompanying software and consumables, and the declaration approach at import.

Who is this for?

This guide is for every role designing, assembling, importing and using kit sets. Manufacturers and representatives build the regulatory counterpart of the set architecture. Distributors doing set assembly carry the documentation load of the combining operation. Importers tie the declaration structure and the component match into the customs file. Regulatory teams run the set and component classifications in separate files. Quality units track component batch traceability and set integrity in acceptance checks. Laboratories show with records that they used the set's components in the right combination. Procurement asks the set guarantee question in part-based alternative supply. Customs brokers build the match between the set declaration, invoice and labelling. At audit the question is set-focused: what is inside this box, in which status is each item, and with what evidence does the whole sit together?

Which products does it cover?

The scope is all diagnostic kits and sets carrying more than one component. Clinical chemistry and immunoassay sets: the reagent R1-R2 structure, together with calibrator and control. Molecular diagnostic kits: extraction, amplification and detection components, internal controls and the software. Haematology and coagulation sets: reagent, calibrator and tube combinations. Rapid test cards: cassette, buffer and sample collection material packages. Microbiology kits: culture media, identification and susceptibility components. Also sets composed of components from different manufacturers, component groups ordered for researchers' own combinations, and platform-specific consumable-set structures. The accompanying material group: mandatory pipette tips, tubes, dilution containers and device-specific carriers. Software: the analyser firmware the set runs on, data processing and reporting software, cloud services. Each component group passes its own status question and takes its line in the set file.

When does it apply?

The set rules apply to every multi-component product procurement; the moments that weigh are these. At a new set launch the component inventory and classification decisions build the first file. When the set's composition changes, when a component's manufacturer or nature changes, the set file is updated and the class re-read. When part-based sales begin, the declaration structure is reviewed: a component sold independently must additionally be assessed in its own status. Adding a component from a different manufacturer demands a compatibility rationale and test evidence. If a software update affects the diagnostic output, it reflects into the set classification. When a component is ordered separately, a match record with the main set is built; using unmatched components exits the performance claim. At import inspection the triple of set content, invoice lines and labelling is compared. In stock management, component-based expiry and batch tracking is the daily protection of set integrity. When the set splits, that is, when components are procured on different calendars, the record chain must show it openly.

Legal framework and authority

The frame comes from the European in vitro diagnostic regulation Türkiye applies nationally. The regulation recognises the concepts of system and set: products combined for use together are assessed within their own whole; the classification rules are applied to the set's diagnostic purpose. Each component, if it enters the diagnostic product definition, is subject to its own conformity assessment; the party forming the set carries the rationale of integrity and inter-component compatibility in the technical file. Combining components from different manufacturers is supported by change management and risk analysis. Software, to the extent it carries diagnostic function, is included in the regulation as part of the product. The competent authority is TİTCK: it applies the legislation, runs registrations and performs market surveillance. On the customs side the declaration structure is determined by the tariff legislation's set and component rules: sets delivered together can be declared under a single position, components of separate commercial character under their own positions. Import inspection runs within the product safety communiqué frame. Current guides must be tracked from official sources.

Step-by-step process

1. Extract the set's component inventory: each component's name, manufacturer, nature and function in the set in one table.
2. Assess each component's status and class: its place in the diagnostic chain and the risk it carries.
3. Determine the set's class as a whole: the component producing the highest-risk diagnostic function governs.
4. File the compatibility rationale and test evidence for components from different manufacturers.
5. Assess the software component: if it produces diagnostic decisions, track it under its own heading in the set file.
6. Clarify the consumable companionship: functional and mandatory consumables into the set file, general consumables in a separate status.
7. Decide the declaration structure: set declaration or component lines; file the decision with its rationale.
8. Build the labelling architecture: set label, component labels and the mandatory Turkish information.
9. Define the traceability plan: set and component batch matching, acceptance and use records.
10. Tie the change triggers: when composition, manufacturer or software changes, the file is updated.

Document checklist

• Component inventory table: identity, manufacturer, nature, function.
• Status and class decision rationale for each component.
• Classification file of the set as a whole and the risk analysis.
• Compatibility test records of multi-vendor components.
• Set declaration of conformity and certificate, in a structure covering the components.
• Software assessment: version, function and diagnostic role.
• Consumable companionship analyses and rationales.
• Declaration structure decision: set or component line, with rationale.
• Label set: set and component labels, with Turkish information.
• Batch traceability scheme and acceptance control records.

Parties and responsibilities

The most fragile link is between assembly and acceptance: if the components do not match the right set with the right batches, the integrity rationale in the technical file finds no counterpart in the field. The record chain becomes physical here.

Exceptions and edge cases

The edge of set practice is full of real procurement questions. Ordering a component on its own disperses the set status: a component sold independently is assessed in its own status and position. Using a component taken out of a set in another set, without a compatibility rationale, is outside the performance claim. Replacing a mandatory consumable with a different-brand equivalent can contradict the manufacturer's instruction and requires validation. In sets where the software lives in the cloud, version management and access conditions are defined in the file; since the set does not run without the computer, the software companionship is as real as a physical component. Loss of a component during transport or separate delivery breaks the set integrity; the acceptance record rejects the incomplete set. Sample collection material, as the head of the diagnostic chain, carries class effect in some sets. Sourcing the control material outside the set brings the third-party rules in. Components remaining as the kit runs out must be entered into the traceability table in partial renewal orders. In every case the tool is the same: the component inventory and the written matching record.

Common mistakes

The most common mistake is treating the set as a single product and never building the component inventory; at audit the content question goes unanswered. The second is adding a multi-vendor component to the set without compatibility evidence. The third is dropping the software from the file; software carrying diagnostic function is the product itself. The fourth is not updating the declaration structure when moving to part sales; the component is imported under the wrong position. The fifth is skipping the consumable companionship analysis; the mandatory consumable is part of the set file. The sixth is not recording the component batch match; the traceability chain breaks. The seventh is reducing the label architecture to a single label; the components' own identities must remain on the labelling. The eighth is not tying the set content change into change management; the file lives on with the old composition.

Important notice

This article is general information, not legal or customs advice; for set and component assessments, the applicable legislation, tariff rules and where necessary the competent authority's opinion must govern. GTİP codes and set examples in the text are for orientation; the GTİP examples are not binding and classification must be reasoned for every set. Legislation can change; official sources must be checked before any transaction.