e2open (Carrier Marketplace, formerly BluJay)

e2open Carrier Marketplace is the carrier side of the e2open transportation management system, formerly the BluJay Carrier Network. Shippers on the e2open TMS tender loads to the carriers they work with, and carriers answer through the free e2open Carrier Portal. Connected to Load Hub, those tenders sit in the same table as loads from your inbox and freight exchanges. The dispatcher or planner who handles shipper tenders switches it on.

What teams use it for

Answer a contract tender before it expires

A shipper on e2open tenders a Columbus to Memphis load at 09:10 with a response window. The tender arrives in Load Hub under the carrier's e2open account with lane, dates, equipment and the window. The dispatcher gets a notification, checks the load against the truck that empties in Columbus that morning, and asks the digital worker to accept. The worker sends the acceptance under the carrier's SCAC, the dispatcher confirms in Load Hub, and the tender turns to booked.

Keep tenders and spot loads in one table

A regional fleet runs contract lanes for two shippers on e2open and fills the gaps from exchanges and email. Each tender arrives in Load Hub when it is issued, next to the exchange loads and emailed offers for the same day. The planner sorts by pickup date and equipment and sees which trucks have contract freight and which still need a spot load.

Counter a tender through the digital worker

A tender comes in below the lane's cost after deadhead. The e2open Carrier Portal lets a carrier accept, decline or counter. The dispatcher types the rate he needs, and the digital worker sends the counter under the carrier's account and logs it on the load. If the shipper accepts, the load turns to booked after the dispatcher confirms. If the shipper declines, the load closes and the truck stays in the spot search.

Set an auto-search for the lanes you want more of

A carrier with a strong Dallas to Atlanta lane sets an auto-search in Load Hub: Dallas to Atlanta, dry van, any pickup this week. Every e2open tender the account is entitled to see is checked against it, and a match sends a notification. The dispatcher opens the load, sees shipper, dates and rate, and decides to accept or counter from Load Hub.

Run the load in the e2open Carrier Portal

After booking, the shipper expects status updates, documents and invoices through the e2open Carrier Portal, which offers them at no cost. The dispatcher keeps doing that in the portal. Load Hub holds the load, the driver assignment and the email thread with the shipper's planner. After delivery, the dispatcher attaches the POD to the load in Load Hub so the invoice goes out with the right document.

How it fits your stack

Your e2open Carrier Portal account stays the account of record. Onboarding happens on e2open's side first: you register with your SCAC or VAT code, and each shipper connects you in their TMS. e2open does not require a paid subscription to work with shippers; EDI, API, the quarterly scorecard and Procurement Discovery are paid tiers. Cargofy reads the tenders your SCAC is entitled to see and sends acceptances, counters or declines through your account. You confirm every booking. Cargofy does not send status updates, documents or invoices into e2open. Your Load Hub data is stored in the EU (Frankfurt).

Who it is for

Fleets of 10 to 100 trucks and larger that run contract lanes for shippers on the e2open TMS, in the United States or Europe. Less useful for owner-operators on spot freight only, since loads come as shipper tenders to connected carriers.