# EDI Compliance: Requirements, Checklist, Testing > What EDI compliance means, why retailers enforce it, requirements by trading partner, a 15-item pre-go-live checklist, and how to maintain compliance long-term. EDI compliance is the ability to send and receive electronic business documents in the exact format, timing, and structure each trading partner requires. Every major retailer (Walmart, Target, Costco, Amazon Vendor Central, Kroger) enforces it with chargebacks ranging from $50 to over $500 per shipment. Compliance covers transaction format, timing windows, label standards, and routing requirements. If you are selling to major retailers, EDI compliance is not optional. It is a prerequisite for receiving purchase orders, getting paid on time, and avoiding [chargebacks](/solutions/reduce-edi-chargebacks) that eat into your margins. Every retailer has its own EDI compliance requirements, and falling short on any of them means real financial consequences. Key authoritative references for EDI compliance: - The [ASC X12 standards body](https://x12.org/) defines the base transaction formats (850, 856, 810, 997) that all trading partner compliance programs are built on - [GS1 US](https://www.gs1us.org/standards) governs GTIN, UPC, and SSCC-18 barcode standards that retailers use for physical label scanning at receiving docks - [DISA](https://www.disa.org/) serves as the secretariat for X12 and publishes the implementation guidelines referenced in most vendor compliance manuals This guide covers what EDI compliance actually means in practice, why retailers enforce it so strictly, what specific requirements look like across major trading partners, a tactical 15-item checklist for pre-go-live testing, and how to maintain compliance over time. > **What is EDI compliance?** EDI compliance is the ability to send and receive electronic business documents (purchase orders, invoices, ship notices, and acknowledgments) in the exact format, structure, and timeframe that your trading partner requires. In North America, this typically means conforming to the [ANSI X12](https://www.x12.org/) standard while also meeting retailer-specific rules layered on top of that standard. ## Why Retailers Enforce EDI Compliance Retailers do not enforce EDI compliance to create busywork. They do it because their entire supply chain depends on accurate, timely electronic data flowing between systems without human intervention. When a supplier sends a properly formatted EDI 856 ship notice, the retailer's warehouse management system can automatically schedule dock doors, allocate labor, and match inbound shipments to open purchase orders. When that 856 is malformed, late, or missing, the whole process breaks down and someone has to fix it manually. Here is what strict EDI compliance gives retailers: - **Automated receiving.** Warehouses scan carton barcodes and match them against the ASN data. If your [856 ship notice](/guides/edi/856-ship-notice) does not include SSCC-18 labels at the carton level, the receiving team has to count and verify everything by hand. - **Three-way matching.** The retailer's AP system automatically matches the PO (850), the ASN (856), and the invoice (810). Discrepancies in any of these documents halt payment. - **Inventory accuracy.** Retailers use ASN data to update inventory counts before shipments even arrive. Bad data means bad inventory numbers, which means stockouts or overstock at the store level. - **Chargeback enforcement.** Compliance programs with financial penalties ensure suppliers take their EDI implementation seriously. Without consequences, data quality degrades quickly across thousands of supplier relationships. According to [GS1 US](https://www.gs1us.org/upcs-barcodes-prefixes/how-to-use-your-upc-barcodes/share-information-electronically), standardized EDI transactions reduce order processing errors by up to 30% compared to manual methods. But those benefits only materialize when your implementation meets the trading partner's spec. ## Core EDI Compliance Requirements While every trading partner has its own spec, most EDI compliance requirements fall into a few common categories. Understanding these categories helps you prepare for any retailer, not just the one you are onboarding with today. ### Transaction Set Support At minimum, you need to support the core EDI transaction loop: 1. **Receive the [EDI 850 purchase order](/guides/edi/850-purchase-order).** This is where it starts. Your system must accept inbound 850s and parse every required segment correctly. 2. **Send the EDI 997 functional acknowledgment.** The [997](/guides/edi/997-functional-acknowledgment) confirms you received the PO. Most retailers expect this within minutes, not hours. 3. **Send the EDI 855 PO acknowledgment.** The [855](/guides/edi/855-purchase-order-acknowledgment) tells the retailer you accept the order (or flag exceptions). Not all retailers require it, but Walmart and Target do. 4. **Send the EDI 856 ship notice (ASN).** This is the most compliance-sensitive transaction. It must be sent before the shipment arrives at the retailer's DC, and it must include the exact hierarchical structure and carton-level detail the retailer specifies. 5. **Send the EDI 810 invoice.** The [810 invoice](/guides/edi/810-invoice) must match the PO pricing and quantities exactly. Even a one-cent variance per unit can trigger a three-way match failure. Some retailers also require the [EDI 860 purchase order change](/guides/edi/860-purchase-order-change) and [EDI 846 inventory inquiry](/guides/edi/846-inventory-inquiry), depending on whether they use vendor-managed inventory or allow PO modifications. ### Data Accuracy EDI standards compliance goes beyond format. The data inside your transactions must be correct: - **Item identifiers.** UPCs, GTINs, and retailer-specific codes (like Target's DPCI) must match what the retailer has in their item master. A single digit off means a rejected line item. - **Pricing.** Your 810 invoice pricing must align with the negotiated cost in the retailer's system. Discrepancies halt payment and sometimes trigger chargebacks. - **Ship-to locations.** Every retailer distribution center and store has a specific location code. Using the wrong code, or substituting a description for a code, causes routing failures. - **Dates and times.** Ship dates, delivery dates, and PO dates must use the format your trading partner expects. The X12 standard supports multiple date formats, so check the spec. ### Timeliness Sending the right data late is almost as bad as sending the wrong data on time. Common timing requirements include: - **997 acknowledgments:** 15 to 30 minutes after receiving an 850 - **855 PO acknowledgments:** Within 24 hours of receiving the PO - **856 ASN:** Before the shipment arrives at the DC (typically sent at time of shipment) - **810 invoice:** Within 24 to 48 hours of shipment, depending on the retailer Miss these windows and you will start accumulating compliance demerits or outright chargebacks. ## Retailer-Specific EDI Compliance Requirements The [ANSI X12 standard](https://www.x12.org/) provides the syntax and structure, but each retailer adds its own layer of requirements. ### Walmart Walmart runs one of the strictest EDI compliance programs in retail: - **OTIF (On Time In Full).** Walmart measures whether your shipments arrive within the delivery window and with the full quantity ordered. OTIF failures carry financial penalties that scale with order value. See our [Walmart EDI requirements](/edi-compliance/walmart) guide. - **ASN accuracy.** Your 856 must include SSCC-18 barcodes at the carton level. Walmart's receiving process is barcode-scan-driven, and missing labels mean manual processing and chargebacks. - **997 response time.** Walmart expects functional acknowledgments within 15 minutes. - **Retail Link monitoring.** Suppliers must actively monitor their compliance scorecard on Retail Link and resolve flagged issues proactively. ### Target - **DPCI codes.** Target uses its own internal product identifier (Department, Class, Item) in addition to UPCs. Your EDI transactions must cross-reference both. See our [Target EDI requirements](/edi-compliance/target) guide. - **Carton-level ASN data.** Like Walmart, Target requires SSCC-18 at the carton level. But Target also requires DPCI references within the tare-level loops of the 856. - **Partners Online.** Target's supplier portal is where compliance status, testing, and communication happen. Registration is required before EDI testing begins. - **Labeling standards.** Target has specific GS1-128 label requirements that must match the data in your ASN. A mismatch between the physical label and the electronic data is a chargeback trigger. ### Amazon (Vendor Central) - **ASIN mapping.** Amazon uses its own product identifier system. Your item master must map UPCs to ASINs. - **PO confirmation deadlines.** Amazon enforces tight windows for confirming purchase orders. Late confirmations can result in order cancellations. - **Routing requirements.** Amazon specifies carrier and routing for most inbound shipments. Non-compliance with routing instructions triggers chargebacks. ### Quick Comparison | Requirement | Walmart | Target | Amazon | |---|---|---|---| | Primary item ID | GTIN-14 / UPC-A | UPC + DPCI | ASIN | | ASN carton tracking | SSCC-18 required | SSCC-18 + DPCI required | Required for FBA | | 997 response window | 15 minutes | 30 minutes | 24 hours | | Compliance portal | Retail Link | Partners Online | Vendor Central | | Key penalty trigger | OTIF failures | ASN/label mismatches | PO confirmation delays | The key takeaway: never assume passing compliance with one retailer means you will pass with another. Review each trading partner's spec independently. ## The EDI Compliance Checklist: 15 Items Before Go-Live A failed EDI test costs you more than time. It delays your first shipment, pushes back revenue, and in some cases gets your vendor account flagged before you have filled a single order. Here are the 15 items to verify before submitting your first test transaction. ### Trading Partner Setup (Items 1-4) **1. Obtain and read the full trading partner spec.** Every retailer publishes an EDI implementation guide (sometimes called a vendor compliance manual). This document defines which transactions are required, which segments are mandatory, and what code values to use. Do not skip sections. Do not assume it matches another retailer's spec. **2. Confirm your ISA/GS identifiers with the trading partner.** Your Interchange Sender ID (ISA06) and Application Sender Code (GS02) must match exactly what the retailer has on file. A single character mismatch means every transaction you send will be rejected at the envelope level, before content is even evaluated. **3. Establish your communication channel.** Whether you are using AS2, SFTP, or a VAN, confirm the connection is active and that test files transmit successfully in both directions. Run a basic connectivity test -- not just a ping, but an actual file exchange. If you need a refresher on how EDI connections work, our [essential guide to EDI](/blog/essential-guide-to-edi) covers the fundamentals. **4. Register for the retailer's supplier portal.** Most major retailers (Walmart Retail Link, Target Partners Online, Amazon Vendor Central) require portal registration before EDI testing begins. Your EDI transactions and the portal work together, so set up access early. ### Transaction Mapping (Items 5-8) **5. Map all required transaction sets.** At minimum, most retailers require the EDI 850 (purchase order), [855 (PO acknowledgment)](/guides/edi/855-purchase-order-acknowledgment), 856 (ship notice/ASN), 810 (invoice), and 997 (functional acknowledgment). Verify which transactions your specific trading partner mandates. Some also require the 846 (inventory inquiry) or 860 (purchase order change). **6. Validate segment-level mapping against the spec.** Do not just map at the transaction level. Go segment by segment. For example, the [EDI 856 ship notice](/guides/edi/856-ship-notice) typically requires hierarchical levels for shipment, order, tare (carton), and item. Missing the tare level is one of the most common 856 failures, and it triggers chargebacks at most major retailers. **7. Confirm code values match the retailer's requirements.** Qualifier codes, unit-of-measure codes, and packaging codes must use the exact values the retailer expects. A common mistake: using "EA" (each) when the retailer's spec calls for "CA" (case) at the pack level. These mismatches pass syntax validation but fail business validation. **8. Set up your 997 functional acknowledgment response.** The [997](/guides/edi/997-functional-acknowledgment) confirms that you received and syntactically accepted (or rejected) an inbound transaction. Most retailers require you to send a 997 within minutes of receiving an 850. If your system does not generate these automatically, fix that before testing. ### Data Validation (Items 9-11) **9. Validate item identifiers (UPC, GTIN, SKU).** Every line item must carry the correct product identifier in the format the retailer expects. Walmart uses GTIN-14 for case-level and UPC-A at the item level. Target requires DPCI codes cross-referenced to UPCs. Run your product catalog against the retailer's item setup file and fix mismatches before you send a single test transaction. **10. Verify pricing and quantity fields.** Your 810 invoice pricing must match what is in the retailer's purchase order system. Price discrepancies, even a fraction of a cent on unit cost, will cause three-way match failures and delay payment. Check extended amounts (unit price times quantity) for rounding consistency. **11. Confirm address and location codes.** Ship-to location codes (N1 segments with qualifier "ST") must match the retailer's distribution center or store location master. Using a description instead of the retailer's internal location code is a common failure point, especially for suppliers shipping to multiple DCs. ### Testing (Items 12-13) **12. Run a complete transaction cycle in the test environment.** Do not test transactions in isolation. Run the full cycle: receive an 850, send an 855 acknowledgment, send an 856 when you "ship," send an 810 invoice, and confirm 997s flow in both directions. This end-to-end test catches timing issues and cross-reference errors that individual transaction tests miss. **13. Validate your test files with a parser before submission.** Before sending test documents to the retailer, run them through an EDI parser to catch syntax errors, missing required segments, and envelope problems. Our [free EDI Inspector](/edi-inspector) lets you paste or upload raw EDI and see the parsed structure instantly. Fix obvious errors locally instead of burning test cycles with the retailer. ### Go-Live Readiness (Items 14-15) **14. Document your error handling and retry process.** What happens when a transaction fails? You need a defined process: who gets notified, how quickly they respond, and what the retry procedure looks like. Retailers expect acknowledgment issues to be resolved within hours, not days. **15. Confirm your team knows the retailer's compliance calendar.** Many retailers have blackout periods (typically around holidays and fiscal year-end) when they do not accept new supplier onboarding or run compliance tests. Know when your testing window is, and do not cut it close. Build in at least two weeks of buffer. ## Common Compliance Failures The same five issues account for most failed EDI compliance tests: 1. **Missing or incorrect ASN hierarchical levels.** The 856 is the most complex transaction, and most failures happen here. Specifically, missing the tare (pack/carton) level or not including SSCC-18 barcodes when the retailer requires carton-level tracking. When receiving discrepancies arise from ASN errors, the retailer may report them via an [EDI 861 receiving advice](/guides/edi/861-receiving-advice), which often leads directly to chargebacks. 2. **997 acknowledgments not sent (or sent late).** Some suppliers do not realize their system is not generating 997s automatically. The retailer sends an 850, waits for acknowledgment, and after the timeout window passes, flags the transaction as failed. If you are receiving [824 Application Advice](/guides/edi/824-application-advice) documents, that means the retailer found business-level errors even after your syntax passed the 997 check. 3. **Mismatched item identifiers.** Sending a UPC-A when the retailer expects a GTIN-14, or vice versa. This also happens when suppliers update their product catalog but do not sync the changes to their EDI mapping. 4. **Envelope-level errors (ISA/GS).** Wrong qualifier codes, incorrect sender/receiver IDs, or mismatched control numbers. Easy to fix but hard to diagnose if you are not inspecting the raw EDI file. 5. **Date and time format inconsistencies.** The X12 standard supports multiple date formats (YYMMDD, CCYYMMDD). If your system sends one format and the retailer's parser expects another, every transaction with a date field will fail validation. ## EDI Compliance Testing: Getting It Right ### Step 1: Validate Locally First Before you send a single test file to the retailer, validate your EDI output yourself. Parse your raw EDI files and inspect the segment structure, data elements, and envelope values. Our [free EDI Inspector](/edi-inspector) lets you paste or upload raw X12 data and see the parsed output instantly. Catching syntax errors locally saves you from burning test cycles with the retailer. ### Step 2: Run the Full Transaction Cycle Run the complete loop: 1. Receive a test 850 from the retailer 2. Send back a 997 acknowledgment 3. Send an 855 PO acknowledgment (if required) 4. Send an 856 ASN with carton-level detail 5. Send an 810 invoice that matches the PO pricing 6. Confirm 997s flow back from the retailer for your outbound documents Testing individual transactions misses cross-reference errors. Your 810 line items must reference the same PO numbers and quantities as the 850 and 856. ### Step 3: Verify with the Retailer's Testing Team Most retailers (or their designated testing partners like [SPS Commerce](https://www.spscommerce.com/resources/edi-documents/) or DiCentral) will review your test files and provide a pass/fail report. Common feedback includes: - Missing required segments (e.g., no tare level in the 856) - Wrong qualifier codes (e.g., using "92" instead of "UP" for UPC) - Envelope mismatches (ISA/GS sender IDs do not match their records) - Timing issues (997 sent too late or not at all) Fix every flagged issue and resubmit. Most retailers allow 2 to 3 test rounds. Failing beyond that may require restarting the process. ### Step 4: Confirm Production Readiness Once you pass testing, confirm: - Your communication channel (AS2, SFTP, or VAN) is pointing to the production endpoint, not the test environment - Your ISA qualifier indicates production ("P"), not test ("T") - Your team knows who monitors for failed transactions and how to escalate - You have a process for handling [PO changes (860)](/guides/edi/860-purchase-order-change) if the retailer sends them ## Maintaining EDI Compliance Long-Term Passing initial testing is the starting line, not the finish line. Maintaining EDI compliance requires ongoing attention. **Monitor your compliance scorecard**: Every major retailer provides a supplier scorecard through their portal. Check it weekly, and treat a declining score as an early-warning signal that chargebacks are coming before they hit your account. **Track transaction success rates**: If your 997 acknowledgment rate drops below 100%, something is wrong. Monitor the ratio of sent transactions to received acknowledgments daily so you catch failures before the retailer's compliance team flags them. **Watch for spec changes.** Retailers update their EDI requirements periodically, sometimes quarterly. According to [GS1 US](https://www.gs1us.org/upcs-barcodes-prefixes/how-to-use-your-upc-barcodes/share-information-electronically), EDI standards evolve to support new supply chain requirements like sustainability reporting and advanced ship notice enhancements. Subscribe to your retailer's portal notifications and review changes promptly. **Audit data quality monthly.** Product catalog updates, new warehouse locations, and pricing changes can all introduce compliance issues. Run a monthly sample of recent transactions through validation to catch drift before it triggers chargebacks. **Maintain your testing environment.** Keep your test connection active even after go-live. When the retailer issues spec changes or you add new product lines, you will need to re-test specific transactions without affecting production orders. **Automate what you can.** Manual compliance monitoring does not scale. If you are trading with three or more retailers, you need automated validation, acknowledgment generation, and exception alerting. OrderSync's [automated order processing](/order-processing-automation) handles this across all your trading partners from a single dashboard, flagging compliance issues before they become chargebacks. The platform supports [multi-format order processing](/multi-format-orders), so your compliance workflow covers EDI, PDF, CSV, and email order channels. If you are evaluating tools, our [B2B order automation software guide](/blog/automated-order-processing) compares approaches for managing EDI compliance at scale. Ready to see how it works? [Book a free intro call](/book-call) or try our [free EDI Inspector](/edi-inspector) to start validating your EDI files today. ## FAQ ### What does EDI compliance mean for suppliers? EDI compliance means your system can send and receive electronic documents in the exact format, structure, and timeframe your trading partner requires. This includes supporting the correct transaction sets (850, 856, 810, 997), populating all mandatory segments, using the right item identifiers and codes, and responding within the retailer's timing requirements. Non-compliance results in chargebacks, rejected transactions, and potentially suspended vendor status. ### What are the most common EDI compliance requirements? **The most common requirements are supporting the core transaction loop (850, 855, 856, 810, 997), sending accurate ASN data with carton-level detail and SSCC-18 barcodes, matching item identifiers to the retailer's product master, maintaining pricing consistency across POs and invoices, and responding with functional acknowledgments within the required timeframe.** For most major retailers, that window is 15 to 30 minutes for 997 acknowledgments and within 24 hours for 855 PO acknowledgments. ### How long does EDI compliance testing take? For most retailers, plan for 2 to 6 weeks. The timeline depends on how many transaction types are required, how quickly the retailer's testing team responds, and whether you pass on your first attempt. Walmart and Target typically have structured testing queues, so factor in wait times between test rounds. ### How do I test EDI compliance with a new trading partner? Start by obtaining the retailer's EDI implementation guide and mapping your transactions to their spec. Validate your EDI files locally using a parser like our [free EDI Inspector](/edi-inspector) before submitting to the retailer's test environment. Run the full transaction cycle (850 through 810) rather than testing individual documents. Most retailers allow 2 to 3 test rounds, with specific error feedback after each round. ### What happens when you fail EDI compliance? Failed compliance leads to three outcomes: chargebacks (financial penalties ranging from $500 to $5,000+ per incident), rejected transactions that stall shipments and delay payment, and in severe cases, suspended vendor status that requires re-testing from scratch. Repeated failures also damage your supplier scorecard, which affects future order allocation. ### How is EDI compliance different from EDI certification? EDI certification is the initial validation process where a trading partner confirms your system can correctly send and receive the required transaction sets. It is a one-time gate you pass to begin trading. EDI compliance is the ongoing requirement to maintain data accuracy, timeliness, and format correctness across every transaction you exchange. You get certified once, but compliance is measured continuously and carries ongoing financial consequences when you fall short. ### Can I test EDI compliance without a VAN? Yes. Many suppliers connect via AS2 (direct point-to-point) or SFTP, bypassing the need for a VAN entirely. The testing process is the same regardless of your communication method. What matters is that your transactions conform to the retailer's spec.