Skip to main content

guide · last reviewed 2026-07-13

How to respond to a supplier code of conduct request

How to review and evidence supplier code of conduct questions without overclaiming.

Summary

Code of conduct requests often need clear acceptance, policy evidence, and escalation for exceptions.

Audience: Supplier operations teams. Risk level: medium.

Check what you are accepting

A supplier code of conduct is often a contractual document, not a survey. Signing or accepting it can create audit rights, termination triggers, and obligations that flow down to your own suppliers. Read the operative wording — especially clauses beginning "the supplier shall" — before agreeing, and treat acceptance as a business decision rather than a formality.

Map evidence

Most codes ask you to confirm you already operate in line with their expectations, so map each commitment to something you actually hold: anti-bribery and corruption policy, whistleblowing route, health and safety policy, working-conditions terms, and any standards you apply to your own suppliers. Where a commitment has no supporting document yet, note that gap explicitly — it is better raised before signature than discovered in an audit.

Flag exceptions

It is legitimate to accept a code with stated exceptions or to ask for clarification on specific clauses. If a clause needs legal or leadership review — indemnities, audit access, flow-down obligations — record who needs to look at it and hold the response until they have. A tracked exception protects you; a silent one becomes an unmanaged commitment.

Source basis

Regulatory or legal conclusions should be reviewed against current official sources before being used externally.

Keep reading

Related resources

More practical material from the resource library.