Home › Guides › Load board vs TMS vs spreadsheets
Load Board, TMS, or Spreadsheets
Most bulk liquid operations run on all three at once — a board to find freight, a system to run it, and a spreadsheet holding the two together.
That is not a failure of discipline. A load board and a TMS answer different questions, neither covers the handoff between them, and the spreadsheet exists because something has to. The real question is not which tool to buy but what the seams between them cost you.
The three operating models
| Spreadsheets + email | General freight tools | Bulk-liquid platform | |
|---|---|---|---|
| Finding freight | Phone and relationships | Load board | Board, inside the same system |
| Running the load | Manual | TMS | Same record throughout |
| Handoff between them | Retyping | Retyping | None — no handoff exists |
| Two products on one load | Extra columns | Often one product per load | Native |
| Several pickups, several BOLs | Extra rows | Usually one document per load | Native, per stop |
| Gross and net | A formula someone wrote | Usually a single quantity | Both, on every line |
| Terminal access rules | In someone's head | Not modelled | Carding drives what a carrier sees |
| Daily rack pricing | Pasted in each morning | Not modelled | Imported from supplier feeds |
| Setup cost | None | Moderate to high | Moderate |
| Breaks down at | More people than you can talk to daily | The first multi-product, multi-drop load | — |
Where spreadsheets are genuinely fine
Worth saying plainly, because most comparisons of this kind will not. A spreadsheet is free, instantly changeable, and understood by everyone you employ. For a small operation running a handful of loads a week with one dispatcher who knows every driver, it is a rational choice, and replacing it with software would be a downgrade.
What a spreadsheet cannot do is be in two places at once. It stops working at the point where more than one person needs the current answer at the same time — which usually arrives before anyone decides to look for a system, and shows up first as two people quoting different numbers to the same customer.
Why general freight tools strain here
Tools built for dry van assume a load is one shipment, of one thing, picked up once and dropped once, whose quantity does not change in transit. Bulk liquid violates all four assumptions routinely:
- A load can carry more than one product, in separate compartments.
- It can be collected at more than one terminal, producing a bill of lading per stop.
- It can deliver to more than one customer — a split load — each with its own ticket and invoice.
- The quantity that arrives differs from the quantity that left, for reasons that are physics rather than error.
None of these is exotic in this trade; they are ordinary Tuesday. When the system cannot hold them, they move into the spreadsheet, and the spreadsheet becomes the real system of record while the software holds an approximation of it.
What the seams actually cost
The expensive part is rarely licence fees. It is the work between systems, and it is invisible because it is nobody's job title:
- Retyping an accepted load into the system that will run it.
- Relaying status by phone and text, then typing it in again.
- Rekeying documents that arrived as photographs.
- Reconciling at month end, because ordered, delivered and invoiced quantities were captured in three different places.
- Chasing the exception — the load whose paperwork never closed, found weeks later.
Each hop is also a place to transpose a digit. A quantity mistyped at the handoff is not caught until the customer disputes the invoice, by which point the driver, the ticket and the truck have all moved on.
How to tell which one you are outgrowing
- Someone's morning starts by copying numbers between two screens.
- The answer to "where is that load?" is a phone call, not a lookup.
- Month end takes days, and finds surprises.
- The spreadsheet has a tab only one person understands.
- A customer knows a delivery went wrong before you do.
Where Energy Connect sits
Energy Connect is the third column: a board and an operating system on one record, built around the way bulk liquid actually moves rather than adapted from general freight. A load carries multiple products, multiple pickups and multiple drops because those are ordinary; gross and net are both kept; terminal carding governs what a carrier can see; rack and index pricing import from supplier feeds.
It is also deliberately not a replacement for your back office. Orders, documents and invoices are exposed over a public API with signed webhooks, so an accepted order can reach the accounting or dispatch system you already run without anyone retyping it — which is the seam this page is about.