Choosing shipping line software is a decision you will live with for years, so it deserves more than a feature comparison. The right system fits the way your shipments actually flow, files with U.S. Customs reliably, keeps accounting tied to every bill of lading, and is backed by a vendor who will still answer the phone when a vessel is closing.
Most software comparisons go wrong at the first step: the buyer collects brochures and counts features. Every system claims bookings, bills of lading and accounting. What separates them is whether information entered once flows through the rest of the shipment without being retyped, and whether the system matches the trades you run.
Before you talk to any vendor, write down your own flow: how a quote becomes a booking, how equipment is released, how LCL cargo is received and consolidated, who issues house and master bills of lading, who files with Customs, and how charges reach the invoice. Note where your team retypes data today and where errors usually happen. That document becomes your scorecard.
Use the table below during demos. A system does not need to be perfect in every row, but a weak answer in Customs filing or accounting integration is expensive to work around.
| Area | Questions to ask |
|---|---|
| Rates and quotes | Can it hold tariffs, service contracts and NRAs and rate quotes and bills of lading automatically from them? Can it compare the rated bill with the original quote? |
| Bookings and equipment | Does it check equipment availability when a booking is made? Does it handle break bulk, hazardous and reefer cargo? |
| LCL and warehouse | Dock receipts, warehouse inventory, stuffing and stripping? |
| Bills of lading | House and master bills, transshipment, custom B/L forms, second-language descriptions? |
| U.S. Customs | How does it transmit ACE manifests? How are status messages, holds, releases and rejections shown? In-bond and General Order? |
| EDI | Which standards (ANSI X12, EDIFACT, XML, CSV) and partners (terminals, truckers, carriers, foreign customs) can it exchange with? |
| Accounting | Do bill of lading charges post automatically to receivables, payables and the general ledger? Multi-currency? Voyage profitability? |
| Customers | Can customers see their own cargo status and documents? |
| Data | Who owns the data? Can you export all of it in a usable format? How is it backed up? |
| Vendor | Who provides support, in which languages, and how fast? Can the system be adapted to your operation? |
If you file your own ocean manifests, Customs capability is the most important line on the checklist. Under 19 CFR 4.7(b)(2), CBP must receive the electronic cargo declaration 24 hours before the cargo is laden at the foreign port, and an NVOCC that files its own must do so through a CBP-approved system. There is no room for a system that is slow, fragile or unclear about what it sent.
CBP publishes the technical requirements for ACE ocean manifests on its ACE Import Manifest Documentation page: the Ocean CAMIR chapters and appendices and the ANSI X12 implementation guides for messages such as the 309 manifest, 350 status information, 355 acceptance and rejection and 357 in-bond information. The same page links to a list of Sea AMS data processing service providers. You do not need to read the specifications yourself, but you should ask a vendor:
For exporters and their agents, reliability matters on the AES side too. 15 CFR 30.4(f) says that if a filer's own transmission method is unavailable, the filer must delay the export or find an alternative filing method, so ask how a vendor handles outages.
The single biggest source of hidden cost in a carrier or NVOCC is retyping operational data into a separate accounting package. Every re-entry delays invoicing and creates differences between what was shipped and what was billed.
Ask to see a bill of lading become receivables, payables and general ledger entries without anyone keying it again, and ask how revenue and costs roll up by shipment, customer and voyage. If the answer involves an export file and an import into another program, factor that labor and its error rate into your comparison. Our guide to freight invoicing and accounting for NVOCCs covers what good shipment accounting looks like.
Software does not make you compliant, but it can make compliance much easier or much harder. Two examples from FMC rules show why the details matter:
You will eventually leave any system, so ask about the exit before you sign. Can you export all of your data, including history, in a documented format? Who holds backups? What happens to your records if the relationship ends?
Ask the same questions in reverse about your current system: how will your customers, vendors, tariffs, open bookings and historical bills of lading get into the new one? Our guide to moving off legacy shipping software walks through a safe migration.
Shipping software is never finished. Customs specifications change, trading partners ask for new EDI formats and your own operation evolves. A vendor that adapts the system to your business and supports it directly will be worth more over ten years than a slightly longer feature list on day one.
Ask who answers support calls, whether support is available in the languages your team and customers use, how changes and customizations are handled, and whether you can talk to the people who build the system. For carriers and NVOCCs in Florida, the Caribbean and Latin America, GDZ-ISIS is one option to put through this checklist: it is built and supported in Miami-Dade, in English and Spanish, and each installation is tailored to the company that runs it.
At minimum: rates and quotations, bookings with equipment control, LCL receipts and stuffing, bills of lading with rating, U.S. Customs filing, EDI and accounting fed directly from the bills of lading. Customer access to cargo status is increasingly expected.
Write down your own quote-to-invoice workflow, then have each vendor demonstrate it with your real shipments. Score them on how little data is retyped, how Customs filing and accounting work, data ownership and the quality of support.
Under 19 CFR 4.7(b)(2), an NVOCC filing its own electronic cargo declaration must use a CBP-approved system. CBP publishes ACE ocean manifest technical documentation and links a list of Sea AMS data processing service providers; ask vendors how they transmit and confirm details with CBP.
It does not have to be, but when bill of lading charges post automatically to receivables, payables and the general ledger, invoicing is faster and revenue matches what was shipped. A separate package means re-entry or file transfers to manage.
Ask who owns it, whether you can export all of it including history in a documented format, how it is backed up, and how your existing records will be migrated in. Get the answers in writing before you sign.