SupplierWiki curates detailed articles 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

HEAR Framework: How Warehouse Receiving Actually Works 

HEAR stands for Hold, Examine, Accept, Route, and it is a simple way to describe the four checkpoints a shipment passes through between the dock door and the warehouse shelf. Most explanations of warehouse receiving stop there and treat it as a physical-handling problem: forklifts, dock doors, labor schedules. That framing misses what is actually going wrong on most receiving docks. 

A linear, horizontal flowchart illustrating a four-step process. The first step, "Hold," is contained in a bold, blue pill-shaped outline with bold blue text. A bright blue arrow points to the second step, "Examine." Another blue arrow leads to the third step, "Accept," followed by a final blue arrow leading to the fourth step, "Route." The last three steps are enclosed in light gray pill-shaped outlines with dark gray text.

hear_framework.png

Receiving breaks down less often because someone mishandled a pallet and more often because the data behind that pallet did not match reality before the truck ever arrived. A wrong quantity on an advance ship notice (ASN), a missing item detail, a purchase order (PO) that does not line up with what physically shows up: These are data problems wearing the costume of a  physical-process. Every stage of HEAR either depends on accurate data or generates it, and the next step can’t happen until that data is right. 

What Does “Hold” Mean in the Warehouse Receiving Workflow? 

Hold is the pre-arrival stage, not a passive waiting period. Before a truck ever reaches the dock, the receiving team needs to know what is coming, when, and in what quantity. That information comes from the supplier’s ASN, and it is what makes dock scheduling possible in the first place. 

A warehouse that receives ASNs on time can pre-assign dock doors, stage labor, and prepare putaway locations before the shipment arrives. A warehouse that does not is reacting in real time to whatever shows up, which is where congestion, missed appointments, and idle labor start to compound. Hold is the step where the receiving workflow either gets ahead of the shipment or falls behind it. 

Why Does "Examine" Depend on ASN Accuracy?

Examine is where the shipment gets checked against what was promised, and it is the step most likely to expose a data problem that started somewhere else. The 

 tells the receiving team what should be in the shipment: item counts, lot numbers, packaging details, carrier information. The physical inspection is really a comparison between that document and what physically arrived. 

Eric Shelton, Sr. Customer Strategist at SPS Commerce

, put it this way: “By the time I’m looking at an ASN accuracy issue, the real problem is usually a few days old already, a warehouse management system and an ERP system that had two different versions of the same order and nobody caught it before the ASN went out.” 

 that carry shipment identification, item-level detail, and 

 references, and a mismatch in any one of those segments cascades into the Examine step. When Target evaluates 

, for example, the item information in the 856 has to match the purchase order or the shipment can be flagged for a compliance deduction, even if every physical unit arrived correctly. The inspection is only as good as the document it is checking against. 

What Happens During the “Accept” Step?

Accept is where the shipment stops being “inbound” and becomes inventory, and it is more of a systems reconciliation moment than a physical one. Signing off on a pallet is the visible part. The less visible part is the warehouse management system (WMS) and the enterprise resource planning (ERP) system agreeing that what was received matches what was ordered, at the item and quantity level, before that inventory becomes available to allocate. 

“Accept gets treated like a formality, but it’s really the last checkpoint before bad data becomes a real inventory number,” Shelton said. “If the reconciliation is sloppy here, everything downstream, cycle counts, replenishment, order promising, inherits the error.” 

This is also the step where the objectives Hold and Examine were building toward finally converge: what the receiving team recorded now has to match what the systems of record expect, or the discrepancy gets logged as an exception rather than quietly resolved. 

How Does Route Connect Receiving to Dock-to-Stock Performance?

Route is where accepted inventory gets directed to its next destination, whether that is a storage location, a cross-dock lane, or an outbound order. It is worth being precise about scope here: SPS Commerce does not make routing or putaway decisions inside a warehouse. What connects Route to fulfillment execution is the same data that made Hold, Examine, and Accept possible in the first place, flowing forward into whatever system decides where that inventory goes next. For a 3PL managing this handoff across dozens of customers at once, a standardized way to receive that data, like 

, is what keeps Route from turning into a bottleneck. 

This is also where receiving performance shows up in dock-to-stock time, the measure of how long a shipment sits between arrival and system availability. A 3PL handling consumer electronics cut its average dock-to-stock time from roughly 10 hours to under 2 by fixing pre-receiving readiness from ASN data, tightening task assignment, and moving to system-driven putaway. Those fixes were less about the physical handling than the data arriving clean enough that the physical steps could run without stopping to sort out exceptions. 

Why Fixing Data Upstream Beats Correcting It Downstream

The financial case for treating receiving as a data problem is not abstract. Walmart’s 

, and a large share of those penalties trace back to documentation, not the physical shipment itself. On the Amazon side, ASN accuracy issues sit squarely inside the chargeback categories that suppliers fight hardest to prevent: One supplier recovered 

 after auditing and correcting its ASN and deduction-tracking process, and a global CPG brand recovered more than $2 million in a year while cutting future fees by 30% through the same kind of root-cause correction. 

Those are supplier-side recovery numbers, not 3PL receiving metrics, so they are not a one-to-one proxy for warehouse operations. What they demonstrate is the scale of cost sitting behind ASN and documentation errors industry-wide, which is the same category of error that shows up as an exception on the receiving dock. Fixing a data mismatch before the truck arrives is nearly always cheaper than untangling it after the pallet is already sitting in a staging lane. 

What Does HEAR Stand for in Warehouse Receiving?

HEAR stands for Hold, Examine, Accept, Route, the four sequential checkpoints a shipment moves through from dock arrival to being available inventory. 

Is HEAR only relevant to 3PL warehouses?

No. The framework applies anywhere goods are received against a purchase order and an ASN, including supplier-owned distribution centers, though it is most commonly discussed in third-party logistics operations managing receiving for multiple customers. 

What is the single biggest point of failure in the HEAR process?

Based on the sources reviewed here, ASN accuracy during the Examine step is the most common failure point, since it is the document every later step depends on. 

Does SPS Commerce make putaway or routing decisions?

No. SPS Commerce provides the data exchange, such as ASN and purchase order information, that WMS and ERP systems use to make those decisions. The routing decision itself belongs to the warehouse’s own systems. 

Want Fewer Exceptions at the Receiving Dock?

Most receiving exceptions trace back to an ASN that did not match reality before the truck arrived. 

 standardizes and automates that EDI exchange with your retail supplier network, so the data feeding Hold, Examine, and Accept is accurate before it reaches the dock. 

 Not ready to evaluate a fulfillment solution yet? The 

Managing Retail Supply Chain Volatility and Strategies That Strengthen Supplier Collaboration

___________________________________________________________________________________ 

, industry leaders examined an often-overlooked reality that continues to shape retail supply chains: the operational fundamentals that keep daily work reactive. 

Moderated by Brandon Pierre, VP of Customer Success at SPS Commerce, the panel included Dr. Gibson of Auburn University, Andy Sutphin of Sprouts Farmers Market, and Tim Forseth of Sunkist Growers. Their discussion examined what is driving volatility, why the “perfect order” remains difficult to achieve, and why collaboration is becoming a defining 

Panel discussion featuring Brandon Pierre of SPS Commerce with Andy Sutphin of Sprouts Farmers Markets, Tim Forseth of Sunkist Growers, and Dr. Brian Gibson of Auburn University, representing retailer, supplier, and academic perspectives on retail supply chain volatility.

1.png

Change has always been part of retail supply chains. The difference today is the speed at which conditions evolve; the need for retailers and suppliers to recognize, communicate, and respond before small adjustments become operational problems. Success is no longer defined by eliminating volatility, but by managing it before it affects execution. 

Across more than 4,000 retailers globally, SPS Commerce data shows that the average order changes six times before fulfillment. Collectively, those changes place more than $600 billion in product, inventory, and shipments at risk each year. 

Teams on both sides of the retail relationship feel this disruption every day, but many organizations are not measuring where changes occur, why they happen, or what they cost. The problem is also accelerating. Order acknowledgments containing changes have doubled year over year, rising from roughly one in ten to one in five. 

That does not mean every change is a failure. Retailers need to respond to shifting demand, promotions, inventory levels, and cost pressures. But when changes are late, unclear, or disconnected from the systems and people responsible for fulfillment, they create margin pressure, service failures, and unnecessary work. 

Infographic showing signs of increasing retail supply chain volatility, including one in five purchase orders containing discrepancies, price mismatches rising from 4.5% to 5.2%, quantity discrepancies increasing from 2.0% to 2.2%, year-over-year order growth of 7% to 15%, higher order volume across toys, food, and electronics, and purchase order values declining by 25% to 31%.

2.png

 (POA) can surface a pricing issue, shortage, or delivery constraint before it becomes a missed shipment. When that confirmation arrives late, the retailer may be planning against inventory that will not arrive as expected. 

For decades, supply chain teams have pursued the perfect order: a transaction delivered complete, accurate, on time, damage-free, and without manual intervention. 

It remains a useful performance standard, but modern retail has made it harder to achieve. Customer demand changes quickly. Retailers are carrying less inventory. Suppliers are managing tighter production schedules and more frequent order adjustments. A process built around the assumption that an order will never change no longer reflects how many retail relationships operate. 

Infographic highlighting retail order volatility, showing that purchase orders experience an average of six or more changes before fulfillment, with more than 15 changes occurring on 20% of all orders.

3.png

The goal is to build a process that identifies meaningful changes early, distinguishes routine adjustments from true exceptions, and gives both partners time to respond. Success no longer means diminishing changes. It means managing it with precision. 

. A late change to quantity or timing can affect whether a supplier meets the retailer’s delivery requirements, even if the supplier had the capacity to fulfill the original order. A late change to quantity or timing can affect whether a supplier meets the retailer’s delivery requirements, even if the supplier had the capacity to fulfill the original order. 

Collaboration and Lessons from Sprouts and Sunkist 

The partnership between Sprouts Farmers Market and Sunkist Growers offered a practical example of how retailers and suppliers can manage volatility without treating every adjustment as a crisis. 

Their approach relies on regular, data-driven conversations using shared third-party sources, including IRI and Nielsen data. Rather than debating whose internal forecast is correct, the teams can begin with a more neutral view of category demand and market movement. That creates a stronger foundation for conversations about production capacity, promotional demand, inventory risk, and upcoming order changes. 

Electronic acknowledgments sent several days in advance can often be processed quickly. Same-day changes are more difficult to manage because they require direct outreach, manual intervention, and faster decisions across inventory, fulfillment, and customer-service teams. 

That distinction is incredibly important. Automation can handle routine, repeatable changes quickly. But urgent exceptions still need clear escalation paths and direct communication between the people responsible for inventory, fulfillment, and customer commitments. 

Four Ways to Build a More Resilient Retail Supply Chain 

1. Plan for Disruption Instead of Perfection 

Scenario planning helps teams prepare for the changes most likely to affect their business. Retailers and suppliers should discuss what happens when demand spikes, production is delayed, pricing changes, or a carrier misses a delivery window. 

This does not require predicting every disruption. It requires identifying where the relationship is most vulnerable and agreeing on how each team will respond before an issue becomes urgent. 

2. Measure Where Order Changes Happen 

Order changes should not disappear into email threads, spreadsheets, or individual inboxes. Teams need visibility into the type, frequency, timing, and source of changes. 

For example, a recurring quantity adjustment may point to a forecasting issue. Repeated price changes may signal an item setup or contract-management problem. Late ship-window changes may reveal a gap between merchandising decisions and supplier capacity. 

Tracking these patterns helps organizations separate necessary business adjustments from preventable process failures. 

3. Get Onboarding and Item Data Right 

Many downstream problems begin with unclear product information or incomplete expectations during onboarding. Retailers and suppliers should align on SKU variations, pack sizes, pricing, lead times, labeling, delivery windows, and escalation procedures before the first order arrives. 

 gives suppliers a clear operating framework. It also helps retailers reduce the manual intervention required when order details, shipping requirements, or product data do not match. 

4. Treat Collaboration as a Performance Metric 

Collaboration is not simply a relationship-building exercise. It is an operational capability. 

Retailers and suppliers should establish regular working rhythms, share relevant data early, and define how they will communicate based on urgency. Weekly touchpoints can prevent small issues from becoming service failures, while neutral data sources can create accountability without turning every disagreement into a debate. 

The strongest partnerships do not eliminate change. They make change easier to see, discuss, and manage. 

What is the Perfect Order in Retail? 

A perfect order is a retail transaction completed accurately, in full, on time, damage-free, and with the correct documentation and invoice. It is a useful benchmark for execution quality, but modern supply chains also need processes that manage legitimate order changes before they create fulfillment or compliance problems. 

What Causes Retail Order Volatility? 

Retail order volatility is caused by changes to demand, pricing, inventory availability, promotions, ship windows, and supplier capacity. Smaller and more frequent orders can add complexity, especially when retailers, suppliers, and logistics partners do not share timely data or have clear processes for communicating exceptions. 

An order acknowledgment is a supplier’s confirmation that it received a purchase order and can fulfill it as requested, or an update identifying changes to quantity, price, availability, or delivery timing. In 

, the EDI 855 purchase order acknowledgment helps retailers identify fulfillment issues before shipment. 

The Retail Value Chain Federation typically hosts its annual conference each fall. Visit the 

, registration information, and agenda updates. 

The modern retail supply chain may never be free of change, but retailers and suppliers can be better prepared to manage it. As Brandon Pierre summarized during the session, “Every change is an opportunity to improve the system if you can see it, measure it, and respond in time.” 

Retailers and suppliers that improve order visibility, strengthen the acknowledgment processes, and build consistent routines will reduce avoidable disruption. They can close the gap between what an order promises and what the supply chain can reliably deliver.  

The work does not stop with a single order, a quarterly review, or one industry conversation. Supply chain conditions, retailer requirements, and customer expectations continue to change, making it valuable for teams to stay connected to the ideas and conversations shaping the industry. 

, for retail supply chain news, practical insights, and updates on upcoming SPS Commerce events! 

What Are Revenue Recovery Metrics?

__________________________________________________________________________________ 

Revenue recovery is the process of identifying, disputing, recovering, and preventing revenue lost to 

, chargebacks, compliance fines, returns, and other invalid claims. For suppliers, it combines financial recovery work with the operational improvements needed to reduce future losses. 

Retailers such as Walmart and Target use performance metrics to evaluate supplier compliance, fulfillment execution, and financial performance. Suppliers can use many of those same metrics to understand where revenue is being lost, which deductions are recoverable, and which operational issues require attention. 

Revenue recovery metrics help suppliers measure the size of their deduction exposure, the effectiveness of their dispute process, and the speed at which revenue is recovered. This article explains four core metrics:  

The following four metrics give suppliers a practical framework for measuring chargeback exposure, recovery performance, and dispute efficiency. 

Infographic explaining four key revenue recovery metrics suppliers should track: gross chargeback rate, net chargeback rate, dispute win rate, and average time to resolution, with formulas for measuring retail deductions and dispute performance.

Chargeback Recovery (6 x 3 in).png

Tracking these four KPIs helps suppliers measure the financial impact of deductions, evaluate dispute success, and identify opportunities to improve revenue recovery performance.

Revenue recovery is a supplier’s ongoing process for finding lost revenue, validating retailer deductions, disputing invalid charges, and preventing the same issues from recurring. It applies to deductions and chargebacks tied to shipping, invoices, 

A strong revenue recovery program does more than recover money after a deduction occurs. It gives suppliers clearer visibility into recurring issues, supports better documentation practices, and helps teams improve the processes that create avoidable deductions in the first place. 

Retail deductions can quietly reduce supplier profitability, especially when teams do not have a clear process for reviewing, disputing, and preventing them. Suppliers can lose an estimated 5% to 7% of retail revenue to erroneous charges, while many invalid deductions go untouched because teams lack the time, documentation, or visibility required to dispute them effectively. 

Revenue recovery matters because it helps suppliers protect margins that have already been earned. By tracking deduction patterns, validating claims with supporting documents, and improving dispute workflows, suppliers can identify which losses are recoverable

 and which operational issues are creating repeat chargebacks. 

The goal is not only to win more disputes. It is to reduce preventable deductions, shorten the time required to resolve valid disputes, and give finance, operations, and customer teams a shared view of revenue risk. 

The gross chargeback rate measures total retailer deductions as a percentage of gross revenue. It helps suppliers track how much revenue is being deducted before returns, allowances, and recovered funds are considered. 

 Total deduction dollars ÷ gross revenue dollars × 100 

Deductions here refer to any decreases in revenue due to: 

Suppliers can use this metric to see how much revenue is being lost to deductions over time and whether their recovery and prevention efforts are reducing that exposure. It can also reveal whether deduction activity is concentrated with a specific retailer, customer program, product category, or fulfillment process. 

Suppliers should evaluate the gross chargeback rate at both the company level and the retailer level. Reviewing the metric by retailer can help teams identify where requirements, documentation gaps, or fulfillment processes are creating the greatest financial risk. 

The goal is to reduce deduction dollars as a percentage of business over time. Rather than relying on a single industry benchmark, suppliers should set targets based on their retailer mix, product category, fulfillment model, and the deduction types included in the calculation. Suppliers should establish a baseline, identify the most common root causes, and measure improvement over time. 

How Do You Calculate Net Chargeback Rate? 

The net chargeback rate measures deductions as a percentage of net revenue after returns, allowances, and recovered revenue are considered. It provides a more complete view of the financial impact of deductions because it accounts for money recovered through successful disputes. 

 Net deduction dollars ÷ net revenue dollars × 100 

Like the gross chargeback rate, this metric helps suppliers track deduction exposure over time. The difference is that the net rate reflects the effectiveness of revenue recovery efforts by showing the deduction amount that remains after recoveries are applied. 

The key difference between gross and net chargeback rates is that the net rate accounts for revenue recovered from invalid deductions and adjusts revenue for returns and allowances. This makes it especially useful for measuring the financial results of a supplier’s dispute and recovery process. 

A high net chargeback rate may indicate that deductions are occurring frequently, that too few deductions are being disputed, or that disputes are not being resolved successfully. Suppliers should review the underlying deduction codes, retailer requirements, 

, and operational processes before assuming the issue is related to customer dissatisfaction or product quality. 

Suppliers can track the net chargeback rate across the entire business or by individual retailer. The objective is to reduce the percentage over time by recovering money lost to invalid deductions and addressing the operational causes behind valid deductions. 

A chargeback dispute win rate measures the percentage of resolved deductions or chargebacks that a supplier successfully overturns. It shows how effective the supplier’s dispute process is at recovering revenue from invalid retailer claims. 

A strong win rate can indicate that a supplier is selecting reasonable disputes, submitting complete documentation, and meeting retailer deadlines. A low win rate may signal that claims are being disputed without sufficient evidence, documentation is incomplete, or recurring compliance issues are creating valid deductions. 

Win rates are helpful for both suppliers and retailers to track, and both parties are invested in keeping an accurate account of these. 

Suppliers can use win-rate data to identify 

, determine which disputes are most likely to succeed, and prioritize process improvements. For example, repeated disputes involving shipment timing, PO accuracy, or proof –of delivery (POD) documents may point to a broader operational issue that needs to be addressed. 

Suppliers should track win rate by retailer, deduction code, dispute type, and time period. This level of detail helps teams distinguish between deductions that are routinely recoverable and deductions that require operational changes to prevent future losses. 

 Number of disputes won ÷ total number of resolved disputes × 100 

A higher win rate generally means a supplier is recovering a greater share of the deductions it chooses to dispute. However, win rate should be evaluated alongside total deduction volume, recovered dollars, and dispute cycle time. A high win rate alone does not necessarily mean the supplier is disputing enough of its eligible deductions. 

By monitoring win rate over time, suppliers can improve dispute selection, strengthen documentation practices, and focus resources on the deductions with the greatest recovery potential. 

How Do You Measure Average Time to Dispute Resolution? 

Average time to dispute resolution measures how long it takes to resolve a retailer deduction dispute, from the date the dispute is filed to the date a final decision is reached. It helps suppliers understand the efficiency of their recovery process and the length of time revenue remains unresolved. 

Long resolution times can delay cash recovery, increase administrative work, and make it harder for teams to identify recurring issues quickly. Tracking this metric can reveal bottlenecks in documentation collection, claim submission, retailer response times, or internal approval workflows. 

 Total time taken to resolve all disputes ÷ number of resolved disputes 

This calculation gives suppliers a measurable average that can be tracked over time, compared across retailers, and reviewed by dispute type. It can help teams determine whether recovery workflows are becoming more efficient or whether specific deduction categories are taking too long to resolve. 

The objective is to reduce the time required to resolve disputes while maintaining accurate, well-supported claims. There is no universal target because resolution time varies by retailer, deduction type, documentation requirements, and dispute complexity. 

By reducing the average time to resolution, retailers can: 

There is no specific target for this metric. Each retailer's average time may vary depending on the complexity of the disputes and industry standards. Some disputes may require more time due to their intricate nature, while others could be settled more swiftly. 

When suppliers monitor gross chargeback rate, net chargeback rate, dispute win rate, and average time to resolution together, they gain a clearer picture of both revenue loss and recovery performance. These metrics can help finance, operations, and customer teams prioritize the deductions that require action, recover more invalid charges, and reduce preventable revenue loss over time. 

How to Reduce Chargebacks from Retailers 

Reducing retailer chargebacks requires suppliers to address both the financial claim and the operational issue that caused it. The most effective programs combine deduction recovery with prevention measures that improve compliance, documentation, and visibility across order fulfillment. 

A supplier cannot eliminate every deduction, but a structured revenue recovery process can reduce preventable chargebacks and improve the likelihood of recovering invalid claims. 

Frequently Asked Questions About Revenue Recovery Metrics 

A good chargeback rate depends on the retailer, product category, fulfillment model, and deduction types affecting the supplier. The most important goal is to establish a baseline and reduce preventable deductions over time. 

What is the difference between gross and net chargeback rate? 

Gross chargeback rate measures total deductions as a percentage of gross revenue. Net chargeback rate measures deductions as a percentage of net revenue after returns, allowances, and recovered revenue are considered. The net rate provides a clearer picture of the financial impact that remains after successful disputes. 

How do I dispute a retailer chargeback? 

To dispute a retailer chargeback, review the deduction reason code, confirm whether the claim is valid, collect the required supporting documents, and submit the dispute within the retailer’s deadline. Supporting documentation may include purchase orders, invoices, bills of lading, proof of delivery, shipping records, or retailer-specific compliance documents. 

Why are suppliers losing revenue to deductions? 

Suppliers lose revenue to deductions when retailers issue chargebacks, compliance fines, shortage claims, returns, pricing claims, or other offsets against invoices. Some deductions are valid, but others may be inaccurate, unsupported, duplicated, or caused by documentation gaps that suppliers can address through a structured revenue recovery process. 

How SPS Commerce Revenue Recovery Helps Suppliers Protect Margin 

SPS Commerce Revenue Recovery helps suppliers identify, validate, dispute, and prevent retailer deductions across their retail business. By connecting deduction data with supporting shipping, invoice, and fulfillment documents, suppliers can review claims more efficiently and build a clearer view of where revenue is being lost. 

 can help teams automate documentation collection, validate deduction claims, prioritize disputes, and identify recurring compliance issues that contribute to chargebacks. This gives finance and operations teams the information they need to recover eligible revenue while reducing future losses. 

Get a complimentary recovery audit to understand where deductions are affecting your business and 

Shelf Life, Expiration, and Stability Testing Basics 

____________________________________________________________________________________ 

On a typical package, shelf life seems like the simplest thing: A date, printed small, easy to skim past. But that single number is the output of three separate disciplines, which most brands manage in three different departments.  

on the label or left off depending entirely on a product's subcategory, and then 

by retailers the moment a shipment hits the dock.  

The trouble starts when a brand treats these as one problem, or assumes the rules that apply to one product apply across the whole catalog. An OTC drug, a face cream, and a supplement can sit side by side on the same shelf and follow three different sets of rules for whether that date is even required. Miss the rule on one end and you carry regulatory exposure. Miss the data on the other and you get rejected shipments, chargebacks, and write-offs on stock that was fine when it left the building. 

This piece examines all three links: what stability testing actually measures, when a date has to go on the label, and what happens to that date once it becomes supply-chain data your trading partners check on receipt. 

Before a date can go on a label or into a shipment, someone has to prove its efficacy. That proof comes from 

, which measures whether a product maintains its quality after time passes and conditions change. 

Stability testing measures four properties: 

A product holds its shelf life only as long as all four stay within spec. The expiration date is the point where the testing can no longer promise they do. 

There are two common ways to perform stability testing. 

Most stability programs run both at once: accelerated studies to support launch and real-time studies to verify shelf-life over time. 

The output is the part brands tend to misread. Stability testing does not hand back a generic number for a category. It produces a shelf-life duration tied to a specific formulation, specific packaging, and specific storage conditions. Change the bottle, change the closure, reformulate, or store it warmer than tested, and the date no longer applies.  

Brands who outsource manufacturing frequently assume their contract manufacturer ran that testing and owns those records, and sometimes that is true. When a retailer, auditor, or recall investigation asks what backs the date, a brand should be able to point to the underlying stability study on file. That documentation is what turns the printed number from a claim into a defensible one. 

The Label: Determining the Subcategory  

Here is where brands with a mixed catalog get caught. Two products can look identical on the shelf, sit in the same store, ship through the same door, and still follow completely different rules about whether a date has to appear at all. Classification, not chemistry, is what decides what the label owes the customer. 

Here are the three subcategories that brands most often deal with: 

: The descriptions above are general orientation, not legal or regulatory advice. Dating requirements vary by product, by the claims a product makes, and by jurisdiction, and they change over time. Before you set dating policy for a specific product, route the specifics to qualified regulatory counsel or the appropriate internal team rather than treating any summary, including this one, as the final word. 

Up to this point, the date has been a lab result and a labeling decision. The moment the product ships, the date becomes operational data that other companies act on. A retailer's receiving system does not care how carefully the stability study was run, but rather cares what date is on the carton, what date is in the file, and whether the two agree.  

. Most retailers will not accept a product just because it has not yet expired. Instead, they require a 

minimum percentage of its shelf life to be still remaining on the day it arrives

, often expressed as a rule like "at least 75 percent of stated shelf life left on receipt." A product with a valid, unexpired date can still be rejected at the dock for arriving too close to that date.  

This means that the expiration or best-by date and the lot code have to travel accurately through the advance ship notice and the item data, and they have to match what is physically printed on the carton. When the ASN says one lot and the pallet holds another, or the date in the item record does not line up with the date on the package, the shipment fails verification.  

Accurate date and lot data are also what makes rotation and recall work. First-expired-first-out and first-in-first-out only function when every unit's date and lot are known and trustworthy, both in the warehouse and in the data moving ahead of the shipment. The same is true for recalls: When a specific lot has to come off shelves fast, clean lot data is what lets a brand and a retailer isolate exactly what is affected instead of pulling everything and eating the difference. 

The Risks of Disconnected Shelf-Life Data 

The three links share one number but rarely share one owner. When different groups work in isolation, the failures surface downstream, at a receiving dock or in a deduction. Three failure modes account for most of it: 

A Practical Shelf-Life Checklist for Brands 

Shelf life is manageable once you treat it as three linked jobs instead of one number. Work the chain in order, and confirm each link before you rely on the next: 

Run top to bottom, the checklist is also a diagnostic: if a shipment gets rejected or a date can't be defended, the failure traces back to whichever link was skipped. Fix it at the source, where it's cheap, instead of at the dock, where it isn't. 

Keep Your Date and Lot Data Accurate with SPS Assortment 

Keeping expiration dates, best-by dates, and lot details accurate and consistent everywhere they travel is exactly the problem 

 solves. SPS Assortment helps ensure the item data sent to each retailer is complete, standardized, and aligned with that retailer’s requirements. 

That means the date and lot data in your item records matches what you determined in the lab and printed on the label, checked for errors before it ever reaches a receiving dock. Connect with SPS to keep every trading partner working from the same accurate product record and stop losing shipments to data that doesn't line up. 

Inbound Freight for New Suppliers: LTL, FTL, and Collect vs. Prepaid 

__________________________________________________________________________________________

For many emerging brands, the transition from direct-to-consumer (DTC) fulfillment to the world of big-box retail is a discipline shift. The moment that first purchase order (PO) hits your inbox, the excitement is often met with a mild sense of panic as you open the retailer’s routing guide. Suddenly, you are staring at terms like LTL, FOB destination, and collect pickup program. 

In most logistics explainers, terms like less-than-truckload (LTL) versus full truckload (FTL) or collect versus prepaid are treated as neutral vocabulary. But for a retail supplier, they are anything but neutral. These are the decisions that determine who controls the truck, who absorbs the compliance risk when that truck is late, and how heavily chargebacks will land on your first scorecard. 

Freight terms are essentially a framework for control and accountability. If you treat them as a back-office detail, you will likely rediscover them later in the form of on time in full (OTIF) fines and margin-eroding deductions. 

Articles

SupplierWiki curates detailed articles to help suppliers win at retail.

Prepping for Walmart Audits

Overview

Articles