Curated articles written by supply chain experts to help suppliers win at retail.

Don't let Walmart Post-Audits catch you off guard in 2025. Join Allie and Bekah to learn best practices for preventing and disputing Post Audits.

Prepping for Walmart Audits

Post Audits are preventable and disputable! Join Allie and Bekah to learn how to best prepare for Walmart Post Audits.

Articles

Chargeback Management Strategy: Chargeback Administration vs. Chargeback Recovery

When a supplier receives a deduction, it’ll land on the remittance with a code and a dollar amount, but usually not much else. What’s missing often includes which of two different processes produced the deduction. 

Most retailers run two separate systems behind every deduction. The first is a real-time compliance engine that checks current shipments against the retailer’s compliance rules. The other is a retrospective review that goes back through closed transactions, looking for what the first system missed.  

A chargeback management strategy built around only one of these processes leaves suppliers guessing on the other, delaying the response to the deduction. This article names both processes, shows the practical tells that separate them, and explains what you can do about each. 

Chargeback administration is the compliance engine running in the background of nearly every retailer transaction. It checks shipments against defined rules: on-time in-full (OTIF) delivery, 

 (ASN) accuracy, and labeling. Additionally, chargeback administration deducts automatically when a shipment misses the mark. Because it runs close to the shipment date, the deduction usually shows up on the very next remittance, tied to a specific purchase order. Chargeback administration is typically an automated process, although manual review could be involved in investigating and disputing deductions. 

The retailer's vendor scorecard tracks the same rules, so most suppliers already recognize this deduction type. It's also mostly automated, and no auditor reviews the case individually before the system generates a deduction. 

Chargeback Administration Often Catches: 

Chargeback recovery works differently. A retailer, or a third-party firm working on its behalf, goes back through closed transactions, looking for what the first process missed. This is often called a 

, and it isn't unique to any one retailer. Most retailers that run a compliance program also run some version of this retrospective audit, typically through a third-party firm paid on a percentage of whatever is recovered. 

Walmart post audits, for instance, can surface up to two years after the original transaction. One of four external audit firms runs them on Walmart's behalf: Apex Analytix, Cotiviti/Connolly, PRGX, or Auditec. Post audit claims typically arrive as a packet and carry a specific signature. The claim numbers run nine digits long, and when deducted from a check, they post under store code "9000."  

: If you see a "9000" deduction but no third-party auditor has contacted you, that's more likely a same-cycle administration deduction, such as OTIF or the 

 (SQEP). This isn’t a post audit and can be disputed directly. 

Chargeback Administration vs. Chargeback Recovery at a Glance 

Why the Distinction Matters for Your Chargeback Risk Management Strategy 

Suppliers who treat every deduction the same way lose ground versus suppliers who don’t. 

A chargeback administration deduction is recent and documented. The shipment, the ASN, and the proof of delivery are all easy to pull, and the dispute window, while real, gives you weeks to work with.  

A chargeback recovery claim, on the other hand, is the opposite. By the time it arrives, the transaction might be a year or two old, the paper trail is harder to reconstruct, and the dispute window can be as short as five days. 

That gap changes what suppliers should prioritize. For administration deductions, speed matters less than accuracy, since you have time to pull the right documentation and dispute properly. For recovery claims, speed is everything, because the clock starts the moment the claim packet arrives. 

A Quick Sorting Aid for Your Next Deduction 

Before you decide how to respond to a new deduction, ask three questions. 

What is chargeback management, and how is it different from chargeback recovery? 

Chargeback management is the umbrella term for how a supplier handles deductions overall. It covers both 

. Chargeback recovery is one specific type of deduction process: the retrospective review, often run by a third party, that retailers like Walmart call a post audit. 

How long does a post audit take to surface? 

It could be years after the original transaction. Suppliers can receive more than one post audit within that window. 

Can suppliers prevent chargeback recovery claims the same way they prevent administration chargebacks? 

Not directly. Clean ASNs, accurate item data, and routing-guide adherence largely prevent chargeback administration. Chargeback recovery works differently. The retailer, not the supplier, controls when a post audit happens, so 

Want To See How Revenue Recovery Handles Both Sides of This? 

Sorting a deduction into administration or recovery is useful. Acting on it fast, with the right documentation, is what actually gets the money back. SPS Revenue Recovery tracks both chargeback types in one place, so a dispute moves at the right speed whether the clock is giving you 90 days or 5. 

Not ready to talk to sales? The Supply Chain Source has more on 

 for suppliers working through the same process. 

Deduction Dispute Prioritization: A Peak-Season Triage Framework 

Most deduction analysts know how to identify a potentially invalid claim. The struggle comes when more claims need attention than the team has time to handle. 

That challenge becomes greater during peak season. Higher order volume can create more deductions while analysts manage tighter deadlines and other operational priorities. 

A clear prioritization process helps teams decide which deductions deserve attention first. It also helps them identify claims that can be handled together and recurring issues that need an operational fix. 

A deduction can be invalid and still require more time to dispute than the potential recovery justifies. 

The second claim may deserve attention first, even though both deductions are potentially invalid, since it’s a larger amount to recoup with the necessary rebuttal easily available.  

 shows that suppliers dispute about 20% to 30% of deductions on average, and suppliers win back about 40% of disputed deductions. These figures show the potential value of having a process for deciding which claims enter the dispute workflow.  

During peak season, that process can help analysts focus their time where it can have the greatest impact. 

A practical deduction prioritization process considers four factors: 

These factors help teams compare claims competing for the same resources. 

We recommend beginning with timing. Review each claim against the applicable retailer or distributor dispute window. A claim that’s approaching its deadline may need immediate attention, even if it would normally rank lower in the queue. 

Before the deadline passes, decide whether to: 

Retailer requirements vary, so teams should use the specific terms and dispute process that apply to each claim. 

Next, look at the amount you could recover through a successful dispute. 

Expected recovery = deduction value × estimated win likelihood 

Historical results can make these estimates more useful. If a supplier has reliable data for a specific retailer and deduction code, past dispute results can help establish an expected win likelihood. 

When reliable history is unavailable, teams can use a conservative estimate and update it as they collect more results (a good reminder that data is your friend in the retail supply chain). 

Expected recovery shows the potential value of a claim. It does not show how much work the claim will require. 

Consider what the analyst needs to do before submitting a dispute: 

A claim with documentation already available may take minutes to prepare. Another claim may require hours of research. 

Teams can compare expected recovery with estimated effort using: 

Expected recovery per analyst hour = expected recovery ÷ estimated dispute time 

This calculation gives analysts another way to compare claims when several need attention at the same time. A high-value claim may deserve additional attention because of its financial impact, retailer relationship, or its potential to reveal a larger issue. 

Look for Opportunities To Group Claims 

Some deductions are easier to manage together. Suppose 40 shortage deductions come from the same distribution center (DC) and follow the same pattern. Researching each claim separately could create unnecessary work. 

Grouping related claims can reduce duplicate work while giving teams a clearer view of recurring problems. 

Decide Whether To Dispute, Group, or Close 

Prioritization should lead to a clear action for each claim. 

Prioritize a claim for dispute when it has meaningful expected recovery and the available evidence supports the claim. 

Group related claims when they share documentation, a root cause, or the same dispute process. 

Escalate when a claim requires a decision that an analyst can’t make from the available information. 

For example, a group of small deductions may have limited value individually but significant combined value. The pattern may also point to an issue that needs attention in fulfillment, shipping, invoicing, or another part of the supply chain. 

A team may decide to close a deduction when the expected recovery does not justify the effort required to pursue it. 

If your team uses a dollar threshold, review it regularly. Changes in staffing, processes, retailer requirements, or technology can change the amount of effort required to recover a deduction. 

Track why claims are closed so the team can identify recurring patterns. 

Bissell provides an example of how manual work can affect deduction recovery. 

Before using SPS Commerce, Bissell had been writing off thousands of deductions under $500 because the manual process required too much time. After implementing 

 eliminated that write-off threshold and recovered 6,000 deductions that otherwise would have been written off. 

The example shows why teams should consider the cost of the dispute process when setting recovery thresholds. 

A $300 deduction that takes an hour to research may receive a different priority from a $300 deduction that takes a few minutes to submit. When technology reduces manual work, more claims may become economically viable to pursue. 

The factors used to prioritize deductions stay the same during peak season, while 

More deductions can enter the queue while analysts manage higher order volume, retailer requirements, and other time-sensitive work. 

That makes three areas especially important: 

Review approaching deadlines frequently. Decide what to do with those claims before the available dispute window closes. 

Compare expected recovery with the effort required to pursue each claim. Use historical results when available. 

Keep recovery work separate from root-cause work. A recurring deduction may point to a process issue that causes more losses over time. 

How Automation Helps Teams Prioritize Deductions 

Manual deduction work makes it hard to set priorities. Analysts often need to pull data from several systems before deciding what to do with a claim. Automated tools bring that data together and cut the manual work needed to research and document each deduction. 

 used Revenue Recovery to automatically spot, document, and dispute deductions. Over seven months, the company disputed $421,500 in invalid Walmart deductions and raised its Walmart deduction recovery rate by 130%. 

The process also showed Eagle Foods more about the root issues behind its deductions, which can help teams make better calls on both recovery and prevention. 

Use this checklist when reviewing potentially disputable deductions: 

The Hidden Cost of Nordic Mergers and Acquisitions (M&A) 

The Nordic region has emerged as one of Europe's most active merger and acquisition (M&A) markets, and this trend shows no signs of slowing. When companies merge, how they handle post-acquisition challenges, especially across multiple ERP systems, determines whether operational disruption lasts months or persists for years. 

Background: M&A Activity in the Nordic Region

, and the pace held steady through mid-year with approximately 1,100 deals continuing each quarter since early 2024. Deal value tells a similar story: Nordic M&A reached $100 billion in 2025, up 25% year-on-year, according to 

Recent high-profile deals underscore this momentum. Finland's Kesko agreed to acquire the Nordic operations of Dahl from Saint-Gobain for €1.20 billion. 

, with completion expected by early 2027.  

Electronics and defense sectors have seen even more intense consolidation: 

, following a record 42 transactions in 2025. 

Why the Nordics Attract So Much M&A Activity

Several structural forces explain why Nordic companies pursue so many acquisitions. 

 separate Nordic acquirers from their peers. Companies in Sweden, Norway, and Denmark typically carry lower debt levels and maintain higher cash reserves than Western European counterparts, which allows them to act decisively during economic cycles. That balance-sheet advantage has only grown as interest rates normalized.  

have also worked in favor of Nordic buyers: the Swedish krona, Norwegian krone, and Danish krone have all softened against the euro and dollar in recent years, making targets outside the region cheaper to acquire. 

 drive acquisition searches. In general insurance, consolidation through M&A became the primary path to scale. If, Tryg, Codan, and Gjensidige established themselves as regional market leaders by acquiring dozens of smaller competitors. Energy transitions and digital infrastructure investments continue to attract buyers. The Nordic region also hosts globally competitive pharmaceutical companies and highly digitalized small-to-medium enterprises, creating valuable acquisition targets for both regional and international buyers. 

. Norwegian outbound acquisitions rose 64% in the first half of 2026 compared to the prior five-year average, as companies use deals to expand internationally and build capabilities outside the region. 

This environment creates opportunity, but it also creates operational complexity that many acquirers underestimate. 

The System Challenge: Why Suppliers Struggle After M&A

When two companies merge, most keep their separate ERP systems running in parallel to avoid disruption. On the surface, this seems practical. The reality, however, is different as many supply chain operations fragment when integration should be strengthening them. 

Retailers and customers see one entity now. What they expect is unified inventory visibility, reliable forecasting, and fast responses when problems occur. What they get is a supply chain scattered across incompatible systems. 

For Nordic suppliers managing complex retailer networks, this fragmentation becomes a competitive liability. The combined business is larger yet operates with less coordination than either predecessor company had. 

An Alternative Path: Integrated Supply Chain Approach 

Most organizations managing multiple ERPs after an acquisition face a technical and operational puzzle. But while no single solution eliminates integration work, you don't have to navigate this alone. 

An integrated supply chain approach creates a single source of truth for inventory, demand, and customer commitments even when that underlying data lives across multiple ERP systems. Teams keep working with their familiar systems. Your supply chain, however, operates as one coordinated network. 

Retailers and customers gain clear visibility into stock levels and delivery windows. Forecasting synthesizes signals from both entities instead of producing competing predictions. Supply chain teams redirect hours previously spent reconciling data toward responding to actual customer needs. 

operates a global supply chain network connecting 1 million trading relationships across 4,000+ retailers and 53,000+ suppliers. It helps suppliers and manufacturers to restore supply chain visibility and coordination.  

EU Buyers Are Asking Where Your Products Come From. Here Is Why.

Where goods are made has become a commercial question in European retail. Three separate shifts are pushing in the same direction, and all three are moving at once in 2026.

EU industrial policy has moved firmly toward European manufacturing. The European Commission's 

, proposed in March 2026, introduces formal "Made in EU" requirements for public procurement from 2029. It also sets a target for businesses to source at least 30% of EU-manufactured inputs for products placed on the EU market. The Act still needs approval from the EU Parliament and Council, and its direct scope covers public contracts rather than retail shelves. Large retailers track policy direction carefully, though. Sourcing strategies take years to build, and the signal from Brussels is clear.

US-EU trade tariffs have added cost pressure to supply chains that rely on non-European sources. The US imposed base tariffs of 15% on agri-food imports from the EU, covering olive oil, wine, pasta, and a wide range of food categories, with 50% tariffs on steel and aluminium still in place. 

, as buyers and suppliers reconfigure supply chains away from routes now carrying higher costs. Suppliers whose materials or components come from outside Europe are seeing this feed directly into cost price discussions with buyers.

Retailers across Europe are making local sourcing a commercial strategy, not only a brand message. 

. Musgrave, which operates SuperValu across Ireland, sources 80% of its products from suppliers on the island. Lidl Italia builds store formats around local supply chain partnerships. 

, with changing sourcing patterns being the most common response to trade disruption.

The implications are different depending on where a supplier's production and sourcing is based.

Suppliers with European manufacturing or sourcing

Origin is now a commercial argument to make explicitly in buyer meetings. Two years ago, most buyers did not ask where inputs came from. That is changing. Buyers who are managing tariff exposure, or who have made local sourcing commitments, want documentation of supply chain geography. Suppliers who can answer that question clearly, at the ingredient or component level, are better placed to hold their margin and to win listings where a local preference is being applied.

Suppliers sourcing primarily from outside Europe

The cost base has risen. US tariffs on EU agri-food products have increased the landed cost of goods that move through transatlantic supply chains, and those increases are difficult to absorb in full. Buyers who understand the tariff context will scrutinise cost price increase requests closely. The commercial case for a product sourced outside Europe needs to address the origin question directly. Waiting for a buyer to raise it in a meeting is the harder position to be in.

Suppliers with mixed European and non-European sourcing

Full supply chain relocation is uncommon. The most practical response for most businesses is shifting specific ingredients or components to European sources, and then documenting that shift clearly. Suppliers who can demonstrate a meaningful share of European-origin inputs gain both a more stable cost base and a stronger position in commercial conversations, without rebuilding their entire operation.

What Buyers Are Asking and What Suppliers Need to Answer

The Industrial Accelerator Act's 30% EU-sourced inputs requirement does not yet apply to retail procurement. The measurement framework it introduces, treating the percentage of European-origin inputs as a documentable supply chain metric, is already shaping how European buyers think about supplier conversations.

A supplier who makes a strong case for European origin in a buyer meeting still needs to deliver on it. Getting a new listing confirmed is one step. Having the trading infrastructure in place to fulfil that first order quickly is the next.

For suppliers building or expanding EU retail relationships, 

 manages EDI connections with major European retailers through its EUR network, with document exchange and compliance requirements already configured for each retail account. The time between a listing being confirmed and the first order being processed correctly is shorter when the operational infrastructure is already in place.

How Suppliers Can Keep up With a Changing Retail Network

________________________________________________________________________________ 

A reliable truth in retail relationships is that they're always moving. Requirements change, sometimes gradually, and sometimes all at once. Retailers inevitably introduce new programs and adjust the way they expect suppliers to operate. Meanwhile, growing suppliers are adding customers and managing more connections of their own. 

Most individual changes are manageable. The difficulty typically comes from keeping track of them across a network of trading partners, systems, and internal teams. 

Network change management gives suppliers a way to think about that ongoing work. It starts with understanding what has changed across a trading relationship, then making sure that information reaches the people and processes affected by it. 

For suppliers, network change management is the process of keeping trading relationships current as retailer requirements and connections evolve. 

Some changes are technical. A retailer may update an EDI implementation guide or introduce a new requirement for the 

 (ASN). Others reach further into the operation through changes to labeling, routing, item data, or 

Change also comes from within the supplier's business. Adding a retailer introduces another set of requirements to maintain. Moving into a new channel may bring different fulfillment expectations, as growth can turn a process that worked well with a few trading partners into one that becomes difficult to maintain across dozens. 

The work is ongoing because the network itself keeps moving and developing. 

Supplier onboarding creates a clear starting point. Requirements are documented, connections are established, and internal processes are built around what the retailer expects at the time. Months or years later, those same processes may still be running even though the requirements behind them have changed. creates a clear starting point. Requirements are documented, connections are established, and internal processes are built around what the retailer expects at the time. Months or years later, those same processes may still be running even though the requirements behind them have changed. 

Retailers can, and often do, revise implementation guides or update routing requirements while orders continue moving through an established workflow. Unless someone is intentionally watching for those changes, the teams managing day-to-day orders may have little reason to know that an update has been made. 

Where Should Suppliers Look for Retailer Updates? 

While there isn't a single channel that retailers use to communicate changes, a trading partner can typically find updates in: 

The challenge is that an updated document does not always arrive with a prominent announcement. More typically, a retailer will publish a new version of a specification that replaces one a supplier has relied on for years, leaving the supplier responsible for recognizing what changed and whether it affects an existing process. 

Knowing where each trading partner publishes updates is what creates a chance to catch a change before an established process falls out of step with a retailer's current requirements. 

One Change Can Reach Several Parts of the Business 

Consider a change to an ASN. The retailer updates its implementation guide and begins requiring information that was not included in the supplier's previous EDI map. 

The map may need to change, but the work depends on where that information originates. If the new data comes from the warehouse or ERP, another system may need attention before the ASN can be updated successfully. 

Testing matters here as well. An EDI standard establishes what a transaction can contain, while each retailer’s implementation guide defines how that transaction should work within its specific environment. That means a transaction can be technically valid and still fail if it does not meet the retailer’s requirements. 

Other changes appear closer to the physical movement of goods. 

A revised carton label can affect the warehouse process that generates and applies labels. New routing instructions may change how a shipment is scheduled or tendered. An item data update can influence information used well beyond the team that maintains the retailer connection. 

The person who discovers the change may therefore have only one piece of the picture. 

A useful first question is simply: Where does this requirement show up in our operation? Asking that question helps the team follow the change far enough to update the process that depends on it. 

Building a Reliable Path for Retailer Changes 

There is no need to turn every retailer update into a large change-management project. Suppliers do need a dependable way to move new information from the trading partner to the people responsible for it. 

Vendor portals and implementation guides are common sources. Retailer emails, testing notices, and compliance communications may carry changes as well. 

Someone should be responsible for reviewing those sources. A shared inbox can collect communications, but ownership still matters. Without it, an important update can sit among routine messages while the old process continues. 

For suppliers with a large retailer portfolio, external compliance monitoring may provide another source of visibility. 

Once a new requirement is identified, look beyond the team that received it: 

This does not need to be complicated. The goal is to identify the parts of the operation that depend on the requirement before making the change. 

Testing should reflect how the requirement will work once orders and shipments are moving through the business. 

For an EDI change, that means checking the updated transaction against the retailer's implementation guide. For an operational change, it may mean following the new requirement through the workflow where it will be used. 

A small update can have downstream effects that are difficult to see on paper. Testing provides a chance to find them before live transactions or shipments are affected. 

A simple change log can save a surprising amount of detective work later. 

The record should give the next person enough context to understand what happened. That might include the retailer, the requirement that changed, and its effective date. From there, the team can capture the process affected and how the update was validated. 

Over time, this history becomes useful when an old transaction begins failing or ownership changes hands. Instead of reconstructing the decision through old emails, the team has a record of why the current process exists. 

Documentation can also help when researching a 

. If a retailer raises a compliance issue tied to a previous change, the supplier can see when the requirement was implemented and what was done at the time. 

The log only needs to be detailed enough to be useful later. 

Network Change Gets Harder as the Business Grows 

A supplier working with a small group of retailers has a relatively contained network to watch. Growth changes that equation. 

Each new trading partner brings its own documentation and operating expectations, even as existing retailers keep updating theirs. The result: The amount of change a supplier has to follow grows right along with the business. 

At that scale, a network approach can reduce some of the work carried out by individual supplier teams. When many suppliers and retailers operate through the same network, common retailer-driven changes can be identified and managed centrally rather than rediscovered by each supplier. 

A Simple Network Change Management Flow 

Retailer changes arrive in different ways, but the work that follows is fairly consistent.  

A sequence can give teams a shared way to handle that work, especially when a requirement moves across systems or departments. 

Seven-step network change management process for identifying, assigning, testing, documenting, and monitoring retailer requirement changes.

Retailer Change Process Infographic.png

The process can be scaled to the size of the change. A minor documentation update may move through quickly, while a change that reaches several systems or operational teams will need more coordination. 

What matters is continuity. Each change should have a clear path from the retailer's communication through implementation, with enough follow-through to confirm the updated process is working as expected. 

What is network change management in retail? 

Network change management is the ongoing process of keeping supplier trading relationships aligned as retailer requirements and business connections change. For suppliers, this can include updates to EDI requirements, compliance programs, operational processes, and other expectations tied to doing business with a trading partner. 

What kinds of retailer changes should suppliers monitor? 

The changes that matter will depend on the retailer and the supplier's relationship with them. Common areas include EDI implementation guides, routing requirements, labeling specifications, item data requirements, compliance programs, and fulfillment processes. 

Who should own network change management? 

Ownership depends on how the supplier is organized. One person or team should have clear responsibility for monitoring retailer communications, with a process for bringing in the teams affected by each change. The owner does not need to implement every update personally. 

How can suppliers keep track of retailer requirement changes? 

Start by identifying where each trading partner publishes or communicates updates. Assign responsibility for monitoring those sources, then keep a simple record of material changes and their effective dates. Suppliers managing many trading partners may also use external monitoring or a network-based EDI provider to reduce the amount of manual tracking required. 

Staying Current in a Changing Retail Network 

Retail networks keep moving. A process that meets a retailer's requirements today may need attention later, and a growing supplier will continue adding new relationships to manage along the way. 

The goal is to make those changes easier to see and easier to follow through the business. Clear ownership helps. So does knowing where retailer updates are published and keeping enough history to understand what has already changed. 

When a new requirement raises a question, there is also value in knowing where to look for an answer. 

 includes more than 1,500 articles covering retailer requirements, EDI, compliance, item data, deductions, and the everyday work of managing trading partner relationships. It is a place to dig deeper when a retailer changes something, a new requirement lands on your desk, or you simply need a better understanding of what comes next. 

3PL-Auswahl-Checkliste: Was neue Marken vor der Unterschrift bewerten müssen

Wenn Sie einen Vertrag mit einem 3PL-Dienstleister (Third-Party Logistics) abschließen, übernimmt dieser die physische Lagerung und den Versand Ihrer Produkte – der Einzelhändler macht jedoch weiterhin Sie verantwortlich, wenn etwas schiefläuft. Wird eine Bestellung verspätet versendet oder stimmt der Versandavis (ASN) nicht mit der tatsächlichen Lieferung überein, geht die Vertragsstrafe des Einzelhändlers an Sie – nicht an Ihren 3PL-Dienstleister.

Rechenschaftspflicht und Datenfähigkeit vor Vertragsabschluss bewerten

Articles

Curated articles written by supply chain experts to help suppliers win at retail.

Prepping for Walmart Audits

Overview

Articles