Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Channel
Plan a reliable EDI exchange for KeHE Distributors / KeHe Food Distributors (via Manhattan Associates). Explore 3 document references, map them to your business records and test the complete workflow before launch.
Implementation guide
Build a reliable EDI workflow for KeHE Distributors / KeHe Food Distributors (via Manhattan Associates). Use 3 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.
The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 990 Response To A Load TenderListed for KeHe Food Distributors (via Manhattan Associates) | load-tender response original load reference, carrier and response |
|
| X12 214 Transportation Carrier Shipment Status MessageListed for KeHe Food Distributors (via Manhattan Associates) | shipment status event shipment reference, event code, event time and location |
|
| X12 204 Motor Carrier Load TenderListed for KeHe Food Distributors (via Manhattan Associates) | load tender load reference, pickup and delivery stop identifiers |
|
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for KeHe Food Distributors (via Manhattan Associates). Compare other KeHE Distributors channels before reusing a mapping.
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.
Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the KeHE Distributors production handoff and save the results of each approved test.
Match records between systems using original load reference, carrier and response. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Document catalog
3 EDI transactions listed in this catalog.
Document flow on this channel
This channel lists 3 of the 9KeHE Distributors document types; other entries appear on KeHE Distributors channels (listed below). Example relationships are shown below; confirm the required sequence in the channel guide.
Network onboarding
The directory associates Manhattan Associates with 16 partner entries across 17 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.
X12 990 Response To A Load Tender; X12 214 Transportation Carrier Shipment Status Message; X12 204 Motor Carrier Load Tender. Confirm which documents, directions and versions apply to your account.
KeHe Food Distributors (via Manhattan Associates) lists 3 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.
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. Use the partner guide to locate these values and check their allowed formats.
Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed.
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. Assign an owner to each failure and obtain partner approval before launch.
Related references
Compare the document lists for other KeHE Distributors channels.
Showing 4 of 4 references
Browse the full directorySee how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
