£35,000 in Chargebacks in Two Weeks: When In-House EDI Breaks
A UK poultry producer tried to save budget by building its retailer EDI in-house. One validation-rule change later, trucks were turned away and the chargebacks reached £35,000 in a fortnight. Here is what went wrong, and what fixed it.
A Transalis case story for finance and compliance leaders
For a finance director, the most expensive decisions often don’t look like finance decisions at all. They look like technical ones; made a layer away; that surface months later as a number on your P&L. This is the story of one of them: a UK poultry producer, one of the largest in the country, that won a major contract with a Tier-1 supermarket and then lost its margin on the first orders to a problem nobody in the room thought was theirs to own.
The build that looked like a saving
Winning the contract came with a condition every supplier to the big retailers knows: you must trade by EDI. The producer had just moved to a new cloud ERP, Microsoft Dynamics, and the internal IT team was confident it could build the required EDI mapping directly inside it. No external provider, no subscription, the work folded into a project that was already under way. On a spreadsheet, it looked like the prudent choice. The connection went live, the first orders flowed, and everyone moved on.
What broke
A few weeks in, the retailer did something entirely routine: it updated its back-end validation rules and the scheduling for electronic dispatch notes. Retailers do this regularly, and a managed connection absorbs it quietly. The custom internal build did not. At one of the busiest points of the year, the producer’s code failed. Advance shipping notices stopped registering. Delivery trucks arrived at the supermarket’s distribution centre carrying data the automated gates would not accept, and the gates did exactly what they are designed to do: they rejected the loads and turned the trucks away. Perishable stock sat spoiling while the team scrambled to work out why a system that had worked last week suddenly didn’t.
The bill: £35,000 in two weeks
The financial damage arrived automatically. Compliance chargebacks for the rejected deliveries totalled more than £35,000 in just two weeks, enough to wipe out the profit margin on the initial orders entirely, before you even count the spoiled inventory and the strained relationship with a brand-new retail partner. This is the part finance leaders should sit with: the cost of in-house EDI is almost never the build. It is the day a partner changes a rule, the build quietly breaks, and nobody is watching the pipeline closely enough to catch it before the penalties land.
The fix: a managed outcome
The producer scrapped months of internal development and moved to Transalis. The difference is one of ownership. Rather than maintain the mapping themselves, they made a single managed connection, and we took ownership of the formats, transmission protocols and the retailer’s shifting validation rules. When a partner changes a requirement now, absorbing it is our job, not a 2am fire drill for an internal team that was never resourced to be an EDI department. With Transalis DataTrack™ in the supply chain, exceptions surface in real time, so a problem becomes something you see and fix before a truck is ever turned away, rather than something you discover from a chargeback notice. The pipeline was secured and the retailer relationship repaired.
Why this matters for finance and compliance
Chargebacks and On-Time, In-Full penalties are a finance risk that usually hides inside a technical decision. When EDI is built and maintained in-house, that risk is unbounded and unpredictable: it rests on whether a stretched internal team happens to catch the next spec change in time. A managed outcome turns it into a known, predictable cost, with the penalty exposure carried by the people whose entire job is to keep the pipeline compliant. For a finance leader, that is the difference between a line you can forecast and a liability you can only hope never triggers.
| EDI maintained in-house | A managed connection | |
|---|---|---|
| Chargeback exposure | Unbounded and unpredictable | A known, predictable cost |
| Who catches a retailer rule change | A stretched internal team, if it notices in time | Absorbed before it affects you |
| How you learn about a problem | From a chargeback notice | Exceptions surface in real time |
The takeaway
The producer didn’t fail because its people weren’t capable. It failed because keeping business-critical EDI compliant through constant retailer change is a specialist, full-time discipline, and the internal team treating EDI as a bolt-on, was always going to be one rule change away from a very expensive fortnight. The fix wasn’t more effort. It was handing the risk to someone who carries it for a living.
Frequently asked questions
- Why am I getting retail EDI chargebacks?
Almost always because a document failed a retailer’s validation or timing rules, often after the retailer changed those rules and your system wasn’t updated to match. The automated compliance gate rejects the non-conforming message and applies a penalty, with no human review. Catching rule changes before they reach the gate is what prevents them.
- What happens when a retailer changes an EDI validation rule?
If your connection is managed, the change is absorbed before it affects you. If you maintain EDI in-house, someone has to notice the change, re-map the data and test it in time; and if they don’t, messages start failing validation. That gap is where most chargebacks and rejected deliveries come from.
- How do we avoid OTIF penalties?
Keep the data pipeline both compliant and visible. A managed connection absorbs retailer rule changes for you, and real-time transaction visibility through Transalis DataTrack lets you catch exceptions before a delivery is rejected, rather than learning about them from a penalty notice.
Map your supply chain with us
Turn unpredictable chargeback exposure into a managed, predictable cost.
Map your supply chain