KeHE EDI Requirements: The Complete 2026 Guide for Natural & Organic Brands

Selling through KeHE Distributors means your brand gains access to over 30,000 retail locations across North America, including Whole Foods, Sprouts Farmers Market, Natural Grocers, and thousands of independent natural product stores. But before a single case ships, KeHE requires every supplier to meet strict Electronic Data Interchange (EDI) standards. These requirements govern how purchase orders, invoices, advance ship notices, and other critical business documents flow between your systems and KeHE's. Brands that fail to meet these standards face shipment rejections, delayed payments, and costly compliance chargebacks that can erode margins on already-thin natural product categories. This guide walks you through every KeHE EDI requirement, from initial vendor setup to ongoing compliance, so your brand can trade efficiently and avoid the penalties that trip up even experienced CPG operators.

Want to skip the complexity? Book a demo with Crstl to see how AI-powered EDI handles KeHE compliance automatically.

What Are KeHE EDI Requirements?

KeHE EDI requirements are the technical and operational standards that every supplier must follow to exchange electronic business documents with KeHE Distributors. These requirements cover document formats (ANSI X12 EDI standard), communication protocols (AS2, VAN, or SFTP), transaction types (purchase orders, invoices, advance ship notices), and data quality rules (accurate GTINs, correct pricing, proper date formatting). KeHE mandates EDI for all suppliers doing business at scale because manual processes introduce errors that cascade through their distribution network serving over 30,000 retail locations. The requirements ensure that purchase orders are acknowledged promptly, shipments are tracked with compliant ASNs, and invoices match what was actually shipped. Suppliers who meet these standards benefit from faster payment cycles, fewer chargebacks, and stronger relationships with KeHE's buying team. Brands that ignore or partially implement these requirements face a predictable cycle of rejected shipments, payment delays, and compliance penalties that compound over time.

DEFINITION

KeHE EDI (Electronic Data Interchange) is the automated, standardized system KeHE Distributors uses to exchange business documents, including purchase orders (850), purchase order acknowledgments (855), advance ship notices (856), and invoices (810), with its supplier network. All documents follow the ANSI X12 format and must be transmitted through approved communication channels.

Which EDI Documents Does KeHE Require?

KeHE requires suppliers to support a core set of EDI transaction types that cover the full order-to-cash cycle: purchase orders (850), purchase order acknowledgments (855), advance ship notices (856), and invoices (810). These four documents form the backbone of every supplier relationship with KeHE. The purchase order initiates the transaction, the acknowledgment confirms the supplier can fulfill it, the ASN provides shipment tracking and contents detail, and the invoice triggers payment. Beyond these core four, KeHE may also require functional acknowledgments (997) to confirm receipt of any EDI transmission, and some supplier tiers may need to support item maintenance documents for catalog updates. Each document type has specific field requirements, timing windows, and data quality standards that suppliers must meet. Missing or inaccurate data in any of these documents can trigger chargebacks, delay payments, or result in shipment rejections at KeHE's distribution centers. The table below breaks down each required document, its purpose, and the key compliance considerations your brand needs to know.

For a deeper dive into how advance ship notices work across retailers, see our complete guide to EDI 856 Advance Ship Notices.

How Do You Set Up EDI with KeHE?

Setting up EDI with KeHE involves a structured process that begins with vendor onboarding, moves through trading partner registration, EDI testing, and ends with go-live certification. The entire process typically takes four to eight weeks depending on your EDI provider's capabilities, your internal readiness, and how quickly you can pass KeHE's testing requirements. KeHE's onboarding team assigns each new supplier a dedicated contact who walks through the technical requirements, but the actual EDI configuration, testing, and troubleshooting falls on the supplier and their EDI provider. Brands using legacy EDI platforms often report the process stretching to three months or longer due to rigid mapping tools, slow support cycles, and manual testing workflows. Modern platforms like Crstl compress this timeline dramatically because KeHE is already in the trading partner network, meaning pre-built maps and automated testing can cut weeks off the process. The steps below outline the standard KeHE EDI setup path from start to finish.

Step 1: Complete KeHE Vendor Onboarding. Before EDI setup begins, you must be an approved KeHE vendor. This means completing KeHE's supplier application, providing product information, agreeing to their trading terms, and receiving your KeHE vendor number. This number is essential for all EDI transactions.

Step 2: Choose Your EDI Provider and Communication Method. KeHE supports multiple connection methods including AS2, VAN (Value Added Network), and SFTP. Select an EDI provider that supports your preferred method and has experience with KeHE's specific document requirements. Your provider will need your KeHE vendor number, qualifier codes, and ISA/GS identifiers to configure the connection.

Step 3: Configure EDI Document Maps. Work with your EDI provider to map KeHE's required document formats (850, 855, 856, 810, 997) to your internal systems. This includes mapping KeHE-specific fields like their distribution center codes, product identifiers (GTINs/UPCs), and pricing structures. Each document must conform to KeHE's implementation guides.

Step 4: Run EDI Testing with KeHE. KeHE requires suppliers to complete a testing phase where sample documents are exchanged and validated. You will send test 855s, 856s, and 810s in response to test 850s from KeHE. Every field must parse correctly, and the data must match KeHE's expected values. Failed tests require corrections and re-submission.

Step 5: Go Live. Once testing passes, KeHE certifies your EDI connection and you begin receiving live purchase orders. Monitor your first few live transactions closely to catch any issues that testing may not have surfaced, particularly around timing, product catalog alignment, and pricing.

"The ability and willingness of Crstl to help is night and day compared to other providers. They're not just a vendor; they're genuinely invested in our success." — Josh Lazenby, Senior Operations Manager, KitchenSupply

What Are KeHE's EDI Communication Protocols?

KeHE supports three primary EDI communication protocols: AS2 (Applicability Statement 2), VAN (Value Added Network), and SFTP (Secure File Transfer Protocol), with AS2 being the preferred method for direct connections. The communication protocol you choose determines how your EDI documents are transmitted to and from KeHE's systems. AS2 is an internet-based protocol that provides secure, real-time document exchange with built-in message disposition notifications (MDNs) that confirm delivery. VAN connections route documents through a third-party network like SPS Commerce, OpenText, or Kleinschmidt, which adds a layer of managed connectivity but also adds per-document transaction fees. SFTP provides batch file transfers on a scheduled basis, which works for suppliers with lower transaction volumes but lacks the real-time confirmation that AS2 provides. Regardless of the protocol you choose, all documents must conform to ANSI X12 format specifications, and your connection must support KeHE's specific ISA/GS envelope requirements. Your EDI provider should be able to configure any of these protocols, but it is worth confirming KeHE compatibility before you commit.

What Are KeHE's Product Data and GTIN Requirements?

KeHE requires every product traded via EDI to have a valid Global Trade Item Number (GTIN), accurate case pack configurations, and product descriptions that match what is registered in KeHE's item master database. Product data accuracy is the single most common source of EDI errors and chargebacks for KeHE suppliers. Every item on a purchase order is identified by its GTIN (typically a UPC-12 or EAN-13), and this number must match exactly between your catalog, KeHE's item master, and the data in your EDI documents. Mismatches between the GTIN on your 856 ASN and what KeHE expects will trigger receiving discrepancies at the distribution center. Case pack quantities must also be accurate: if KeHE orders 10 cases and your EDI documents report a different inner pack or case count than what is registered, the shipment may be short-received or rejected entirely. Beyond GTINs, KeHE requires accurate product dimensions, weights, shelf life information, and allergen declarations for food and beverage products. Keeping this data synchronized across your systems, KeHE's vendor portal, and your EDI documents is essential for compliance.

For a complete overview of how purchase orders flow through EDI systems, check out our guide on EDI 850 Purchase Orders.

How Do KeHE EDI Chargebacks Work?

KeHE issues chargebacks (also called compliance deductions) to suppliers who fail to meet EDI and shipping compliance standards, with penalties typically ranging from flat fees per violation to percentage-based deductions on the affected purchase order. These chargebacks are KeHE's mechanism for enforcing compliance across their supplier network, and they cover everything from late or missing ASNs to pricing discrepancies on invoices to labeling errors on shipped product. The most common KeHE chargebacks hit suppliers for ASN non-compliance: either the ASN was not sent before the shipment arrived, the ASN data did not match what was physically received, or the ASN was missing required fields like SSCC-18 barcodes or accurate case counts. Invoice discrepancies are the second most frequent source, triggered when the 810 invoice amount does not match the original purchase order or when pricing does not reflect agreed-upon promotional allowances. Brands new to KeHE often underestimate how quickly these chargebacks accumulate. A single missing ASN field replicated across dozens of shipments can result in thousands of dollars in deductions within a single quarter.

For a comprehensive breakdown of chargeback prevention across all major retailers, see our guide on how to avoid EDI chargebacks.

How Does KeHE EDI Compare to UNFI EDI?

KeHE and UNFI are the two dominant natural and organic distributors in North America, and while their EDI requirements share the same ANSI X12 foundation, they differ meaningfully in document specifications, testing processes, chargeback structures, and vendor portal functionality. Many natural product brands sell through both distributors simultaneously, which means maintaining compliance with two distinct sets of EDI rules. UNFI tends to have more granular ASN requirements, particularly around pallet-level SSCC-18 barcodes and hierarchical shipment structures, while KeHE's ASN requirements focus more heavily on case-level accuracy and GTIN validation. Both distributors require the core 850/855/856/810 document set, but their implementation guides differ in field-level details like date formats, reference number usage, and how promotional pricing is communicated. From a chargeback perspective, both distributors penalize ASN non-compliance and invoice discrepancies, but the fee structures and dispute resolution processes differ. Brands that sell through both KeHE and UNFI benefit significantly from an EDI platform that maintains retailer-specific maps and validates documents against each distributor's rules before transmission.

For full details on UNFI's requirements, read our UNFI EDI Requirements guide.

What Are KeHE's Labeling and Packaging EDI Requirements?

KeHE requires all shipments to include GS1-128 compliant shipping labels with SSCC-18 barcodes, accurate case markings, and packing slips that match the corresponding EDI 856 advance ship notice. Labeling compliance is where EDI data meets the physical supply chain, and errors here are among the most visible and costly. Every case shipped to KeHE must be labeled with a scannable barcode that matches the GTIN in the corresponding ASN. Pallet labels must include the SSCC-18 (Serial Shipping Container Code) that ties the physical pallet to the electronic ASN data KeHE's receiving team scans at the dock door. If the barcode on the case does not match what the ASN says, KeHE's warehouse management system flags the discrepancy immediately, potentially rejecting the entire pallet. Beyond barcodes, KeHE requires that case markings include the product description, case count, lot number, and expiration date for food and beverage items. Packing slips should reconcile exactly with the ASN contents. Brands using modern EDI platforms can generate these labels directly from EDI data, ensuring that what the label says always matches what the ASN reports.

"As a startup, our biggest advantage is speed of execution. Having a partner, like Crstl, who shares that same advantage and acts quickly was incredibly valuable, especially when it allowed us to get EDI set up with UNFI sooner, which in turn allowed us to secure better payment terms." — Russ Wallace, CEO and Co-founder, Freestyle

How Can AI-Powered EDI Simplify KeHE Compliance?

AI-powered EDI platforms automate the most error-prone aspects of KeHE compliance by pre-validating documents against KeHE's specific rules before transmission, auto-generating compliant ASNs from shipment data, and flagging pricing discrepancies before they become chargebacks. Traditional EDI solutions require suppliers to manually configure document maps, monitor for errors reactively, and troubleshoot compliance failures after they have already triggered a chargeback. AI-powered platforms like Crstl flip this model by catching errors before they leave your system. When a purchase order arrives from KeHE, the platform automatically validates it against your current inventory and pricing, generates the acknowledgment, and queues the downstream documents (ASN and invoice) with pre-populated data that matches the original PO. If any field is missing, formatted incorrectly, or conflicts with KeHE's requirements, the system alerts your team before the document is transmitted. This pre-transmission validation is the difference between reactive chargeback management and proactive compliance. Brands using Crstl for KeHE EDI report that onboarding takes days instead of weeks, and ongoing compliance requires minimal manual intervention because the platform handles the complexity.

Ready to automate your KeHE EDI compliance? Book a demo with Crstl and see how brands like yours are eliminating EDI chargebacks.

For more on how AI is transforming EDI, read our complete guide to AI-powered EDI.

What Does a KeHE EDI Compliance Checklist Look Like?

A complete KeHE EDI compliance checklist covers five domains: vendor registration, document readiness, data quality, labeling standards, and ongoing monitoring, and every supplier should validate all five before going live. This checklist is not a one-time exercise. KeHE periodically updates their requirements, adds new distribution centers with different routing codes, and adjusts chargeback thresholds. Suppliers who treat compliance as a set-it-and-forget-it task inevitably encounter issues when KeHE makes changes. The most effective approach is to build compliance checks into your daily operations: validate every ASN before it is sent, reconcile every invoice against the original PO, and review your chargeback reports monthly to catch patterns before they become expensive trends. Below is the checklist format that successful KeHE suppliers follow.

Frequently Asked Questions About KeHE EDI

What EDI standard does KeHE use?

KeHE uses the ANSI X12 EDI standard, which is the dominant B2B document exchange format in North American commerce. All documents including purchase orders (850), acknowledgments (855), advance ship notices (856), and invoices (810) must conform to X12 specifications as detailed in KeHE's implementation guides.

How long does KeHE EDI setup take?

KeHE EDI setup typically takes four to eight weeks from vendor onboarding through go-live certification. The timeline depends on your EDI provider's familiarity with KeHE, the complexity of your product catalog, and how quickly your team can complete testing. Modern platforms with pre-built KeHE maps can reduce this to days.

Does KeHE require AS2 for EDI connections?

KeHE supports AS2, VAN, and SFTP connections, but AS2 is their preferred protocol for direct connections because it provides real-time transmission with delivery confirmation. Suppliers already connected to a VAN can use that existing connection, and SFTP is available for lower-volume suppliers.

What happens if my ASN does not match the physical shipment?

When KeHE receives a shipment that does not match the ASN data, they will flag the discrepancy and may issue a chargeback for the difference. Common mismatches include incorrect case counts, wrong GTINs, or missing pallet information. Repeated mismatches can also delay payment processing on affected invoices.

Can I use the same EDI setup for KeHE and UNFI?

While both KeHE and UNFI use ANSI X12 EDI, their implementation guides differ in field-level requirements, timing windows, and chargeback structures. You need retailer-specific document maps for each distributor. A capable EDI platform maintains separate configurations for each trading partner while presenting a unified interface to your team.

What are the most common KeHE EDI chargebacks?

The most common KeHE chargebacks are ASN non-compliance (missing, late, or inaccurate advance ship notices), invoice pricing discrepancies (amounts that do not match the purchase order), short shipments, and labeling violations. Pre-transmission validation and automated document generation prevent the majority of these issues.

Does KeHE charge for EDI transactions?

KeHE does not charge suppliers directly for EDI transactions, but suppliers must bear the cost of their own EDI provider and connectivity method. VAN-based connections include per-document fees charged by the VAN provider, while AS2 and SFTP connections avoid per-document charges after the initial setup.

Start Trading with KeHE the Right Way

KeHE EDI compliance is not optional for suppliers who want to build a lasting relationship with one of North America's most important natural and organic distributors. The requirements are detailed, the testing is rigorous, and the chargeback penalties for non-compliance are real. But the upside is equally significant: brands that get EDI right with KeHE gain access to over 30,000 retail locations, benefit from faster payment cycles, and build the operational foundation needed to scale across additional retailers.

The brands that succeed with KeHE EDI are the ones that invest in the right platform from the start. Rather than wrestling with legacy EDI providers that take months to onboard a single trading partner, modern brands choose platforms that already have KeHE in their network and can automate compliance from day one.

"Our team is a lot more efficient since switching to Crstl. When it comes to onboarding a customer, the time that it takes is very short." — Silas Ang, Director of Supply Chain, Immi

Book a demo with Crstl to see how AI-powered EDI makes KeHE compliance effortless for natural and organic brands.