Skip to content
EDI CHEP CHEP (via BlueYonder)

Channel

CHEPCHEP (via BlueYonder)

CHEP (via BlueYonder) is one of CHEP's 1 EDI trading channels. It supports 4 document types including X12 210, X12 204, X12 214, X12 990.

Book a demo ← All CHEP channels
Documents
4 transactions
Standards
X12 + EDIFACT
Transport
AS2 · SFTP · API

Document catalog

EDI documents we support for CHEP CHEP (via BlueYonder)

4 EDI transactions ready to integrate.

Document flow on this channel

How documents flow on CHEP (via BlueYonder)

This channel carries all 4 of CHEP's document types.

Network onboarding

CHEP (via BlueYonder) is routed through BlueYonder

Stacksync maintains a certified BlueYonder connection covering 1 trading partner across 1 channel. Onboarding with CHEP on this channel reuses that connection — no separate VAN contract or certification cycle.

Blue Yonder (formerly JDA Software) is a supply chain software vendor whose transportation management system exchanges carrier EDI through the Blue Yonder Cloud EDI service. Shippers running Blue Yonder TMS use it to tender loads to carriers (204), receive tender responses, track shipment status (214), and receive freight invoices (210), in X12 or EDIFACT for motor, air, and ocean freight.

Connecting via BlueYonder
  1. The shipper confirms the carrier is EDI-capable and submits it as a pre-qualified carrier to the Blue Yonder Cloud EDI team, which manages the setup from there.
  2. Blue Yonder applies its common maps and workflows; where requirements are not met out of the box, the Blue Yonder team evaluates the request and builds the mapping changes.
  3. The carrier establishes connectivity to Blue Yonder Cloud FTP/SFTP servers.
  4. Both sides test connectivity and message exchange; mapping issues found in testing are resolved by the Blue Yonder Cloud EDI team before go-live.

Testing: Carriers must demonstrate they can connect to Blue Yonder Cloud FTP/SFTP servers and send and retrieve correctly translated messages before production. The Blue Yonder Cloud EDI team fixes mapping issues surfaced during testing, and post-launch it provides standard daily reports of failed messages.

Timeline: Blue Yonder does not publish a standard carrier onboarding timeline. Duration depends on whether the common maps fit the carrier's formats and how quickly the carrier completes connectivity and message testing with the Blue Yonder Cloud EDI team.

Most-traded documents on BlueYonder
  • 204 1 ch
  • 210 1 ch
  • 214 1 ch
  • 990 1 ch

Ready to automate your CHEP EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a CHEP EDI demo Tour the platform on your own