ERP creates a new SKU because the pack count changed. Marketing creates a new model name because a feature was added. Engineering calls two versions equivalent because the platform is shared.

None of those statements is a regulatory conclusion.

The boundary should be built from the device’s intended purpose, basic design and essential characteristics, safety and performance, and the evidence that covers the differences. SKU count is an input to the reconciliation—not the answer.

The boundary test

For every model difference, document five decisions.

**1. Intended purpose** Has the patient population, user, clinical purpose, use environment, anatomical site or claimed outcome changed?

**2. Design identity** Does the model retain the same operating principle and essential design characteristics? A change in size may be different from a change in patient-contacting material, energy source or measurement algorithm.

**3. Safety and performance** Could the difference create a new hazard, modify a risk control or change performance? The assessment should consider impact, not the number of changed drawings or software lines.

**4. Evidence coverage** Which verification, validation, risk, clinical or performance evidence covers the model? If a representative configuration was tested, explain why it represents the remaining range.

**5. Grouping and identification** Does the proposed family, system or IVD grouping meet the applicable SFDA criteria? What are the separate consequences for labels, UDI/Saudi-DI, packaging, catalogues and master data?

Do not use a universal shortcut

A colour option may require limited assessment. A new patient-contacting material may affect biological evaluation and risk. A sterile version cannot be treated as a packaging preference. A software update that changes clinical output may need a much deeper assessment than its version number suggests. A new pack quantity may change packaging and UDI data without creating a new device.

These are starting points, not automatic outcomes. The product evidence and current requirements control the conclusion.

Create a model boundary record

A defensible record should list the legal manufacturer, trade name, model, SKU, catalogue code, intended purpose, class, relevant nomenclature, difference description, risk impact, supporting evidence, proposed grouping and regulatory disposition.

It should also identify every system affected by the decision: technical documentation, MDMA scope, label, IFU, UDI/Saudi-DI, ERP, distributor catalogue and tender mapping.

Finally, test the record in reverse. Pick an invoice SKU and trace it to the physical label, approved IFU, technical file and authorisation scope. A grouping strategy that cannot identify a shipped product is not operationally controlled.

Use boundary cases to challenge the record before approval. Compare the smallest and largest size, a sterile and non-sterile configuration, the current and proposed software release, and an accessory sold separately. For each pair, state which evidence remains representative and which assessment must be repeated. Then assign one owner to reconcile engineering, regulatory, UDI, ERP and catalogue changes. Without that ownership, each system can remain internally correct while the product presented to the market becomes inconsistent.

Requirement versus professional assessment

SFDA MDS-G028 provides criteria for medical-device and IVD grouping. UDI requirements govern device identification through a separate but connected control. Neither the commercial SKU nor the product name alone determines whether a model is a new device.

Basier can build the model/SKU crosswalk, facilitate difference assessments and review consistency across technical and commercial records. Basier cannot guarantee that SFDA will accept a proposed grouping or assign UDI on behalf of the responsible manufacturer.

Official sources

01
SFDASFDA MDS-G028
Document date
Last verified

Turn the requirements into a clear plan for your case

Start with an assessment of the device and available evidence before deciding on submission.

Basier Regulatory Services