2023-05-10

What COA and HPLC Each Show in API Quality Review

A B2B guide explaining how COA, HPLC, Specification, and batch information support API quality review.

Many B2B buyers ask first for purity and COA when contacting an API supplier. For a quality team, one result value is not enough. COA and HPLC are different review materials: one reports whether a batch meets stated tests, while the other helps the buyer understand analytical method and chromatographic information.


What COA should answer

A COA should identify batch number, product name, test items, acceptance limits, results, test date, and document version. Buyers should first confirm that the COA matches the product, batch, and review purpose, then check whether the test items cover internal quality concerns.


What HPLC should answer

HPLC information is commonly used to review purity, main peak, related peaks, retention time, and integration logic. It does not replace COA or full method documentation. Buyers may request method summary, chromatogram, testing conditions, and result explanation so analytical teams can decide whether the file is sufficient for the next review step.


COA and HPLC comparison



Where Specification fits

Specification is the quality standard framework. Buyers use it to judge whether COA items and limits are relevant. It also helps confirm whether HPLC-related methods align with the agreed quality framework. Without Specification, COA and HPLC become isolated files.


Buyer questions

  • Which batch and product code does the COA cover?
  • Does the HPLC chromatogram match the same batch?
  • Can the supplier provide a method summary or method number?
  • Which version of Specification applies?
  • Can the supplier explain impurity or related peak logic at a high level?
  • Will storage conditions affect retest or transport planning?


Common risk signals

  • Only a purity value is provided, without batch or method information.
  • COA tests do not match buyer quality concerns.
  • HPLC lacks basic identifiers or cannot be tied to a batch.
  • Document version, product name, or batch number is inconsistent.
  • The supplier avoids discussing document purpose, buyer country, or quality requirements.


FAQ

Can COA alone be used for supplier screening?

It can be a first step, but should not be the only basis. Specification, HPLC, and batch information should also be reviewed.

Does high HPLC purity mean the supplier is qualified?

No. Method, batch consistency, document response, and buyer jurisdiction still matter.

When should buyers request more analytical information?

When the project moves into quality audit, registration preparation, or supplier selection, more complete method and batch information is often needed.


Internal links


CTA

If your team is comparing API supplier documents, submit the target product, batch concerns, and required document types. We can help organize a quality review communication checklist.