Saudi Arabia's device AR carries a licence of its own

One law now, after a decade under an interim one

Saudi Arabia regulated devices for years under a Medical Devices Interim Regulation, and that framework was formally replaced by the Law of Medical Devices and Supplies, issued through Royal Decree M/54 — the instrument the Saudi Food and Drug Authority's own device programme now runs on. The newer law carries forward most of the interim regulation's substance rather than rebuilding it from scratch, and SFDA's device classification still runs the same four-tier structure, Class A through D, low risk to high, that GHTF-style regimes elsewhere in this series already use — unsurprising, given SFDA's own participation in the Global Harmonization Working Party and the wider IMDRF process the rule set descends from. What changes market to market isn't the classification logic. It's how many separate instruments a device needs before SFDA lets it reach a shelf.

Two authorizations, not one

SFDA splits the marketing decision from the establishment decision, the way Health Canada splits a device-level MDL from a company-level MDEL. A Medical Device Marketing Authorization, the MDMA, is the product-level clearance — the decision that a specific device can be marketed in Saudi Arabia, tied to the classification and technical file SFDA reviewed to reach it. A Medical Device Establishment Licence, the MDEL, is a separate, entity-level credential naming the party responsible for an establishment activity: manufacturing, importing, distributing, or acting as authorized representative. A device can hold a valid MDMA while the establishment behind it has let its own MDEL lapse, and the reverse is just as possible — neither credential's status is inferable from the other's. Getting to an MDMA in the first place still runs through a conformity assessment: for the higher classes, that means a quality management system certified to ISO 13485 by an SFDA-recognized conformity assessment body, reviewing the technical file the way a notified body would under the EU's own framework, before the marketing authorization itself is granted.

The representative isn't just a name on the label

A foreign manufacturer with no Saudi legal presence has to appoint an authorized representative, and that appointment is a heavier commitment than the EU's own authorised-representative mandate asks for on paper: the Saudi representative doesn't just accept a set of named duties, it has to hold an MDEL of its own, issued by SFDA in the representative's name, before it can act as anyone's authorized representative at all. The representative's name, address, and contact details are printed on the device's technical documentation, labeling, and instructions for use — the same information a European authorised representative carries — but only in Saudi Arabia's system is the party behind that printed line independently licensed to occupy the role, rather than merely bound to it by a signed mandate.

Renewal runs on the MDMA's own shorter clock

An MDMA is typically valid for three years, or for whatever shorter period the underlying reference approval it was built on carries, whichever comes first — a ceiling a manufacturer relying on a foreign clearance has to track against the foreign approval's own status, not just against SFDA's three-year default. The MDEL behind it runs on its own separate renewal schedule, tied to the establishment rather than to any one product. A file that tracks a single “Saudi Arabia: authorized” status has usually merged a product-level clock that can be shorter than three years with an establishment-level licence that doesn't move on the same date at all.

Where this meets the file

A Saudi Arabia registration record needs the MDMA's own expiry — capped by whichever reference approval it leaned on — tracked apart from the authorized representative's MDEL renewal, with the representative's licence number recorded as its own field rather than folded into a generic contact entry. A cross-border registration tracker built to carry that split, alongside the launch catalog's other device-registration templates, is previewed there now. If your program tracks SFDA's two credentials differently, the shelf takes that correction directly.