Nuance Infotech
Logistics

Roadrunner Customer Website

Building a secure self-service portal where Roadrunner Freight customers track shipments, get freight quotes, create a Bill of Lading and run account reports in one place, connected to Roadrunner's rating, tracking, BOL and customer portal systems.

Client
Roadrunner Freight
Industry
Logistics / LTL freight
Region
USA and Canada
Users
Guests, logged-in customers, linked customer accounts
Stack
Next.js 16, React 19, TypeScript, Tailwind CSS 4, Azure
Jump to the result

01Primary Objective

Primary Objective

Give Roadrunner customers one website where they can track, quote, book (Bill of Lading) and report online at any time, so everyday shipping tasks no longer need a phone call or an email.

02Project Details

Project Details

User type What they can do
Guest Track shipments, view proof of delivery, get LTL and volume quotes, view maps and documents, request an account
Logged-in customer Everything a guest can do, plus dashboard, Bill of Lading, BOL management, reports, all shipment documents, notifications and account pricing
Customer account The accounts linked to a login, used in quotes, BOLs, reports and saved data

03Executive Summary

Executive Summary

Roadrunner customers needed a modern, self-service way to handle daily shipping tasks. We built a Next.js customer website that connects securely to Roadrunner’s SOAP and REST services and customer portal API, turning complex freight operations into simple guided screens.

What changed

  • Phone and email requests to self-service: track, quote, book and report online 24/7.
  • One-by-one tracking to bulk tracking: up to 20 PRO numbers with documents and history in one view.
  • Re-typing details to quote-to-BOL: saved addresses and commodities pre-fill the Bill of Lading.
  • Generic pricing to account pricing: quotes and reports follow the customer’s own accounts.

04The Challenge

The Challenge

Freight customers handle many shipments, documents and accounts every day. Doing this through calls and emails is slow for customers and costly for the carrier.

Operational pain

  • Manual requests: quotes, tracking updates and documents requested by phone or email.
  • Repeated data entry: shipper, consignee and commodity details typed again for every BOL.
  • No single view: status, proof of delivery, invoices and history in different places.
  • Reporting effort: account reports prepared and sent manually.

Technical pain

  • Mixed backends: SOAP rating and transit services alongside REST tracking, quote and BOL APIs.
  • Credential security: service logins and API keys must never reach the browser.
  • Complex freight rules: freight class, density, accessorials, insurance limits and dates.
  • Account-based data: pricing, reports and saved data scoped to each customer’s accounts.

05Goals and Success Criteria

Goals and Success Criteria

Business goals

  • Self-service tracking, quoting, BOL creation and reporting.
  • Guided forms that reduce errors in quotes and BOLs.
  • Account-based pricing and reports for logged-in customers.
  • Useful public tools for guests: tracking, quotes, maps and documents.

Technical goals

  • Server-side API layer that keeps all credentials on the server.
  • Unified handling of SOAP and REST services.
  • Strong form validation for freight business rules.
  • Automated build and deployment to Dev, UAT and Production.

06Solution Overview

Solution Overview

The website is built with Next.js 16 (App Router) and React 19. The browser only calls the website’s own /api routes; the server then adds the right login or token and calls Roadrunner web services or the customer portal API. Responses are turned into simple screens and clear messages.

Roadrunner architecture ยท browser, Next.js app, server API layer, 3 backend groups
Roadrunner architecture ยท browser, Next.js app, server API layer, 3 backend groups

Every request passes through the server-side /api layer, so service logins and API keys never reach the browser.

How it works

  • Browse: the customer uses the website in the browser.
  • Request: pages call the website’s own /api routes.
  • Secure call: the server adds the right login or token and calls Roadrunner services or the portal API.
  • Respond: answers are turned into simple screens and clear messages.
  • Protect: private pages such as the dashboard, reports and profile open only after login.

07The product, live

The product, live

Screenshots of the live product, taken on 3 November 2026.

08Product Modules Delivered

Product Modules Delivered

23 modules grouped into six areas, covering every common customer task.

Area Modules What it does
Quoting 5 Step-by-step LTL quote with transit days, Smart Guarantee and estimated total; Volume Spot Quote; quote cart with printable receipt; transit time tool; density calculator
Shipment Tracking 3 Track up to 20 PRO numbers with status, map, timeline and signature; download POD, BOL, invoice and inspection images; email and text notifications
Bill of Lading 2 Four-step BOL form with instant PDF; start a BOL from a quote; saved addresses, commodities and BOL history
Reports 2 8 account reports (Aging, BOL History, Consignee/Shipper Status and more) filtered by account and date; scheduled email delivery
Account and Security 5 Login/logout, account request, password reset, linked customer accounts, profile and notification preferences
Dashboard and Information 6 Dashboard with shipment summary and quick actions; map of 41 service centers; ZIP-based center search; label maker; document download center

09Backend Services

Backend Services

Service Used for
RateQuote (SOAP) Standard LTL rates, with account pricing for logged-in customers
Transit Time (SOAP) Transit business days
Spot Quote V2 (REST) Volume spot rates and the accessorial list
Tracking API (REST) Shipment data and document images
BOL API (REST) Creates the BOL and returns the PDF
Customer Portal API Auth, lookups, reports, subscriptions, notifications, address book and commodities
OpenStreetMap / OpenFreeMap Map tiles and city locations for the shipment map

10Key Business Rules

Key Business Rules

Rule Details
Volume shipment 12+ linear feet counts as volume, insured at $1 per lb up to $100,000
Insurance Standard LTL includes $1 to $10 per lb by freight class, up to $50,000
Dates Pickup date cannot be in the past; BOL ship date must be within 31 days
Dimensions Cubic feet = length ร— width ร— height (inches) รท 1,728
Accessorials Chosen from Roadrunner’s live list; a BOL allows up to 5
Delivery dates Estimated dates skip weekends and carrier holidays
Accounts Reports and saved data are limited to the customer’s own accounts

11Security, Privacy and Performance

Security, Privacy and Performance

  • Server-side API layer: service logins and API keys never reach the browser.
  • Protected routes: dashboard, reports and profile open only after login.
  • Account scoping: customers only see data for their own linked accounts.
  • Validated input: Formik and Yup enforce freight rules before any request is sent.
  • Fast UI: Next.js App Router with Tailwind CSS 4 and shadcn components.
  • Interactive maps: Leaflet with MapLibre GL for shipment routes.

12Delivery Process

Delivery Process

  • Module-by-module delivery across quoting, tracking, BOL and reports.
  • Separate Dev, UAT and Production environments.
  • CI/CD with Azure Pipelines to Azure App Service (Node.js 22).
  • Automated tests with the Node.js test runner; code quality enforced with ESLint 9 and TypeScript 5.

13Outcomes and Business Impact

Outcomes and Business Impact

  • Self-service: customers track, quote, book and report online at any time.
  • Faster tracking: many shipments, documents and history in one view.
  • Easier quoting and booking: guided forms, saved addresses and quote-to-BOL.
  • Account-based experience: pricing and reports follow the customer’s own accounts.

14Technology Stack

Technology Stack

Area Technology
Framework Next.js 16.2.1 (App Router)
UI and language React 19.2.4, TypeScript 5
Styling and components Tailwind CSS 4, shadcn with Base UI, lucide-react icons
Forms and validation Formik 2.4, Yup 1.7
API and SOAP Axios 1.15, fetch, fast-xml-parser 5.8
Maps and messages Leaflet 1.9 with MapLibre GL 5.24, Sonner toasts
Testing and quality Node.js test runner, ESLint 9
Hosting Azure App Service, Node.js 22, Azure Pipelines

15Lessons Learned and Best Practices

Lessons Learned and Best Practices

  • Keep secrets on the server: a single /api layer hides every credential and makes SOAP and REST look the same to the frontend.
  • Encode business rules in the form: validation catches freight-rule errors before submit, so fewer quotes and BOLs need correcting.
  • Reuse data across journeys: quote-to-BOL, saved addresses and commodities remove duplicate typing.
  • Automate the release path: Dev, UAT and Production with Azure Pipelines, tests and linting on every build.

Result

What changed.

23 modules

Across quoting, tracking, BOL, reports, account and dashboard

20 shipments at once

Track up to 20 PRO numbers in a single search

8 account reports

With scheduled email delivery, daily to yearly

Dev, UAT, Production

Automated deployments with Azure Pipelines

Technology

The stack, for the engineers.

Core stack
  • Next.js 16.2.1 (App Router)
  • React 19.2.4
  • TypeScript 5
  • Tailwind CSS 4
  • shadcn with Base UI
  • lucide-react icons
  • Formik 2.4
  • Yup 1.7
  • Axios 1.15
  • fetch
  • fast-xml-parser 5.8
  • Leaflet 1.9 with MapLibre GL 5.24
  • Sonner toasts
  • Node.js test runner
  • ESLint 9
  • Azure App Service
  • Node.js 22
  • Azure Pipelines

Start a conversation

Discuss a similar project.

Bring the workflow, the system or the feature. An engineer reads every message and replies with a suggested first step, usually a small fixed-price assessment rather than a sales deck.

  • NDA before you share a brief, a repo or a client name
  • Your first call is with a senior engineer, not a salesperson
  • A realistic plan and an honest cost range, whether or not you build with us

info@nuanceinfotech.com  ·  +91 99070 77806  ·  WhatsApp us

Tell us about it

NDA on request

One workflow is enough. We’ll reply with what a first step looks like.

Used only to reply to you. No marketing sequence, no data sold.