Uber Freight TMS

Shipper-focused TMS for transportation procurement, execution, shipment visibility, and freight payment workflows.

About Uber Freight TMS

Uber Freight TMS helps shippers manage transportation procurement, execution, shipment visibility, and carrier-payment workflows. Control Tower provides connected-shipment visibility; Freight Exchange supports procurement and routing-guide workflows; Dock Scheduler supports freight appointments; and predictive pricing, Insights AI, and other capabilities are described in Uber Freight materials. The availability, configuration, and commercial scope of individual modes, integrations, services, dock APIs, and parcel capabilities should be confirmed with Uber Freight. Customer outcomes and performance depend on each shipper’s network and implementation.

Listed capabilities

  • Control Tower shipment visibility and exception monitoring (connected-data coverage varies)
  • Freight Exchange procurement: routing guides, spot auctions, bids, and carrier communication
  • Dock Scheduler appointment booking (confirm current SSC-standard API availability and scope)
  • Carrier-document audit, freight settlement, and payment workflows (confirm financial controls)
  • Routing-guide and contract-rate management (confirm fallback and rule-governance scope)
  • Shipment tracking through connected carrier, API/EDI, and portal data sources (coverage varies)
  • Predictive spot-pricing estimates and quotes (price and capacity are not guaranteed by this listing)
  • Load tendering and capacity procurement (provider, connection, and coverage vary)
  • Parcel TMS/API capabilities (confirm separate module, implementation, and entitlement)
  • Multimodal transportation and visibility (confirm mode, region, and execution scope)

These are catalog-listed capabilities. Confirm current availability and any plan or setup requirements directly with the provider.

Listed integrations

  • ERP, order-management, and warehouse-system integrations (customer-specific configuration)
  • Carrier and transportation-partner connectivity (provider and coverage vary)
  • Uber Freight TMS customer/document APIs (developer access and scope require confirmation)
  • EDI connectivity (exact partners, messages, and mappings require confirmation)
  • Parcel Shipper APIs (confirm separate product and entitlement)

Ask the provider to confirm the supported connection and implementation requirements for your systems.

Browse all TMS (Transportation Management System) solutions

Compare with other solutions

How Uber Freight TMS works in the operation

Transportation Management Systems capabilities to compare with your workflows.

Planning and multimodal execution

How transportation demand moves through procurement and execution in Uber Freight TMS.

  • Routing, carrier selection, procurement, and mode decisions (native): Uber Freight describes TMS capabilities for optimizing routing, carrier selection, procurement, and mode utilization with automation and data-driven insights.

    Condition: The public page does not enumerate every mode, solver constraint, planning limit, or implementation boundary.

  • Detailed replan and appointment governance (not verified): The reviewed public material does not provide enough detail to verify replan triggers, appointment constraints, approvals, or decision audit behavior; this is not a conclusion that the product lacks them.

Questions to test in a demo

  • Plan a shipment across applicable modes and show routing, carrier, procurement, cost, service, and capacity decisions.
  • Miss an appointment and demonstrate replan timing, approvals, notifications, downstream execution, and audit history.

Carrier, rate, and tender management

How Uber Freight TMS procures capacity and converts awards into execution.

  • End-to-end procurement and carrier management (native): Uber Freight describes TMS coverage from procurement through execution and carrier-management workflows for shippers.

    Condition: The public material does not specify bid rounds, award splits, acceptance windows, fallback rules, or rate-card limits.

  • Tender fallback and rate governance (not verified): The reviewed pages do not provide enough detail to verify tender rejection, timeout fallback, accessorial configuration, or effective-dated rate governance; this is not a conclusion that the product lacks them.

Questions to test in a demo

  • Run a procurement event through bid, award, carrier acceptance, rejection, fallback, and execution with a complete event log.
  • Show contract, spot, fuel, and accessorial rates, including expiration, precedence, approvals, and audit history.

Shipment visibility and exception handling

How operators monitor freight and respond to disruptions.

  • Shipment, carrier, and performance visibility (native): Uber Freight describes real-time shipment visibility, carrier visibility, foresight, control, and transportation performance reporting in one platform.

    Condition: Coverage, event latency, ETA methodology, and data-source responsibilities are not specified on the reviewed page.

  • Predictive exception response (not verified): The reviewed public material does not provide enough detail to verify exception taxonomies, escalation timers, predictive accuracy, or automated remediation; this is not a conclusion that the product lacks them.

Questions to test in a demo

  • Trace a shipment from tender to delivery and show source timestamps, ETA confidence, carrier status, performance reporting, and missing-signal behavior.
  • Create a late or disrupted shipment and demonstrate alerting, ownership, escalation, customer communication, replan, and audit history.

Freight audit and order-to-cash

How Uber Freight TMS connects transportation payments with financial controls.

  • Carrier document audit and payment (native): Uber Freight documents carrier document audits and payment workflows intended to reduce missing paperwork, mischarged late fees, overcharges, and duplicate invoices.

    Condition: Public materials do not specify matching dimensions, tolerances, dispute handling, payment rails, tax, or country coverage.

  • Customer billing and cash application (not verified): The reviewed sources verify carrier-side audit and payment, but do not provide enough detail to verify customer billing, receivables, collections, or cash application; this is not a conclusion that the product lacks them.

Questions to test in a demo

  • Submit carrier documents with duplicate, accessorial, late-fee, and overcharge scenarios and show audit rules, exception, approval, dispute, and payment.
  • Identify which order-to-cash steps beyond carrier payment are native, managed, integrated, or outside the reviewed TMS scope.

Configuration and connectivity

How Uber Freight TMS connects transportation partners and enterprise systems.

  • Transportation network and partner connectivity (native): Uber Freight describes a connected transportation network and a platform that brings procurement, execution, visibility, payments, and insights together for shippers and logistics partners.

    Condition: The reviewed public pages do not provide a complete API catalog, authentication model, throughput limit, or connector implementation plan.

  • Detailed self-service rule administration (not verified): The reviewed material does not provide enough detail to verify no-code administration of rates, tenders, alerts, roles, environments, testing, versioning, or rollback; this is not a conclusion that the product lacks them.

Questions to test in a demo

  • Connect the ERP, WMS, carriers, brokers, and visibility sources used by the operation and show mappings, retries, monitoring, replay, and promotion.
  • Change a tender, payment, or exception rule and show permissions, test results, effective dating, audit history, and rollback.

Before you choose: Confirm which capabilities apply to your plan and setup, and ask about any listed conditions.