Multi-Product API Facilities and the Contamination Gap FDA Finds

FDA issued a warning letter to Henan Lvyuan Pharmaceutical Co., Ltd. on March 26, 2026, citing cross-contamination risks across the company's multi-product API manufacturing operations. The letter was made public March 31. The specific observations have not been fully summarized in public channels yet, but the pattern the warning letter fits into is not new. It is one of the most consistent enforcement themes in API manufacturing, and the reason it keeps appearing in warning letters is structural, not accidental.

Multi-product API facilities face a contamination control problem that dedicated facilities do not. When the same equipment, the same rooms, the same HVAC infrastructure, and the same cleaning cycles serve multiple active compounds, every changeover becomes a regulatory event. The question FDA asks is not whether the facility has a cleaning procedure. The question is whether the facility can demonstrate, with current and product-specific evidence, that cleaning actually achieves acceptable carryover limits for every product pair that shares that equipment.

That distinction matters because many quality teams conflate administrative qualification with demonstrated control. A cleaning validation study done in 2018 for the original product slate does not automatically cover a new API added to the facility in 2022. A limit based on the lowest acceptable daily intake of one compound may not be the binding constraint when a more potent or more reactive compound enters the mix. ICH Q7, the Good Manufacturing Practice Guide for Active Pharmaceutical Ingredients, places explicit responsibility on the manufacturer to define acceptance criteria based on the pharmacological activity, toxicity, and stability of the specific compounds being shared — not on a generic "visually clean" threshold or a protocol inherited from a single original product.

The engineering dimension is where many facilities are most exposed. Under 21 CFR 211.42, facilities must be designed and maintained to prevent cross-contamination, including contamination from airborne particulates and residues. For API manufacturing, this standard interacts directly with 21 CFR 211.46, which governs ventilation, air filtration, and air handling systems. A multi-product facility that was built around an original product set and later expanded its portfolio may never have formally assessed whether the HVAC configuration still adequately manages contamination risk across the current product range. Airflow patterns that were acceptable for two chemically similar compounds may not be acceptable when a third compound with different dust characteristics, reactivity, or potency is introduced to adjacent manufacturing areas.

Inspection teams know this history. They know that API facilities add products incrementally, that risk assessments often lag behind operational decisions, and that the facility validation package may reflect what the building was designed to do rather than what it actually does now. When FDA cites cross-contamination risk at a multi-product site, the question behind the citation is usually not "did something go wrong." It is "can this facility prove that nothing is going wrong, and that its controls are calibrated to its current product risk profile."

Cleaning validation is the clearest test of whether that proof exists. ICH Q7 Section 12.7 requires that cleaning procedures be validated, that acceptance criteria be based on the limits for pharmacologically active substances, and that the validation address equipment shared between products. The practical requirement is a cleaning validation matrix: a documented assessment of every equipment-product combination, with acceptance limits derived from the worst-case carryover scenario for each combination. Firms that manage this as a living document — updated when new products enter, when equipment is repurposed, when cleaning chemistry changes, or when analytical methods are updated — are generally in a defensible position. Firms that treat the original validation package as permanent tend to find gaps during inspections that they did not know existed.

Campaign-based manufacturing adds another layer of complexity. Many multi-product API facilities reduce cross-contamination risk by running dedicated campaigns for each product and fully cleaning before switching. That model is defensible, but only when the campaign controls are actually enforced and documented. If scheduling pressure leads to compressed cleaning cycles, if operators make informal exceptions, or if the manufacturing record does not clearly capture which cleaning cycle was performed and verified before which campaign started, the campaign model loses its protective logic. An inspection that finds documentation gaps in campaign execution does not credit the intent of the system. It evaluates the evidence of how the system actually ran.

There is also the supplier qualification angle for API manufacturers selling intermediates or finished APIs into finished dosage form supply chains. When a buyer's quality team qualifies an API source, they are relying on that source's contamination controls as part of their own material qualification package. If an API facility has contamination control weaknesses, the risk does not stay on site. It transfers downstream into every product that uses that material. Finished dosage manufacturers who source from multi-product API sites should be asking explicit questions about the contamination control validation strategy as part of supplier oversight, not accepting a GMP certificate of analysis as a complete answer to a product-specific risk question.

The Henan Lvyuan warning letter arrives in the same enforcement window as other developing signals on CGMP failures at contract testing and supplier facilities. The pattern across these cases is not a story about individual firm misconduct. It is a signal about where the gap between documented systems and demonstrated performance tends to open under scrutiny. Multi-product API manufacturing is one of those places. The controls that prevent cross-contamination require active, product-specific validation, engineering that accounts for the current product range, and documentation that can demonstrate how every changeover was managed — not policies that describe how changeovers should be managed in principle.

Quality leaders at companies that source API from multi-product facilities, or that operate multi-product API sites of their own, should treat this signal as a prompt for a focused gap assessment. The questions worth answering now are: whether the cleaning validation matrix covers the current product slate, whether acceptance criteria are based on compound-specific pharmacological and toxicological data rather than generic thresholds, whether the HVAC and facility validation reflects the current product range rather than the original design basis, and whether campaign controls are documented with enough precision to withstand the kind of scrutiny FDA applied at Henan Lvyuan in March 2026.

If those answers are uncertain, the right move is not to wait for Helix's next brief on the subject. The right move is to identify where the contamination control evidence is weakest and start closing the gap before an investigator does it for you. The DSRV Inspection Risk Scan at /submit is built to surface that kind of exposure before it becomes a warning letter. Multi-product contamination control is exactly the type of operational risk it is designed to find.