Uzbekistan Medical Device Import and Customs Clearance: Consistency Rules and Pre-shipment Workflow

1. Key takeaways

In Uzbekistan, devices without national registration cannot be cleared through customs, stored, distributed, sold or used in medical practice. The verification focus at customs clearance is consistency across three documents: the product name on the customs declaration, the product name and specifications on the invoice, and the registered scope in the state register entry must all point to the same registration unit. Any single inconsistency exposes the shipment to detention. In practice, this check is where theoretical regulatory compliance meets operational reality: a device can hold a perfectly valid certificate and still be stopped at the border because the commercial paperwork names the product differently from the register. Importers who use informal or translated product names on invoices, or who ship configuration variants that were never covered by the certificate, discover that customs verification reads the register entry literally. Beyond the three-document check, two additional import-side obligations operate in parallel — batch information must be entered into the dedicated electronic system of the Center by the authorized representative for products of enterprises without a valid conformity certificate, and for devices subject to national UDI coding, the codes must be applied before import. All of these steps sit upstream of the physical clearance event, which means the customs outcome is determined long before the truck arrives at the border. Import planning should therefore treat registration coverage, document consistency, batch data entry and coding as a single integrated pre-shipment workflow owned jointly by the manufacturer and the local representative. The division of labor matters as much as the checklist itself: the manufacturer controls what is registered and what is actually built, the representative controls what is entered into the systems and what is declared to the operator, and the importer controls how the goods are described in commercial documents. Where these three parties work from a shared specification of the registered unit — the same model naming, the same configuration description and the same register reference — clearance becomes a routine confirmation rather than an investigation.

2. Legal basis

3. Expert insights

Insight 1: registration covers the unit, not the product name. Whether a shipment is covered by a registration is judged against four elements: the manufacturer, the manufacturing address, the model (including configuration) and the intended use. Any difference in any element makes the device unregistered. This is why the same configuration requirement discussed elsewhere in this series matters so much — configuration drift affects not only eligibility for recognition routes but also customs clearance, because the register entry describes a unit that the shipment no longer matches.

Insight 2: electronic batch data entry is a standalone pre-import action. Resolution No. 628 requires that for products of enterprises without a valid conformity certificate, the authorized representative must enter batch, name, dosage form, international nonproprietary name, quantity, price and production date into the dedicated electronic system of the Center (or provide it in paper form), with the accuracy of the information being the responsibility of the manufacturer. This is a pre-import obligation that is easily overlooked because it does not appear anywhere on the registration certificate itself.

Insight 3: coding must be completed before import. For devices subject to national UDI coding, the codes must be applied before import, and the representative must conclude an agreement with the national digital coding operator and register every imported batch. This moves coding from a sales-side action to an import-side action, and shipment plans must include coding time. Shipping first and coding later is not workable under the current framework.

Insight 4: hospital procurement and customs increasingly share register data. The register is public information, and both hospital tenders and customs clearance cross-check against it. The practical effect is that any inconsistency between the register and the physical goods is detected repeatedly at multiple checkpoints, not just once at clearance. A data discipline that keeps commercial documents aligned with the register entry therefore pays off across the entire distribution chain.

4. Practical recommendations

1. Run a three-document consistency check: customs declaration, invoice and state register entry verified before shipment.
2. Have the representative complete electronic batch data entry before every import.
3. For devices subject to coding, include coding time in the shipment plan to ensure completion before import.
4. Where models, specifications or configurations change, complete the variation filing before shipping.
5. Agree a fixed wording of customs product names with the importer, so the same product is never declared under different names.

5. Verification checklist

• □ Customs declaration, invoice and register entry checked for three-document consistency
• □ Batch information entered into the electronic system by the representative
• □ Coding completed before import for devices subject to coding
• □ Variation filing completed before shipment where models, specifications or configurations changed
• □ Fixed wording of customs product names agreed
• □ Status of the agreement between the representative and the national digital coding operator confirmed

GRZAN supports manufacturers, importers and authorized representatives with medical device import, customs clearance preparation and market access in Uzbekistan. For assistance with your product portfolio, contact info@grzanglobal.com.

Regulatory information verified as of October 29, 2026.