PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
OmnistuSTUDIO / SERVICESStart a project

White-label

Load board software, white-labelled for you

Customizable freight load-board software under your branding. Original code, finished under your branding, scoped in writing before any build starts.

What it typically includes

How white-labelling works

Related reading

Scope areas for this kind of build

Overview

The Board Is Only the Front Door

  • Posting and bidding bring carriers in, but dispatch, drivers, settlements and documents are what keep them - which is why a bare load board stops growing at the same size every time.

Adapters Instead of Lock-In

  • Payments, telephony and messaging sit behind interfaces, so you change provider when the rate changes rather than when the contract finally allows it.

white label load board platform - Carrier & Dispatch

  • The carrier surface. Search and filter the board, submit bids and counter-offers, post available trucks, then dispatch the won load to a vehicle and driver with routes, GPS tracking, HOS logs, DOT records, fuel purchases, maintenance and geofence alerts.
  • Try: mike@miketransport.com | password123

Coverage, Negotiation & Carrier Intelligence

  • The margin side. Work uncovered and at-risk loads, search by lane, date, equipment and distance, check hot lanes and rate history, review carrier verification, fleet, ratings and credit, then negotiate through counter-offers and hold the conversation record against the load.
  • Try: broker@chrobinson.com | password123

Governance, KYC, Compliance & Revenue

  • Operator governance. User lifecycle and role management, load intervention, KYC review queues, compliance records, financial overview and invoice ageing, platform analytics, module toggles, pricing plans, SEO surfaces and the audit and activity logs behind every admin action.
  • Try: admin@mxloader.com | password123

Modelled Reference - Freight Marketplace and Carrier TMS Deployment

An illustrative configuration showing how this platform would be set up for a mid-market brokerage. It describes no client engagement, and every figure is a property of the software rather than a result any customer has reported.

Freight Sector Load Board and Carrier TMS Platform

What Is White Label Load Board Software?

It is a finished freight marketplace with a carrier TMS sitting underneath it. Shippers and brokers post freight, carriers find it and bid, and whichever load is won then gets dispatched, tracked, proven and invoiced without ever leaving the system. What it takes off your hands are the genuinely hard parts: a load record that survives multi-stop lanes, a negotiation trail that still holds up months later, and compliance gating that decides who is allowed to haul at all.

More Than A Listings Board

  • The value lives in everything after the match: dispatch, GPS, compliance, documents and invoicing, all against one load record. A listings script hands you search and leaves execution entirely to you.

Not a Rental Platform

  • Full source, the Drizzle schema and the migration path all transfer. No per-seat charge, no waiting on a vendor roadmap, and ordinary PostgreSQL beneath it.

Three First-Class Surfaces

  • The React client, the Flutter application and the operator console are each first-class, all speaking to one Express API, rather than a web app with a wrapper bolted on and called a mobile strategy.

What a Load Board Script Has to Solve

  • Nobody struggles with the search filter. What is hard is a status machine keeping posted, assigned, in transit and delivered honest across four roles simultaneously, a document pipeline that validates what it accepts before anyone leans on a proof of delivery, and an ownership model preventing one carrier from reading another freight. Those are precisely the parts already built.
  • Load posting with multi-stop pickup and delivery legs
  • Bids, multi-round counter-offers and auto-bid rules
  • Carrier TMS with fleet, drivers, HOS, DOT and fuel

Platform Features - Marketplace, TMS, Intelligence, Compliance & AI

Posting And Multi-Stop Legs

  • Equipment, weight, commodity, distance and target rate on the load itself, with PickupLocation and DeliveryLocation child tables holding sequence, dates, times, contacts and instructions beneath it.
  • Passport and bcrypt behind session-cookie auth on web and admin
  • Bearer JWTs for the Flutter client and any external consumer
  • Role middleware at route level across admin, carrier and broker

Searching The Board

  • Filter the live board by lane, date, equipment and distance, with rate history and hot lane context sitting right where the decision gets made.
  • Equipment, weight, commodity, distance and target rate captured on post
  • Sequenced pickup and delivery legs carrying dates and contacts
  • File upload in bulk for desks running real volume

Bidding And Counter-Offers

  • Straight bids alongside multi-round counter-offers, with bid statistics, bookmarking and lost reasons recorded against the load itself rather than in somebody call log.
  • Lane, date, equipment and distance filters across the board
  • Bids submitted and managed, with statistics and bookmarks
  • Counter-offers over several rounds, lost reasons captured

Auto-Bid Rules

  • Rules fire on lane, equipment, bid ceiling, margin and acceptance threshold, and an automation log keeps both the action taken and the reasoning behind it for later review.
  • Available capacity posted by truck and equipment
  • Carrier assigned and the load status moved on
  • Routes dispatched to a named vehicle and driver

Posting Capacity

  • Capacity is posted by equipment type and location, which means a broker holding freight finds a truck as readily as a carrier finds a load.
  • Live maps drawn from the gps_tracking store
  • Geofences configured to alert on arrival and departure
  • Tracking links shareable with parties outside the platform

Dispatch And Routing

  • Winning a load assigns it to a named vehicle and driver through a route record, and that task appears on the driver phone.
  • Fleet records carrying status and current assignment
  • Drivers managed with performance history attached
  • Hours-of-service monitoring beside DOT compliance records

Tracking And Geofences

  • Position tracked live against the assigned vehicle, geofences configured to fire on arrival and departure, and public links so parties outside the platform can follow a load.
  • Fuel purchases tracked and reported through IFTA
  • Maintenance scheduled against full service history
  • Cost visible per vehicle and per route

Carrier TMS

  • One operational backbone covering vehicles, drivers, hours-of-service logs, DOT compliance records, fuel purchases feeding IFTA, maintenance scheduling and speed violations.
  • Benchmarks and history for every lane
  • Alerts on the lanes you choose to watch
  • Hot lane signals and market context

Market Intelligence

  • Lane benchmarks and rate history, alerts you configure per lane, hot lane signals, contract rates, and trihaul evaluation for positioning across multiple legs.
  • Verification status gating who can transact
  • Ratings and reviews held against companies
  • Credit scores on brokers for counterparty risk

Revenue Models - Subscriptions, Fees, Services & Licensing

Income arrives from several directions at once here, and each is modelled separately so that adjusting one lever leaves the others where they were.

Transaction Fees

  • A placement fee per load, or commission on the bid that wins. Since bid and assignment both settle onto the same load record, there is never any ambiguity about what the fee attaches to.

Managed Dispatch Services

  • Brokerage or dispatch run by you, through the admin control plane. The same console that governs the platform can also work the desk on a customer behalf.

Add-On Modules

  • AI coverage, cold chain monitoring, compliance submissions, deeper analytics and additional storage all sold as modules. Because toggles govern them, an add-on is switched on rather than deployed.

White-Label Licensing

  • License the whole platform to partners under their own branding. System configuration, module toggles, brand tokens, pricing plans and SEO surfaces are exactly what make that possible without forking anything.
  • Two of these move the numbers more than the rest: subscription tiers and transaction fees. The first is predictable and recurring, the second grows with whatever volume the board genuinely clears.

Admin Console - Governance, KYC, Compliance & Revenue

This is where the platform is governed rather than simply watched, and it is the surface most freight builds postpone and then never come back to finish.

User Lifecycle

  • Accounts created, edited, suspended and restored across all four roles, with every role change and ban written into the admin activity log.

Load Intervention

  • Inspect any load, correct a bad posting, reassign it or cancel it, and move its status along when the parties cannot settle a lane between themselves.

Compliance Records

  • Review DOT records, hours-of-service exceptions, cold chain logs and regional submissions, and see at a glance which carriers are approaching an expiry.

Financial Overview

  • Revenue, average rate, delivered load counts and invoice ageing across both paid and outstanding, with the underlying invoices reachable without leaving the view.

Platform Analytics

  • Growth in users, activity on loads and bids, message volume and revenue trends, all drawn from the same tables the operational screens read.

Module Toggles

  • Switch capability areas on and off per deployment, which is what makes add-on pricing and white-label configuration workable without branching the codebase.

SEO Surfaces

  • Public pages and metadata managed in-console for operators running this as a branded marketplace with organic acquisition.
  • User lifecycle across shipper, broker, carrier and admin roles
  • Role changes, suspension and restoration
  • Load intervention including reassignment and cancellation

Audit & Activity Logs

  • Two distinct trails: audit_logs holding data mutations with before and after values, admin_activity_log holding administrative actions, each attributable to an actor and an IP address.
  • Compliance records across DOT, HOS and cold chain
  • Financial overview with revenue, average rate and invoice ageing
  • Platform analytics on user growth, load and bid activity

What an engagement can include

What transfers is a complete, deployable platform: application source, the schema beneath it, and the documentation any technical buyer will ask to see. Ownership is outright, with no runtime licence, no per-seat charge and no dependency on what we build next.

Web Application

  • React (version confirmed in writing) in TypeScript on Vite, routed by wouter, server state through TanStack Query, shadcn/ui over Radix primitives, with Tailwind, Framer Motion and Recharts.
  • TypeScript React (version confirmed in writing) client built on Vite
  • Routing via wouter, server state via TanStack Query
  • Radix primitives under shadcn/ui, styled with Tailwind

Express API

  • TypeScript Express API running on Node.js (version confirmed in writing)
  • Role middleware plus ownership checks per object
  • Method, path, status and duration logged on every call

Schema And Migrations

  • Seventy-four PostgreSQL tables modelled in Drizzle ORM, co-validated by drizzle-zod, with the migration metadata required to move the schema forward without breaking it.
  • Drizzle ORM across seventy-four PostgreSQL tables
  • Inserts and updates co-validated by drizzle-zod
  • Metadata supporting safe forward migration

Mobile Application

  • Flutter across 126 screens on iOS and Android
  • State on Riverpod, networking on Dio, routing on go_router
  • Every module at role parity with web

The Operator Console

  • Account lifecycle, load intervention, the KYC queue, compliance records, financial overview, analytics, module toggles, pricing tiers and both audit trails.
  • A control plane covering accounts and KYC
  • Compliance records, finance and analytics together
  • Toggles for modules, pricing tiers and SEO surfaces

The Adapter Layer

  • Payments, calls, voice, email, market rates and regional compliance each sit behind a swappable interface, and each carries a mock so the surface works offline.
  • Payments on Stripe, calls and SMS on Twilio, voice on Whisper
  • Inbound mail over IMAP, outbound through Nodemailer
  • Rate and compliance providers chosen by environment variable

Deployment Stack

  • Vite and esbuild produce one artifact packaged for cPanel, aaPanel or PM2, deployed onto your infrastructure with the environment configuration walked through with you.
  • Helmet headers with CSP alongside a CORS allowlist
  • API rate limited, with tighter ceilings on auth
  • Zod schemas refusing any unknown field

Technical Documentation

  • A PRD and ERD, the schema guide, feature catalogue, API collection, technical dossier, the developer and security handbook, and the VAPT compliance document.
  • Client bundled by Vite, server bundled by esbuild
  • One artifact packaged for cPanel, aaPanel or PM2
  • Configuration by environment variable, no secrets committed

Who Is This White Label Load Board Platform Built For?

Four roles plus an operator plane mean this fits several quite different freight businesses without anybody maintaining a fork.

If your business depends on covering freight quickly, on knowing which carrier is safe to give it to, and on being able to prove afterwards what happened, an owned freight platform becomes a long-term asset rather than a subscription you keep renewing.

Use Cases - Brokerage, Fleet, Regional & White-Label

Which side of the market leads determines what this becomes. A brokerage leans on coverage and carrier intelligence; a carrier leans on dispatch and compliance; a network leans on governance. All three are configuration, not a fork somebody has to maintain.

Take a brokerage off the phone and out of the spreadsheet, so the board, the counter-offer thread and the assignment record stand in for the call log, and the evidence behind a margin outlives the conversation that set it.

Technology options we may propose

React (version confirmed in writing) TypeScript Vite

Node.js (version confirmed in writing) Express 4.21.2

How the Platform Works - Post, Bid, Dispatch, Track & Invoice

A load board looks like a search screen from the outside and runs on a tightly sequenced identity, negotiation, dispatch, compliance and settlement pipeline underneath. Here is the path a load takes from posting to payment.

Load Journey - From Posting to Payment

  • A shipper or broker creates the posting, and the load becomes discoverable the moment it publishes.
  • Equipment, weight, commodity, distance and target rate captured on the load
  • Multi-stop pickup and delivery legs with sequence, dates, times and contacts
  • Bulk upload from file for high-volume desks

How we would approach the architecture

One Load Aggregate

  • Pickup legs, delivery legs, bids, counter-offers, routes, GPS positions, documents and invoices all hang off a single load record, which is what lets a status question be answered without joining external systems.
  • Domain services grouped by marketplace, TMS, payments, compliance, AI, admin and notifications. Boundaries are drawn where a service would later be extracted, without paying distributed-system cost on day one.

One API, Three Surfaces

  • React web, Flutter mobile and the admin console consume the same Express API and the same role model. Nothing in the mobile client talks to a parallel backend.

Ownership Checks Before Logic

  • Route-level role middleware and object-level ownership checks run in auth middleware before any handler executes, which is what closes the IDOR surface on loads, bids, messages and documents.

Validation at the Boundary

  • Strict Zod schemas reject unknown fields outright rather than silently dropping them into a service, which closes the mass-assignment path on every mutation.

Adapters at the Edge

  • Payments, calls, voice, email, market rates and compliance each sit behind an interface with a real and a mock implementation, selected by environment variable at boot.

How we would design for scale

At the edges the architecture stays ordinary; where freight demands something specific it specialises. One deployable artifact that runs on hosting you already have, a relational model indexed around the queries a board genuinely makes, and an adapter layer that contains a slow third party instead of letting it stall a request someone is waiting on.

Deployment That Fits Real Hosting

  • Vite bundles the client, esbuild bundles the server, and the result is one artifact packaged for cPanel, aaPanel or PM2. The commercial consequence matters: you can run this on hosting you already pay for instead of standing up a container platform before a single load has been posted.
  • Single artifact rather than a multi-service deployment
  • Environment-variable configuration with no secrets in source
  • Health and request logging on every API call

Indexed for the Queries That Actually Run

  • Rather than indexing everything uniformly and hoping, the schema guide marks temporal and composite indexes on the paths that take the heaviest traffic: GPS positions, hours-of-service logs, violations, fuel purchases, predictions and nearby-place lookups.
  • Temporal indexes on append-oriented operational histories
  • Composite indexes on the board search paths
  • Drizzle typed queries rather than an opaque ORM layer

Adapter Isolation Under Load

  • Every external service sits behind an interface that also has a mock. A payment provider running slow, a rate API throttling you, or a compliance endpoint timing out is absorbed at the adapter rather than blocking the request a dispatcher is sitting in front of.
  • Real and mock implementations behind one interface
  • Provider selected by environment variable at boot
  • Regional provider swaps without touching domain logic

Integrity Under Concurrency

  • Freight brings real concurrency problems: two carriers bidding the same load, a status change racing a dispatch, a webhook delivered twice. Validation happens at the boundary, ownership is confirmed before any logic runs, and the status machine is written down rather than implied.
  • Explicit status machine across posted, assigned, in transit, delivered and cancelled
  • Strict Zod schemas rejecting unknown fields on every mutation
  • Object-level ownership checks before any state change

Single Deployable Artifact

  • One bundle out of Vite and esbuild, packaged for cPanel, aaPanel or PM2, which is precisely what makes ordinary hosting workable instead of demanding a container platform on day one.

Indexed for the Hot Paths

  • Temporal and composite indexes aimed at GPS positions, hours-of-service logs, violations, fuel purchases and nearby-place lookups, being the queries that grow fastest.

Explicit Status Machine

  • Posted, assigned, in transit, delivered and cancelled are each modelled explicitly, so no load drifts into a state nobody defined when concurrency bites.

Validated at the Boundary

  • Unknown fields are rejected by strict Zod schemas before any value reaches a service, closing off mass assignment across every mutation.

Observable by Default

  • Method, path, status and duration logged on every API call, sitting alongside two audit trails covering data change and administrative change separately.

Security and privacy requirements we can design for

Controls and evidence trails arranged so that an operator pursuing certification already holds the audit logging, access control and change records the assessment will ask to see.

A written PII inventory, personal data reachable only within role scope, and audit trails that turn a subject access or erasure request into a query rather than an excavation.

Encrypted Data

  • HSTS over HTTPS in production, session cookies marked httpOnly with same-site and secure flags set by environment, and passwords hashed with bcrypt.

Secure Auth

  • Passport local sessions with server-side revocation on web and admin, short-lived JWTs for mobile and API consumers, and both paths extensible to MFA or SSO at the middleware layer.

DDoS and Abuse Protection

  • a large number of requests per fifteen minutes across the API, five login attempts per fifteen minutes on auth routes, with Helmet headers and a CORS origin allowlist behind both.

File and Content Validation

  • Every upload checked on extension, MIME type and magic-byte signature, filenames stored as UUIDs, size limits enforced, paths resolved safely on download, and virus-scan status fields waiting for a scanner.
  • Note for Serious Operators: The VAPT document carries an authorization summary endpoint by endpoint, an inventory of Zod schema coverage and a PII inventory. It is deliberately drier than any marketing checklist, and it is precisely the document your own security reviewer will ask for. Better we hand it over before purchase than have it appear midway through a procurement review.

Add-Ons - Telematics, Compliance, Enterprise & Regional

ELD and Telematics Integration

  • GPS tracking and hours-of-service logging are already built. Wiring in a certified ELD provider, so hours arrive automatically instead of being typed, is the integration a regulated fleet will want.

Enterprise Single Sign-On

  • Role middleware is in place and built to extend. Connecting an enterprise identity provider is the step a regulated or internal deployment will need.

Regional Payment Rails

  • Stripe is what is modelled. Adding a market-specific rail plugs into that same payment adapter without touching domain code.

Factoring Workflow

  • Factoring invoices are modelled in both the schema and the admin surface. The full carrier-facing workflow is marked future in the documentation and is scoped as a module.

Building in Logistics & Delivery? We Have the Whole Market Covered.

The white label load board platform is one platform in a complete logistics suite. If your roadmap extends beyond freight brokerage and carrier TMS, these connect naturally.

Digital freight matching with instant pricing and app-first carrier onboarding.

Describe your Load board software

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com

More pages on this build

4 pages describing this proposed build.