MC 1209052 · DOT 3580175 · SCAC: RJBH · Grand Prairie, TX

Customer Portal
RAJO Transportation logo
Quote

Customer setup

What RAJO needs before customer setup moves forward

This page replaces the old PDF-packet mindset with a structured setup path. Send the details once, then RAJO can review service fit, packet requirements, visibility rules, billing setup, and portal readiness without chasing basics across multiple threads.

Start customer setupQuote a lane

Company and contacts

  • -Legal company name and DBA if different
  • -Primary freight contact
  • -Dispatch or operations contact
  • -Billing / AP contact
  • -After-hours escalation contact

Compliance packet

  • -MC 1209052, DOT 3580175, and SCAC RJBH
  • -COI holder language and insurance requirements
  • -W-9 and carrier agreement path
  • -RMIS, Highway, or other setup invite if required
  • -Safety, compliance, or scorecard requirements

Lane and freight profile

  • -Origin and destination markets
  • -Spot, pilot lane, recurring lane, mini-bid, or RFP
  • -Expected weekly or monthly volume
  • -Commodity, weight, appointment rules, and facility notes
  • -Drop/live load rules, detention terms, and receiver instructions

Power-only details

  • -Trailer owner or trailer program
  • -Loaded or empty status
  • -Trailer type, unit number, pickup yard, and delivery location
  • -Drop-and-hook rules, road-readiness, and responsibility terms
  • -Tracking requirement before the driver rolls

Intermodal drayage details

  • -Rail ramp or terminal
  • -Container number, booking, BOL, or release reference when available
  • -SSL, freight forwarder, broker, and customer contacts
  • -Import LFD, export cutoff, prepull need, and yard plan
  • -Chassis status, delivery appointment, and empty-return plan

Visibility and systems

  • -Macropoint, FourKites, EDI 204/214, API, portal, or email update needs
  • -Tender method and acceptance expectations
  • -Status update cadence
  • -Document and POD delivery path
  • -Invoice delivery preference and billing reference requirements

Review first

No blind portal or integration access

Customer setup is not just a login. RAJO needs to know who the customer is, what lanes they need, what visibility rules apply, and which loads or documents they are allowed to see before portal or integration access expands.

Review path

  1. 1Customer submits setup details through onboarding, quote, or sales.
  2. 2RAJO reviews service fit, missing fields, packet requirements, and urgency.
  3. 3Approved accounts move toward packet completion, portal setup, quote review, or a pilot lane.
  4. 4EDI/API and recurring programs are scoped after the customer, lane, and data rules are stable.