The supplier code of conduct as a compliance instrument, not a poster

Where the code sits in the contractual stack

A code has force where it is referenced by the agreement governing supply and where breach carries a defined consequence: a right to audit, a cure period, a right to suspend or terminate. Left as a website document, it functions as a statement of intent that a supplier can decline to have read. The drafting question is whether it operates as a warranty, an ongoing obligation or a condition, since each gives a different remedy. Many manufacturers discover the answer only during a dispute, when the code turns out to have been appended to a framework agreement superseded three purchase cycles ago.

Cascading upward beyond the supplier you pay

Most codes ask direct suppliers to impose equivalent standards on their own sources, which is how a buyer reaches stages it has no relationship with. Whether that happens is another matter. A tier-one supplier with modest purchasing power may be unable to impose anything on a mill or a smelter, and will simply sign. Verifying cascade means asking to see the terms actually used with their suppliers, not the promise that terms exist. Where leverage is genuinely absent, joint industry approaches tend to achieve more than another clause nobody can enforce.

Clauses that collide with local law and local practice

Codes drafted centrally can require things that are unlawful, impossible or meaningless in a supplier's jurisdiction — freedom of association where independent unions do not exist, working-hour limits below what local regulation permits and customers demand, or grievance channels that conflict with data rules. Blanket wording invites either quiet non-compliance or a supplier signing something they know is untrue. The workable approach states the principle, names the higher standard where local law and the code differ, and gives a route to raise conflicts rather than pretending they do not arise.

The records that make acceptance provable

Evidence usually means a signed acknowledgement by someone with authority, dated and tied to a version number of the document, held against the supplier record rather than in an inbox. Version control matters because codes get revised and old acceptances may not carry forward. Add to that any training or briefing provided, correspondence about specific clauses, and the audit and self-assessment history. A buyer asked how it discharged its own due diligence duty will want to show which suppliers accepted which version and when, and reconstructing that from procurement email is a bad afternoon.

Enforcement, escalation and the decision to walk away

The credibility of the whole instrument rests on what happens after a serious breach. Immediate termination sounds decisive and frequently harms the workers affected while removing your visibility of the site. Established guidance from labour and economic bodies leans towards a corrective route with defined milestones, escalation where progress stalls, and responsible exit as a last resort. Whichever path, the decision needs an owner senior enough to overrule the category manager whose line stops. Legal effect and available remedies depend on the governing law of the contract, so drafting belongs with counsel.

Frequently asked questions

A customer asks us to sign their code. What should we check before doing so?

Read what it obliges you to do beyond your own site: audit access at short notice, cascade to your suppliers, disclosure of subcontractors, data reporting, and any right for the customer to publish findings. Check whether it conflicts with codes you have already signed for other accounts or with local employment rules. Then confirm the operational commitments are ones your plant can actually meet, because signing on behalf of a site that has never seen the document is where later findings come from.

Should our code differ by supplier category?

One set of principles applied consistently is easier to defend than several variants, but the verification attached to it can reasonably vary with risk. A local packaging printer and a labour-intensive assembler in a high-risk market need different levels of checking, not different ethics. Keep the document stable and put the differentiation into what you ask for as evidence and how often you look, which is also how risk-based due diligence expectations are generally framed.

How often should a code be reissued?

Reissue when the substance changes rather than on a calendar, and treat each revision as needing fresh acknowledgement, since a supplier's earlier signature covers the version they saw. Frequent cosmetic updates generate acknowledgement chasing that produces no benefit and dilutes attention when a substantive change does arrive. Keep an archive of superseded versions with their effective dates, because a dispute will turn on which text applied at the time of the conduct in question.