factory, fish, sauce, tanks, boat, worker, nature, man, hose, vietnam, industry, production. Supplier ethics mistakes that experienced operators still make
Photo by unitea on Pixabay

Maintenance

Part of How to make supplier ethics work in practice

Supplier ethics mistakes that experienced operators still make

Nine supplier ethics mistakes buyers make, from auditing what you can see to exiting fast for the wrong reason, each with the repair that works.

The mistakes below are made by capable people running real programs. Each one is the natural result of a reasonable decision about where to spend a limited budget.

For each: how it happens, what it produces, and the repair.

What to take away

  • The commonest mistake is auditing where it is easy rather than where the risk is, which produces a full file and no findings.
  • Requiring standards you do not fund is a request that the supplier absorb your ethics. Some will; more will appear to.
  • Exiting the moment you find something protects you and often harms the workforce. It is defensible only after you have compared it with staying.
  • A chain producing no grievances does not have good conditions. It has no working channel.

1. Auditing where the light is

How it happens: audit budget goes to the largest suppliers, because that is where the spend is and where the relationship managers are.

Rank by risk, not spend

Audit by spend

Basis
Spend size
Top target
Largest supplier
File quality
Thorough
Result
Coverage rises

Audit by risk

Basis
Risk factors
Top target
Labor-intensive site
File quality
Thin
Result
Findings rise

What it produces: a thorough file on low-risk relationships and nothing on the small supplier in a labor-intensive category with seasonal peaks. Coverage rises, findings do not.

The repair: rank by risk, not by spend. Labor intensity, country, seasonality, whether recruitment runs through intermediaries, whether the process is dangerous. Then work down that list and accept that the top of it may be commercially trivial.

2. Requiring what you do not fund

How it happens: the code is written by one function and the price is negotiated by another, and nobody multiplies the two together.

Fund the code or change it

Does the arithmetic close at your volumes?

Yes

requirement stands

No

fund the difference

What it produces: a supplier who has agreed to standards their margin cannot support. The purchase order wins, and the gap is absorbed by unrecorded hours or an undisclosed second site.

The repair: cost your own code at your own volumes for the suppliers that matter. Where the arithmetic does not close, either fund the difference or change the requirement. Continuing to require it unfunded is the decision to be lied to.

3. Treating the signature as the finding

How it happens: coverage is easy to count and easy to report. Ninety-odd per cent of suppliers signed up to the code is a satisfying number.

Replace coverage with three measures

  • Unannounced findings against announced ones
  • Recurrence at the next visit
  • Grievances per thousand workers

What it produces: a program measuring its own contracting process. The number rises every year and says nothing about conditions.

The repair: replace coverage with three measures that can go the wrong way: unannounced findings against announced ones, recurrence at the next visit, and grievances per thousand workers. The discipline expected of serious diligence is described in government guidance on modern slavery and human trafficking in supply chains, which is organized around finding things rather than documenting coverage.

4. Announcing every visit

How it happens: announced audits are cheaper, easier to arrange, and get cooperation.

What it produces: a measurement of preparation. Records are tidied, the unregistered shift is absent, and the second floor is not on the route.

The repair: keep announced audits for what they can do, and add a short-notice sample. The comparison between the two is the actual measurement, and it tells you what your standard program has been seeing.

5. Never doing the arithmetic

How it happens: nobody owns the question of whether the site could physically make what it shipped.

Annual capacity arithmetic

  • Declared headcount
  • Shift pattern
  • Equipment
  • Against received volume

What it produces: undisclosed subcontracting that survives years of clean audits, because the audited site is not the site doing the work.

The repair: declared headcount, shift pattern and equipment against received volume, once a year, for the suppliers that matter. It uses records you already hold, it cannot be prepared for, and it is the highest-yield check in the whole subject.

6. Applying home standards without thinking

How it happens: it sounds principled, and the alternative sounds like relativism.

What it produces: work moved to a tier you cannot see, where conditions are worse and nobody is watching, or removed from people who needed it.

The repair: separate the absolute from the improvable. A short list you will exit over anywhere, and for everything else a trajectory with a date and a named payer for the change. Write down which standard you applied and why, because these decisions get relitigated and an unrecorded reason becomes whatever is convenient later.

7. Exiting fast to feel clean

How it happens: a finding arrives, the exposure is obvious, and termination is available under the contract.

Three exit options compared

Stay with conditions

Workforce
Keeps orders
Supplier fix
Incentive kept
Practice
Stays visible
Your file
Exposed

Exit on timetable

Workforce
Wages secured
Supplier fix
Incentive kept
Practice
Stays visible
Your file
Managed

Exit at once

Workforce
Loses orders
Supplier fix
Incentive lost
Practice
Moves to others
Your file
Clean

What it produces: the workforce loses the orders, the supplier loses any incentive to fix anything, and the practice moves to a buyer who is not asking. Your file is clean and the people are worse off.

The repair: Deal with immediate danger on its own clock. Then compare three options in writing: staying with specific conditions, exiting on a timetable with wages secured, and exiting at once.

The third is sometimes self-protection described as principle. Comparing staying, exiting on a timetable, and exiting at once is the same comparison worked through in a supplier ethics case study.

8. Building a channel and fearing its output

How it happens: a worker-facing channel is built, it starts working, and reports rise.

Reading a rise in reports

Working channel

Reports
Rise
Meaning
Mechanism works
Response
Protect reporters

Decayed channel

Reports
Fall
Meaning
No working channel
Response
Let it decay

What it produces: a program that reads the rise as deterioration, then quietly lets the channel decay. A supply chain producing no grievances has no working channel, not good conditions.

The repair: agree in advance, in writing and with whoever will see the report, that a rise means the mechanism is working. Where a worker raises a concern, what protection they have is set by law rather than your policy, and regimes like the UK's whistleblowing framework show the shape one such scheme takes.

The same dynamic inside your own organization, where a rise in reports is read as a problem rather than as the channel working, is covered in employee ethics.

9. Ignoring the suppliers closest to you

How it happens: supplier ethics is understood as a distant-factory subject, so the small local supplier is not in scope.

Local supplier payment failures

  • Extended payment terms
  • Terms imposed on renewal
  • Invoice queries near due date
  • Cancellations leaving work unpaid

What it produces: extended payment terms, terms imposed on renewal, invoice queries raised near the due date, and cancellations that leave work in progress unpaid. A treasury optimization for you; an existential event for them.

The repair: measure the gap between agreed terms and actual payment dates, own it as a number, and apply the same care you extend to a distant workforce. What is owed to a party who cannot refuse your terms is the same question asked in customer ethics from the other side.

The pattern

MistakeWhat it optimizesWhat it costs
Auditing where the light isCoverageFindings
Requiring what you do not fundThe code's ambitionThe truth of the answers
Signature as findingReportabilityAny knowledge of conditions
Announcing every visitCooperationThe chance of seeing anything
No arithmeticEffortYears of undetected subcontracting
Home standards applied bluntlyFeeling principledVisibility, and sometimes the work
Fast exitYour exposureThe workforce
Fearing the channelA quiet dashboardThe one mechanism that worked
Ignoring small suppliersWorking capitalTheir survival

Seven of the nine optimize something the buyer is measured on. That is the honest summary, and it is why this subject is mostly about the buyer rather than the supplier, as supplier ethics argues at more length. Who is placed to change any of it is the subject of leadership ethics.

Common questions

Which of these should we fix first?

The arithmetic, because it costs a day and tells you whether you have a visibility problem at all. Then your own order stability, because it is the cause you control.

We cannot afford unannounced visits. What then?

Do the arithmetic and build the channel. Both are cheaper than auditing and both see things an announced visit cannot.

Is it ever right to keep buying after a serious finding?

Yes, when staying with specific conditions leaves the workforce better off than your departure would, and when you actually enforce the conditions. What makes it wrong is staying without conditions, or leaving without comparing.

More in Maintenance

Latest from Costs Desk