Grouping Post-Approval Variations in the EAEU — Cut Costs, Avoid Delays
By the end of the year, the regulatory affairs department of a major pharmaceutical company has typically accumulated dozens of changes: a manufacturing site address has been updated, excipient specifications revised, storage conditions adjusted. Technically, each variation requires a separate application, a separate state fee, and a separate waiting period for the regulator’s response. If you count only the direct costs, the picture is discouraging. But Decision of the EEC Council No. 78 (as amended on 26.11.2025) provides a mechanism to consolidate all of this into a single package — and many companies either never use it or apply it incorrectly, which ends up being even more expensive.
Here we break down how the EAEU variation type system is structured, when grouping is permissible, when it causes delays across the entire package, and how to build a regulatory calendar that reduces costs and avoids wasted time.
Three Types of Variations and the Regulator’s Logic
Annex No. 19 to EEC Council Decision No. 78 divides all changes to the registration dossier of a medicinal product (MP) into three categories. The logic is straightforward: the higher the potential risk to safety and efficacy, the stricter the control.
Type IA variations. Minor changes with minimal regulatory consequences. Updating the legal address of the marketing authorisation holder (MAH), revising contact details for the authorised representative, making minor technical corrections in Module 1. These follow a notification procedure: either an immediate notification (subtype IA IN) within 30 days of implementing the change, or an annual report in which the MAH notifies the regulator of multiple changes at year-end.
Type IB variations. So-called «variations by default» — those that fall into neither Type IA nor Type II. Moderate risk: for example, adding a new finished dosage form manufacturer or adjusting shelf life. These are subject to a tacit consent procedure: if the regulator raises no objections within 30 days of the application’s validation, the variation is deemed approved. In practice, a typical Type IB variation takes around two months from submission to implementation.
Type II variations. Major changes: adding a new indication, modifying the active pharmaceutical ingredient (API) manufacturing process, revising critical specifications, or changing the safety profile. These require a full examination in the reference state, with timelines that can reach 90 or more calendar days for the assessment phase alone.
| Parameter | Type IA | Type IB | Type II |
|---|---|---|---|
| Risk level | Minimal | Moderate | High |
| Procedure | Notification / annual report | Simplified (tacit consent) | Full examination |
| Estimated timeline | 30 days / end of year | Up to 60 calendar days | 90+ calendar days |
| Requires examination | No | Generally no | Yes |
Examinations for quality-related variations are conducted by the FSBI «Scientific Centre for Expert Evaluation of Medicinal Products» (SCEEMP) of the Ministry of Health of Russia, acting on assignment from the Ministry (Order of the Ministry of Health of Russia No. 558n of 24.08.2017, as amended on 31.03.2025).
How Much It Costs
State fees for variations are set out in Article 333.32.1 of the Tax Code of the Russian Federation (as amended by Federal Law No. 299-FZ of 31.07.2025) and differ significantly depending on the procedure used.
| Type of variation | National procedure (Russia) | EAEU procedure |
|---|---|---|
| With examination | 490,000 RUB | 150,000 RUB |
| Without examination | 5,000 RUB | 5,000 RUB |
For variations requiring examination, the difference is more than threefold: 490,000 RUB under the national procedure versus 150,000 RUB under the EAEU procedure. For companies planning regular dossier updates, this alone is a strong argument in favour of EAEU registration. For veterinary medicinal products under the EAEU procedure, the fees differ: 323,000 RUB (with examination of the dossier and samples), 191,000 RUB (dossier examination only, no samples), or 11,000 RUB (without examination).
Administrative Type IA variations that require no examination cost 5,000 RUB per application under both procedures. This is precisely where grouping delivers the greatest effect: instead of fifteen separate applications at 5,000 RUB each, a single annual report is filed, and the fee is paid once.
How Grouping Works
Grouping gives the MAH the right to submit multiple variations in a single application. One document package, one fee, one regulatory decision — instead of multiple separate procedures.
Two rules apply without exception.
The absorption rule. If a group contains variations of different types, the entire group is processed under the procedure for the highest type included. Add one Type II variation to a package of ten Type IA changes, and the entire package goes through a full examination. From the regulator’s standpoint, this is logical: a partial assessment cannot be carried out when one of the changes affects drug safety. Before grouping, weigh carefully whether to include a «heavy» variation in the joint package or submit it separately.
The principle of consequential variations. Some changes inevitably trigger others. If the API manufacturing process is modified (Type II), the API specification changes too — and possibly the finished product specification as well. If these are filed separately, the regulator will detect internal dossier inconsistencies during validation of each package. The result is either a validation rejection or a request for additional data. Consequential variations must always be grouped.
Here is a practical example. A manufacturer updates the API synthesis method (Type II). This triggers an update to the API specification and a correction to the summary of product characteristics (SmPC) in the composition section. All three variations are filed as a single Type II package — the right approach. However, if a secondary packaging site address change (Type IA) is added to the same package, that administrative variation will be held up pending the completion of a complex examination. It is better to include it in the annual report and keep it separate from the lengthy procedure.
The Annual Report as a Tool
For Type IA variations, the Rules provide a dedicated pathway: the annual report. The MAH accumulates all minor changes throughout the year and submits them as a single block. A company that makes 15 minor administrative changes across different products over the course of a year can consolidate the entire volume into one report and pay the fee once.
One condition applies: Type IA variations with immediate notification requirements (subtype IN) do not qualify for the annual report. These must be reported to the regulator within 30 days of implementation. This covers variations that directly affect a product’s market availability or safe distribution.
Where the System Breaks Down
In practice, several scenarios turn grouping from a cost-saving tool into an additional burden.
Classification error. The applicant includes a variation as Type IA, but during validation the regulator reclassifies it as Type II. The entire package is either returned for resubmission or routed for a full examination — with delays for every other variation in the group. The fix is straightforward: verify each classification against Annex No. 19 before every submission.
Artificial grouping. The regulator assesses whether the edits in a group share a logical or scientific connection. If an applicant combines an API synthesis method change with the addition of a new excipient colorant, these are two independent variations from different dossier sections — and their consolidation will appear unjustified. The Module 1 cover letter must explain the rationale: why the variations are submitted together, how they are connected, or that this is a scheduled administrative package.
Urgent variation in a slow package. Sometimes a SmPC correction is needed quickly — for instance, following a new safety study. Including it in a long-term Type II package is a poor choice: the entire procedure must complete before anything can be implemented. Urgent variations should be submitted separately to reduce their turnaround time.
Desynchronisation across concerned member states. Under the EAEU procedure, once a group of variations is approved in the reference state, the concerned member states must confirm agreement within the established timelines. If a state fee payment is delayed in one of them, the procedure there may be suspended. The dossier ends up in different statuses across different Union countries — and that becomes a separate regulatory task.
Financial Arithmetic: A Concrete Example
Take a company that has accumulated 15 Type IA variations for a single product over the course of a year. Filing each separately results in 15 applications at 5,000 RUB each — 75,000 RUB in total. Using the annual report pathway, the same scope costs 5,000 RUB: a difference of 70,000 RUB on a single product. For a company with a portfolio of 20 products and a comparable flow of administrative changes, that sum becomes significant.
For Type II variations, the logic differs. Grouping two independent changes theoretically saves on fees but raises the risk of delays: if the regulator raises questions about one variation, the entire package stalls. Companies with large portfolios generally avoid grouping independent Type II variations unless there is a clear consequential relationship.
Worth mentioning separately: the PACMP (Post-Approval Change Management Protocol) from ICH Q12. This protocol allows the MAH to agree with the regulator in advance on a strategy for future variations. If the protocol is approved, subsequent changes filed under it may be reviewed under a lighter procedure. Within the EAEU, this mechanism is currently in the early stages of implementation.
What to Do
Build an annual variations registry. Compile all current and planned changes for each product. Classify every variation against Annex No. 19 to Decision No. 78. When a classification is uncertain, take a conservative position (higher type) and document this in the cover letter.
Identify consequential variations. Go through the list and find pairs or sets of changes where one inevitably follows from another. These are mandatory groups — submit them together regardless of whether it is financially advantageous.
Set up a regulatory calendar. Accumulate Type IA changes through to year-end and file them via the annual report. Group Type IB variations with planned implementation dates when there is a logical connection. Plan Type II variations tied to manufacturing projects at least 12–18 months ahead of the target implementation date.
Do not include urgent changes in a slow package. If a variation needs rapid implementation, submit it separately. Waiting for a full package examination to complete for the sake of one urgent change is not rational.
Justify the grouping. In the Module 1 cover letter, briefly explain why the variations are filed together: either because they are consequential (and why), or because this is a scheduled administrative package.
Grouping works as a tool only when applied systematically. Companies that plan changes in advance and maintain an up-to-date variations registry spend a fraction of the resources compared to those addressing each change as it arises. It is not inherently complicated — it simply requires the habit of keeping such records.
Regulatory Framework:
1. Decision of the Council of the Eurasian Economic Commission of November 3, 2016 No. 78 «On the Rules of Registration and Examination of Medicinal Products for Medical Use» (as amended on November 26, 2025), Annex No. 19
2. Federal Law of April 12, 2010 No. 61-FZ «On the Circulation of Medicines»
3. Tax Code of the Russian Federation, Article 333.32.1 (as amended by Federal Law of July 31, 2025 No. 299-FZ)
4. Order of the Ministry of Health of the Russian Federation of August 24, 2017 No. 558n «On Approval of the Rules for Conducting Examination of Medicinal Products…» (as amended on March 31, 2025)
5. ICH Q12 «Technical and Regulatory Considerations for Pharmaceutical Product Lifecycle Management»