Factory delivery failure — what European buyers must document
In brief: Factory delivery failure in Bangladesh garment sourcing is a compliance event under CSDDD and LkSG, not only a commercial one. European buyers must document the supplier risk identified, escalation steps with dates, communications, remedial action attempted, and the decision to delist or continue. Without that file — produced inside 48 hours — the failure itself becomes evidence of weak due diligence.
5
Documents on file
The minimum evidence set a CSDDD or LkSG regulator will ask to see.
48 hrs
Response window
Documentation must be retrievable in two days, not assembled later.
2022
The failure I own
Three orders failed at one factory. Every protocol below was built after.
The brands I speak to treat a missed shipment as a commercial problem: late goods, lost markdown, an angry merchandiser, a chargeback negotiation. That is half the story now. Under the German Supply Chain Act and CSDDD, the same event is also a due diligence test. If you cannot show what you knew, when, and what you did, a regulator will read the failure as evidence the controls were never there in the first place.
Why does factory delivery failure happen in Bangladesh garment sourcing?
Most delivery failures in Bangladesh do not start on the production floor. They start at the bank. Factories operate on bank credit, not their own cash. Under the back-to-back letter of credit system, a factory borrows against your purchase order to buy fabric from the mill. If the bank withdraws or shrinks that facility, production halts. The order does not move because the fabric was never paid for.
I have seen this pattern across knitwear, woven, denim, and sweater factories for twenty-five years. The factory rarely tells the buyer in time. They say "fabric delay" or "vessel issue" until the gap is too wide to close. The financial signal — wages slipping from the 7th of the month to the 15th, utility payments delayed, capacity utilisation pushed above 95% with no buffer — was visible six to twelve weeks earlier, to anyone watching for it. The way Bangladesh factory financing actually works is the precondition for almost every failure I have investigated.
What documentation do CSDDD and LkSG require when delivery fails?
A regulator does not care that your order shipped late. They care whether you identified the risk, took steps, and kept records. CSDDD requires ongoing monitoring of suppliers including Tier 2; LkSG requires risk analysis, preventive measures, remedial action, and an annual public report. Neither is satisfied by a missed-delivery email thread and a BSCI certificate from twelve months ago.
The file a regulator will ask for has five elements. A written record of the supplier risk identified, with the date and the source. Dated escalation steps with the names of who acted. Communications with the factory and the buying house — saved, not remembered. Remedial action attempted, with the outcome of each step. The decision to delist the factory or continue with conditions, with the reasoning written down. What EU CSDDD requires from a Bangladesh sourcing partner covers the broader directive; for a delivery failure specifically, those five documents are the test.
How should European brands document escalation in real time?
Documentation written after the fact reads like it was written after the fact. Regulators have seen the difference. Escalation must be logged as it happens, in a dated record the brand and the buying house both maintain — and Bangladesh factory delivery failure prevention starts with that habit being in place before there is anything to escalate.
The escalation log I use runs in three columns: date, signal observed, action taken. A signal is specific — "factory wages paid on the 19th instead of the 7th, confirmed by HR contact" or "electricity bill receipt overdue, pending second request." An action is specific — "bank solvency certificate requested with 7-day deadline" or "backup factory placed on standby at 30% of order volume." If the order then fails, the log shows a brand that monitored, escalated, and acted. If the log is empty, the brand monitored nothing and acted on nothing — and that is what a regulator will read.
This is not a CSDDD theory point. It is the file my European clients receive every fortnight on every active order. It exists for exactly this reason.
Delivery failure documentation — file vs. memory
Written record of supplier risk identified, dated
Escalation steps with named owners and dates
Saved communications with factory and buying house
Remedial action attempted, with outcomes
Decision to delist or continue with conditions
Quarterly financial health checks behind the order
An email thread and a missed-shipment date
A memory of phone calls, no written log
BSCI certificate from twelve months ago
Verbal subcontracting understanding
No backup factory designated for the order
A commercial dispute, not a due diligence file
What is the difference between commercial loss and compliance event?
A commercial loss is a number. A late shipment costs you airfreight, markdown, a chargeback, a relationship. You absorb it, learn from it, move on. A compliance event is a record. It either shows your due diligence system worked or it shows there was no system in the first place.
The same factory failure produces both. The split is decided entirely by what you can show on paper. In 2022, I lived this from the buying-house side. One factory lost its bank financing mid-production, took on subcontract work to cover operations, three client orders failed. The commercial loss was visible. The accountability gap, which I name openly, was that I did not have a written subcontracting prohibition in place. The understanding was verbal. A verbal understanding, under financial pressure, is worth nothing. The 2022 supply chain failure that built Bengal Origin Co. is documented in full because the same failure today, under CSDDD and LkSG, would also be a compliance event — and the file is what decides whether you survive that inspection.
What This Means for European Brands
Treat every Bangladesh factory delivery failure as two parallel events: one commercial, one regulatory. Ask the buying house for the dated escalation log on every active order, not only when something goes wrong. Ask for the financial signals being monitored between audits — wage timing, utility payments, capacity utilisation, bank solvency certificate refresh date. If your buying house cannot produce that log inside 48 hours, you do not have a CSDDD-ready supply chain. You have a supply chain that has not yet been tested by a regulator.
The question worth asking, before the next failure, is simple. If a factory you currently buy from collapses next month, what file do you hand a regulator? If the honest answer is "an email thread and a chargeback," the work to do is not commercial — it is documentary, and it starts now. Further reading is published at bengalorigin.co/sourcing-intelligence/.
If you are unsure whether your current Bangladesh factory delivery failure documentation would survive a CSDDD or LkSG inspection, I am happy to walk through what the file should contain in practice.
Talk through your setup →