How Should a Bag Factory Make a Supplier Code of Conduct Work?

Almost every bag factory that sells to export customers has signed a code of conduct. Far fewer have one that changes anything on the floor.

The document usually arrives from the buyer, gets signed by an owner, and is filed. The paragraphs about working hours, wages, child labour and freedom of association then sit untouched while production runs exactly as before. When an audit arrives, the factory produces records to satisfy the auditor, and the gap between the signed text and daily practice is managed rather than closed.

That gap matters commercially. Buyers are increasingly audited themselves, and a supplier who cannot show how a code is implemented becomes a risk to be replaced. This article is about implementation from the manufacturer’s side: what the clauses actually require, what makes them hard to meet in a bag factory, and what a credible system looks like when it is built for production rather than for an audit.

A code of conduct is not a promise about intentions. It is a set of operating controls that either exist in the daily routine or do not exist at all.

Why Signed Codes Fail

Failure is predictable, and the reasons repeat.

The Document Was Never Translated Into Controls

Words without a mechanism.

A clause stating that working hours shall not exceed a limit means nothing unless someone tracks hours, someone reviews the number weekly, and someone has the authority to stop booking overtime. Without those three, the clause is an aspiration.

Nobody on the Floor Knows It Exists

A file in an office.

In most failed implementations, supervisors and workers have never seen the code. The requirements live with an admin manager and an auditor, which guarantees that daily decisions are made without reference to them.

Records Are Produced for Audits, Not for Management

Reverse-engineered paperwork.

When a factory assembles records the week before an audit, the records describe what an auditor wants rather than what happened. That is both a compliance risk and a management loss, because the factory learns nothing from its own data.

The Buyer Never Asked How

Signature-level diligence.

Many buyers collect signed codes and never ask for evidence of implementation. Factories respond rationally to that signal, and the code becomes a formality on both sides until an incident makes it urgent.

What the Clauses Actually Require

Read as operating requirements, not values.

Working Hours and Overtime

The hardest clause in the bag industry.

Peak seasons, sample deadlines and shipment windows push hours up. Meeting a limit requires capacity planning, honest order booking and a weekly hours review, not a policy statement. Factories that accept unlimited orders against fixed capacity cannot comply regardless of what they signed.

Wages and Payroll

Calculation, not just payment.

Requirements usually concern minimum wage levels, overtime premiums, lawful deductions and payslips that a worker can understand. The common failures are calculation errors in piece-rate systems and deductions that are customary but not lawful.

Child Labour and Age Verification

Documents at hiring.

The control is an age verification step at recruitment, with identity documents checked and retained, plus a rule for what happens when a young applicant appears. In practice the risk sits with subcontracted processes and with informal labour, not with the main payroll.

Freedom of Association and Grievance

The clause most often left inert.

A functioning grievance channel means a worker can raise a problem without retaliation and see it answered. Factories often have a suggestion box and no process behind it, which is worse than nothing because it demonstrates the intent was never real.

Health and Safety

Fixed hazards, visible controls.

In leather goods, the recurring hazards are machine guarding on sewing and cutting equipment, ventilation and chemical handling in finishing, ergonomics at long stitching stations, and fire safety in storage. These are engineering and routine issues, and they are the easiest clauses to demonstrate.

Subcontracting and Homework

Where responsibility leaks.

Codes usually require disclosure and approval of subcontractors. Bag factories subcontract embroidery, printing, plating and sometimes stitching during peaks, and unapproved subcontracting is one of the most common findings because it is easy to do and hard to detect.

Turning Clauses Into Controls

The practical middle layer.

Assign an Owner per Clause

Not one compliance manager for everything.

Working hours belong to production planning, wages to payroll, age verification to HR, safety to the maintenance or EHS function, and subcontracting to the commercial team. Each owner needs a specific duty, not a general obligation to comply.

Define the Check and Its Frequency

What is looked at, and when.

A workable control names the record, the person who reviews it and how often. Weekly hours review, monthly payroll sample, quarterly subcontractor register review and daily safety rounds are all simple enough to survive a busy month.

Set the Escalation

What happens when the check fails.

A control without a consequence is a ritual. If the hours review shows a breach, the response should be defined in advance: which orders get re-phased, who is informed, and what the buyer is told.

Make It Visible to Workers

The clause has to be known.

Posting the code in the local language, explaining it at induction and repeating it at shift meetings are low-cost actions that turn a document into a reference point. Workers who know the rules are also the most effective monitoring system a factory has.

Records That Reflect Reality

The difference between evidence and decoration.

Time Records

Complete, and consistent with output.

Hours records should reconcile with production output and with payroll. When a factory reports 48 hours in a week but ships output consistent with 70, the inconsistency is visible to any experienced auditor and undermines everything else in the file.

Payroll and Piece-Rate Working

Show the calculation.

Piece-rate systems are common in bag stitching and are legitimate where the resulting pay meets the applicable requirements and overtime is calculated correctly. Keeping the workings, not only the total, is what makes the payroll defensible.

Hiring Files

Simple and complete.

An identity copy, a signed contract, an age check and a job description per worker is enough. The failure mode is not missing paperwork but paperwork for the wrong people, with informal or agency labour outside the file.

Grievance Log

Outcomes, not just entries.

A log that records the issue, the date, the response and the closure tells a buyer that the channel works. A log with entries and no outcomes tells them it does not.

Making Working Hours Realistic

The clause that exposes capacity decisions.

Planning Against Actual Capacity

The root fix.

Overtime is usually a symptom of accepted orders exceeding capacity. A factory that models output per line, per style and per week can quote lead times that do not require breaching limits, which is a commercial decision made at quotation rather than at shipment.

The Weekly Hours Review

Fifteen minutes that changes behaviour.

A short weekly review of hours by line, with a named owner, catches drift early. Where a peak is unavoidable, the review is where the response is agreed: re-phasing, temporary labour, or a discussion with the buyer about timing.

When a Peak Cannot Be Avoided

Decisions, not defaults.

Some peaks are structural. The honest approach is to plan them in advance, agree the approach with the buyer where required, and keep the records that show the planning was deliberate rather than a scramble.

Subcontractors and Hidden Labour

Where the code most often breaks.

Why Factories Subcontract

Capacity, capability, cost.

Embroidery, printing, plating and sometimes stitching go outside during peaks because the factory either cannot do them or cannot do them fast enough. Every one of those flows carries the code’s obligations to workers the factory never sees.

Disclosure That Works

A register, not a promise.

A subcontractor register with name, process, location, headcount and approval status is the basic tool. Where the register is incomplete, the factory cannot know what it is responsible for.

Verifying Without Owning

Proportionate checks.

A factory is not expected to run a full audit of a plating workshop, but it is expected to visit, to ask about hours and age verification, and to stop using a supplier that fails. Documented visits with a short checklist are enough.

Ending a Relationship

The step nobody plans.

Where a subcontractor cannot meet the requirements, the code’s obligations do not end with notice; they include a plan. Factories that think this through in advance avoid the situation of discovering a problem and having no alternative capacity.

Training and Communication

A code that nobody can recite is a code nobody follows.

Induction

The first hour of employment.

Induction should cover hours, wages, safety rules, the grievance channel and the right to raise concerns. A signed induction record is a weak proof but a useful habit, and the conversation itself is the real control.

Notice Boards in the Right Language

Accessible, not decorative.

The code and the key points should be posted where workers actually pass, in the languages they read. Boards in an office corridor satisfy nobody.

Supervisor Briefings

The layer that decides daily behaviour.

Supervisors convert policy into instruction. A short monthly briefing on hours limits, safety rules and grievance handling keeps the operating layer aligned, and it is the cheapest intervention available.

Refreshing After Change

New lines, new risks.

When a factory adds a process, changes a chemical or takes on a new product category, the relevant parts of the code need re-communication. Change is when compliance most often lapses.

Audits, Buyers and the Honest Conversation

Preparing well is not the same as performing well.

What an Auditor Is Looking For

Consistency across sources.

Experienced auditors compare records from different systems: hours against output, payroll against attendance, hiring files against the floor. Consistency is what they are really testing, which is why genuine records are easier to defend than reconstructed ones.

The Value of a Real Gap

Disclosing a finding first.

Where a factory finds a breach before an auditor does, disclosing it with a corrective plan is treated very differently from being caught. Buyers understand that problems occur; what they cannot accept is discovering them second-hand.

Answering Questions About Subcontracting

Precise, not defensive.

A clear register and a description of how subcontractors are checked answers the question completely. Vagueness invites a deeper investigation, which is the outcome the factory was trying to avoid.

Signs the Implementation Is Real

What a buyer can observe in an hour.

A short walk-through reveals most of it: hours reviewed this week, guarding in place, the code visible in the right language, a grievance log with outcomes, a subcontractor register that matches the work being done on the floor. None of those can be fabricated in a week.

When a Buyer’s Requirement Is Impossible

Say so, with a plan.

Occasionally a requirement cannot be met immediately, for example where a capability does not exist locally. Stating the constraint, the interim control and the timeline is more credible than agreeing and failing later.

The Cost Side

Honest accounting of what implementation takes.

What Actually Costs Money

Fewer items than expected.

The real costs are time-based: planning capacity honestly, running weekly reviews, visiting subcontractors, maintaining records properly. Capital costs, such as machine guarding or ventilation, are one-off and often smaller than the cost of an interrupted order.

What Saves Money

The same controls, seen commercially.

Accurate hours records reduce payroll disputes. A subcontractor register reduces the risk of an undisclosed supplier creating a recall or a reputational event. Safety maintenance reduces stoppages. Most code controls pay for themselves in operational terms well before they satisfy an auditor.

The Cost of a Suspended Order

Rarely counted in advance.

A suspension stops revenue on finished goods, holds material that has already been paid for, and consumes management time for weeks. Where it leads to re-inspection, the factory pays for the audit and for the delay, and where it leads to replacement, the sampling cycle restarts. None of that appears in a quotation, which is why the routine cost of compliance looks larger than it is.

The Cost of Failure

Larger and less predictable.

A failed audit can suspend orders, trigger re-inspection costs and, in the worst case, end a customer relationship. Compared with that, the routine cost of implementation is modest.

The Buyer’s Side of the Bargain

A code is a two-party arrangement.

Prices That Allow Compliance

An uncomfortable truth.

A buyer who negotiates a price that only works with excessive hours has created the breach they will later audit. Factories should be able to show the cost basis of a quotation, and buyers should expect to see it.

Lead Times That Fit

The same point, in time.

Compressed lead times are the most common cause of overtime peaks in bag production. A realistic development calendar, with sampling and approval time built in, removes most of the pressure before it reaches the floor.

Orders That Match Capacity

Forecasting discipline.

Rolling forecasts and honest capacity disclosure let both sides plan. Where a buyer shifts volumes late, the factory needs the option to re-phase rather than to absorb.

Health and Safety Controls That Hold

The clauses that are easiest to demonstrate and easiest to let lapse.

Machine Guarding on Cutting and Stitching

Engineering first.

Needle guards, pulley covers and interlocked guards on cutting presses are fixed once and then forgotten. A maintenance round that checks them weekly is more effective than a policy, because guards are removed for a difficult operation and not always replaced.

Ventilation and Chemical Handling

The finishing room.

Adhesives, edge paints, cleaners and finishes generate vapour, and the controls are extraction at source, correct containers, labelled secondary containers and suitable gloves. These are visible, checkable conditions rather than abstractions, which makes them fair audit questions.

Fire Safety and Storage

A warehouse risk.

Bag factories store leather, lining, cartons and foam, often in the same building as production. Clear aisles, maintained extinguishers, no smoking enforcement and an evacuation plan that has actually been drilled are the controls that matter.

Ergonomics at Long Stations

The slow hazard.

Stitching and edge finishing involve long periods in fixed postures, and the controls are bench height, seating, task rotation and breaks. Factories that ignore this see it in turnover and absence long before an auditor raises it.

Grievance and Worker Voice

The clause that reveals whether the rest is real.

Why Channels Fail

Fear and follow-up.

A channel fails when raising an issue is visibly risky or when nothing happens afterwards. Both are structural: anonymity has to be genuinely available, and outcomes have to be recorded and visible.

A Workable Design

Simple, owned, answered.

A written form or a message channel, a named owner outside the line management of the complainant, a response time and a log of outcome categories is enough. Sophistication is not the point; response is.

Reading the Log

What a healthy log looks like.

A log with a steady trickle of minor issues and a high closure rate is healthier than an empty log. An empty log usually means the channel is not trusted, not that the factory has no problems.

Protection Against Retaliation

Stated and demonstrated.

Workers need to know that raising a concern will not affect their work, and supervisors need to know that retaliation is itself a disciplinary matter. The rule only becomes real when a case is handled and the outcome is visible.

Chemicals, Leather Finishing and Worker Exposure

Specific to leather goods.

Where Exposure Happens

Finishing, bonding and cleaning.

Edge painting, adhesive bonding, degreasing and cleaning are the operations where workers are closest to chemicals. These stations deserve the specific controls: extraction, containers, gloves and a written handling instruction in the local language.

Training That Matches the Task

Not generic.

A general chemical awareness session does not replace instruction on the specific products in use. Training should name the products, the hazards and the required precautions at the station where they are used.

Records That Mean Something

Issue logs, not posters.

A chemical issue log that records what was given to which station, in what quantity and with what protective equipment is the record that demonstrates control. Posters alone demonstrate intent.

Working With Agents and Buying Offices

The intermediary layer.

Who Actually Holds the Code

Often not the buyer.

Codes frequently arrive through an agent or buying office, which may summarise, interpret or simplify them. Factories should obtain the actual requirements rather than a summary, because the details that get dropped are usually the operational ones.

Aligning Factory and Agent Expectations

One version of the requirement.

Where an agent briefs the factory differently from the buyer’s written code, the written code prevails. Confirming the interpretation in writing prevents a finding that everyone thought was already agreed.

When the Agent Pressures the Calendar

The source of many breaches.

Compressed sampling and shipping windows negotiated through agents are a common cause of overtime peaks. The capacity conversation belongs with whoever controls the calendar, which is often the agent rather than the buyer.

Documentation That Survives Scrutiny

Contemporaneous, Not Reconstructed

The dividing line.

Records written as work happens are credible. Records assembled before an audit are detectable because they agree too neatly and disagree with other systems. The practical rule is that every control should leave a trace on the day it runs.

Cross-System Consistency

The test auditors actually apply.

Hours must agree with output, payroll with attendance, hiring files with the people on the floor. Where the systems disagree, the file fails regardless of how complete each document looks in isolation.

The File a Buyer Will Ask For

Eight items, kept current.

• Time records by line, with the weekly review notes
• Payroll summary and the piece-rate workings behind it
• Hiring file checklist including agency and temporary labour
• Age verification evidence tied to the hiring file
• Subcontractor register with process, location and approval status
• Safety rounds record and the maintenance log for guards and extraction
• Grievance log with outcomes and response times
• Training records for induction and for any process change

Retention

Long enough to be useful.

Records should be kept for the period the buyer requires and for the period needed to answer a question about a past shipment. For most factories that means several years of hours, payroll and hiring files, stored so they can be retrieved by person and by period.

A Twelve-Month Implementation Path

Sequenced so that it survives.

Months One to Three: Measure

Before fixing anything.

Track hours, payroll workings, hiring files and subcontractor flows exactly as they are. The purpose is not to publish the result but to know the starting point, because a corrective plan built on assumptions fails at the first real peak.

Months Four to Six: Fix the Structural Issues

Capacity and records.

The first substantive changes are usually a capacity model, a payroll calculation check and an age verification step at hiring. These are the changes that remove the causes rather than the symptoms.

Months Seven to Nine: Build the Routine

Reviews, rounds, logs.

Weekly hours review, monthly payroll sample, daily safety rounds and a live grievance log turn the fixes into habits. This is the phase where implementation either becomes routine or quietly stops.

Months Ten to Twelve: Verify and Disclose

Test it yourself.

An internal check against the code, run as an auditor would, shows what a buyer will see. Findings should be corrected and, where material, disclosed with the corrective plan.

The First Thirty Days

A short plan that produces visible change.

1. Appoint one coordinator and name an owner for each clause area
2. Start recording hours by line, exactly as they are, without editing
3. List every subcontractor currently used, with process and location
4. Post the code and the grievance channel in the languages spoken on the floor
5. Walk the floor for guarding, ventilation, aisles and extinguishers
6. Open a grievance log with a named owner and a response time
7. Check one month of payroll for calculation and deductions
8. Set the date of the first weekly hours review and keep it

Why the Order Is Deliberate

Measuring before fixing.

The first actions are measurement and visibility, not correction. A factory that changes things in the first month without knowing its starting point cannot tell later whether the change worked, and usually cannot explain its own numbers to an auditor.

What Thirty Days Will Not Fix

Managing expectations.

Capacity, payroll systems and subcontractor replacement take longer than a month. The thirty-day plan is designed to establish the routine and expose the gaps, not to close them all.

Working With a New Buyer’s Code

Every buyer sends a different document.

Mapping Overlaps

Most clauses are common.

Buyers’ codes overlap heavily on hours, wages, age, safety, grievance and subcontracting. Mapping a new code against the existing controls shows quickly which clauses are already covered and which need new work.

Identifying the Genuinely New Requirement

A short list, not a project.

Occasionally a buyer adds something specific: a particular reporting format, a restriction on a chemical, a requirement for a worker committee. Isolating those items keeps the response proportionate.

Keeping One File per Buyer

Different audiences, one truth.

Each buyer may require its own declarations and formats, but the underlying records should be the same. Factories that maintain separate truths for separate buyers eventually contradict themselves.

Common Findings and What They Signal

Frequently Asked Questions

Is a signed code of conduct legally binding?

It is a contractual commitment between the parties and can carry consequences under the supply agreement, but its practical effect depends on how it is implemented. A code without controls is enforceable in principle and unverifiable in practice.

What is the single most useful first step?

Start tracking working hours honestly and review them weekly. Hours are the clause that most often fails in bag production, and the weekly review creates the visibility needed to fix capacity, which is usually the underlying cause.

How do we handle peak season without breaching hours limits?

Plan capacity against confirmed orders rather than against hope, quote lead times that reflect that capacity, and agree re-phasing with buyers early. Where a peak is unavoidable, decide in advance how it will be covered rather than defaulting to extra hours.

Are piece-rate wages compatible with a code of conduct?

Yes, where the resulting pay meets the applicable requirements and overtime is calculated correctly on the right basis. The risk is calculation error and unlawful deductions, so the workings should be kept and reviewed, not only the totals.

What should we do about subcontractors we cannot fully verify?

Register them, visit them, ask the specific questions the code requires, and record the outcome. Where a subcontractor cannot meet the requirements, plan a replacement rather than continuing without a decision.

How do we prove age verification to an auditor?

With an identity document copy and a hiring checklist per worker, including agency and temporary labour. The common failure is not missing paperwork but a hiring channel that bypasses the file.

Is it acceptable to prepare records before an audit?

Organising existing records is normal. Creating records that did not exist is not, and experienced auditors detect it by comparing hours against output, payroll against attendance, and hiring files against the floor.

What if a buyer’s requirement cannot be met immediately?

State the constraint, describe the interim control, and give a timeline. That is treated very differently from agreeing and failing later, and it keeps the relationship workable.

Does implementation require a dedicated compliance department?

Not necessarily. Clause ownership spread across production planning, payroll, HR, maintenance and commercial functions, with one coordinator tracking the routine, works in small and mid-sized factories. A department with no authority over production is less effective.

How often should the code be reviewed internally?

At least annually, and whenever a process, chemical or product category changes. Change is when compliance quietly lapses, and a review tied to change is more useful than a calendar date.

What does a grievance channel need to be credible?

A named owner, a log with outcomes and a published summary. Workers need to see that raising an issue produces a response without retaliation, which is demonstrated by outcomes rather than by the existence of a box.

The Bottom Line

A supplier code of conduct works when it stops being a document and becomes a set of weekly and monthly routines: hours reviewed, payroll checked, hiring verified, safety walked, subcontractors registered, grievances answered. Each of those is small. Together they are the difference between a signed commitment and a functioning system.

The manufacturer’s interest here is not purely defensive. The same controls that satisfy a buyer also produce better capacity decisions, fewer payroll disputes and fewer stoppages, which is why factories that implement properly tend to keep the discipline after the audit.

For a leather bag factory, the honest starting point is the hardest clause: working hours. A factory that can show a capacity model, a weekly hours review and a planned response to peak demand has demonstrated more about its conduct than any signed page, and buyers who understand production will read it that way.