Spreadsheets run a surprising number of small shipping lines and NVOCCs, and for a while they work. They stop working when the same shipment lives in several files, when Customs rules need to be enforced rather than remembered, and when nobody can say which version is current. Here is an honest comparison, and a way to move off spreadsheets without losing what they do well.
There are good reasons spreadsheets are everywhere in ocean freight. Everyone already knows them, they cost nothing extra, and a capable operations manager can build a booking log, a rate sheet and a container list in an afternoon. When a lane or a customer changes, the spreadsheet changes with it, with no vendor to call.
At ten shipments a month that flexibility is worth more than structure. The trouble starts later, and it starts quietly: a second booking sheet for a new lane, a copy of the rate file for a big customer, a separate tab for containers. Each one is reasonable. Together they become a system that nobody designed.
Ocean shipping is regulated data, and the rules are specific. CBP requires every bill of lading to carry a unique identifier made of the issuer’s SCAC and up to 12 more characters, not reused for 3 years after issuance; it rejects generic descriptions such as “FAK”, “general cargo” and “STC”; and it wants quantities at the lowest external packaging unit (19 CFR 4.7a). For cargo arriving by vessel, the electronic cargo declaration must reach CBP 24 hours before the cargo is laden at the foreign port (19 CFR 4.7(b)(2)).
None of that is impossible in a spreadsheet, but all of it depends on someone remembering. A shipping system can generate the number, block the duplicate, refuse the vague description and warn when a cut-off is close. Container numbers are similar: the check digit described by the Bureau International des Containers exists precisely so that software can catch a mistyped number at entry.
| Area | Spreadsheets | Dedicated shipping software |
|---|---|---|
| Start-up | Immediate, no cost | Setup, data load and training |
| Data entry | Same data typed in several files | Entered once, reused downstream |
| Validation | Only what you build with formulas | Built-in checks on numbers and required fields |
| B/L numbering | Manual; duplicates possible | Generated from your SCAC, duplicates blocked |
| Customs filing | Separate portal or re-keying | Built from the bills of lading already issued |
| Audit trail | Limited | Who changed what and when |
| Accounting | Invoices built by hand | Posted from the rated bill of lading |
| Customer status | Phone and email | Self-service portal, where offered |
If three or more of those sound familiar, the spreadsheet is no longer saving you time. It is costing you time in a way that does not show up on any invoice.
Our guide on the NVOCC software features that matter can help you write the requirements list for step one.
A dedicated system is not a cure for every problem, and it is worth being honest about that before you buy. Software enforces the rules you configure; it cannot invent a correct cargo description that a shipper never gave you, and it cannot make a late shipping instruction arrive on time. If the bookings desk accepts “general merchandise” from a customer today, it will still have to push back after the change, only now the system will flag it.
Process ownership matters just as much. Someone has to own the customer and rate data, someone has to review exceptions every day, and someone has to decide which reports actually get read. Companies that move off spreadsheets most smoothly usually name those owners before go-live, write down the two or three rules that caused the most corrections in the past year, and check that the new system enforces them from the first sailing.
Moving to a system of record does not mean giving up spreadsheets. They remain excellent for ad hoc analysis, one-off reports and sharing numbers with people outside the operation. The difference is that the spreadsheet becomes an export, not the source. GDZ-ISIS, for example, exports voyage, management and grid reports to Excel, CSV and PDF, so analysts keep their pivot tables while bookings, bills of lading, Customs filing and accounting stay in one place. If you are weighing the change, schedule a demonstration with a few of your own shipments.
At very low volume, many do. The risk grows with each additional user, lane and customer, because retyping and version conflicts multiply and Customs data rules depend on someone remembering them.
Retyped data. When the same shipment is typed into separate booking, bill of lading, filing and invoice files, any one copy can be wrong, and the error often appears as a freight correction or a Customs hold.
It can enforce rules that spreadsheets cannot, such as unique SCAC-based bill of lading numbers, rejecting generic cargo descriptions and building the manifest from issued bills of lading. Compliance still depends on accurate data from your team.
It depends mostly on how clean your customer, vendor and rate data is. Running one or two voyages in parallel before switching off the old files is a safe way to confirm the totals match.
Yes. Most systems export reports to Excel or CSV, so spreadsheets remain useful for analysis while the shipping system stays the single source of record.