Skip to content
EDI E2open, LLC Leprino (via E2open)

Channel

E2open, LLCLeprino (via E2open)

Leprino (via E2open) is one of E2open, LLC's 37 EDI trading channels. It supports 4 document types including X12 210, X12 204, X12 990, X12 214.

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

Document catalog

EDI documents we support for E2open, LLC Leprino (via E2open)

4 EDI transactions ready to integrate.

Document flow on this channel

How documents flow on Leprino (via E2open)

This channel carries all 4 of E2open, LLC's document types.

Network onboarding

Leprino (via E2open) is routed through E2open

Stacksync maintains a certified E2open connection covering 9 trading partners across 41 channels. Onboarding with E2open, LLC on this channel reuses that connection — no separate VAN contract or certification cycle.

E2open operates e2net, a multi-enterprise supply chain network; its transportation management platform (which absorbed the BluJay and LeanLogistics TMS products) connects shippers with contracted carriers. Shippers running e2open TMS require carriers to integrate electronically: load tenders (204) flow out to the carrier, and tender responses (990), shipment statuses (214), and freight invoices (210) flow back. Carriers join through tiered Carrier Marketplace subscriptions that determine portal, EDI, or API access.

Connecting via E2open
  1. Enroll in the e2open Carrier Marketplace at the tier matching your integration needs: Web Connect+ provides browser access, EDI connectivity is an optional add-on on the eConnect and eConnect+ tiers, and APIs come with eConnect+ (as an optional add-on) and LTLConnect.
  2. After enrollment the carrier enters the implementation queue; e2open states an implementation team member normally reaches out within a few business days with an estimated project start date.
  3. Configure connectivity and map the transaction sets to the TMS specification, in X12 (204, 990, 214, 210) or EDIFACT (IFTMIN, IFTSTA).
  4. Validate outbound documents with e2open's self-service Carrier EDI Validation Tool, submitting the received 204 or IFTMIN alongside the response document.
  5. Complete end-to-end testing with e2open before production cutover.

Testing: A self-service Carrier EDI Validation Tool checks whether 990, 214, and 210 EDI files (or EDIFACT and XML equivalents) contain the data required to update loads and invoices in the TMS; carriers submit the received 204 or IFTMIN together with the document under test. E2open's AS2 software is Drummond Group certified and is resubmitted for certification twice per year.

Timeline: E2open publishes no end-to-end figure. Newly enrolled carriers are normally contacted within a few business days with an estimated project start date; total duration then depends on subscription tier, integration method, and the number of shippers being connected.

Most-traded documents on E2open
  • 204 41 ch
  • 214 41 ch
  • 990 41 ch
  • 210 31 ch
Other partners reachable via E2open

Leprino (via E2open) questions

Which transaction sets does Leprino use on this E2open channel?
EDI 204, 990, 214, and 210 — load tender, tender response, shipment status, and freight invoice.
Does this channel cover the whole logistics cycle with Leprino?
Yes. The 204/990/214/210 document set constitutes the complete logistics chain, from tender through invoice.

Trading partners

36+ 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.

Browse the full directory

Ready to automate your E2open, LLC EDI?

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

Book a E2open, LLC EDI demo Tour the platform on your own