Seven Quality Clauses That Decide an API Supply Dispute

The commercial negotiation takes four weeks and settles on price, payment terms and volume. The quality annex is attached on the last day, two pages, copied from the previous contract with the product name changed. Everybody signs.

Eighteen months later a batch is disputed. The customer's laboratory reports 0.11 per cent of an impurity against a 0.10 per cent limit. The supplier's laboratory reports 0.08. Both are competent. Both ran the method. The annex says the supplier's certificate is the basis for release, and it says nothing about what happens when the two laboratories disagree.

That silence is the most expensive thing in the contract.

The seven clauses

#	Clause	The question it settles
1	Specification and its change control	Which version binds, and how it can move
2	Certificate content and method reference	What the COA must state to be accepted
3	Sampling and retention	Whose sample decides, and how long it is held
4	Audit rights	Frequency, scope, remote access
5	Deviation and OOS disclosure	What the customer learns, and when
6	Recall and traceability	Who calls whom, within how many hours
7	Dispute resolution by analysis	Which laboratory breaks the tie

Clauses 1, 5 and 7 do most of the work. The others prevent smaller failures that are annoying rather than existential.

Clause 1: the specification has a version, and it binds

The annex should attach the specification as a numbered, dated document, and state that the version in force at the date of the purchase order governs. Without that sentence, a supplier can tighten or loosen limits between orders and argue that the current document applies.

It should also state how a specification can change: prior written agreement for a limit change, notification for an editorial correction, and a defined period before either takes effect. A specification that can move without agreement is not a specification. It is a description of whatever was shipped.

Clause 5: what the customer is entitled to know

Two events matter more than the rest. An out-of-specification result on a batch destined for this customer, and a deviation that could affect a batch already shipped.

The clause should require disclosure of both, with a period, and it should say what the disclosure contains. "We will inform you of any quality issue" is not a clause; it is a sentiment. "Within five working days of closing the laboratory phase of an OOS investigation affecting a batch supplied under this agreement, the supplier will provide the investigation summary, the impact assessment and the proposed disposition" is a clause.

The asymmetry is worth naming. The supplier's instinct is to disclose after the conclusion, because a conclusion is easier to communicate than an open question. The customer's need is to know before they release material made from the batch, which is earlier.

Clause 7: the one that ends arguments

Two laboratories, two results, one batch. Without a mechanism, the disagreement becomes a negotiation in which the material sits in a warehouse and the relationship absorbs the cost.

A workable mechanism has five parts.

1. A named referee laboratory, agreed in advance, independent of both parties.
2. The sample: the retained sample, or a joint sample drawn and split at receipt, sealed and signed.
3. The method: the pharmacopoeial method where one exists, otherwise the method in the specification, with the version stated.
4. The cost: usually the losing party, sometimes shared, occasionally the requesting party regardless of outcome. Each has a different effect on how often the mechanism is used.
5. The status of the result: binding, or advisory with a further step.

Five lines. The clause is cheap to draft and impossible to retrofit once a batch is in dispute, because at that point neither party wants to agree on which laboratory decides.

Clause 3: whose sample is evidence

Sampling is where disputes become unwinnable. If the customer's sample was drawn from the top of the drum and the supplier's from the composite, the two are not the same material and no referee laboratory can reconcile them.

The clause should specify the sampling plan at receipt, the retention period at both sites, and the chain of custody. It should also say what happens to the sample after the retention period, because a disputed batch whose sample was discarded a month earlier has no mechanism left.

Clause 4: audits that match how people actually work

A clause allowing one audit a year with thirty days' notice is a clause written for a world of flights. It should also cover a remote walk-through, a document-only review and a request for a specific record within a stated period. The last of these is the one that gets used most, because most questions are answerable with a document and do not need a visit.

The scope matters as much as the frequency. An audit clause that covers the site but not the suppliers of critical starting materials describes a boundary that the customer's own risk assessment does not recognise.

Clause 6: the call that has to happen at two in the morning

A recall clause for a raw material is really a notification and traceability clause. Who calls whom, on which number, within how many hours. Which distribution records exist, in what format, and how quickly a list of affected customers can be produced.

Test it once. Send a request for a mock traceability report on a batch shipped a year ago and see how long it takes. The answer is more informative than the clause.

What not to put in

Two things worth refusing. A clause making the supplier the sole judge of whether a batch conforms, which converts every dispute into an argument about the clause. And a clause allowing specification changes without prior notice, which is the same problem wearing a different hat.

Both appear in templates, and both are usually signed because the annex was read by nobody.

Where this leaves a supply-chain partner

We sign a quality annex with the seven clauses in it, including a named referee laboratory and a disclosure period that starts before the conclusion rather than after it. The annex is not where a supplier demonstrates goodwill. It is where the customer finds out, in a calm month, what the supplier will do in an uncalm one.

Read the two pages before you sign the forty.

The clauses people add after the first dispute

There is a predictable set of clauses that appear in the second contract and not the first. Each one exists because somebody spent a month learning why it was needed.

Business continuity. What happens if the site stops producing: how much notice, what stock is held, whether a technical package can be released to a second site. The clause is often refused on the grounds that it is commercially sensitive, and it can usually be satisfied with a statement about notification rather than about capacity.

Sub-supplier visibility. Whether the customer is told when a critical starting material changes source. Without it, the notification duty stops at the supplier's gate and the chain beyond that gate is invisible, which is where the last decade's most expensive quality failures have lived.

Regulatory support. What the supplier will provide, and how quickly, when the customer's own filing is questioned. A letter, a batch record extract, a method summary. The clause is two lines and it converts a favour into an obligation at the moment the customer has least leverage.

Exit. What happens to the technical package, the retained samples and the open investigations when the relationship ends. Suppliers rarely plan for this and customers rarely ask, and both regret it when a source is discontinued.

The ICH Q10 framework supplies the vocabulary for most of these, and the PIC/S inspection guides show how each is tested in practice. The EudraLex volume 4 requirements on quality agreements are a reasonable template for what the annex should cover even outside the EU.

A two-page annex that works

Two pages is enough if the pages are organised around events rather than around topics. A topic list produces a document that is comprehensive and unusable. An event list produces one that is short and gets read.

When a batch is released. What documents travel with it, in what format, within what period.

When a batch fails. Who is told, within what period, with what content, and what happens to material already shipped.

When something changes. The categories, the notice periods, the data package.

When the customer disagrees. The referee laboratory, the sample, the method, the cost.

When the relationship ends. The records, the samples, the open items.

Five events, two pages, and the annex becomes a document that somebody can actually consult at the moment it matters. The alternative, a twenty-page annex organised by topic, is consulted once at signature and never again, which is why the referee laboratory is usually chosen by argument rather than by contract. The specification gap analysis belongs in the first section and the complaint loop in the second.

Frequently asked questions

Is a quality agreement legally binding?

It is a contract annex and it binds the parties that sign it. Its practical force comes from being specific: an annex that says the supplier will notify significant changes is decorative, while one that lists the changes, the notice period and the data package is enforceable. Vague clauses are not enforced because they cannot be tested.

Which clause causes the most disputes?

The testing-dispute clause, or its absence. When two laboratories disagree about a batch, an agreement that names the referee laboratory, the sample to be used and who pays decides the matter in a week. Without one, the same disagreement becomes a commercial negotiation in which the material is held hostage by the argument.

Should the quality agreement be signed before the first order?

Yes. A quality agreement signed after the first shipment is a description of what already happened rather than a set of obligations. Suppliers sometimes offer to send it with the first delivery, which is a polite way of saying it does not exist yet.

How often should audits be allowed?

Once a year for cause, plus once every two to three years routinely, is a common shape. The clause should also cover remote audits and document-only audits, because a supplier who will accept a visit but not a video walk-through is a supplier whose audit clause was written before 2020.

Do we need a recall clause for a raw material?

Yes, even though a raw material is rarely recalled in the consumer sense. The clause is about notification and traceability: who calls whom within how many hours, what distribution records exist, and how far back the chain can be reconstructed. Without it, a downstream problem becomes a search through invoices.

What should we refuse to accept in a quality annex?

A clause that makes the supplier the sole judge of a specification dispute, and a clause that allows specification changes without notice. Both appear in templates more often than they should, usually because nobody read the annex before signing it.