Post-marketing obligations after Kenya PPB registration: surveillance, renewals, and variations

Once a product is registered and marketed in Kenya, the Marketing Authorisation Holder and Local Technical Representative share responsibility for ongoing pharmacovigilance. This includes the collection, assessment, and reporting of adverse drug reactions and product quality complaints to the PPB within the timeframes specified under the Pharmacy and Poisons Act and the PPB's pharmacovigilance guidelines. Expedited reports for serious unexpected adverse reactions are required within 15 days of the MAH becoming aware of the event. Periodic Safety Update Reports covering the post-marketing safety profile must be submitted on a schedule defined by the PPB at registration.

In practice, the pharmacovigilance obligation falls most heavily on the LTR, who is the local contact point for authority communications and the entity responsible for ensuring that adverse event reports received by distributors, healthcare providers, or directly from patients are escalated appropriately. LTRs who do not have a formal pharmacovigilance procedure, including a documented process for collecting, assessing, and reporting events, are exposed to compliance risk that typically surfaces during PPB inspections or when a product quality issue attracts attention.

The PPB has progressively strengthened its post-marketing surveillance infrastructure, and the expectation that MAHs and LTRs maintain genuine pharmacovigilance records is increasingly backed by inspection activity. Teams that have relied on informal processes during the earlier years of a product's commercial life should treat any renewal cycle as an opportunity to formalise their pharmacovigilance system before it becomes an inspection finding.

Product registrations in Kenya are valid for a specified period, after which a renewal application must be submitted to maintain the marketing authorisation. The PPB's renewal requirements broadly follow a CTD-based format, meaning that the renewal dossier must include updated quality documentation, current GMP certificates, stability data generated since the initial registration, and a post-marketing safety update covering the product's pharmacovigilance history since the last registration.

One of the most common renewal failures is submitting outdated GMP certificates. GMP certificates have their own validity periods, and the certificate submitted with a renewal application must be current at the time of submission. Where a manufacturer has changed GMP certification body or had their certificate suspended and reinstated, the renewal dossier must include an explanation and the relevant documentation. Submitting a renewal with an expired GMP certificate will result in rejection at screening, adding months to the timeline.

Stability data for renewals must cover the full approved shelf life under Zone IVb conditions. If ongoing stability studies have been conducted since registration and results have been within specification, this data should be included and presented in a format that demonstrates compliance with the stability commitment made at registration. Where out-of-trend or out-of-specification results have occurred during the post-marketing period, these must be disclosed and explained in the renewal submission.

The post-marketing lifecycle of a registered product generates a continuous stream of regulatory documents: GMP certificates that are renewed annually, stability study data at each annual timepoint, safety reports, variation approvals, renewal decisions, and authority query letters. Without a structured record-keeping system, this accumulation creates the same problems at renewal that many teams encounter at initial registration: documents are missing, the wrong version of a specification is on file, and the regulatory history of the product cannot be reconstructed quickly.

For LTRs managing post-marketing obligations across multiple client MAH portfolios, the organisational challenge compounds. Each product has its own renewal date, its own stability commitment timeline, and its own pharmacovigilance history. Tracking all of this in spreadsheets carries the risk that version control breaks down, renewal deadlines are missed, and pharmacovigilance records are kept inconsistently across clients. This is a structural risk that grows with portfolio size.

Dossierly supports the post-marketing regulatory record by maintaining a current lifecycle stage for each project, tracking authority queries with their response deadlines, and linking documents to the specific CTD requirements they satisfy. When a renewal cycle approaches, the full submission history is on record, including which variation approvals were received, which stability reports were generated, and which authority queries were raised and resolved. This turns the renewal compilation from a reconstruction exercise into an update of a record that has been maintained continuously.