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

Supply Chain Management From Order to Fulfillment 

___________________________________________________________________________________ 

Most content about the supply chain management process explains the concept. Far less of it walks through what actually happens between the moment a retailer's purchase order arrives and the moment a product reaches a shelf. This article maps that sequence step by step: order receipt, acknowledgment, allocation, the advance ship notice, the handoff to a carrier or third-party logistics (3PL) provider, receiving at the retailer's distribution center (DC), and the invoice that closes the loop.  

Two things move through each of these steps, the physical goods and the data describing them. The process tends to work or break at the points where one party's output becomes the next party's input. 

A digital supply chain runs on two parallel tracks. One is physical: raw materials become finished goods, get picked and packed, ship, and arrive at a store or DC. The other is data: a purchase order becomes an acknowledgment, then a shipping notice, then an invoice. These steps map to the standard process components of planning, sourcing, fulfillment, and returns described by the Association for Supply Chain Management (ASCM). 

The data track exists so each party can act on the physical track before a problem compounds. If a supplier can only fill part of an order, the data track is what tells the retailer's warehouse to expect a shortfall before a truck arrives without enough product on it. When that data moves on schedule, an exception is a quick correction. When it doesn't, the same exception travels downstream until someone finds it the hard way, usually at receiving or on an invoice. 

How Does a Purchase Order Become a Shipment? 

Each step in this process pairs a physical action with a document, and naming both shows exactly where the process is built to catch problems. 

Order receipt starts the sequence. A retailer sends a purchase order, formatted as an electronic data interchange (EDI) transaction known as an EDI 850, specifying items, quantities, pricing, and delivery requirements. Everything downstream measures itself against this document. 

Acknowledgment follows. The supplier responds with an 

, confirming it can fill the order as written or flagging a change in quantity, price, or timing. This is the cheapest point in the process to catch a mismatch. A correction made here is a one-line update. The same mismatch caught later is a short shipment. 

Allocation and fulfillment happen next, on the physical side. The supplier checks available inventory, allocates stock to the order, and the warehouse picks and packs it. 

, tells the retailer's DC what's coming before the truck arrives: item counts, pallet configuration, carton labeling, and expected arrival time. The ASN is what lets a receiving team scan a pallet and know immediately whether it matches what was promised. 

A carrier or 3PL handoff is the point where the supplier's responsibility for the physical goods ends and a logistics partner's begins. The data track keeps pace through carrier confirmations and tracking updates, so both sides know where a shipment stands without picking up the phone. 

Receiving and reconciliation happen at the DC, where the ASN is checked against what physically arrived. A match closes the loop quietly. A mismatch becomes an exception that someone, on one side or the other, now has to resolve by hand. 

Invoice and payment matching close out the sequence. The supplier sends an EDI 810 invoice, and the retailer matches it against the original purchase order and the ASN before paying. Together, these four EDI transactions form the core document flow used by retailers and suppliers. 

For a fuller walkthrough of how these documents work together, 

What Does Orchestration Mean at Each Handoff? 

Orchestration gets used as a label for "things are connected" without saying what's connected or how. In this process, it has a specific meaning: each handoff is the point where one party's data becomes another party's working instructions. A supplier's ASN becomes the DC's receiving plan. A 3PL's delivery confirmation becomes the supplier's shipment record. 

When that data passes automatically, an exception surfaces at the handoff, while it's still cheap to fix. When it doesn't, and someone has to re-key a number or wait on an email, the same exception travels downstream until it shows up as a deduction, a chargeback, or an out-of-stock. The mechanism doesn't change between those two outcomes. What changes is whether the data arrives in time for someone to act on it. 

The cost of letting that happen has gone up because major retailers have formalized the penalty for it. Walmart's Supplier Quality Excellence Program (SQEP) rolls out defect categories in phases, covering purchase order accuracy and missing or late ASNs in an early phase and barcode and labeling errors in a later one, each carrying chargebacks separate from On-Time In-Full (OTIF) penalties, according to a compliance guide from 

. OTIF misses are billed at roughly 3% of the value of non-compliant cases, and the two programs can stack on the same shipment. For a supplier shipping $50,000 a week, a 10% miss compounds to roughly $78,000 a year, according to a separate 

. Other major retailers and distributors run comparable programs. 

Where Do Small Errors Turn Into Chargebacks? 

Three short examples show how the same kind of error costs differently depending on where it gets caught. 

A quantity mismatch is the simplest case. If a supplier can only fill 8,000 of 10,000 units on a purchase order and flags that on the EDI 855, the retailer adjusts its expectations before the shipment ever leaves the warehouse. If the same mismatch isn't flagged until the goods arrive at the DC, it becomes a short shipment, which falls under OTIF. 

A missing or late ASN turns a routine receipt into a manual one. Without 

, a DC has to verify the shipment by hand, which slows down the dock and can trigger an 

 on top of any OTIF penalty already in play. 

A labeling error compounds further downstream. A barcode that doesn't match the case contents, or isn't placed on the required side of the pallet, can cause an automated DC system to reject the pallet outright, turning a packaging mistake into a full return. 

The underlying error is small in each case. What determines the cost is how many steps it travels before someone catches it. 

Two cases from outside the SPS Commerce network show what sits at either end of this process. Neither involves an SPS Commerce customer; they're useful because they show the same mechanism running at a scale most suppliers will never operate at. 

In February 2018, KFC's UK business switched its logistics partner from a company running six distribution centers to a single new warehouse operated by DHL, with the cutover happening overnight and no period where the old and new systems ran side by side. Within days, more than two-thirds of KFC's 900 UK restaurants were closed or running on a limited menu, and the disruption cost the business a 2% drop in same-store sales and a 5% hit to operating profit in the first quarter, according to 

. Supply problems continued for weeks afterward, including a 

The failure traces back to that single overnight cutover. When the new warehouse ran into delivery delays in its first days of operation, there was no connected visibility between the supplier side, KFC, and DHL to catch the problem while restaurants still had product on hand. By the time anyone outside the warehouse knew something was wrong, it had already shown up as closed restaurants. 

Zara's Continuously Connected Supply Chain 

Zara, the flagship brand of Inditex, runs on close to the opposite principle. Designers, market specialists, production planners, and store managers exchange sales data and design feedback continuously, which lets the company move a new design from sketch to store in roughly two to three weeks, against an industry norm closer to several months, according to 

 of the model, an assessment that has held up well over the two decades since. Store managers report what's selling, that data feeds back to design and production almost immediately, and stores 

None of this requires becoming Zara. The mechanism behind its speed is the same one behind an accurate ASN: data moves between every party without a built-in delay, so a problem surfaces as soon as it happens instead of 

 as a stock-out. Zara just runs that mechanism at a faster cadence and a larger scale than most suppliers need to. 

How Can You Check Your Own Process This Week? 

A supplier can hold their own version of this process up against five questions. 

A shortage reported first through a deduction notice traces back to one of the handoffs above, the point where the data should have surfaced the problem earlier. 

Reduce Friction Between Every Supply Chain Handoff 

With SPS Commerce Fulfillment, the network manages retailer spec changes and monitors your transactions proactively, so your team isn't debugging EDI workflows and can focus instead on moving the business forward. 

How to Launch a Product Into Retail: A Step-by-Step Guide for Brands 

Most retail launch content stops at the pitch. This guide starts where the pitch ends. 

Winning the purchase order is a real milestone. But the brands that stay on the shelf past the first reorder are the ones who treated the operational infrastructure as seriously as the buyer presentation. The brands that don't are the ones receiving chargebacks in week two. 

, and the operational gap is where most first-time suppliers run into trouble. 

This is a walkthrough of that operational infrastructure in the order you need to build it. 

The buyer has committed. You have a launch date. Now the clock is running on a sequence of operational steps that most DTC founders have never had to execute before. 

The sequence is not flexible. Skipping or rushing a step early in the process just relocates the problem. A reused UPC shows up as a rejected item setup. Sloppy item data shows up as a receiving exception at the distribution center. Manual order handling shows up as missed ship windows and fines. 

Every shortcut taken early in a retail launch resurfaces later as a chargeback, a rejected shipment, or a damaged buyer relationship. 

The checklist below follows the order that matters. 

Step 1: Assign a Unique Identifier to Every Product Variant and Pack Level 

Before you can sell a product to a retailer, that product needs a globally unique identifier the retailer can look up and verify. 

In the U.S., this means obtaining a GS1 company prefix and assigning a unique universal product code (UPC) to each sellable unit. The key detail most first-time suppliers miss: Every distinct variant and every distinct pack level requires its own UPC. 

A product in three sizes has three UPCs. Each size as a unit, an inner pack, and a case has nine. A retailer that scans a barcode and finds nothing in the GS1 registry, or finds a code that belongs to a different company, will reject the item before it ever reaches item setup. 

. The process, cost structure, and registry verification process are documented directly at their site. Don't use reseller barcodes for retail, and don't reuse codes from a discontinued product. Both fail at item setup. 

Step 2: Build Accurate Item Data Before Anyone Asks for It 

The item data you submit to a retailer feeds every downstream system they operate: the item setup in their product information management tool, the receiving plan at their distribution center, the shelf tag that gets printed, and the online product listing if applicable. 

Errors here are not corrected in the item setup step. They show up as receiving exceptions and deductions when a shipment arrives and the dimensions on the pallet don't match what's in the system. 

The data retailers typically require includes product dimensions and weights at the unit and case level, case configurations and pack quantities, product images (multiple angles, white background, label-readable), ingredients or materials, and applicable certifications or compliance attributes. 

Collect and verify all of this before you begin retailer-specific item setup. The cost of correcting bad item data after a distribution center has received a shipment is much higher than verifying it at your desk. 

Step 3: Get Your Packaging and Labeling to Retailer Spec 

Retailers publish vendor guides that specify exactly how your product must be packaged, labeled, and ticketed before it arrives at their facility. These guides are not suggestions. A carton that arrives without the right label in the right location is either refused or processed with a deduction attached. 

The two distinct labeling requirements to address at this stage are retail packaging compliance (what's on the product's consumer-facing packaging, including barcodes, nutrition panels, and net weights) and warehouse/carton labeling compliance (the GS1-128 shipping labels applied to cases and pallets). 

For regulated categories, specifically food, dietary supplements, and cosmetics, consumer-facing label requirements are governed by the FDA and FTC, not the retailer. This article covers retailer compliance. For regulated-label requirements in your category, consult legal and category-specific compliance counsel before going to print. 

Step 4: Build a Cost Structure That Survives Wholesale Economics 

DTC pricing is built on margin assumptions that don't survive retail. The economics are different in ways that are not obvious until your first invoice reconciliation. 

In retail, your gross margin has to absorb freight costs, trade spend (promotional pricing, Co-Op advertising, slotting fees depending on the retailer), deductions and chargebacks when compliance errors occur, and returns. Brands that enter retail at DTC-derived margin targets often discover the channel is not profitable at launch volume. 

The framework for thinking about this before the first purchase order: 

Deductions are their own discipline and worth a dedicated resource. The structure, documentation requirements, and dispute process are specific to each retailer.  

Step 5: Stand Up the Order and Fulfillment Infrastructure Retailers Require 

This is where most first-time suppliers underestimate the operational gap. 

Retailers don't email purchase orders and accept emailed acknowledgments. They transmit structured electronic data interchange (EDI) documents over standardized connections, and they expect suppliers to receive and respond in kind. For most significant retail channels, EDI capability is a pre-condition of trading. 

The core EDI transaction set for a standard retail supplier relationship includes the 850 purchase order (the retailer sends this to you), the 855 purchase order acknowledgment (you confirm receipt and acceptance), the 856 advance ship notice (you send this before the shipment arrives), and the 810 invoice. Retailers also require shipping labels (GS1-128 format) to be generated from the same system. 

Compliance with these transaction requirements is measured and enforced: Most large retailers operate chargeback programs that automatically deduct amounts from invoices when EDI documents arrive late, contain errors, or are missing. 

For brands building EDI capability for the first time, the two paths are building internal EDI capability (significant technical investment, ongoing maintenance, and compliance update burden) or connecting through an EDI network that already has trading relationships built with the retailers you're entering. SPS Commerce connects brands to more than 1,000 retailers through SPS Commerce Fulfillment, handling the transaction mapping, compliance monitoring, and retailer-specific formatting so brands meet requirements without building that infrastructure from scratch. 

, crediting easy retailer onboarding and pricing that scaled with their growth. 

For the broader make-vs.-buy evaluation, the process and software resources in this series go deeper on what to look for and what to avoid. 

What To Have Before Your First PO: 

Step 6: Scale Channel by Channel, Proving Velocity Before Adding Doors 

It’s helpful to think of a retail launch is being more than a single event. It is a first channel launch, evaluated, and then a second. 

The brands that expand successfully from one retail relationship to many use the same discipline: Prove sell-through at one account before adding the next. This matters for two reasons. First, buyers talk to each other, and a brand that demonstrates velocity at one retailer walks into the next conversation with proof instead of projections. Second, each new retail relationship requires the same infrastructure investment. Adding three simultaneously before the first is running smoothly creates operational risk across all three. 

Harry's executed this deliberately. The brand built presence in boutiques and J.Crew before an exclusive Target launch in 2016, then expanded to Walmart in 2018 only after the Target relationship was established and performing. 

, the kind of data that makes the next retailer conversation straightforward. 

OLIPOP took a different but equally staged path. The brand launched in roughly 40 Northern California grocery stores, used early sell-through data and its direct-to-consumer (DTC) subscription data as evidence of demand, and scaled from there. By the time 

, the operational model had been tested and refined repeatedly rather than deployed at full scale from the start. 

Adding retail doors creates operational obligations. Obligations you can't meet reliably destroy retailer relationships faster than not having them at all. 

Go Channel by Channel With Retailer-Specific Setup Guides 

The steps above apply across every retail channel. The execution details are retailer-specific. 

Each major retailer, Target, Walmart, Amazon, Kroger, Whole Foods, and regional grocery distributors, has its own item setup process, vendor portal, EDI requirements, routing guide, and compliance program. SupplierWiki publishes setup guides for each. Once you know which channels you're entering, the retailer-specific guide is the right next resource. 

Ready to Set Up Your Retail Operations? 

The checklist above covers the sequence. For retailer-specific execution, SPS Commerce has setup guides for Target, Walmart, Amazon, Kroger, Whole Foods, and regional distributors written for first-time suppliers working through each channel's vendor portal, EDI requirements, and routing guide. 

On the EDI side: if you're building trading relationships with several retailers at once and don't want to manage each connection on its own, SPS Commerce Fulfillment handles transaction mapping, compliance monitoring, and retailer-specific formatting across more than 1,000 retail connections. 

 to find out which retailers you can connect to and what onboarding looks like before your first purchase order arrives. 

How to Manage Product Assortment and Avoid Excess Inventory 

Excess inventory rarely arrives without warning. In most cases, the slow mover was visible in the sell-through data for weeks, sometimes months, before it became a markdown, a deduction dispute, or a discontinued item with channel inventory to unwind. Product assortment management is the discipline that catches those signals early enough to act on them. 

This article is written for suppliers, not merchants. Most assortment content is written for buyers deciding what to carry. This piece focuses on the supplier side: reading sell-through velocity at the SKU and account level, setting thresholds that surface slow movers before they become excess inventory, and making keep-fix-cut decisions deliberately rather than by default. 

The stakes are real. IHL Group's research puts 

, and vendor issues are identified as the primary driver of both overstocks and out-of-stocks. Buyers have data-driven reasons to scrutinize supplier assortments. The supplier who surfaces a problem first and arrives with a recommendation controls the narrative. The one who waits to be told has already lost the conversation. 

Why Slow Movers Persist: The Timing Problem 

Slow movers persist for one reason: suppliers act on assortment data late. The item is visibly underperforming, weeks of supply are creeping upward, and sell-through is trailing the category baseline. Without a systematic review cadence and clear thresholds, these signals drift until a buyer flags the item or a markdown hits the invoice. 

The fix is more about having consistent habits than it is adopting a more sophisticated tool. It is a consistent habit. Generating reports on weekly read of sell-through by SKU and account, with thresholds defined in advance so action is not discretionary, is a great place to start. 

Sell-through rate is units sold divided by units available, expressed as a percentage over a defined time window, typically four weeks or 13 weeks depending on the category's natural replenishment cycle. A sell-through rate of 60% means 60% of available inventory moved through to the consumer in that window. 

The number matters because it sits upstream of everything else: inventory health, forecast accuracy, buyer confidence, and gross margin. A sell-through rate that trails the category baseline by more than 10 to 15 percentage points for two or more consecutive periods is usually worth investigating. It won't always indicate a demand problem. That is what the next section covers, but it is the first signal worth catching. 

Setting Up an Early-Warning System for Slow Movers 

The goal is a simple threshold logic a supplier can implement and review weekly, even without a dedicated analytics team. Three metrics do most of the work: 

Sell-Through Rate Versus Category Baseline 

Pull the sell-through rate for each SKU at each account where it is active. Compare it to the category's historical average. A SKU running 15 or more points below baseline for two consecutive four-week periods warrants a closer look. 

Divide current channel inventory by the four-week average sales rate. A weeks-of-supply figure climbing above eight to 10 weeks, when the item's typical replenishment cycle is four weeks, signals that inventory is accumulating faster than it is moving. This is often the first visible sign before sell-through rates deteriorate noticeably. 

How long since the last purchase order was issued for this SKU at this account? A lengthening reorder gap means the buyer has enough inventory and is not replenishing. Combined with the weeks-of-supply signal, it suggests the item is slowing structurally, not just from a one-off timing gap. 

A spreadsheet tracking these three metrics weekly, with conditional formatting to flag anything outside the threshold, will surface 80 to 90% of slow movers before they become an excess. The discipline is in the cadence more than the choice of tools. 

How to Read Retailer Sell-Through Data Like an Operator 

Point-of-sale (POS) data answers specific questions. Knowing what those questions are, and what POS can't tell you, is what separates a useful read from a misleading one. 

POS data tells you units sold per store per week at the account level, by SKU and size. From this, you can calculate the sell-through rate, identify which stores are turning inventory and which are not, and spot velocity trends over time. What POS can't tell you on its own is whether a velocity problem is a demand problem, a distribution problem, or an execution problem. These three failure modes look similar in aggregate and require different responses. 

Demand Problem vs. Distribution Problem vs. Execution Problem 

A demand problem is when units per store per week are weak across all stores where the item is stocked. The item is on the shelf and visible, but consumers are not choosing it. This is a true velocity signal and warrants a keep-fix-cut analysis. 

A distribution problem is when velocity looks fine where the item is stocked, but store count is the issue. The item is performing where it exists but has not been set in a meaningful portion of the chain. The fix is a conversation about distribution expansion, not a sell-through intervention. 

An execution problem is the most commonly misread signal. 

 (inventory recorded in the system but not physically on the shelf), voids (planogram positions empty due to replenishment failures), and off-shelf placement all suppress sell-through in ways that look like demand failures. shelf), voids (planogram positions empty due to replenishment failures), and off-shelf placement all suppress sell-through in ways that look like demand failures.  

Before drawing conclusions from a weak sell-through read, check whether the item is actually available on a shelf where the system says it should be. Void rates above 5 to 7% in any given week are a reliable sign that execution, not demand, is the problem. 

The supplier who can separate these three failure modes in a buyer conversation is demonstrating a level of operational fluency that changes how the relationship works. Most vendor conversations about slow movers don't reach this granularity, and the ones that do are shorter and more productive. 

Not all slow movers should be cut. The keep-fix-cut framework forces a deliberate call on each underperformer rather than letting the tail persist by default or cutting indiscriminately. 

Some items earn their shelf space for reasons that don't appear in velocity data. An item may anchor a size or flavor architecture: the 16-oz size moves slowly, but its presence protects the facing for the 32-oz size that moves well. Some items are seasonal and will show weak velocity outside their window; cutting them based on an annual average distorts the read. Some items earn a facing strategically because the retailer wants the breadth, even if sell-through is modest. 

The test for a keep decision: does this item earn margin, protect adjacent items, or fulfill a buyer requirement that its removal would threaten? If yes, keep it and document why. 

Fix applies when the demand signal is there, but something operational is suppressing it. This is where the distribution-versus-execution analysis from the previous section matters. An item with acceptable velocity where stocked but low distribution is a fix candidate, not a cut. An item losing velocity because of a packaging issue, a pricing mismatch at retail, or a planogram placement problem can often be recovered. Fix candidates require a specific intervention with a defined timeline. If the intervention has not moved the needle within two review cycles, the item moves to cut. 

Cut applies to the item where the demand signal is structurally weak, the intervention window has closed, and holding inventory serves no one. This is the Coca-Cola logic scaled down. In 2020, Coca-Cola cut roughly half its brand portfolio, retiring products like Tab, which still had a devoted fanbase but 

, to concentrate resources on products with the greatest growth potential. The chief executive 

 that began as a pandemic supply chain triage and became a permanent strategy. 

The same logic applies to a supplier managing 40 SKUs. The item that accounts for 2% of revenue and requires 15% of the category management attention is a candidate for removal. 

 identifies two lenses for the keep-fix-cut decision:  

Cutting an item that is complex to manufacture and moving slowly is a stronger case than cutting one that is simple to produce. Both lenses belong in the analysis, and it is worth keeping the over-cutting risk in view.  

A supplier who rationalizes too aggressively can lose breadth that buyers actually require, trigger out-of-stocks on items that were seasonal rather than structurally weak, and create the impression of a shrinking line at precisely the moment the buyer is evaluating whether to give more shelf space. The antidote is documentation. Every cut decision should have a written rationale that will hold up in a buyer conversation. 

Excess Inventory Starts Earlier Than You Think 

The common framing of excess inventory as a fulfillment or logistics problem misses where it originates. Excess inventory is an assortment decision that was made too late, or in many cases, deferred rather than made at all. The IHL Group figures cited earlier attribute more than $400 billion in annual inventory distortion losses to vendor-side issues. The operational translation: slow movers accumulate in the channel because suppliers did not act on the signals they already had. 

The early-warning system described here surfaces those signals at the SKU and account level, on a weekly cadence, with thresholds defined before the review begins. It requires three metrics, a spreadsheet, and a standing block of time to look at it. For most suppliers managing 30 to 60 active SKUs across a small number of accounts, that is roughly an hour a week. 

That hour determines whether a slow mover becomes a keep-fix-cut decision in week six or a markdown dispute in week 22. 

How Visibility Across Orders and Inventory Makes This Possible 

The method described here depends on access to data that is current, complete, and connected across accounts. Suppliers who manage assortment well are typically the ones whose order, inventory, and sell-through data flows consistently rather than through manual retailer portal exports assembled once a month. 

 connects sell-through and inventory data across retail accounts so suppliers can monitor days of supply, surface early signals of decline, and act before slow movers become excess. For a deeper look at how data quality affects planning decisions downstream, see 

An Introduction to the Fashion, Apparel, & Footwear Category 

If your brand is built on direct-to-consumer channels, moving into wholesale retail often requires a reset in how operations work, especially in the fashion, apparel, and footwear categories. 

These are among the most operationally demanding categories in retail. SKU counts expand quickly across size and color, and each variation carries its own data and compliance requirements, increasing complexity. Retailers define strict rules for how products must be ticketed, packaged, and shipped, while seasonal calendars compress delivery windows into fixed deadlines. When execution can’t meet demands, chargebacks can arrive before an invoice is fully processed. 

Understanding this category starts with how those requirements fit together in practice, and what they demand from your team before the first purchase order is fulfilled. 

Why Wholesale Is Back and Why Many DTC Brands Are Not Ready 

The economics of pure direct-to-consumer growth have tightened. Customer acquisition costs rose through the early 2020s, and many brands that once prioritized DTC-only models have since added wholesale as part of their growth strategy. 

 illustrate this shift. Skims launched in 2019 as a DTC brand, partnered with Nordstrom within months, and has since built wholesale and physical retail into a business valued at $5 billion. Vuori used early wholesale relationships with partners such as Nordstrom and REI to support its working capital model and has since expanded into international markets. 

Wholesale provides access to established retail networks, physical shelf presence, and more predictable demand patterns. What it does not provide is time to adjust. Retailers expect suppliers to arrive compliant and operationally ready from the first shipment. 

The challenge is that many DTC brands are built on Shopify-era systems and fulfillment models that were never designed for EDI-driven relationships. That gap between DTC operations and retail supplier expectations is where early wholesale relationships often encounter friction. 

Item setup is much more complex operationally than other categories, primarily because a single style multiplies into many SKUs.  

A T-shirt available in five colors and six sizes becomes thirty unique SKUs. Each requires its own Universal Product Code (UPC), along with its own item record and attributes maintained in the retailer's system. 

Retailers such as Nordstrom require UPC assignment at the size and color level. They also require standardized National Retail Federation color and size codes so that terms like "Medium" or "Navy" are consistent across all suppliers, which helps with customer satisfaction when searching. 

Required item attributes typically include fabric composition, country of origin, care instructions, dimensions, tariff classifications, and standardized identifiers used across merchandising and fulfillment systems. When this data is missing or inconsistent, onboarding slows, warehouses generate exceptions, and fulfillment requires manual correction. These lead to chargebacks and revenue loss. 

Apparel vs General Merchandise: Operational Differences 

Apparel operates differently from most other retail categories, and those differences show up quickly once a brand begins fulfilling purchase orders. Compared to general merchandise, apparel introduces more variation, more data requirements, and tighter operational constraints across every step of the supply chain. The comparison below highlights where those differences matter most in day-to-day execution. 

The Compliance Structure Behind Retail Execution 

Retail compliance programs exist because retailers manage millions of units across thousands of suppliers. Standardized rules for labeling, ticketing, routing, and delivery timing make that scale possible. 

For apparel suppliers, these requirements typically include several key areas: 

Suppliers that view compliance as just another administrative task often end up feeling its impact through deductions. Those that make it part of their day-to-day operations from the start are better positioned to protect margins and avoid disruptions. 

EDI as the Backbone of Wholesale Operations 

, or EDI, is how retailers and suppliers exchange structured business documents that move a purchase order through fulfillment and payment. 

Three transactions form the foundation of most apparel wholesale relationships. 

The EDI 850 purchase order communicates demand and initiates fulfillment. The EDI 856 advance ship notice provides detailed shipment contents before arrival, often down to carton and SKU level. Accuracy here is essential because errors can trigger receiving exceptions. The EDI 810 invoice supports billing and payment reconciliation. 

When EDI processes are stable, information flows cleanly between partners and manual work is reduced. When they are not, missing or incorrect documents lead to delays, deductions, and strained trading relationships. 

As brands scale across multiple retailers, complexity increases quickly. Each partner may have different requirements and systems, which makes manual management difficult to sustain. 

 reached that wall after a period of acquisitions left it running five separate EDI systems. Getting a new retail partner up and running took up to six months. "We reached a point where it was taking up to six months to get a new partner up and running, which was resulting in lost opportunities in the marketplace," said Chris Krebs, the company's Chief Information Officer. After consolidating onto a single EDI system, onboarding dropped to six weeks, which was enough of a difference, Krebs noted, to capitalize on time-sensitive opportunities rather than lose them. 

Returns as a Structural Cost in Apparel 

According to the National Retail Federation, returns accounted for an estimated 

 of annual retail sales in 2025, totaling roughly $850 billion. Online apparel returns are even higher, often approaching 19 percent, driven by fit uncertainty and multi-size purchasing behavior. 

Some of this return volume is inherent to the category. However, a portion is driven by operational issues. Inaccurate item data, incorrect shipments, and fulfillment errors all contribute to preventable returns. 

Improving SKU accuracy and ASN reliability reduces exceptions throughout the supply chain, including returns processing. Returns are not only a customer service issue. They also affect inventory accuracy, labor, transportation costs, and overall margin. 

This article is an introduction to apparel wholesale operations. More detailed guidance on retailer requirements, compliance programs, and EDI processes is available on SupplierWiki: 

Brands that succeed in wholesale are not defined by product alone. They are defined by operational readiness, particularly in item data accuracy, EDI execution, and compliance discipline built before the first purchase order arrives. 

Comment l'intégration EDI pour SAP fonctionne avec une approche full service

 pour SAP permet une communication rapide, efficace et précise avec les partenaires commerciaux, et contribue à rationaliser les processus à travers les différents systèmes d'une organisation. Mais comme nous l'avons évoqué dans notre article précédent, n'importe quelle 

 ne suffit pas si vous souhaitez véritablement tirer le maximum des avantages que l'automatisation des systèmes a à offrir.

Considérations particulières pour les connexions EDI SAP

Pour commencer, il est important de noter que SAP ne fonctionne pas directement avec l'EDI. SAP possède ses propres messages appelés IDOCS, qui sont similaires aux messages EDI, mais qui ont leurs propres formats. De ce fait, pour intégrer l'EDI dans SAP, une conversion des informations doit avoir lieu, que la conversion se fasse de SAP IDOC vers EDI, ou d'EDI vers SAP IDOC. Par exemple, lorsque vous recevez un bon de commande dans SAP, il est traduit du format EDI en un IDOC qui est ensuite intégré dans le processus de commande. Lors de l'émission d'une facture depuis SAP, un IDOC est généré et converti au format EDI pour son envoi.

C'est cette question de traduction de SAP vers EDI, et d'EDI vers SAP, qui pose souvent problème à de nombreux fournisseurs EDI. Le Transactional Remote Function Call (tRFC), l'interface standard SAP pour la communication entre les systèmes SAP, agit presque comme un pare-feu et détermine quelles informations entrent et sortent de SAP, et comment elles y parviennent. Cela inclut les données envoyées à et depuis vos partenaires commerciaux.

De nombreuses configurations EDI ne fonctionnent pas correctement avec le tRFC, vous laissant gérer vous-même la transmission et la traduction des informations. Selon les systèmes et les partenaires commerciaux que vous souhaitez connecter avec l'EDI et SAP, les informations peuvent nécessiter d'être traduites et transmises vers plusieurs destinations. Sans les bonnes configurations, vous pourriez vous retrouver avec plus de travail que prévu. Vous pourriez même avoir besoin d'embaucher du personnel supplémentaire, alors que l'automatisation EDI est censée vous aider à réduire les processus manuels et les besoins en personnel.

Mise en œuvre de l'intégration EDI pour SAP

Comme vous pouvez l'imaginer, l'intégration de SAP avec l'EDI nécessite une préparation abondante et une expertise approfondie avant de se lancer. La manière dont vous intégrez chaque système et partenaire commercial dans votre solution EDI exige une préparation minutieuse pour chaque étape de la mise en œuvre, de la pré-planification au déploiement final.

La façon dont vous prévoyez d'utiliser l'EDI pourrait influencer la solution dont vous avez besoin. Utilisez-vous l'EDI pour tous vos partenaires commerciaux ou seulement quelques-uns ? Quels processus manuels automatisez-vous ? Quels documents devront être mappés et intégrés ? Quels systèmes et partenaires commerciaux doivent être connectés pour atteindre ces objectifs ? Comment allez-vous aligner tous les processus pour des opérations fluides ?

Plus important encore, à quoi vous attendez-vous que le succès ressemble une fois votre solution EDI en production ?

Ces questions et d'autres devraient être soigneusement étudiées et répondues avant de prendre une décision sur une solution EDI. Vous voulez vous assurer que le fournisseur que vous choisissez sera en mesure de concrétiser votre vision et de répondre à tous les besoins qui pourraient survenir.

SPS Commerce offre une solution EDI complète de bout en bout pour SAP, incluant la capacité de prendre en charge les transmissions tRFC et les formats SAP IDOC, le tout au sein d'une intégration transparente. Nous apportons la technologie éprouvée et les experts SAP pour gérer le processus depuis la mise en œuvre jusqu'aux opérations quotidiennes continues.

SPS Fulfillment automatise les communications entrantes et sortantes pour vous maintenir connecté avec vos fournisseurs, vendeurs et entreprises de 

. Cela inclut les communications concernant les bons de commande, les factures, les mises à jour d'inventaire, les expéditions et plus encore.

Ce qui rend l'intégration EDI SPS pour SAP si réussie, c'est en partie la manière dont elle traite la question du tRFC. Pour échanger tous les documents listés ci-dessus, les données  doivent pouvoir entrer et sortir de vos systèmes de manière sécurisée. Nous avons trois façons de vous aider à y parvenir, selon vos préférences et exigences :

L'intégration EDI SAP via SPS peut également vous aider à diffuser les informations reçues par tRFC et les agents sur site à travers les départements essentiels, rationalisant et améliorant vos flux de travail actuels pour des transactions plus rapides, plus précises et plus sécurisées. Les solutions EDI de service complet de SPS sont flexibles, évolutives et personnalisables pour s'adapter à vos systèmes, vos besoins de support, vos objectifs d'automatisation des systèmes et des communications au sein de votre organisation.

D'autres solutions ne peuvent faire que le minimum dans leur capacité à transférer les informations et à traduire les IDOCS vers et depuis l'EDI. Dans la plupart des cas, on s'attend à ce que vous trouviez vous-même comment acheminer les informations de SAP vers votre EDI (et vice versa). SPS peut le faire pour vous afin d'incorporer et d'automatiser tous les documents, règles et processus essentiels à votre entreprise.

 est compatible avec les multiples environnements de SAP. Là où d'autres solutions EDI échouent, SPS vous permet d'envoyer facilement les informations dont vous avez besoin là où vous en avez besoin, que vous travailliez dans des environnements de Test, de Production ou de Développement.

La solution EDI SPS Fulfillment offre un niveau de visibilité, d'automatisation et d'orchestration des processus pour vos opérations qui est incomparable à toute autre solution EDI sur le marché. Vous pourrez obtenir une vue de ce qui se passe dans le système et de la façon dont les transactions progressent.

Articles

SupplierWiki curates detailed articles to help suppliers win at retail.

Prepping for Walmart Audits

Overview

Articles