Saudi Arabia Sfda Medical Device Registration Service
Saudi SFDA medical device registration service means preparing and executing a Medical Devices Marketing Authorization (MDMA) filing through the Saudi Food and Drug Authority (SFDA). Marketing authorization is a product decision; it is not the same as a manufacturer, authorized-representative, importer or distributor establishment licence. A device ordinarily must be registered and obtain MDMA before it is made available for distribution or use in Saudi Arabia.
Start with a controlled list of exact products, models and versions, intended purposes, risk classes, manufacturer and proposed applicant. Do not submit a catalogue first and resolve those questions later. This guide focuses on filing execution for general medical devices; in-vitro diagnostics (IVDs) have distinct technical evidence.
Identify the applicant and account owner
MDS-REQ1 permits submission by a licensed local manufacturer, an overseas manufacturer, or its Saudi authorized representative (AR) if the overseas manufacturer chooses that route. The filing party must verify the applicable account and licensing prerequisites in GHAD. The foreign manufacturer remains responsible for the technical evidence. Do not assume that an importer’s or consultant’s licence itself authorizes it to lodge every MDMA application.
Assign responsibility before sharing access or releasing the dossier:
- Manufacturer — approves intended purpose, classification, declarations, QMS and the current technical file.
- Applicant / licensed AR where applicable — controls GHAD submission, notices, payment and response routing.
- Importer or distributor — checks its own required establishment permissions and the authorized product scope; importing is not itself the MDMA decision.
- SFDA — reviews the submitted evidence, may request clarification and issues or declines the authorization.
Select the application route before assembling the file
The ordinary MDMA route uses the Saudi technical dossier and risk classification. A separate SFDA reliance guidance dated 9 September 2026 offers a potentially reduced assessment for qualifying existing approvals from specified recognized regulators. It is an eligibility test, not an automatic conversion of a CE certificate or FDA clearance into Saudi authorization. For reliance, the authorized device must have identical design, manufacturing process and intended use, satisfy Saudi-specific requirements and avoid the stated exclusions.
| Route | Decision gate | Filing consequence |
|---|---|---|
| Ordinary MDMA | No qualifying reliance case, or reliance not selected. | Compile Saudi-classified dossier and submit the applicable MDS-REQ1 evidence. |
| 2026 reliance pathway | Valid approval from a listed recognized regulator; identical technical aspects; Saudi requirements met; no excluded route/device or unresolved safety restriction. | In the GHAD overview identify regulator approvals and upload evidence plus the SFDA Reliance Form; SFDA may still request more. |
| Do not claim reliance | Self-declaration without eligible third-party assessment, predicate-equivalence-only pathway, custom-made device, significant regulator safety restriction or potentially excluded SaMD/AI device. | Use an appropriate ordinary filing assessment; check the exact exclusion and ask SFDA where uncertain. |
The September 2026 guidance lists regulators in Australia, Canada, the EEA, Japan, the UK and the USA, subject to future SFDA updates. For a multi-device submission, apply the newer MDS-G028 bundling criteria, not merely the fact that products share a brand.
Build a device-specific technical dossier
The technical-documentation index should follow MDS-REQ1 Annex 3 for general devices, with the depth appropriate to the class and characteristics of the product. Use one device master-data sheet to keep GHAD fields, labeling, certificates, test evidence and catalogue references consistent. Some low-risk, non-IVD devices qualify for a reduced initial upload under MDS-REQ1; sterile, measuring, reusable-surgical and novel devices are not covered by that simplified treatment. SFDA can request the full technical file.
| Dossier block | Evidence / reconciliation check |
|---|---|
| Identity and scope | Legal manufacturer, intended purpose, Saudi risk class, model/SKU list, accessories, grouping rationale; align with labels and portal entries. |
| Safety and performance | Essential Principles checklist linked to tests, risk-management file and applicable verification/validation evidence. |
| Design and quality | Manufacturing and design descriptions, relevant sites, controlled technical file and ISO 13485-based QMS documentation. |
| Clinical and user information | Clinical evaluation where applicable, labels, IFU, language and local power/storage/transport suitability; justify omissions. |
| Lifecycle and approvals | Post-market surveillance plan and reports, existing foreign approvals if any, change history and traceability of each uploaded version. |
Submit through GHAD and manage SFDA questions
Use the live GHAD Medical Devices Marketing Authorization service. File preparation, portal acceptance, SFDA technical review and certificate issuance are separate milestones. SFDA’s service page indicates 35 working days for the MDMA service; the 2026 reliance guidance states 35–60 working days for a complete reliance application. Neither is a contractual guarantee or a prediction for a file with questions, missing information or route changes.
- Freeze the model list, intended purpose, risk class and proposed grouping against the latest labeling.
- Confirm applicant eligibility, establishment/account identifiers and the person who can answer SFDA queries.
- Index the dossier; resolve contradictions and decide whether the 2026 reliance criteria genuinely apply.
- Complete the MDMA application in GHAD; for reliance, enter recognized-regulator approval data and upload the Reliance Form.
- Pay the assessed SFDA fee when requested; log submission ID, queries, deadlines, responses and replacement file versions.
- Check the issued MDMA certificate against manufacturer, models, intended scope and validity before commercial release.
Avoid common preventable filing delays
These defects should be checked before pressing submit. Each may require a corrected evidence package rather than a superficial portal edit.
| Trigger | Corrective control |
|---|---|
| SKU, label and application disagree | Reconcile model numbers, manufacturer identity, intended purpose and revision across every attachment. |
| Ineligible grouping | Test each family/system/pack against MDS-G028; for a general-device family the guidance includes limits of five technical files and 50 items plus substantive sameness criteria. |
| Reliance chosen from foreign logo alone | Verify approval type, identical technical configuration, Saudi labeling and exclusions; retain evidence of each decision. |
| Incomplete evidence or unanswered SFDA query | Maintain an evidence owner, versioned response log and explicit open-items list; recheck the file after each replacement. |
Maintain the authorization after a decision
MDMA issuance is not the end of regulatory work. Maintain a controlled register of approved models and labels, expiry and renewal dates, vigilance and post-market records. Under MDS-G012, significant changes are reported for SFDA approval and non-significant changes notified according to the stated procedures; classification of the change must follow the manufacturer’s QMS and current SFDA guidance. Do not distribute a significantly changed device before the required SFDA approval.
What a registration support mandate should deliver
A well-defined filing assignment should produce an agreed SKU/application-scope register, applicant and account verification, indexed document request, gap-and-decision log, portal submission evidence, SFDA question tracker and final certificate/scope check. Regulatory advice, formal authorized representation, establishment licensing, import operations and product-specific IVD work are separate workstreams unless expressly included. Filing support cannot guarantee SFDA approval.
For upstream classification and regulatory strategy, see SFDA registration consulting. For IVD technical filings, use the dedicated IVD registration service; for a wider Saudi product-regime map, see Saudi product compliance and market access.
Official SFDA sources
Frequently asked questions
Can we file without an EU or US approval?
An overseas approval is not a general prerequisite for the ordinary Saudi MDMA route under MDS-REQ1. It is, however, central to eligibility for the new reliance pathway; the required Saudi evidence still applies.
Can one MDMA cover several models?
Sometimes. First identify whether the products form an eligible family, system or procedure pack under MDS-G028. A shared brand alone is not enough; check intended use, manufacturer, risk class and the relevant technical-file and item limits.
Who submits if our factory is outside Saudi Arabia?
MDS-REQ1 identifies the overseas manufacturer and, if it chooses, its licensed Saudi authorized representative among possible applicants. Verify current GHAD permissions, AR arrangements and separate establishment licences before assigning the filing.
Does an FDA clearance automatically qualify for reliance?
No. MDS-G030 excludes approvals based primarily on predicate equivalence and certain other routes/devices. Review the approval basis, technical identity, safety status and Saudi-specific requirements before selecting reliance.
May we ship or sell after receiving a submission number?
A submission receipt is not MDMA. Check the issued authorization, its product scope and the relevant establishment/import conditions before making a device available in Saudi Arabia.