Label Verification and Warning Letters: How the FDA Checks Labels in Use

1. Key takeaways

Yes. Under AO No. 2025-0030 and its implementing circulars, the FDA may carry out physical product verification to confirm that the label on devices actually in circulation matches the approved version. Where a discrepancy is found, a warning letter is issued to the MAH; the MAH must submit an FSCA report form within 14 calendar days of confirming receipt of the letter; and the proposed corrective action must be completed within 60 calendar days.

• Label compliance is now an enforcement subject, not only a dossier requirement.
• The 14-day response runs from confirmation of receipt, and service is deemed to occur by default rather than requiring actual reading.
• A label mismatch enters the FSCA process, so it becomes part of the product compliance history.
• Four mismatch types account for most cases: unregistered label changes, non-compliant stickers, incorrect or missing registration numbers, and Chinese text on the label.
• Corrective actions are scheduled within 60 calendar days, and the schedule must appear in the initial report.

2. Legal basis

The mechanism combines the PMAS framework in AO No. 2025-0030 with a draft FDA guideline on records, complaints, adverse events and FSCA. The table below sets out the trigger, the response deadlines and the label elements against which verification is performed. The design assumes that the approved label is a fixed reference point: verification only works if the company can produce the approved version for the batch in question, which makes version control the first practical requirement rather than an administrative afterthought.

3. Expert insights

Insight 1: label verification upgrades the label from a dossier item to an enforcement object.

In the past, label problems were mainly caught at the submission stage. The FDA now goes to the market and examines the physical product, comparing the label in circulation with the approved version. This chain works because of the traceability system created by AO No. 2025-0030: since companies must keep lot-level distribution records, the regulator is able to locate a specific batch and verify its label. The two obligations therefore reinforce each other, and a company that treats them as separate projects will find the gap between them is exactly where an inspection lands.

Insight 2: the 14-day response runs from confirmation of receipt, not from actual reading.

The rule states that service is deemed complete 5 calendar days after the FDA issues its acknowledgement, unless receipt is confirmed earlier. A company therefore cannot buy time by claiming it never saw the letter, because service is presumptive. In practice, the MAH should establish a dedicated channel and register for FDA correspondence so that letters do not disappear inside the organisation. The first internal act on receipt should be to record the date, because that date defines the response window.

Insight 3: a label mismatch goes straight into the FSCA process, and that is where the cost lies.

Receiving a warning letter does not call for an explanatory reply. It requires an FSCA report form and completion of corrective action within 60 calendar days. The label issue is thereby recorded as an FSCA, becomes part of the product compliance history, and will be visible in renewals and inspections. That visibility, rather than the immediate administrative burden, is the real cost: a matter that could have been handled as a documentation correction is instead recorded as a field safety event.

Insight 4: four mismatch types account for most findings.

GRZAN’s summary of frequently observed non-conformities:

• Label changes made without a variation, such as adding an indication or changing the packaging design;
• Sticker labels whose content differs from the approved version;
• Registration number printed incorrectly or omitted;
• Chinese text appearing on the label.

All four can be avoided by finalising the label at the submission stage and carrying out periodic physical self-checks after launch. Neither measure is technically difficult; both fail when ownership is unclear, which is why the recommendation below assigns the task explicitly.

4. Practical recommendations

• Finalise and obtain approval for the label and the labelling scheme at the submission stage. Treat the sticker configuration as part of the approved label, not as a downstream packaging decision.
• Maintain a label version register. Archive every approved version and compare before implementing any revision.
• Carry out periodic physical self-checks after launch. Each quarter, sample product in circulation and compare it item by item against the approved version.
• Set up a dedicated channel for FDA correspondence. Register the letter on the day it arrives and set the internal target against the 14-day clock (submitting within 7 days is advisable).
• Schedule corrective actions within the 60-day limit. State the schedule in the initial report so that later reporting has a baseline.

5. Verification checklist

• □ Approved label version archived in the version register
• □ Physical product matches the approved version, verified by periodic sampling
• □ Sticker label content matches the approved version
• □ Registration number printed correctly
• □ No Chinese text on the label
• □ Correspondence receipt mechanism in place, with a named owner and same-day registration
• □ Response deadline set at 14 calendar days (internal target 7 days)
• □ Corrective action deadline set within 60 calendar days

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support across Southeast Asia, including the Philippines. Our team prepares CMDN/CMDR dossiers to ASEAN CSDT structure, manages submissions and deficiency responses with the FDA Philippines, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com