Retire the spreadsheet your operation actually runs on.
The car-tracking sheet. The paper switch list. The inspection binder. The inventory workbook. The dispatch board. The invoice somebody rebuilds by hand every month. Rebulk replaces them with one operating record, one sheet at a time.
Why it happens
Nobody decided to run the terminal on Excel
Every spreadsheet in a rail or bulk operation exists for a good reason. That is exactly why they are so hard to get rid of.
The spreadsheet worked
It started as one person's tracking sheet and became the system of record because it was faster and more flexible than anything on offer. Nobody chose it. It won.
Software was built for warehouses, not terminals
Generic systems have no concept of a railcar, a spot, a free-time clock, or a customer's tons sitting on your ground. The workarounds have to live somewhere, and they live in Excel.
Each new system replaced one column
A scale system here, a railroad portal there, an accounting package. Every tool covered one slice, so the spreadsheet stayed on as the thing that joined them together.
The knowledge is in a person, not the file
Whiteboards, paper switch lists, and a dispatcher who knows which tab is current. When that person is out, the operation slows to the speed of asking someone.
Have one sheet in particular? Go straight to the fix: the demurrage sheet, the inspection binder, the inventory workbook, or the month-end invoice rebuild.
How Rebulk solves it
One operating record, replacing one sheet at a time
Rebulk does not ask you to rip out everything at once. Start with the file that costs you the most time, get it running the way your crew already works, then connect the next piece.
Three products are live today: Transload, Track & Trace, and Inventory. Yard and Rail Maintenance are in Early Access. What is live already covers most of what a rail-served terminal keeps in Excel.
- Replace one sheet at a time, not the whole operation
- Configured around your tracks, commodities, and terms
- Each product reads and writes the same record
- Nothing gets re-entered to make the next piece work
The thesis underneath it: one connected operational record instead of separate data in rail software, yard software, maintenance software, a TMS, an ERP, inventory systems, and spreadsheets. See the Rebulk Platform.
| A | B | C | D | E | F | G | |
|---|---|---|---|---|---|---|---|
| 1 | Site / Pile | Material | Last Measured | Est. Tons | Actual (if known) | Variance | Notes |
| 2 | Pile A - North | Wheat | 1/14/26 | 2,100 | 1,740 | =D2-E2 | Bob estimated visually |
| 3 | Pile B - East Lot | Corn | 12/3/25 | 840 | need to re-measure?? | ||
| 4 | Pile C (old barley) | Barley | Nov 2025 | ~1,400 | 1,020 | #REF! | formula broken - ask Jeff |
| 5 | Pile D - Staging | Mixed | ??? | 600 | moved from pile A? or new delivery | ||
| 6 | Pile E - South | Soybeans | 2/28/26 | 3200 | 2,910 | =D6-E6 | |
| 7 | |||||||
| 8 | TOTALS | =SUM(D2:D6) | =SUM(E2:E6) | #REF! | does this include pile D? | ||
| 9 | |||||||
| 10 | SHRINKAGE ADJ: | ~5% | =D8*0.95 | per Warren 1/20 call | |||
| 11 | BULK DENSITY FACTOR | 0.82 | CHECK THIS | was 0.78 last quarter?? | |||
| 12 | |||||||
| 13 | $ VALUE (approx) | =D8*215 | =E8*215 | =D13-E13 | $215/ton - update for March |
Products involved
What each product replaces
Retire the spreadsheets, whiteboards, and aging software holding the operation together.
The workflow
How the replacement actually goes
No big-bang cutover, and no six-month implementation before anyone sees anything work.
- 1
We walk the operation
Onsite, with the crew. We watch how the sheet actually gets filled in, and where it breaks.
- 2
Start with the sheet that hurts most
Usually the car log or the month-end invoice rebuild. One workflow first, not the whole operation.
- 3
Configured around your terminal
Your tracks, your commodities, your billing terms, and the reports your customers expect. Not a template.
- 4
Go live with the crew
The people who kept the spreadsheet are the people we train, because they know every exception in it.
- 5
Connect the next piece
Each product added reads and writes the same operating record, so nothing gets entered twice to make it work.
Proof
Two operations that made the switch
Venezia Transport
700+ trucks, 1,800+ trailers, and 21 terminal locations, with railcars and transloading in the middle of it. From first meeting to a working model in weeks, not months.
Read the Venezia Transport story“Before Rebulk, we were spending too much time chasing information and then manually inputting it. Now we can see what is happening across the operation much faster.”
Usher Transport
Family-owned since 1946. Before Rebulk, finding a car's status meant radio calls and walk-outs, every transfer was handwritten and then copied again for billing.
Read the Usher Transport story“Rebulk completely changed how we run this operation. Everything is seamless now, and it has made our team's lives dramatically easier.”
Your operation shouldn't run on spreadsheets
Bring us the file. The one with the tabs nobody is allowed to delete. We'll show you what it looks like as an operating record, built around the way your team already fills it in.