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

Customer Portal
RAJO Transportation logo
Quote

Tracking and portal access

Public lookup stays narrow. Customer portal access stays controlled.

RAJO can support fast shipment checks without turning public tracking into account access. Approved customers move into an invite-only portal where load visibility, documents, invoices, and future EDI/API workflows are controlled by customer account and linked loads.

Start customer setupView portal path

Live shipment lookup

Track a shipment

Anyone holding the paperwork can look a shipment up — no account, no sign-in. The customer portal adds account load lists, documents and invoices.

Portal access

Enter the reference in full, exactly as it appears on your paperwork.

Load #BOLContainer #POPROPickup #Customer Ref

Public shipment lookup

Public tracking is for quick one-load status checks. It should answer the basic question without exposing account-level freight activity.

  • -Basic shipment status by RAJO load number, customer reference, PO, BOL, PRO, or LoadStop ID
  • -Limited origin, destination, pickup, estimated delivery, equipment, and current status details
  • -No broad account list, invoice history, document library, or customer-wide shipment search
  • -Best for quick one-load checks before a portal invite is active

Invite-only customer portal

Portal access is account-specific. The operating rule is simple: no customer sees a load unless RAJO has linked that load to the customer account.

  • -Invite-only account access after RAJO reviews the customer setup
  • -Shipment lists scoped to loads explicitly linked to the customer account
  • -TMS-backed visibility as load records, planned equipment, documents, and invoices become available
  • -Future EDI/API tendering and invoice workflows after data rules and account controls are stable

Portal rollout path

01

Start with customer setup

RAJO needs company contacts, lane profile, compliance requirements, billing path, visibility rules, and the load references a customer should be able to see.

02

Link only approved loads

Portal access should not expose every mirrored TMS record. Each customer account gets access only to loads RAJO explicitly links.

03

Expand by workflow

Documents, invoices, EDI/API tenders, and richer status history should open in phases after the customer, lane, and data rules are clear.