NVOCCs running private rail ramps live in a different world than container forwarders. You have rail terminal moves, drayage to bulk ag loaders, outbound train release for transpac ocean export, plus the regular NVOCC paperwork on top. A pure freight forwarding TMS does not cover the terminal side. A pure terminal OS does not cover the export side. So most intermodal operators run a stack: CargoWise for the forwarding files, a terminal operating system like Octopi for the ramp moves, an accounting platform like Sage Intacct, and a layer of Excel that holds it all together. This guide walks through why that franken stack happens, what an intermodal NVOCC actually needs from software, how to consolidate rail, drayage and ocean export in one platform, and how to report across the whole operation.
Most intermodal NVOCCs do not set out to run three or four systems in parallel. It happens one decision at a time. A new hire arrives who knows CargoWise, so the company licenses CargoWise for the forwarding files. The terminal needs its own system for gate moves and rail manifest building, so Octopi or a similar terminal OS gets bolted on. Accounting is already in Sage Intacct or QuickBooks. Reporting falls through the cracks, so the finance team builds a master Excel sheet that everybody updates by hand.
An upstate New York NVOCC running 3 private BNSF rail ramps described the result in a sentence:
“We have a lot of systems. They don't all work together. It's all manual. It's all manual.
Logistics Manager, upstate New York NVOCC and rail terminal operator
That franken stack creates four predictable problems for an intermodal operator:
An NVOCC running rail ramps is not a candidate for a stripped down freight broker tool. But it is also not the global enterprise that CargoWise is built for. If you are new to the NVOCC operating model itself, our explainer on what an NVOCC actually is and how it differs from a freight forwarder covers the basics.
Strip away the enterprise nice to haves and the real software requirements for a rail and ocean export NVOCC come down to a short list.
| Workflow stage | What the software has to do | Why it matters |
|---|---|---|
| Empty train build at the rail ramp | Track inbound empties by car, assign to outbound trains, record gate moves. | If the empty data is wrong, you cannot release a train. |
| Drayage to bulk loaders | Dispatch local drayage moves to ag commodity loaders, capture POD, link the move to the parent shipment. | Drayage cost is a margin line item. It belongs on the same shipment record, not a separate dispatch sheet. |
| Outbound train release | Confirm loaded car list against the train manifest, transmit release to the railroad, file documents. | A miscounted or mismatched manifest delays the whole train. Manual reconciliation is the failure mode. |
| Transpac ocean export | Book vessel space, generate HBL and MBL, file AES, manage carrier and customer documents. | The terminal move only matters if the export shipment goes out clean. |
| Accounting and billing | Generate invoices from the same shipment record, push entries to Sage Intacct or QuickBooks, hold accruals. | If accruals live in Excel, month end always slips. |
| Reporting and customer status | Dashboard per employee or book of business; weekly customer reports pulled from the system, not built by hand. | Customer trust depends on consistent updates. Excel reports break the moment someone forgets to refresh them. |
What is striking is what is not on this list. Air freight is missing. Global customs brokerage is missing. A 17 way menu of features you can access from a dozen places is missing. As one VP of logistics at the same rail NVOCC said, "We don't need a bus."
For a fuller comparison of platforms that fit a focused NVOCC, see our roundup of top NVOCC software solutions, which walks through the trade offs by company size and modal mix.
The consolidation play for an intermodal NVOCC is not "rip out everything and start fresh." It is "stop using three systems where one well chosen platform plus targeted integrations would do the job."
The work breaks into four moves:
The Excel master sheet is sticky. Even after the new platform is live, finance teams keep updating the spreadsheet "just in case." Set a hard cutoff date and stop maintaining the sheet on that date. If reporting breaks, you find out which numbers were actually being consumed.
The point of consolidating rail, drayage and ocean export onto one system is not just fewer logins. It is reporting that can answer questions the franken stack cannot.
Questions an intermodal NVOCC needs to answer weekly:
On a franken stack, every one of those reports is a combine and clean job in Excel. On a consolidated platform, they are dashboards. The same rail NVOCC framed the upside as: "Having a dashboard for all your op shipments by whatever employee has their own book of business." That dashboard does not exist when the data lives in three systems.
Consolidation also fixes the customer status problem. Instead of a couple of times a week running an Excel update meeting, the customer sees their shipments through a portal that reads from the same shipment record the operations team works in. No double maintenance, no out of date numbers.
Run your rail ramp moves, drayage and ocean export on one platform built for NVOCCs. See how GoFreight consolidates the franken stack.
Request a GoFreight Demo →Intermodal terminal operator software is a platform that manages cargo moves at a terminal where rail meets road, road meets ocean, or all three meet. For an NVOCC running private rail ramps, it covers empty car management, train build, gate moves, drayage dispatch and the link from the terminal move to the parent ocean export shipment.
It happens one decision at a time. A new hire knows CargoWise so the company licenses CargoWise. The terminal needs its own software for gate moves so a terminal OS gets added. Accounting is already in Sage Intacct or QuickBooks. Reporting is not covered by any of them, so finance builds an Excel master sheet. None of the systems talk to each other, so staff retype data between them and the spreadsheet holds it all together.
For many focused NVOCCs the answer is no. CargoWise is built for global forwarders running every mode in every country. A US export NVOCC moving ag commodities through private rail ramps will typically use only a fraction of the licensed features while still paying for the rest. The phrase operators use is that CargoWise is "a really big car that we don't need all the functions and features of." A platform sized for ocean export and NVOCC workflows is usually a better fit.
Yes. Drayage moves sit on the same shipment record as the ocean export leg, with cost lines tied to that record. That means one container number, one customer, one set of charges across the rail, drayage and ocean stages, instead of a separate dispatch tool and a separate Excel reconciliation.
The platform tracks loaded cars built at the ramp, reconciles them against the train manifest, generates the export documentation (HBL, MBL, AES) for the onward ocean leg, and keeps the whole sequence on one shipment record. The goal is to remove the manual reconciliation step where a mismatched car count delays the train release.
GoFreight supports accounting integrations so that entries from the shipment record push into your accounting system on a defined schedule. The book of record stays in Sage Intacct or QuickBooks; staff stop retyping invoices between systems. Specific integration details are confirmed during the implementation scoping.
Reporting moves from manual Excel combining to dashboards built on the live shipment data. You can see open shipments per employee or per book of business, dwell time at each ramp, drayage cost per loaded container by lane, and unbilled accruals at month end, without rebuilding a spreadsheet each week.
It gets retired. Accruals move into the platform and tie to the shipment record they belong to. Set a hard cutoff date for the spreadsheet and stop maintaining it on that date. If any reporting breaks, you find out which numbers were genuinely being consumed and can rebuild them as saved views or scheduled exports inside the system.
No. The franken stack problem of one or two people holding the keys to the castle goes away when the platform is straightforward enough that any operations user can do their daily job in it. New hires get productive faster, and the operation does not stop when a single power user leaves.