Skip to content

Channel

KeHE DistributorsKehe via SPS

Plan a reliable EDI exchange for KeHE Distributors / Kehe via SPS. Explore 3 document references, map them to your business records and test the complete workflow before launch.

Documents
3 transactions
Standards
X12
Implementation
Mapping and launch plan

Implementation guide

KeHE Distributors / Kehe via SPS: EDI implementation plan

Build a reliable EDI workflow for KeHE Distributors / Kehe via SPS. 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.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
X12 855 Purchase Order AcknowledgmentListed for Kehe via SPS purchase-order response

original purchase order, response revision and order line

  • Test a partially accepted order with a backordered line and retain both outcomes.
  • Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates.
X12 810 InvoiceListed for Kehe via SPS accounts-receivable or accounts-payable invoice

invoice number, purchase order and invoice line

  • Reconcile line amounts, allowances, charges and tax to the invoice total.
  • Submit the same invoice twice and verify that it cannot create a second payable.
X12 850 Purchase OrderListed for Kehe via SPS purchase order or sales order

buyer purchase order, order line and trading-party identifiers

  • Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit.
  • Resend one purchase order and confirm that only one sales order is created.

Implementation steps

  1. Choose the trading account and channel

    Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Kehe via SPS. Compare other KeHE Distributors channels before reusing a mapping.

  2. Map records and assign owners

    Start with purchase-order response, accounts-receivable or accounts-payable invoice, purchase order or sales order. 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.

  3. Test a complete exchange

    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.

  4. Check results after launch

    Match records between systems using original purchase order, response revision and order line. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.

Go-live checklist

  • The required X12 documents, versions and sample files are agreed.
  • Sender and receiver IDs, test connections and production connections are agreed with the channel owner.
  • Delivery receipts, document validation and business responses have monitoring and a named owner.
  • Tests cover duplicates, partial processing and reconciliation with realistic business records.

Document catalog

EDI documents listed for KeHE Distributors / Kehe via SPS

3 EDI transactions listed in this catalog.

Document flow on this channel

Document relationships on Kehe via SPS

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.

Listed on other KeHE Distributors channels

Network onboarding

Plan the SPS Commerce connection

The directory associates SPS Commerce with 74 partner entries across 94 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.

Most frequently listed documents on SPS Commerce
  • 850 92 ch
  • 810 91 ch
  • 856 90 ch
  • 855 87 ch
  • 860 56 ch
  • 846 29 ch

Kehe via SPS questions

Which EDI documents are listed for KeHE Distributors / Kehe via SPS?

X12 855 Purchase Order Acknowledgment; X12 810 Invoice; X12 850 Purchase Order. Confirm which documents, directions and versions apply to your account.

How should I choose the KeHE Distributors EDI channel?

Kehe via SPS 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.

Which identifiers should the KeHE Distributors mapping preserve?

For X12 855 Purchase Order Acknowledgment, plan around original purchase order, response revision and order line. For X12 810 Invoice, use invoice number, purchase order and invoice line. Use the partner guide to locate these values and check their allowed formats.

Does a successful EDI receipt mean KeHE Distributors accepted the business document?

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.

What should be tested before launching KeHE Distributors / Kehe via SPS EDI?

Test a partially accepted order with a backordered line and retain both outcomes. Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.

Related references

Other KeHE Distributors channels

Compare the document lists for other KeHE Distributors channels.

Connect KeHE Distributors EDI to your business systems

See 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.