ICH Q7 clause 9: Packaging and identification labelling of APIs and intermediates

Packaging materials affect API stability and integrity. Procedures must cover the full lifecycle similar to raw materials. Container closure integrity is critical — incompatible packaging or defective containers can cause API degradation, contamination, or loss during storage and shipment.

Container integrity protects the API throughout its shelf life. Selection considers: moisture barrier (for hygroscopic materials), oxygen barrier (for oxidation-sensitive), light protection (for photosensitive), mechanical strength (for shipping), chemical compatibility (with the API and any residual solvents). Containers must arrive clean and may need sanitization for microbially sensitive products.

Container-API compatibility is demonstrated through stability studies in the actual container. Extractables and leachables from container materials can migrate into the API, especially for liquid or solution forms. Solid APIs have lower risk but can still interact with container coatings or moisture barriers. Testing includes accelerated stability, extractables identification, and compatibility over proposed shelf life.

Like raw materials, packaging materials follow receive-quarantine-test-release. Testing varies by material type: dimensional checks for containers, visual inspection for labels, identification tests for printed items. Specifications should cover physical properties (dimensions, weight, thickness), chemical composition (for contact materials), and visual attributes (color, print quality, absence of defects).

Labels are a high-mix-up-risk material — a wrong label can cause product misidentification and patient harm. Controls include: locked storage, access logs, organization by product and batch, FIFO usage, periodic reconciliation. Electronic label printing reduces risk by generating labels on-demand rather than holding stocks.

Obsolete labels in stock create mix-up risk. Destruction with documentation prevents their use. Returned labels from incomplete runs pose the same risk — they should be evaluated and either destroyed or returned to stock only after verification. Destruction logs provide evidence that obsolete materials were removed from circulation.

Label issuance is a controlled transaction. A designated person (typically a label control clerk under warehouse or QA supervision) issues labels against authorized requests. The issuing person verifies: correct product, correct revision, correct quantity, authorized requestor. Documentation of issuance creates the audit trail for label movement.

Pre-use label examination catches printing errors, wrong labels, or obsolete revisions before they reach product. Verification checkpoints: content (text, batch number placeholders, expiry format), appearance (color, print quality, clarity), adhesion (for self-adhesive), dimensional (size, placement). Archived samples of each label revision support regulatory audits.

Label reconciliation ensures that labels don't go missing (potential counterfeit risk) or mistakenly applied to wrong products. Math: labels issued = labels applied + labels destroyed + labels returned. Discrepancies require investigation. Common discrepancies: counting errors, waste during label application, labels destroyed during troubleshooting. Unexplained discrepancies trigger thorough investigation.

Pre-printed batch numbers tie labels to specific batches. If excess labels remain after packaging, reusing them for different batches creates mix-up risk. Destruction is preferred. Only reuse for the same batch is acceptable (e.g., when packaging continues over multiple days). Labels without pre-printed batch numbers (generic labels where batch is applied separately) don't have this specific concern.

Labels returned from production may be contaminated, damaged, or mixed with other labels. Reuse requires verification: original product confirmed, physical condition acceptable, no mixing with other products' labels. Conservative approach: destroy returned labels rather than risking contamination or mix-up. Only labels known to be clean and correct should be returned to stock.

Start-of-run label examination catches errors before committing large quantities of product. A sample from each label lot is examined against the specification: verify batch number (if pre-printed), expiry date format, product name, strength, storage conditions, manufacturer information. The examination is documented in the batch record.

In-line inspection catches issues that develop during a run: mis-applied labels, labels from wrong product getting mixed in, printing drift over time, mechanical issues with label application. Automated systems (vision systems) provide consistent inspection. Any incorrect label detection should halt the line until the issue is understood and corrected. Affected product is segregated for disposition.

Packaging SOPs integrate with labeling SOPs and production SOPs. Content: line clearance before starting, material staging verification, start-of-run checks, in-process monitoring, end-of-run reconciliation, cleanup and changeover. Mix-up prevention is paramount — only one product/batch per packaging line at a time, clear visual identification, physical or administrative controls between operations.

Label content is regulatorily prescribed. The minimum set listed must be present on all API labels. Additional content may be required by specific markets (e.g., pharmacopeial reference, manufacturer license number, product code). Content must be accurate and consistent with regulatory filings. Labels for bulk containers may have different requirements than consumer-facing labels.

Status labels are separate from content/product labels. They communicate the QA disposition status: quarantine (awaiting release), released (approved for use/shipment), rejected (disposition pending), hold (investigation underway). Color coding is standard: yellow for quarantine, green for released, red for rejected. Status label changes are controlled transactions requiring authorization.

Tamper-evident seals protect against tampering during distribution. Common seal types: heat-shrink bands, adhesive tape with tamper evidence, metal seals with unique numbers, electronic seals with GPS tracking. Seal numbers or codes should be documented in shipping records for traceability. Customers inspect seals upon receipt and report any issues.

Tamper evidence goes beyond simple seals — the entire container closure system should make tampering visible. Examples: induction-sealed bottles (aluminum seal visible when removed), child-resistant closures with tamper bands, shrink wrap around entire container, tamper-evident tape across box lids. For primary packaging (direct contact), tamper evidence is most critical; secondary packaging provides additional protection.

Intermediates (materials between steps) have different label requirements than finished APIs. They're typically used internally or between sites, so labels focus on internal traceability rather than consumer information. Minimum content: intermediate identification (often a code rather than name), batch number for traceability, date of manufacture, storage conditions, and hold time if applicable. Retest or expiry dates apply where intermediates are held for extended periods.

Pre-release examination is the final check that packaging and labeling are correct. Scope: verify label content matches batch record, verify container integrity, verify tamper evidence, verify status labels, verify quantity. Discrepancies could indicate errors during packaging that affect the entire run. QA performs or reviews this examination as part of batch release.