Skip to content
EDI Hostess Hostess via Blujay

Channel

HostessHostess via Blujay

Hostess via Blujay is one of Hostess's 1 EDI trading channels. It supports 3 document types including X12 990, X12 214, X12 204.

Documents
3 transactions
Standards
X12 + EDIFACT
Transport
AS2 · SFTP · API

Document flow on this channel

How documents flow on Hostess via Blujay

This channel carries all 3 of Hostess's document types.

Network onboarding

Hostess via Blujay is routed through BluJay

Stacksync maintains a certified BluJay connection covering 5 trading partners across 5 channels. Onboarding with Hostess on this channel reuses that connection — no separate VAN contract or certification cycle.

BluJay Solutions was a transportation management and logistics network provider and is now part of e2open; its carrier network operates as the e2open Carrier Marketplace (formerly BluJay's Carrier Network). Shippers running the TMS tender loads to carriers and receive status updates and freight invoices back, so carriers on the network exchange 204 load tenders, 990 tender responses, 214 shipment statuses, and 210 freight invoices.

Connecting via BluJay
  1. Enroll in the e2open Carrier Marketplace and choose a subscription tier: Web Connect+ (browser only), eConnect (optional EDI), eConnect+ (EDI plus API), or LTLConnect.
  2. After enrollment, an e2open implementation team member reaches out, normally within a few business days, with an estimated project start date.
  3. For eConnect and eConnect+, configure EDI or API connectivity for the 204, 990, 214, and 210 flows; new EDI or API configuration may involve implementation fees.
  4. Validate documents with e2open's carrier EDI validation tool, which checks that EDI, EDIFACT (IFTSTA), or Document Upload XML files contain the required information to update a load or invoice.
  5. Once the carrier's SCAC is integrated, additional shippers can be added at no extra charge.

Testing: e2open provides a self-service carrier EDI validation tool: the carrier pastes a 204/IFTMIN received from e2open together with its response document (990, 214, 210, IFTSTA, or Document Upload XML) and the tool verifies the fields required to update a load or invoice. New EDI or API configurations are also handled as an e2open-managed implementation project.

Timeline: e2open states an implementation team member contacts enrolled carriers, normally within a few business days, with an estimated project start date; total time to production depends on that scheduling and the EDI or API configuration work.

Most-traded documents on BluJay
  • 204 5 ch
  • 214 5 ch
  • 990 5 ch
  • 210 4 ch

Ready to automate your Hostess EDI?

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