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

Recall Readiness for Health and Beauty Brands

____________________________________________________________________________________ 

The majority of plans for product recalls present the wrong question, trying to predict whether a contamination event, a mislabeling error, or a supplier failure will happen in the first place. But the question that actually determines what happens next is narrower and far more urgent: If a recall does happen, can the brand act fast and precisely? 

The moment a recall starts, response time becomes the only variable that matters. The clock starts the instant a safety signal appears, and every hour without an answer is an hour exposure keeps compounding. Everything else waits behind one question: Exactly which lots are affected, and where did they go?  

Recall readiness is not a single document in a compliance folder. Instead, a brand’s data and operations capability determines whether they can trace a lot in hours instead of weeks. 

The Regulatory Floor in Health, Beauty, and Wellness 

For most of the history of the U.S. cosmetics industry, the FDA had almost no lever to pull. The rules, which dated back to 1938, gave the agency authority to act only after a product had already caused harm. There was no federal registration requirement, no mandatory listing of what was in a product, and no way for the FDA to order a company to pull something off shelves. Recalls happened, but they happened because a brand chose to cooperate, not because the FDA could compel it. 

 (MoCRA) was passed, with its core provisions taking effect in December 2023. Due to MoCRA, the FDA can order a mandatory recall of a cosmetic product when it determines the product presents a reasonable probability of causing serious adverse health consequences or death. These are mandatory orders, usually with a public announcement attached. 

 (defined as the manufacturer, packer, or distributor whose name and address appear on a cosmetic product's label) now has to report a serious adverse event to the FDA within 15 business days of learning about it. The FDA requires the responsible parties to keep the underlying records for six years (three years for small-business distributors who don't manufacture or process the product themselves).  

Drugs and supplements have lived with a version of this for years. Cosmetics haven't, which is why this is a bigger shift for health and beauty brands than it might look on paper. And for brands with a portfolio that spans categories, the compliance clock across the whole business now moves at the pace of its most strictly regulated category. 

A 15-business day deadline looks generous on paper but can be difficult for a brand to meet. A brand has to identify the affected lot, trace every location that lot shipped to, and get pull-back moving, all before the reporting deadline. 

For example, consider two brands facing a recall after receiving back lab results. The first brand carries its lot number through every system downstream of the plant, and the other stops tracking it the moment the product leaves manufacturing. 

The first brand can query its systems and get a lot number, a list of every retailer and distribution center that received it, and shipment dates, within the hour. By the end of day one, pull-back requests are sent to every affected location. By day three, the brand can tell the FDA and its retailers exactly how much product has been recovered and how much is still in transit. 

The second brand starts the same morning with the same lab result and spends that first day just figuring out which system has the shipping records. Lot numbers were captured at the plant but never carried through to the warehouse management system (WMS). Distribution data lives in one format for direct accounts and another for distributor-fulfilled orders. By day three, this brand is still building the list the first brand had within the hour. 

The gap between the two is in whether the operational and data groundwork existed before the clock started running. 

Recall readiness consists of three pillars, all of which are essential. Losing any one of them collapses the value of the other two. 

Nearly every manufacturer assigns lot numbers, because it's required for basic quality control. The harder requirement, and the one that actually determines recall speed, is carrying that lot number through every downstream transaction: the shipment out of the plant, the receipt at a distribution center, the sale into a retailer's system. A lot number that is only used at the manufacturing line is a quality record but doesn’t function as a traceability system.  

Knowing where a lot went means knowing it with confidence. A brand needs to know exactly which retailers, which distribution centers, and in some cases which individual stores received a given lot, down to the unit. An approximation built from total shipment volume gets the scale of a recall roughly right but gets the specifics wrong, and specifics are what a recall requires. 

Knowing where product is doesn't help to transport it back from the retailer. A brand also needs the operational rails already built: carrier relationships that can be activated same-day, retailer processes for accepting returned product, and a way to check that product has actually stopped moving.  

What Happens if a Brand Isn’t Ready for a Recall 

Recall readiness is a chain, and missing any of the three pillars above can cascade into a series of failures.  

Every extra day spent figuring out which lots shipped where is a day the product stays on shelves and in homes. A longer window means more consumer exposure, which means more adverse events, more customer complaints, and in some cases more people affected by the same issue a faster brand would have already contained.  

A wider exposure window also draws more scrutiny from the retailers carrying the product, since they're the ones fielding customer questions the brand hasn't answered yet. 

That retailer scrutiny is the part brands often underestimate. A retailer watching a supplier struggle to figure out which lots are affected is updating its read on that supplier's reliability across the whole relationship. A slow recall response becomes evidence in a much broader conversation about whether this supplier can be trusted to handle other problems when they come up. 

Recall readiness is a data condition, not a single planning document. It's the accumulated result of choices made long before any crisis. Readiness is built the same way traceability is: one accurate transaction at a time, over months of ordinary operations. 

Signs a Brand Isn’t Ready for a Recall 

The easiest way to test a brand’s recall capabilities is to check for the concrete signs of readiness, such as: 

A brand that's actually ready for a recall can prove it, in specific and checkable ways: 

Build Recall Readiness Into Every Shipment  

The three pillars in this piece all depend on one thing: whether a lot number and its shipment data travel all the way to the retailer. That's the exact data flow SPS Fulfillment automates. Every ASN, PO, and invoice moves through one connected system, so lot and shipment details stay attached to the transaction instead of getting lost between the plant, the warehouse, and the receiving dock. 

If a recall ever starts, that's the difference between tracing a lot in an hour and rebuilding the trail from scratch. See how 

 keeps order, shipment, and lot data connected across every retailer you work with. 

GS1 Standards for New Suppliers: GTINs, UPCs, and Case Codes

__________________________________________________________________________________________

Many first-time suppliers view barcoding as a simple checkout formality, but this assumption often leads to technical hurdles for brands transitioning into retail. Item identification is one of the most critical technical decisions a brand will make because it serves as the foundation for every downstream transaction, from 

Getting this right before your first PO is a matter of practical prevention. Retailers have become increasingly strict about validating ownership and accuracy of these identifiers, and errors often surface as rejected item setups or expensive compliance chargebacks. To navigate this landscape, you must understand that 

 are not interchangeable names for the same barcode. These terms are distinct identifiers doing different jobs at various levels of the supply chain. 

, is the umbrella term for the entire family of 

 data structures. Think of a GTIN as a unique digital fingerprint for your product that allows it to be identified anywhere in the world. It is used for items sold, ordered, or invoiced at any stage, from the manufacturing floor to the store shelf. 

While people often use the word GTIN to refer to a specific barcode, it actually refers to the number itself. The most common formats you will encounter are: 

Every variation of a product — every size, color, style, or packaging configuration — requires its own unique GTIN. For instance, if you sell a shirt in three sizes and three colors, you have nine distinct identification requirements. 

What Are Universal Product Codes (UPC)? 

The Universal Product Code is the 12-digit identifier that most consumers recognize. In the 

 system, this is technically a GTIN-12. It is assigned to individual selling units, which are the smallest units of a product a consumer can buy, such as a single bottle of shampoo or a box of cereal. 

When a retailer’s point-of-sale (POS) system scans this code, it pulls the item data, description, and price from the retailer’s database. For a new supplier, the UPC is often the first step in product setup. 

While the UPC handles the consumer interaction, the case code (or GTIN-14) handles the logistical journey. A case code is assigned to the vendor pack configuration, which is the box or carton you use to ship multiple individual units to a retailer’s distribution center (DC). 

Many new suppliers mistakenly apply the consumer UPC to the outside of a shipping carton. But this is both incorrect and a recipe for possible compliance fines. If a warehouse associate scans a box of 12 items and the scanner reads it as a single consumer unit, your inventory records will immediately degrade.  

 at the case level, often applied via an ITF-14 or 

 barcode format on the carton itself. This allows the retailer to know exactly what is inside a carton without ever opening it, facilitating efficient receiving and cross-docking. 

The only way to ensure your product identifiers are accepted by major retailers and marketplaces is to license them directly from GS1 US. Retailers increasingly check new supplier identifiers against the 

 to confirm that the brand owner listed in the registry matches the company applying for onboarding. 

When you go to GS1 US, you generally have two paths: 

It is important to avoid cheap and/or resold UPCs. Some third-party websites sell "discounted" barcodes that were originally licensed to other companies. Because major retailers like Amazon and Walmart now validate prefix ownership, using a resold code can lead to your item setup being rejected or your products being delisted entirely. 

Retailer-Specific Standards and Hierarchy 

Identification requirements evolve as retailers invest more in automation. Walmart, for example, recently shifted its policy to require GTINs at every single level of the packaging hierarchy: the each, the warehouse pack, the 

This hierarchy is essential for accurate ordering and tracking. A typical setup might look like this: 

If you change your case pack quantity or the net content of your product, you cannot simply update your records. GS1 standards require you to issue a new GTIN. Reusing a GTIN from a retired product is also generally prohibited. Once a GTIN is assigned to a product, it is permanent.  
Reassignment can lead to 

 in retailer systems where an old product description might overwrite a new one. 

Why Identification Accuracy Matters Downstream 

The consequences of a missing or incorrect case code extend far beyond a rejected setup form. In an omnichannel environment, item data supports a massive web of automated systems, including warehouse robots, replenishment algorithms, and digital shelf displays. 

When item data is wrong, it creates cascading failures. For example, Amazon maintains a GTIN-14 gold list. If your case-level barcode scans correctly but the number is not registered on Amazon’s list, their receiving process will fail, triggering a compliance chargeback. Similarly, if your case dimensions or weights are submitted incorrectly during setup, the retailer’s warehouse management system (WMS) will assign products to the wrong bin locations, leading to bottlenecks and manual workarounds. 

Furthermore, your GTIN is the primary key for 

. When you send an EDI 856/ASN, the GTIN-14 on the physical carton must match the data in the electronic message. If there is a mismatch, the retailer’s automated receiving system will flag an exception, often resulting in a fine and a strained trading partner relationship. 

Correctly identifying your products is a business process that uses technology, not an IT task to be checked off and forgotten. It requires executive sponsorship to set standards and operational ownership to maintain them as your catalog grows. 

By treating GTINs, UPCs, and case codes as strategic assets rather than administrative burdens, you position your brand for a smoother onboarding experience and more efficient operations. Your identification strategy is the foundation that your entire retail fulfillment story sits upon. Once your identifiers are accurate and registered, you can move forward with confidence into the worlds of EDI, 

 automation, and scalable retail growth. 

Success in the retail supply chain starts with understanding the rules of the game. At 

, we provide the community knowledge, expert insights, and practical resources you need to turn complex mandates into competitive advantages. Whether you are navigating your first item setup or optimizing an existing network, our library of webinars, cheat sheets, and articles is designed to help you learn faster and think bigger. 

Fashion Supply Chain Traceability, and Why Documentation Matters More Than Ever 

For years, traceability was largely associated with sustainability initiatives and corporate responsibility reports. Today, it affects far more than a company's environmental commitments. Regulators, retailers, and consumers increasingly expect apparel, footwear, and accessories suppliers to document where products and materials come from, how they move through the supply chain, and whether public claims can be supported with evidence. 

That shift has made traceability an operational requirement. It influences whether shipments clear customs, whether sustainability claims withstand regulatory review, and whether suppliers can meet new disclosure requirements in global markets. 

Although these requirements come from different regulators and apply in different situations, they all depend on the same foundation: accurate, consistent supply chain documentation. Companies that understand where materials originate and can connect that information to product data are better prepared to respond to changing regulations, retailer requirements, and customer expectations. 

Different Regulations, One Common Requirement 

Several regulatory developments are reshaping expectations for apparel and footwear suppliers. Each has a different purpose, but all require suppliers to maintain reliable information about product origin, materials, and sourcing. 

Whether the issue is customs enforcement, sustainability marketing, or regulatory reporting, documentation has become just as important as the product itself. Companies that maintain accurate supply chain data are in a stronger position to respond to audits, retailer requests, and evolving compliance requirements. 

UFLPA: Documentation Matters at the Border 

 changed how imports are evaluated at the U.S. border. Rather than requiring regulators to prove goods were produced with forced labor, the law establishes a rebuttable presumption that products made wholly or in part in China's Xinjiang Uyghur Autonomous Region, or by companies listed on the UFLPA Entity List, are prohibited from entering the United States. 

For apparel suppliers, this matters because cotton remains one of U.S. Customs and Border Protection's highest-priority enforcement areas. Importers must be prepared to demonstrate where raw materials originated and how they moved through the supply chain before finished goods reached the United States. 

 During the first half of 2025, U.S. Customs and Border Protection detained more than 6,600 shipments under the UFLPA (more than during all of 2024). Since enforcement began in June 2022, the agency has examined more than 16,700 shipments, denied entry to more than 10,000, and expanded the UFLPA Entity List to include 

Congress enacted the law in response to documented concerns about forced labor involving Uyghurs and other ethnic and religious minorities in China's Xinjiang region. For suppliers, however, the practical takeaway is operational. Importers need documentation that demonstrates where materials originated and how products moved through each stage of production. 

For products that contain cotton, this often means tracing materials beyond the cut-and-sew factory to spinning mills, fabric manufacturers, and raw fiber sources. Without that documentation, shipments may be delayed, detained, or denied entry. 

If Customs detains a shipment, suppliers should involve experienced international trade counsel immediately. A detention notice is a legal matter, not simply a documentation request, and the appropriate response depends on the specific facts of the case. 

Green Claims: Support Every Claim With Evidence 

Consumers increasingly expect brands to explain how products are made, where materials come from, and what environmental impact they have. Regulators expect the same level of transparency. The difference is that regulators also expect companies to prove every claim they make. 

For apparel suppliers, that includes statements about recycled content, sustainable sourcing, product origin, and environmental benefits. If documentation cannot support a claim, regulators may consider it deceptive, even if the company intended to provide accurate information. 

 sustainability scorecards. In 2022, investigations found errors in the 

 displayed for many products. Regulators concluded that the supporting data did not adequately substantiate the environmental claims being presented. The result included regulatory action, litigation, and the removal of several consumer-facing sustainability claims. 

It’s important for suppliers to take note that good intentions aren’t enough; companies need documentation that supports every environmental or sourcing claim they publish. 

Before making a sustainability claim, suppliers should be able to answer questions such as: 

Reliable documentation protects both consumers and businesses. It also reduces the risk of marketing teams publishing claims that sourcing or compliance teams cannot verify. 

EU Regulations are Expanding Product Transparency 

European regulations are moving beyond traditional product safety requirements and placing greater emphasis on product-level information throughout the product lifecycle. 

Several initiatives will affect apparel and footwear suppliers over the next several years. 

 introduces new sustainability requirements for many product categories, including restrictions on destroying unsold textile goods for certain companies. 

 require European Union member states to establish Extended Producer Responsibility (EPR) programs for textiles. These programs shift more responsibility for collecting and managing textile waste to producers and importers. 

The European Commission is also developing a 

 for textiles. Expected to roll out through future delegated acts, the DPP will provide standardized product information, including material composition, origin, and other data that supports circularity initiatives. 

Although implementation timelines continue to evolve, the direction is clear. Companies selling into European markets will need more detailed product information and stronger documentation practices than they have in the past. 

Suppliers that organize product data today will be better positioned as these requirements expand. 

Retailers Increasingly Expect Traceability From Suppliers 

Many suppliers encounter traceability requirements long before they interact with a regulator. 

Major retailers routinely ask suppliers to complete sourcing questionnaires, certify compliance with supplier codes of conduct, provide country-of-origin information, and document material composition. Depending on the retailer and product category, suppliers may also need to provide restricted substance declarations, sustainability certifications, or factory information during onboarding. 

 can help demonstrate compliance with specific standards. However, certifications are only one part of the process. Retailers often request supporting documentation that connects certifications to specific products, suppliers, and production records. 

As retailer expectations continue to evolve, maintaining accurate product information becomes an operational advantage rather than an administrative task. 

How Suppliers Can Strengthen Supply Chain Traceability 

Building a traceability program does not require an entirely new compliance department. Most organizations can strengthen traceability by improving how they collect, manage, and maintain supply chain information. 

Many compliance requirements extend beyond the finished goods manufacturer. For products made with cotton or other high-risk materials, suppliers should understand where raw materials originate and how they move through the supply chain. 

Maintain Accurate Chain-of-Custody Records 

Documentation should remain current and readily accessible. Purchase records, supplier declarations, production information, and transportation records all contribute to a complete chain of custody. Maintaining organized records also helps suppliers respond more efficiently to retailer requests or customs reviews. 

Country of origin, fiber composition, material attributes, and supplier information should remain consistent across product catalogs, customs documentation, labels, and retailer systems. Inconsistent data creates unnecessary risk during audits and product reviews. 

Review Public Claims Before Publication 

Marketing, sourcing, product development, and compliance teams should work together before environmental or origin claims are published. Every public statement should have supporting documentation that is current and readily available, as many clothing brands have been accused of “greenwashing” while not actually following up with their statements in practice.  

Regulations continue to evolve across global markets. Companies that establish strong documentation practices today can adapt more quickly as new reporting and disclosure requirements emerge. 

Documentation is Becoming a Competitive Advantage 

Traceability is no longer limited to sustainability reporting. It has become an important part of customs compliance, retailer onboarding, product transparency, and risk management. 

Although regulations differ across countries and agencies, they all depend on the same foundation: accurate, consistent supply chain data. Companies that understand where materials originate and maintain reliable documentation are better prepared to respond to customs reviews, retailer requirements, and changing regulatory expectations. 

As documentation requirements continue to expand, companies that invest in stronger product data management today will be better positioned to support compliance efforts tomorrow.  

Learn More From Primary Regulatory Sources 

This article provides a general overview of traceability requirements affecting apparel and footwear suppliers. It is intended for educational purposes only and should not be considered legal or regulatory advice. 

If your company receives a customs detention notice, faces regulatory scrutiny over marketing claims, or must comply with specific disclosure requirements, consult qualified legal or compliance professionals who can provide advice based on your circumstances. Keep up to date with compliance updates on 

Supply Chain Management Software: How to Compare Your Options 

Most suppliers shopping for supply chain management software start the same way: they find a comparison list, scan the vendor logos, and start booking demos. The problem is that comparison lists assume you already know which category of software solves your problem. Most of the time, you don’t, and that’s the most reliable path to an expensive mismatch. 

The two most expensive supply chain software failures in modern retail history weren’t caused by bad software. For example, Hershey and Lidl both deployed reputable systems from major vendors. What failed was the match between the tool and the situation: wrong scope in one case, wrong fit in the other. The mechanics of both failures are worth understanding before you evaluate anything, because they happen at every company size, not just at the enterprise level. 

This guide walks through the supply chain solutions landscape by category, explains what each category actually does and who it’s built for, and gives you a diagnostic for identifying which gap in your own order-to-fulfillment workflow you’re trying to close. Vendor comparisons come after that. Category selection comes first. 

Why Supply Chain Software Purchases Go Wrong 

Two failure modes account for most of the expensive mistakes in this space. 

The first is wrong scope: buying a suite of software when one workflow is broken. This is what happened to Hershey. In 1999, the company implemented enterprise resource planning (ERP), customer relationship management (CRM), and supply chain planning software from three vendors at the same time. Testing was compressed to hit a target go-live date. The date happened to be just before Halloween, the single most critical fulfillment period of the year for a candy company. Order processing and fulfillment broke. Roughly $100 million in finished product sat in warehouses while retailer orders went unfilled. Quarterly profits fell 19 percent. 

Hershey’s order processing broke not because the software was bad, but because the scope was too large, the testing was too compressed, and the go-live date was timed for the worst possible moment. The same risk applies to a mid-market supplier implementing an ERP, a new electronic data interchange (EDI) platform, and a warehouse management system (WMS) simultaneously while onboarding a major retail account. The company size changes. The failure mechanics don’t. 

The second failure mode is wrong fit: buying a tool whose design assumptions conflict with how your business actually runs. This is what brought down Lidl’s seven-year SAP implementation. SAP for Retail values inventory at retail prices. Lidl’s entire operating model runs on purchase prices. Rather than adapt its model, Lidl customized the software progressively until the system became unstable, then abandoned the project in 2018 after spending an estimated 500 million euros. 

The lesson isn’t specific to ERP. A demand planning tool built around stable, predictable demand will fight a supplier whose business is seasonal and promotional. An EDI point solution that requires building every trading partner connection from scratch will fight a supplier whose account list changes frequently. When the tool’s assumptions and your operating reality diverge, someone pays, and it’s usually you. 

Diagnosing which gap you’re trying to close, before you open a single vendor comparison tab, is how you avoid both failure modes. 

Supply Chain Software Categories: What Each One Actually Does 

Supply chain solutions are not a single category. They are a set of specialized tools, each built to solve a specific layer of the order-to-fulfillment workflow. Here’s what each category does, who it’s built for, and the symptom that points to the need for implementation. 

ERP is the system of record for finance, inventory, production, and human resources (HR). It manages master data across the business (items, vendors, customers, costs) and connects financial transactions to operations in a single platform. 

Built for: organizations that need a single source of truth across functions. The typical trigger is spreadsheets across multiple departments that have multiplied past the point where anyone agrees on the same number. 

What it doesn’t do: An ERP receives and stores orders, but it doesn’t manage the document exchange layer with trading partners. It won’t set up EDI connections, enforce retailer-specific compliance requirements, or translate purchase orders (POs) from retailer formats into your system. That work lives in a separate category. 

Telltale symptom: “Our data lives in four different spreadsheets and no two of them match.” 

EDI Software and Order Management Networks 

Electronic data interchange (EDI) software manages the exchange of business documents between a supplier and its retail trading partners: POs, advance ship notices (ASNs), invoices, and inventory feeds. The key distinction within this category is whether the provider is network-based, bringing pre-built connections and stored retailer requirements, or a point solution, which requires building and maintaining each connection from scratch. 

Built for: suppliers managing orders across multiple retail accounts, particularly where retailer-specific document requirements, compliance rules, and chargebacks are consuming hours that should be going elsewhere. 

What it doesn’t do: EDI software doesn’t replace your ERP or warehouse systems. It manages the document exchange layer between those systems and your retail accounts. 

Telltale symptom: “We re-key orders from retailer portals and emails, and chargebacks from document errors show up on every invoice reconciliation.” 

A warehouse management system controls physical warehouse operations: 

Built for: suppliers with real warehouse complexity, including multiple stock-keeping units (SKUs), multiple storage locations, or fulfillment volume that requires real-time inventory accuracy to execute reliably. 

What it doesn’t do: a WMS doesn’t manage trading partner relationships or generate compliant EDI documents. It produces the fulfillment data that downstream EDI systems use to generate ASNs and other transaction documents. 

Telltale symptom: “Our inventory counts are never right, and we don’t know why until someone goes and physically looks.” 

Transportation Management Systems (TMS) 

A transportation management system handles the freight side of the operation: 

If your focus is on what happens after the product leaves the warehouse, this is the category. 

Built for: suppliers with enough outbound freight volume that carrier selection, rate negotiation, and shipping visibility are real cost levers, not afterthoughts. 

What it doesn’t do: A TMS doesn’t manage warehouse operations or produce EDI documents. It manages what happens after the shipment leaves the dock. 

Telltale symptom: “We don’t know what shipping is actually costing us until the invoice lands, and we have no real ability to push back on carrier rates.” 

Demand Planning and Inventory Optimization Tools 

Demand planning tools forecast future demand using historical data, seasonality, and market signals, then drive replenishment and safety stock decisions. The practical test for whether you need one is: If removing one person from your team would break your forecasting process, you have a planning problem, not just a staffing one. 

Built for: suppliers where stockouts and overstock are recurring, where forecasting lives in a spreadsheet, or where retailer sell-through data exists but isn’t being used to inform purchasing decisions. 

What it doesn’t do: Planning tools don’t execute fulfillment or manage document exchange. They feed decisions into ERP and WMS systems as an input layer, not an execution layer. 

Telltale symptom: “Our forecasts live in one person’s spreadsheet. When that person is on vacation, we’re guessing.” 

Visibility platforms aggregate data from across the supply chain (orders, shipments, inventory, supplier performance) into a monitoring layer that surfaces exceptions and performance trends. 

Built for: organizations that have multiple systems producing data but no unified view of order or shipment status. 

What it doesn’t do: A visibility platform surfaces gaps but doesn’t fix them. A platform that shows you chargebacks are rising doesn’t prevent them. Fixing chargebacks requires addressing the document layer. If operational gaps are present, a visibility platform will show you where they are, but you’ll still need to fix the underlying workflow. 

Telltale symptom: “I can see there’s a problem, but I have to check four different systems to understand what actually happened.” 

Which Software Category Fits Your Situation 

How to Diagnose Your Gap Before You Evaluate Anything 

Before talking to a single vendor, run through this symptom map and identify which layer of your order-to-fulfillment workflow is actually breaking. 

Orders arriving by email and re-keyed manually points to the EDI and order management layer. The pain is at the trading partner interface, not inside the warehouse or the ERP. 

Chargebacks from document errors points to the same layer. Compliance gaps at the document level produce financial consequences at the invoice level, and fixing the reconciliation process doesn’t fix the document problem. 

Inventory counts that never match reality is a WMS or inventory management gap. The execution is breaking inside the warehouse, not in planning or at the trading partner level. 

Forecasts that live in a spreadsheet signal a demand planning problem. Forecasting accuracy is a data and modeling issue. Fixing EDI or buying a WMS won’t touch it. 

Freight costs that are opaque until the invoice arrives point to TMS. The gap is in the transportation layer. 

Everything is operationally fine, but leadership has no single view points to a visibility platform need, with one caveat. If any of the operational gaps above are present, a visibility platform will surface them but won’t solve them. Fix the workflow gaps first, then add the monitoring layer. 

5 Steps for Evaluating Supply Chain Solutions 

Once you’ve identified the category that matches your gap, evaluating supply chain solutions within it is straightforward. What makes it go wrong is skipping step one. 

If the Gap Points to the Trading Partner Layer 

If your diagnostic lands on the EDI and order management category (orders arriving by email and portal, retailer requirements consuming manual hours, fulfillment document errors generating chargebacks), that’s the layer SPS Commerce is built for. 

 provides so much more than just full-service EDI and order management for suppliers managing retail relationships, with pre-built connections across a network of retailers and stored requirements that reduce the setup work on new trading partner relationships. We partner with retailers, brands, and logistics providers of all sorts to connect them to the largest supply chain network. 

If your gap is knowledge rather than software (you need to understand EDI basics, retailer-specific requirements, or how the order-to-fulfillment workflow is supposed to function), 

 covers that ground without a sales conversation attached. 

The Supply Chain Management Process 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. 

What Are the 2 Tracks of a Digital Supply Chain? 

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 EDI 855 purchase order acknowledgment, 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. 

The advance ship notice, or EDI 856, 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, SupplierWiki has a plain-English breakdown of the full sequence. 

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. Orchestration is what a digital supply chain is for. 

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. 

Articles

SupplierWiki curates detailed articles to help suppliers win at retail.

Prepping for Walmart Audits

Overview

Articles