When an Advance Ship Notice (ASN) fails at 11 p.m. on a Thursday, someone gets a call. Usually it's whoever has the misfortune of being listed as the EDI contact in a retailer's system: an IT analyst, a supply chain coordinator, or in smaller organizations, whoever set up the integration two years ago and never quite handed it off. They fix the immediate problem. They do not fix the reason it happened.
That's the pattern. And it's not a fluke. It's a structural feature of how most mid-sized suppliers manage their retailer integrations.
The Problem Has a Name, But Not an Owner
Most supplier organizations have a gap between IT and supply chain that nobody officially owns. IT manages the systems: the EDI platform, the API connections, the translation maps, and the VAN subscriptions. Supply chain owns the outcomes: the orders, the shipments, the chargebacks, and the retailer scorecards. When those two worlds collide (and they do every time a PO comes in, a shipment goes out, or a label gets printed) accountability for what happens in between is undefined. McKinsey has framed this directly: the central unresolved question in supply chain digitization is whether IT or the business function actually owns the outcome.
It doesn't start out intentionally ambiguous. EDI gets set up by IT because "it's a system." The supply chain team signs off because "it's order management." Over time, nobody updates the routing guide translation maps when a retailer changes requirements. Nobody notices that the GS1 label template is pulling the wrong qualifier until Target sends a chargeback. Nobody owns the integration roadmap because, technically, the integration works. Until it doesn't.
The result is split incentives and no shared owner. IT measures uptime while supply chain measures fill rate, and the integration layer sits in between, generating chargebacks that show up in accounts receivable, trace back to the warehouse, and were caused by a mapping error nobody was watching.
What Actually Breaks, and Why It Compounds
The failure modes that fall into this gap are specific and predictable. They're also the kind that compound quietly over months before someone with P&L visibility connects the dots. Research on EDI compliance errors puts chargeback exposure from integration failures at 1–5% of gross invoice value, a number that rarely shows up on anyone's radar until it's already significant.
Failed or Late ASNs
The Advance Ship Notice is one of the most chargeback-heavy documents in retail compliance. A missed ASN window, a timing error between the WMS and the EDI platform, or a shipment that doesn't match the 856 exactly can trigger a penalty regardless of whether the product actually arrived on time.
UPC and Item Setup Mismatches
When a new item launches or a UPC changes, the update has to cascade correctly through every system: ERP, EDI platform, and the retailer’s portal. When it doesn't, the retailer's system rejects the transaction or flags a compliance defect. IT may not know a new item launched. Supply chain may not know what fields the EDI platform is reading from.
Routing Guide Violations
Routing guides change. Carriers get added, removed, and reassigned by lane. If nobody is actively monitoring and updating routing logic in the integration layer, violations accumulate. This is a particular problem when the team that negotiates carrier contracts isn't the team that updates the translation maps.
API Drift and Certificate Expirations
As more retailers move to API-based integrations, the maintenance surface grows. API specs get updated. Authentication tokens expire, and the rate limits change. These failures tend to be layered: an ERP-to-WMS sync issue compounds into an EDI transmission error, which compounds into a compliance defect the retailer flags two weeks later. None of them are dramatic in isolation. They're the kind of thing that breaks quietly and goes unnoticed until a batch of orders doesn't process.
GS1 Label Errors
Label compliance requirements vary by retailer and change more often than most suppliers expect. A label template that was accurate 18 months ago may be noncompliant today, and the team that built it may not be monitoring for updates.
What these failures share is that none of them have a clear preventive owner. Fixing them after a chargeback lands is reactive and expensive. Preventing them requires someone whose job it is to monitor compliance requirements, track retailer updates, and keep the integration layer current. That's a cross-functional role most org charts don't have a box for.
Three Ways Suppliers Close the Gap
There's no single right answer here, and any article claiming otherwise is oversimplifying. The best path depends on company size, IT capacity, and how deeply integrated the supplier is with major retailers. But the options are clear.
Option 1: Name a single owner and give them real authority.
Pick a person in IT or in supply chain and make them accountable for the integration layer end to end. Not "go-to for EDI questions." Accountable. With authority to prioritize work in both IT and supply chain when integration issues come up, with visibility into both compliance requirements and system configuration.
This works best for larger suppliers with the headcount to support a dedicated role and the org maturity to enforce cross-functional accountability. It also requires genuine executive support. An integration owner without authority to act across both functions is just a person who gets blamed faster.
Option 2: Build a dedicated integration function.
Some suppliers, particularly those with heavy retailer footprints across Walmart, Target, and Amazon simultaneously, have formalized a small integration team that sits between IT and supply chain with shared reporting. This team owns compliance monitoring, retailer requirement updates, testing, and incident response.
This is the right answer for complex, high-volume suppliers. It's probably not realistic at $25M–$100M in revenue, where the volume of integration work doesn't justify the headcount and the org isn't large enough to sustain a shared-services model without constant politics about priorities.
Option 3: Outsource the integration layer entirely.
For many mid-sized and growing suppliers, the cleanest answer to the ownership question is to remove it. A full-service EDI and integration partner doesn't just handle transaction processing. They own the monitoring, the retailer requirement updates, the compliance testing, and the incident response. The supplier doesn't need to resolve whether IT or supply chain owns the integration layer because a vendor does.
This isn't the right answer for every organization, and it doesn't solve every problem. But it's worth naming honestly: the reason many suppliers land here isn't because they couldn't figure out the org design. It's because they decided the org design problem wasn't worth solving internally when a reliable external option existed.
| Single Owner | Dedicated Function | Outsource |
Speed to implement | Fast | Slow | Moderate |
Cost | Low | High | Moderate |
Control | High | High | Lower |
Scales with retailer complexity | Limited | Yes | Yes |
Best for | Mid-size, one or two retailers | Large, complex footprint | SMB to mid-market |
Why This Question Is Getting Harder to Avoid
Suppliers who have managed the integration accountability gap through heroic individual effort are running into a problem: the gap is getting wider.
Retailer compliance requirements are tightening. Walmart's OTIF threshold now sits at 98%, with penalties reaching 3% of COGS on noncompliant shipments. SQEP has added new defect categories around PO accuracy and labeling. Target, Amazon, and Kroger have followed with similar tightening. The cost of getting integration details wrong is higher than it was three years ago, and it's not trending back down.
At the same time, IT teams at many mid-sized suppliers are leaner than they were in 2021. Headcount cuts in 2023 and 2024 reduced the capacity to proactively manage integrations even as the complexity increased. Gartner's research on CIO priorities reflects this directly: IT leaders are increasingly being pushed to share ownership of digital outcomes with business functions rather than manage infrastructure independently, a shift that makes the integration ownership question harder to defer.
And there's a third pressure starting to surface in conversations that wouldn't have happened two years ago: AI. Suppliers evaluating AI-driven demand sensing, automated exception handling, and integrated planning are bumping into an uncomfortable prerequisite. You can't build automation on a data foundation nobody owns. The integration layer isn't just where chargebacks happen. It's where the data that AI needs to function lives. If that layer is fragmented, unmaintained, and unowned, the AI conversation stalls fast.
Four Questions Worth Asking Your Org
Before any structural decision gets made, it's worth getting honest about where the accountability gap actually lives. Four questions tend to surface it quickly:
1. Who gets notified first when an ASN fails? And is that person empowered to fix the underlying cause, or just the immediate symptom?
2. Who is responsible for monitoring retailer requirement updates? Not "who would do it if someone asked them to." Who owns it as a standing responsibility today?
3. When was your EDI configuration last audited against current retailer specs? If the answer is "when we set it up," that's a gap.
4. If your primary EDI contact left tomorrow, what would break and how fast? If the honest answer is "a lot, quickly," the integration layer is currently owned by an individual, not a function.
The reason these questions are worth asking isn't to assign blame. The integration accountability gap is most expensive when it's invisible. Chargebacks are often attributed to operational failures (wrong carrier, late shipment, warehouse error) when the root cause is a mapping error or a configuration that was never updated. Until the org acknowledges the gap, it can't close it.
Automated Operation with SPS Commerce
SPS Commerce operates your full EDI stack as a managed service: transaction processing, map maintenance, retailer spec updates, compliance testing, and 24/7 exception handling. No internal routing debates about who owns what. One SLA, one team, continuous monitoring across every trading partner connection.
