A Field Guide for Fuel Carriers

The Re-Keying
Tax

What disconnected TMS systems really cost a fuel carrier and how to connect them so loads, BOLs, and compliance data move on their own.

MANIFOLD  ·  BUILT BY RIYEX
2026 EDITION  ·  PG 01
02 / 10
Contents

What's
Inside.

01The Re-Keying Tax03 02Where the Data Leaks04 03What Good Integration Looks Like05 04Build, Buy, or Bolt-On06 05What Changes When Systems Talk07 06Where to Start08 07One Layer. Every System.09
The Re-Keying Tax
The Stakes

Your systems don't talk.
Your people pay for it.

Most fuel carriers run two to five systems (dispatch, billing, compliance, telematics) that don't share data. So people do. Every load, BOL, and status update gets re-keyed by hand from one screen to the next. That handoff is where the money quietly leaves the building.

$12.9M Average annual cost of poor data quality to an organization1
1–3 hrs Per day the average worker spends just moving data between systems2
$90.89 Hourly cost to run a truck: what every hour a load waits on data is worth3

It's not a staffing problem.

Re-keying feels like a labor cost, so carriers solve it by hiring. But the moment someone types a tender into a second system, you've created two versions of the truth and a roughly 1-in-100 chance the copy is wrong.4 Hiring doesn't fix the architecture. It just adds more people to keep the copies in sync.

The errors don't stay small.

A fat-fingered quantity, a transposed BOL number, a load assigned to a driver who's already out of hours. Each one becomes a phone call, a delayed delivery, or a billing dispute downstream. The cost compounds far past the minute it took to mistype.

1  Gartner, “How to Improve Your Data Quality,” 2021. Average annual cost of poor data quality.

2  Zapier, “State of Business Automation Report.” 76% of workers spend 1–3 hrs/day moving data between systems.

3  American Transportation Research Institute, “Operational Costs of Trucking” (2024 data); $90.89/hr.

4  Keyed-entry error rates cluster near ~1%; JAMIA (2019) measured ~2.8% on complex records.

manifold.riyex.com03
The Re-Keying Tax
The Map

Where the Data Leaks.

Five handoffs where a fuel carrier loses data between systems: every one of them re-keyed by a person today.

01

The same load, typed three times

A tender lands in dispatch. Someone keys it into billing. Someone keys it again into compliance. Three systems, three copies, three chances to get it wrong. And none of them update when the load changes.

02

The verified BOL never reaches the load

The digital BOL lives in DTN, the system of record for fuel BOLs, but it never lands on the matching load in your TMS. Billing, audit, and reconciliation teams are left working without the verified document they can trust.

03

Hours and inspections that arrive too late

Driver HOS, DVIRs, and inspection records live in telematics but not in dispatch, so you assign a run to a driver who's already out of hours. Falsified or missing records carry penalties up to $15,846 each.1

04

Tolls nobody reconciles

Toll charges flow in from one vendor; the route the driver was supposed to run lives in another. Nobody lines them up, so off-route tolls (and the revenue they represent) quietly disappear.

05

Compliance trapped in a state portal

Tank registration and environmental data (TCEQ numbers and the like) sit in a government portal someone checks by hand, instead of on the site record in the TMS where dispatch and billing actually work.

1  FMCSA Penalty Schedule (49 CFR Part 386), 2025; HOS violations $1,000–$16,000 per violation.

manifold.riyex.com04
The Re-Keying Tax
The Standard

What good integration looks like.

Connecting two systems isn't a one-time script you run and forget. Real integration has five properties, and most homegrown fixes have one or two of them.

01Triggered on change
Data moves the moment a load, tender, or status changes. Not in a nightly batch that's already stale by the time dispatch reads it. The trigger is the event, not the clock.
02Mapped field by field
A tender in one system rarely matches the next. Good integration maps each field deliberately and transforms the mismatches (units, status codes, date formats) instead of hoping they line up.
03Idempotent & retried
The same event syncs exactly once, even if it fires twice. Transient failures retry on their own without creating duplicate loads or double-billed orders. The difference between a self-healing system and a 2 a.m. phone call.
04Observable
Every sync is visible. You can replay any run and see the exact field that failed, not just a generic “sync error” discovered three days later when billing doesn't reconcile.
05Auditable
An operations-grade log of every field change, end to end. When a customer and your billing team disagree about what was delivered, the record settles it in seconds.
manifold.riyex.com05
The Re-Keying Tax
Three Paths

Build, buy, or bolt-on.

Three ways to connect your stack. Only one is built for how fuel carriers actually move data. The gap rarely shows on day one; it shows in year two, when a vendor changes an API and everything quietly breaks. Across industries, the average company has integrated just 28% of its applications.1

Build in-houseMost control
Generic iPaaSFast, generic
Purpose-builtBuilt for carriers
Speed to live
Months to build
Quick to stand up
Live in weeks
Speaks TMS natively
Only if you build it
Rebuilt from scratch
Tenders & BOLs built in
Connector upkeep
Yours, 15–25%/yr2
You wire & watch
Maintained for you
Console & audit trail
Build it yourself
Not dispatch-grade
Included
Built in Possible, on you Works against you

You don't need AI to move a load.

Reliable sync is a solved engineering problem: deterministic, observable, testable. Point AI at the genuinely fuzzy work (reading a smudged BOL, flagging an odd exception) and let plain engineering handle the sync itself, which is most of the job. A model that's right 95% of the time is a liability on a load that has to be right every time.

1  MuleSoft, “2024 Connectivity Benchmark Report” (Salesforce / Vanson Bourne): avg. 900+ apps per enterprise, 28% integrated; 81% say data silos hinder them.

2  Long-standing software-engineering benchmark: annual maintenance runs 15–25% of original build cost.

manifold.riyex.com06
The Re-Keying Tax
The Outcomes

What changes when systems talk.

Manifold in production

When data moves on its own, the daily firefights stop being daily. The figures below are from fuel carriers running Manifold today. Product performance, not an industry benchmark.1

2.4M Loads synced last quarter

Volume stops being a headcount problem

That's 2.4 million loads that moved between systems without anyone re-typing them. The work scales without the typing pool scaling alongside it.

99.98% Sync uptime, rolling 90 days

The integration is boring on purpose

Boring is the goal. When sync just works, dispatch stops keeping a side spreadsheet “just in case” and starts trusting the screen in front of them.

1.8s Median end-to-end latency

Near real-time, not next morning

A change in one system shows up in the others in under two seconds. Fast enough that nobody has to call and ask whether it made it across.

11+ TMS connectors maintained

Someone else owns the breakage

When a vendor changes an API, the connector gets fixed upstream. Your team never opens the ticket, and the load keeps moving.

1  Manifold platform metrics: trailing-quarter load volume; rolling-90-day uptime and latency.

manifold.riyex.com07
The Re-Keying Tax
The Plan

Where to Start.

You don't need a platform project to stop the bleeding. You need to fix one handoff well, then the next.

01

Map every handoff

Before connecting anything, list every system you run and every place a human re-keys data from one into another. That list, usually shorter than people expect, is your integration backlog, ranked by how often each handoff happens.

02

Fix the busiest handoff first

Don't boil the ocean. Take the single load or record path that gets re-typed most and connect just that one. One integration (live, observable, trusted) beats a six-month project that connects everything at once and nothing well.

03

Make it observable before you make it bigger

You can't scale what you can't see. Get logging, retry, and an audit trail working on the first connection before you add the second. Want a map of your own integration gaps? Manifold's team will walk your stack and show you exactly where data is leaking, no commitment. Start at manifold.riyex.com.

manifold.riyex.com08
The Re-Keying Tax
Manifold

One layer.
Every system.

Manifold is the integration layer that keeps fuel moving. It connects your TMS platforms so your team stops re-entering data and starts running the operation. Built by Riyex: human-centered engineering that adds the connective tissue between your systems instead of ripping them out.

Built for fuel carriers

Already understands tenders, BOLs, manifests, and dispatch. No generic platform to teach.

Maintained for you

We watch every connector and ship updates when vendor APIs drift. Your team never opens the ticket.

Observable by design

Every sync is visible, replayable, and auditable: the operator console dispatch actually trusts.

manifold.riyex.com09
The Close

Stop re-entering.
Start moving.

Manifold connects your TMS platforms so loads, BOLs, and compliance data move between them automatically. When you're ready to see where data is leaking in your own stack, we'll walk it with you.

Get started

manifold.riyex.com

MANIFOLD · BUILT BY RIYEX · 2026