White Label Load Board Software · Features

White Label Load Board Software Features: Past the Match

Most board software stops working the moment a carrier wins a load. This is the platform underneath the load board clones, and it keeps going: the booked load is dispatched to a named truck and driver, followed on GPS, closed with a proof of delivery and billed from the same record. A carrier TMS and broker-side intelligence sit beneath it. Below is everything that ships, grouped by the person who uses it.

Request a Live Demo →See Pricing
Full source yours to change
126 native mobile screens
6 days to go live
Your brand
No supplier name shown
One Load, Start to Finish
01Posted, with every stop in order
02Bid, then rounds of counter-offers
03Won and handed to a truck and driver
04Followed on the map, geofence alerts
05Proof of delivery checked and stored
06Invoiced against the same load
74
Database Tables in the Schema
280+
REST Endpoints Documented
126
Flutter Screens Included
4
Member and Operator Logins
By Role

What Each Person Gets

Shippers, carriers, dispatchers, fleet managers, brokers and the operator each work in a screen shaped for their job, yet all of them read and write one shared load record through a single API.

01

The Shipper

Creates a posting with locations, dates, equipment, weight, commodity, distance and a target rate, then adds extra pickup and delivery legs. Each leg is its own record with a sequence number, times, a contact and instructions. Desks with heavy volume can bring loads in by bulk file upload, and incoming bids can be compared against carrier trust signals before anyone is chosen.

02

The Carrier

Works the live board with lane, date, equipment and distance filters, places bids, answers counter-offers and bookmarks loads worth returning to. Available trucks can be posted too, so capacity is found as easily as freight. Rate history and hot lane signals appear where the accept-or-decline choice is made.

03

The Dispatcher

Turns a won load into a route with a named vehicle and driver, which then lands as a task on the driver's phone. The map shows live positions and geofences fire on arrival and departure. A public tracking link lets a consignee follow the freight without creating an account, so the status call rarely needs to be made.

04

The Fleet Manager

Keeps vehicle and driver records, hours-of-service logs, DOT compliance records and expiry dates for insurance, licences, medicals and inspections. Fuel purchases feed IFTA reporting, maintenance is scheduled against service history, and speed violations are logged per vehicle. Cost is visible by truck and by route.

05

The Broker

Works uncovered and at-risk loads and searches by lane, date, equipment and distance. Before tendering, the same screen shows carrier verification status, fleet, ratings and reviews, broker credit scores and preferred or blocked lists. Counter-offers are negotiated in place and the conversation stays attached to the load.

06

The Operator

Governs the whole marketplace from an admin console: accounts and roles, load intervention, the KYC review queue, compliance records, the financial overview with invoice ageing, analytics, module toggles, pricing plans and public SEO pages. Every administrative action is written to an audit trail.

Members use a React 18 web client or the Flutter app, and operators use the console. All three surfaces call the same Express API, so nothing on the phone runs against a separate backend.

Compare

Rented Platform vs One-Time Script vs Miracuves Platform

Three ways to get load board software, compared on the points that decide whether freight keeps moving once the novelty wears off.

What decides itRented or hosted platformOne-time scriptMiracuves platform
How you payA recurring fee, so cost continues for as long as the board runsA single purchase, roughly $250 to $1,500 on the open market$4,899 once, with no per-seat fee
Life after the matchDepends on the plan and on what the vendor chooses to buildOften listings and bidding, with execution left to youDispatch, GPS, documents and invoicing on the load record
MobileWhatever the vendor ships, on the vendor's scheduleCheaper tiers often ship web-view apps rather than native onesNative Flutter app, 126 screens, same API as the web client
Source codeTypically stays with the vendorSome vendors withhold source from every published tierThe full monorepo transfers to you
Your brandFrequently your logo on someone else's productVaries by script and by tierBrand tokens and toggles, no supplier name in the product or the app stores
Carrier operationsFrequently a separate product with a separate billRarely includedA carrier TMS with HOS, DOT, fuel and maintenance built in
Changing a providerLimited to what the vendor has connectedOften wired straight into the codeAdapters with mock fallbacks, chosen by environment variable
Operator toolingWhatever the plan exposesCommonly thin or absentKYC queue, compliance, finance, analytics, toggles and two audit trails

Hosting, a CDN and licensing are often folded into a subscription, so a rented platform is not a bad fit for every buyer. The honest comparison is a one-time software cost against a recurring fee, and we make no claim about the total cost of getting to launch.

End to End

A Load, Traced From Post to Payment

Follow a single load through the platform and see what gets written down at each stage, all of it on the same record.

01

A posting that matches the real freight

The shipper records equipment, weight, commodity, distance and a target rate. Stops beyond the first pickup and last delivery are stored as ordered child records with their own dates, contacts and instructions, so a run with three stops is three stops in the database, not a paragraph in a notes box.

02

Search that carriers can steer

The board filters on lane, date, equipment and distance. Lane benchmarks, rate history and hot lane signals are placed beside the posting, giving a carrier something firmer than instinct to weigh against the offered rate.

03

Haggling that leaves a paper trail

A carrier can bid outright or enter a counter-offer exchange lasting several rounds. Bid statistics, bookmarks and lost reasons are stored against the load, so months later the desk can still see what was proposed, who turned it down and why.

04

Trust checked before freight is handed over

Verification status, fleet size, reviews and ratings, and broker credit scores are visible at the moment of tender. Transacting can be gated on verification, which turns carrier vetting from a memory exercise into a screen anyone on the desk can open.

05

Assignment that moves the status

Once a bid is accepted the load shifts from posted to assigned, and a route ties it to one vehicle and one driver. Posted, assigned, in transit, delivered and cancelled are defined states, which means no load can quietly sit in a status nobody named.

06

Movement that outsiders can watch

GPS positions plot on the map and geofences raise an alert on arrival and departure. A public tracking link can be shared with anyone who needs to follow the shipment, and speed violations are recorded against the assigned vehicle.

07

Delivery that ends in an invoice

The driver's proof of delivery goes through checks on extension, MIME type and magic bytes before it is accepted. An invoice is then raised on the same load, and invoice ageing, paid and outstanding, appears in the operator's financial overview.

Deliberate

Why Each Module Is in the Package

Every item here is present because a freight marketplace breaks without it, and none is there to pad a feature list.

ModuleThe reason it ships
Sequenced stop recordsFreight rarely runs between exactly two points. Without ordered stops, a multi-drop cannot be dispatched, tracked leg by leg or billed correctly.
Counter-offer roundsPrices in this industry are settled by negotiation. When the rounds live on the load, your rate history stops depending on who remembers a call.
Lost reasonsA refusal with a recorded cause tells the desk which lanes and rates to rethink. A bare refusal gives it nothing to learn from.
Hours-of-service monitoringRegulated carriers track driving hours as a matter of course. If the platform ignores them, the carrier keeps a second system open alongside yours.
Fuel purchases and IFTAFuel tax reporting comes round on a schedule. Recording purchases when they happen beats rebuilding a quarter from receipts.
GeofencesAutomatic arrival and departure alerts make tracking an event stream, not a dot on a map that someone has to keep watching.
Public tracking linksThe people asking where the freight is are often the ones with no login. A link answers them without adding to the dispatcher's inbox.
Upload validationA proof of delivery can decide a payment dispute. Checking extension, MIME type and magic bytes, and storing files under UUID names, keeps that evidence trustworthy.
Broker credit scoresCarriers avoid brokers who pay late. Showing that score at the point of tender helps you keep good carriers on your board.

Alongside these, the console holds the KYC review queue, company verification, ratings and reviews, and compliance records.

Stack

What the Features Are Built On

Nothing exotic, which is the point: your own engineers will recognize every layer when the codebase becomes theirs.

SchemaSeventy-four PostgreSQL tables defined in Drizzle ORM, including loads with their pickup and delivery children, bids, counter-offers, vehicles, drivers, routes, HOS logs, compliance records, fuel, maintenance and invoices, with migration metadata for moving forward safely.
Web clientReact 18 in TypeScript on Vite, using wouter for routing, TanStack Query for server state and shadcn/ui over Radix primitives, styled with Tailwind.
APITypeScript on Node.js 20 with more than 280 REST endpoints. Each call passes role middleware and ownership checks, and every request is logged with method, path, status and duration.
Access controlSessions through Passport and bcrypt for web and admin, Bearer JWTs for the Flutter app and outside consumers, and object-level ownership checks so a valid session cannot open another company's loads, bids, messages or documents.
MobileA native Flutter application with 126 screens built on Riverpod, Dio and go_router, reading the same API and role model as the web client.
IntegrationsPayments, calls, voice, email, market rates and regional compliance each sit behind an adapter with a mock beside it. Providers are chosen by environment variable at boot, and the platform runs offline without any of them.

Why the adapters decide who is in control

Freight contracts get renegotiated: a rate provider changes terms, a telematics vendor is dropped, a payment rail is added for a new market. When any of those is welded into domain code, leaving it means a rewrite. Behind an adapter with a mock, the change is a setting, and the demo you watch before buying runs without a single external account attached.

74PostgreSQL tables
280+REST endpoints
126Flutter screens
$4,899One-time price

Because every adapter carries a mock, your first deployment does not have to wait on a vendor contract to be tested end to end.

Honest Readiness

What Is Not Included in the Base Package

These limits are written down now, before purchase, so they cannot turn into surprises later.

Software, not freight, data or authority

No freight, carrier data or rate feeds are supplied. Loads, carriers and shippers are yours to bring, and no third-party rate data ships inside the source.

Your authority is your own. Holding a broker authority, a surety bond and insurance, checking each carrier's operating authority, and meeting the transport rules of every market you serve remain your responsibility. We supply software, and not the authority to broker loads.

Every outside provider needs your account. Payments, calls and SMS, voice transcription, email, market rates and compliance feeds all run on credentials you hold. The adapters and mocks are built, but live data arrives only after you sign with the provider. A market rate feed in particular is your own commercial agreement.

ELD and telematics links are add-ons. GPS tracking and hours-of-service logging are already built. Bringing hours in automatically from a certified ELD provider is separate integration work.

Some hardening and workflows are scoped, not shipped. Immutable audit storage, IP allowlisting on admin endpoints, single sign-on with an enterprise identity provider, a warehouse feed for analytics, EDI translation for partners and the carrier-facing factoring workflow are quoted separately. The upload virus-scan status field is present, but no scanner ships with it.

What is built is real and demonstrable: role middleware on the routes, ownership checks on each object, strict Zod schemas that reject unknown fields, rate limiting, and validated uploads.

Provider

Compare who you could buy this from

Rented platforms, script vendors, custom agencies and Miracuves side by side, with the questions worth asking each of them, a six-step delivery plan and a modelled reference deployment for a mid-market brokerage - on the Provider page.

See the comparison →
FAQ

Frequently Asked Questions

What does the platform cover beyond a listings board?
A board is where a load is posted, searched and bid on. The rest of the lifecycle is included as well: assignment to a named vehicle and driver, GPS tracking with geofences, document upload, and an invoice raised on the same record. Beneath that sits a carrier TMS for fleet, drivers, HOS, DOT records, fuel and maintenance, plus broker-side intelligence and an operator console.
How does it store loads with several stops?
Pickups and deliveries are separate child records attached to the load, each with a sequence number, dates, times, contacts and instructions. Because the order is data rather than text, the platform can filter, dispatch and invoice a multi-stop run correctly, which two address fields and a comments box cannot support.
Will market rate data come with the build?
No. A market rate adapter is included, but it stays inactive until you add credentials from a provider you have signed with, and no third-party rate data ships in the source. What works from day one is rate history and hot lane context built from your own platform activity.
Do the freight and the carriers come with it?
No. The platform supplies the software and nothing else: no loads, no carrier records and no rate feeds. Building both sides of the marketplace is your work, and it is worth planning for early, since a board without freight or without carriers attracts neither.
How much of it can carry our own branding?
Effectively all of it. Brand tokens, CSS custom properties, module toggles, pricing plans and the public SEO pages are configured per deployment, and no supplier name appears in the product or the app stores. Because these are settings and not code branches, nobody has to maintain a fork to keep your look.
Is the mobile app a wrapped website?
No. It is a native Flutter application with 126 screens, built on Riverpod, Dio and go_router, and it calls the same REST API and follows the same role rules as the web client. A milestone a driver checks in on the phone therefore shows up in the dispatcher's browser with no second integration.

Watch a load travel the whole lane

Ask for the demo and we will post a multi-stop load, run a counter-offer, assign it to a driver, trigger a geofence alert and raise the invoice while you watch.

Explore

Explore White Label Load Board Software

Own the freight platform, not a seat on someone else's

Go live in six working days with the board, the carrier TMS, broker intelligence and the operator console, adapters aimed at providers you pick, and the complete source running on your own infrastructure.

Talk to Us →
Miracuves · White Label Load Board Software Feature set, stack and scope limits cross-verified against the hub, 2026-09-29
Disclaimer

Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by DAT, Truckstop, or any other load board or freight technology provider.

About this category

“White label load board software” describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.

Who built this

The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party load board website or application.

Authority and compliance are yours

No freight, carrier data or rate feeds are supplied with the platform. Holding your own broker authority, surety bond and insurance, verifying carrier operating authority, and meeting the transport regulations of every market you operate in are your responsibility. We supply software, not authority to broker loads. All third-party names and marks are the property of their respective owners.