Product Identity Requirement: Consistency with the Reference Approval

1. Key takeaways

The core premise of the abbreviated pathway is full product identity: the product submitted in Mexico must be identical to the product approved by the reference regulatory authority in its design, materials, manufacturing process and packaging. If any of these elements differs, the application will be redirected to the standard pathway rather than being allowed to continue within the abbreviated route with supplementary explanations. Identity is therefore not a documentary formality but a substantive engineering fact that must be verified against the reference approval before the dossier strategy is chosen. Where the verification is done late, it tends to surface differences that are already embodied in the shipped product, at which point they can no longer be corrected for the Mexican filing and the route decision is made by default rather than by design. This page explains the four-element identity test, why material changes are the most frequent cause of redirection, how packaging and software versions count toward identity, and why a redirection is a change of route rather than a rejection of the application.

2. Legal basis

The identity requirement comes from the abbreviated pathway guidelines, the documentation depth of the fallback route comes from the implementing regulation, and the labeling consistency duty comes from the new labeling standard. Read together, the three instruments describe one continuous chain: the product must match its reference approval, the dossier must meet the depth of whichever route the match supports, and the label must agree with what was finally registered. The table below lists each instrument with its date or articles and the point it establishes.

3. Expert insights

Insight 1: identity means four-way equality, not functional equivalence. Design, materials, manufacturing process and packaging all four must be the same as the reference version. A product that performs identically but sources a material from a different supplier does not satisfy the test. Functional equivalence is a concept that belongs to other regulatory frameworks; here the standard is sameness, element by element, and any gap in any element breaks the premise of the route. Teams accustomed to demonstrating equivalence through performance testing should note that performance data cannot repair a difference in the underlying design, material or process.

Insight 2: material changes are the most common reason for redirection. Switching a material, changing a supplier or altering the sterilization method between the domestic version and the export version of the same device all break identity. The cost-optimization changes that a company makes after obtaining the approval in the reference country are precisely the changes that create the break point for the Mexican application. Manufacturing and regulatory teams need a shared change-control discipline so that commercial improvements do not silently disqualify the faster route.

Insight 3: packaging differences also count as non-identity. Packaging is expressly listed among the elements of the identity assessment. If the product is supplied in a sterile single package in the reference country but is intended to be offered in Mexico non-sterile, or in multi-unit packs, the identity condition fails. Packaging configurations therefore need to be frozen alongside design and materials, not treated as a local marketing decision that can vary by market. The identity comparison table used for the filing should carry packaging as a named column, equal in weight to design and materials, so that configuration changes are visible in the same review.

Insight 4: software versions must be identical too. For software-bearing devices, the version identification or release date is information required to be accessible under NOM-137-SSA1-2025. A different version means a different product, and the abbreviated pathway does not apply. Version locks should be treated as regulatory commitments, documented and enforced across development releases, so that the version submitted in Mexico can always be matched to the version in the reference approval, release by release.

Insight 5: redirection is not rejection. Being required to proceed under the standard pathway means the application can still be filed; only the documentation depth and the intensity of the review return to the conventional level. Treating the redirection as a failure and abandoning the submission altogether is a misjudgment, since the product remains registrable, merely through the longer and heavier route. The correct response to a redirection is to switch the dossier plan, not to question whether the product can reach the Mexican market at all.

4. Practical recommendations

• Before submission, prepare an identity comparison table comparing design, materials, process and packaging item by item against the reference approval, with evidence attached to each row.
• Freeze a dedicated product configuration for the Mexican market and resist carrying local cost optimizations into that configuration.
• Lock the software version, and keep the version identifier synchronized across the labeling and the digital interface.
• Where a genuine difference exists, prepare the complete technical dossier under the standard pathway instead of gambling on the breadth of the review.
• Keep the label information consistent with the registration documents, so that a labeling inconsistency does not trigger an amendment after registration.

5. Verification checklist

• □ Design, materials, manufacturing process and packaging have been compared item by item
• □ The identity comparison table is in the dossier with supporting evidence
• □ The software version is locked and identical to the reference version
• □ No material or sterilization changes were made for localization purposes
• □ The label information is consistent with the registration documents
• □ Where differences exist, the standard pathway has been adopted for preparation

Regulatory information verified as of October 28, 2026.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for the Mexican market. Our team manages COFEPRIS registrations and equivalence (equivalencia) reviews, coordinates third-party authorised centre routes, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com