KeHE Distributors EDI
integration guide.
Plan your KeHE Distributors EDI integration using 9 listed document types across 5 channels. Compare channels, map business records and test the operational handoff.
Adopted by fast-scaling companies moving mission-critical data in real time
Implementation guide
KeHE Distributors: document mapping and implementation plan
KeHE Distributors has 9 distinct document types listed in this catalog across 5 channels. Use the document-to-record plan below to scope your ERP, warehouse or transport integration. Catalog presence describes available reference material; your agreement determines the required messages and versions.
| Document or decision | Record and correlation | Acceptance tests to agree |
|---|---|---|
| X12 990 Response To A Load TenderListed on 1 channel: KeHe Food Distributors (via Manhattan Associates) | load-tender response original load reference, carrier and response |
|
| X12 214 Transportation Carrier Shipment Status MessageListed on 1 channel: KeHe Food Distributors (via Manhattan Associates) | shipment status event shipment reference, event code, event time and location |
|
| X12 204 Motor Carrier Load TenderListed on 1 channel: KeHe Food Distributors (via Manhattan Associates) | load tender load reference, pickup and delivery stop identifiers |
|
| X12 855 Purchase Order AcknowledgmentListed on 4 channels: Kehe Supplier, Kehe via SPS, KeHE Distributors (via SPS Commerce)… | purchase-order response original purchase order, response revision and order line |
|
| X12 850 Purchase OrderListed on 4 channels: Kehe Supplier, Kehe via SPS, KeHE Distributors (via SPS Commerce)… | purchase order or sales order buyer purchase order, order line and trading-party identifiers |
|
| X12 810 InvoiceListed on 4 channels: Kehe Supplier, Kehe via SPS, KeHE Distributors (via SPS Commerce)… | accounts-receivable or accounts-payable invoice invoice number, purchase order and invoice line |
|
| X12 860 Purchase Order Change Request Buyer InitiatedListed on 1 channel: KeHE Distributors (via SPS Commerce) | buyer order-change request original purchase order, change revision and affected line |
|
| X12 856 Ship Notice ManifestListed on 1 channel: KeHE Distributors (via SPS Commerce) | shipment notice (ASN) shipment, order, package and item references |
|
| X12 812 Credit Debit AdjustmentListed on 1 channel: KeHE Distributors (via SPS Commerce) | credit or debit adjustment adjustment reference, original invoice and reason |
|
From business event to reconciled record
-
Identify the exact trading relationship
Choose among KeHe Food Distributors (via Manhattan Associates), Kehe Supplier, Kehe via SPS, KeHE Distributors (via SPS Commerce) and the remaining listed channels. Confirm the business unit and account before copying a mapping from another channel.
-
Map business records and responses
Start with load-tender response, shipment status event, load tender. For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event.
-
Prove the channel with representative cases
Run a normal exchange and the document-specific exception cases below. Capture transport receipt, syntax validation and business processing as separate results. Agree the KeHE Distributors test/production handoff and retain the evidence for each approved message.
-
Reconcile after cutover
Compare source and destination counts using original load reference, carrier and response. Investigate missing responses, duplicates and rejected records with a named owner. Approve recovery behavior before enabling automatic retries.
Before approving production
- Current X12 guide, release/version, required subset and sample files are recorded.
- Sender/receiver identifiers, test endpoint and production endpoint are agreed with the channel owner.
- Transport receipts, document acknowledgments and business responses have separate monitoring and escalation.
- Duplicate handling, partial processing and reconciliation have passed with realistic source-system records.
Document catalog
EDI documents listed for KeHE Distributors
18 transactions across 5 channels.
Kehe Supplier
3 docsKehe via SPS
3 docsKeHE Distributors (via SPS Commerce)
6 docsKehe Retailer
3 docsDocument flow
Example document relationships for KeHE Distributors
Where each document sits in its trading cycle, based on the 9 document types listed for KeHE Distributors across 5 channels. These are example relationships; the trading agreement determines the required sequence.
Order-to-cash
All example steps listedLogistics
Some example steps listed- 204 Motor Carrier Load Tender
- 990 Response To A Load Tender
- 214 Transportation Carrier Shipment Status Message
- 210 Motor Carrier Freight Details and Invoice not listed for KeHE Distributors
- 204 Motor Carrier Load Tender — is listed on 1 of KeHE Distributors's 5 channels
- 214 Transportation Carrier Shipment Status Message — is listed on 1 of KeHE Distributors's 5 channels
- 810 Invoice — is listed on 4 of KeHE Distributors's 5 channels
- 812 Credit Debit Adjustment — is listed on 1 of KeHE Distributors's 5 channels
- 850 Purchase Order — is listed on 4 of KeHE Distributors's 5 channels
- 855 Purchase Order Acknowledgment — is listed on 4 of KeHE Distributors's 5 channels
- 856 Ship Notice Manifest — is listed on 1 of KeHE Distributors's 5 channels
- 860 Purchase Order Change Request Buyer Initiated — is listed on 1 of KeHE Distributors's 5 channels
- 990 Response To A Load Tender — is listed on 1 of KeHE Distributors's 5 channels
Network context
KeHE Distributors channel references for Manhattan Associates and SPS Commerce
These network names are derived from the listed KeHE Distributors channels. Confirm routing, enrollment and contractual requirements for your account before selecting a connection method.
Manhattan Associates
17 channels · 16 trading partners in the catalog
KeHE Distributors channel on this network: KeHe Food Distributors (via Manhattan Associates)
- 204 17 ch
- 214 17 ch
- 990 17 ch
- 210 9 ch
SPS Commerce
94 channels · 74 trading partners in the catalog
KeHE Distributors channels on this network: Kehe via SPS, KeHE Distributors (via SPS Commerce)
- 850 92 ch
- 810 91 ch
- 856 90 ch
- 855 87 ch
- 860 56 ch
Still with a legacy EDI vendor? We cover the buyout.
Stacksync buys back your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. No migration cost, no overlap billing.
Check your eligibility for the EDI migration fundSecurity teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Trading partners
0+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
FAQ
KeHE Distributors EDI questions
Which EDI documents are listed for KeHE Distributors?
X12 990 Response To A Load Tender; X12 214 Transportation Carrier Shipment Status Message; X12 204 Motor Carrier Load Tender; X12 855 Purchase Order Acknowledgment; X12 850 Purchase Order; X12 810 Invoice; X12 860 Purchase Order Change Request Buyer Initiated; additional documents are shown in the mapping plan. These are catalog listings. Confirm the required subset, direction and version for your trading agreement.
How should I choose the KeHE Distributors EDI channel?
This catalog lists 5 channels for KeHE Distributors, including KeHe Food Distributors (via Manhattan Associates), Kehe Supplier, Kehe via SPS, KeHE Distributors (via SPS Commerce). Match the channel to your actual trading relationship and compare its document list before reusing a mapping.
Which identifiers should the KeHE Distributors mapping preserve?
For X12 990 Response To A Load Tender, plan around original load reference, carrier and response. For X12 214 Transportation Carrier Shipment Status Message, use shipment reference, event code, event time and location. Confirm field locations, qualifiers and allowed values in the applicable guide; these are business-level mapping recommendations.
Does a successful EDI receipt mean KeHE Distributors accepted the business document?
Track three outcomes separately: transport receipt, syntax or implementation validation, and business processing. An AS2 MDN acknowledges the transport exchange; an X12 997 or 999 concerns technical validation. The agreed business response or reconciliation confirms whether the order, shipment or invoice was processed.
What should be tested before launching KeHE Distributors EDI?
Associate acceptance with the correct version of the load tender. Test a declined tender and ensure it returns to dispatch for reassignment. Also test missing responses and recovery after a destination failure. Confirm partner approval and named exception owners before choosing a production date.




