QMS for Saudi Importers, Distributors and Authorized Representatives

One of the most persistent misconceptions is that ISO 13485 and quality management belong to the manufacturer alone. In Saudi Arabia, quality does not end at the factory gate. Regulatory information, importation, storage, distribution, complaints, incidents, recalls and customer traceability pass through local establishments. If those interfaces are unmanaged, a capable manufacturer can still have a weak market response.

The scope of MDS-REQ10 covers QMS inspection and audit requirements for manufacturers, authorized representatives, importers and distributors. It also cites Article 22 of the Medical Devices Law, which requires establishments seeking to circulate medical devices in the Kingdom to adhere to a QMS.

The role shapes the system

Each establishment does not need a copy of the manufacturer's QMS. It needs a system proportionate to its regulatory role, licensed activities, device categories and actual operations. An authorized representative concentrates on regulatory communication, manufacturer representation and post-market coordination. An importer adds controls for shipments, clearance and receipt. A distributor needs disciplined storage, delivery, traceability, returns and complaint intake. One company may hold several roles; its scope, responsibilities and records must show that reality.

SFDA guidance MDS-G024 explains that an organization should identify its regulatory role and the roles performed by suppliers, apply a risk-based approach and provide the resources needed for an effective QMS.

A minimum evidence map

To turn this analysis into a product-specific plan, review Authorized Representative and Local Role Support and the related regulatory insight.

Five shared controls

Despite different roles, the operating backbone is familiar: document and record control; task-based competence; supplier and service-provider control; nonconformity and CAPA; internal audit and management review. The difference is not the procedure titles. It is their scope, decisions and execution evidence.

A distributor's complaint procedure, for example, does not need to repeat the manufacturer's technical investigation. It does need to capture device and lot identity, the event and user outcome, preserve a sample when needed, escalate within defined times and prevent sales staff from issuing an unapproved technical explanation. Those operational details separate a tidy file from a usable system.

Quality agreements are part of the QMS

Where the process is distributed among a manufacturer, authorized representative, importer and distributor, responsibilities cannot remain in memory or scattered email. A quality agreement defines who notifies whom, which data must travel with a case, who decides reporting or field action, how changes are assessed, who retains distribution records and how recall readiness is tested. The agreement does not transfer statutory responsibility, but it prevents a gap between parties.

A certificate does not replace the system

ISO explains that ISO 13485 specifies a medical-device QMS and that certification is not a requirement of the standard itself, although regulators may require evidence or certification. In Saudi Arabia, MDS-REQ10 sets routes for QMS conformity evidence according to establishment role and device category. The certification or inspection decision must therefore follow the licensed activity, product scope and current Saudi requirement—not a generic interpretation.

More importantly, a certificate alone does not prove that complaint information flows, inventory is traceable or a change is assessed before implementation. Review records and outcomes, not the certificate title alone.

Begin with one end-to-end flow

Map the movement of the device and its data from shipment receipt to the last customer, then reverse the path for a complaint or recall. Identify systems, handoffs, fields that cannot be lost and the owner at each step. Write procedures after that. The QMS then becomes a controlled description of real work instead of a template beside it.

How Basier supports Saudi establishments

Basier builds the QMS from the licensed role and product scope. We define interfaces with the manufacturer and local parties, develop the procedures and records the operation needs, and test them through shipment, complaint, recall and regulatory-change scenarios. We also prepare an inspection evidence map, training plan and management indicators. We do not copy a manufacturer's system onto a distributor; we build a system that proves what the establishment actually does and what it must control.

References: [1] [2] [3]