2023-05-10

API Supplier Qualification Document Checklist and Screening Questions

A staged checklist for B2B procurement and quality teams reviewing API supplier documents, technical responses, traceability and readiness for further qualification.

✓For qualified B2B partners only. Documentation available upon request. Not for personal use or direct consumer sale.

Direct answer

An API supplier qualification checklist should help a B2B buyer decide whether a supplier and a specific product can proceed to the next review stage. Start by confirming the supplier identity, target API, specification and available batch documentation. Then assess whether the COA and supporting records are traceable, whether technical questions receive clear answers, and whether the supplier can support the document scope required for the buyer's project.

Qualification should be staged. Initial screening does not require every confidential quality or regulatory file. Request enough information to verify product scope and reviewability first, expand the document package for shortlisted suppliers, and plan a formal audit or deeper quality-system review only when justified by risk, intended use and the buyer's procedures.

Separate initial screening from full qualification

Supplier screening, document review and formal qualification are related but not identical activities:

Initial screening confirms the legal entity, contact, product scope, requested quantity and whether basic technical communication is possible.
Product document review checks the specification, batch COA, analytical support, storage, packaging and traceability information relevant to the target API.
Quality-system review assesses the supplier's procedures, responsibilities, change handling, deviation communication and available qualification evidence according to buyer risk.
Audit and approval follow the buyer's own risk-based process and may include remote review, third-party assessment or an on-site audit where appropriate.

This sequence prevents procurement teams from requesting a complete regulatory dossier before the product, jurisdiction and intended B2B use are understood. It also prevents a quotation or a single COA from being treated as supplier qualification.

API supplier qualification review matrix

The matrix below provides a practical starting point. The exact evidence required depends on the product, project stage, buyer quality system and jurisdiction.

Review area	Information or document	Questions to answer	Decision or follow-up
Supplier identity	Legal company name, address, contact and role in the supply chain	Who supplies the material, issues documents and manages technical communication?	Resolve unclear entity names or responsibilities before document review
Product identity	Product name, CAS number, material form and intended supply scope	Does the offered material match the buyer's request and current product reference?	Reject or clarify mismatched product identity before comparing results
Specification	Applicable tests, methods or references, units and acceptance criteria	Which revision applies, and does it cover the buyer's required attributes?	Record the agreed revision and open specification differences
Batch quality	Batch-specific COA and relevant supporting analytical records	Are product, batch, results, limits, methods and authorization traceable?	Request clarification for missing tests, inconsistent values or unclear batch links
Impurity and analytical information	HPLC, identity or mass information and impurity reporting where applicable	Do supporting records correspond to the COA batch and stated method?	Define any additional data or third-party testing needed for the project
Storage and logistics	Storage, packaging, label and transport information	Are the conditions appropriate for the supplied form, quantity and destination?	Confirm protective packaging and destination requirements before shipment
Quality communication	Document-control, deviation, complaint and change-communication scope	Who responds, what changes are communicated and how are updates controlled?	Agree contacts, timelines and evidence for material changes
Regulatory and audit scope	Project-specific regulatory or quality-system material, when applicable	What does the buyer's jurisdiction and intended use actually require?	Verify applicability and evidence; do not infer certification from a document name
Commercial coordination	Quantity, availability, lead-time confirmation, quotation validity and supply assumptions	Are the commercial terms based on the same specification and document scope?	Resolve differences between technical and commercial assumptions

Stage 1: supplier and product screening questions

The first questionnaire should be concise enough to receive a useful response. Ask:

What is the legal company name and business address?
What is the supplier's role for this material?
Who is responsible for commercial and technical communication?
Is the target API within the current supply and documentation scope?
What product name, CAS number and material form are being offered?
What quantity and packaging configurations can be discussed?
Which specification and batch documents are currently available for review?
What information does the supplier require before confirming document scope?

A supplier should not be rejected merely because confidential documents are not sent during an initial inquiry. The important screening signal is whether the supplier can identify the product, explain the available review process and respond consistently.

Stage 2: product and batch document review

For shortlisted suppliers, compare the offered specification and a relevant batch COA. Check product and batch identifiers, methods, units, acceptance criteria, actual results, document dates and authorization. Where supporting HPLC, identity, impurity, storage or packaging information is part of the agreed review, confirm that it applies to the same material and batch.

Quality-control documentation for an API can include several distinct records. A specification defines requirements; a COA reports batch results; an HPLC record can support chromatographic purity and peak reporting; identity or mass information supports assignment of the material; storage and packaging information connects the reviewed batch to handling and shipment. These records should not be treated as interchangeable.

Record open questions instead of relying on verbal assumptions. If a result or document cannot be interpreted, request the relevant method context or explanation before moving the supplier forward.

Stage 3: quality-system and audit preparation

A deeper quality-system review should follow the buyer's risk assessment. Before an audit, define the audit objective, scope, participants, confidentiality arrangements and requested pre-read material. Relevant topics may include:

document approval, revision and retention controls;
material and batch traceability;
analytical responsibility and method control;
deviation, out-of-specification and corrective-action communication;
complaint handling and recall communication;
change notification affecting the supplied product or documents;
storage, packaging and shipment controls;
subcontracted activities relevant to the buyer's supply chain.

Do not present DMF, ASMF, CEP, GMP status or another regulatory item as universally required. Applicability depends on the actual material, manufacturer, project, jurisdiction and intended use. When a regulatory claim is material to the qualification decision, verify it through current, appropriate evidence.

How to record and score supplier responses

A simple status system is more useful than an arbitrary numerical score. Mark each review item as:

Confirmed: sufficient and traceable information has been reviewed.
Open: clarification or an additional document is required.
Not applicable: the item does not apply to the present product or project stage.
Not acceptable: a material mismatch or unresolved risk prevents progression.

For every open or unacceptable item, record the owner, requested evidence, response deadline and final decision. This creates an audit trail without implying that document quantity alone determines supplier quality.

Information the buyer should provide

Supplier qualification works better when the buyer provides enough context. Include:

buyer company type and responsible department;
target product and CAS number;
project stage and professional use scenario;
requested quantity and anticipated schedule;
required specification or quality attributes;
destination and storage, packaging or transport requirements;
documents needed for the current review stage;
jurisdiction-specific requirements that affect the requested evidence.

The buyer remains responsible for determining local registration, import and regulatory requirements. Supplier information supports the review but does not replace the buyer's qualification procedure or jurisdictional assessment.

FAQ

What documents should be requested first during API supplier qualification?

Start with supplier and product identity, the applicable specification, a relevant batch COA, and the available analytical, storage, packaging and traceability information needed for the current stage.

Is a COA enough to qualify an API supplier?

No. A COA reports batch results. Qualification also considers the specification, supporting records, traceability, communication, quality-system risk and the buyer's own approval process.

What is quality-control documentation for APIs?

It can include specifications, batch COAs, analytical records, impurity information, storage and packaging records, and controlled procedures relevant to testing and release. The required scope depends on the project.

Should a complete confidential dossier be requested during initial screening?

Usually not. Confirm product scope and core reviewability first, then expand the request for shortlisted suppliers under appropriate confidentiality controls.

Are DMF, ASMF or CEP documents mandatory for every API supplier?

No. Their relevance depends on the material, manufacturer, intended use and jurisdiction. Availability and applicability must be verified case by case.

When should an API supplier audit be considered?

The buyer should determine this through a risk-based qualification process considering the product, intended use, supply-chain role, document review and internal procedures.

How should incomplete supplier answers be handled?

Record the question as open, define the required clarification and deadline, and assess whether the unresolved item prevents progression to the next stage.

Which teams should participate in qualification?

Procurement may coordinate the process, while quality, analytical, regulatory, logistics and other functions contribute according to the product and project risk.