How to choose software for your forwarding business: an honest checklist

Choosing the software you’ll run your forwarding business on is a decision you live with for years. It’s a mistake to look only at the pretty demo or the price of the first invoice. These are the criteria that really separate a tool that changes how you operate from one that ends up being just another place to type data by hand.

1. Are the integrations real, or a promise?

This is question number one for a forwarder. Ask it plainly:

• Does it connect to your carriers via official API and the DCSA standard, or does it scrape their websites fragilely?
• Does it include vessel AIS and flight data, or just repeat the ETA the carrier published?
• Is the integration working today, or is it “on the roadmap”?

A real integration makes the status flow in on its own. A fake one leaves you copying statuses just like before.

2. Does it cover every mode in one place?

If you move ocean, air, rail and road, you need to see them together. Software that only does ocean forces you to keep another tool for the rest, and you’re back to blind spots. Look for multimodal visibility on a single map, with ETA and alerts.

3. Does it reach invoicing?

Tracking is great, but the margin is won or lost at invoicing. Check that:

• You see the margin of each file before you invoice.
• Invoicing is wired to VeriFactu (mandatory in Spain from 1 January 2027 for companies and 1 July 2027 for everyone else).
• You don’t need a second tool to invoice what you already operate.

4. Whose data is it, and where is it?

Buying committees look at this more and more:

• Is your data in the EU?
• Is there a lock-in, or can you leave whenever you want?
• Can you export everything if you decide to switch?

If the answer to “can I take my data?” isn’t a clear yes, be wary.

5. How long does onboarding take?

A twelve-month project is a project that dies before it starts. Ask what the real onboarding looks like: migrating your data, switching on integrations and training. Weeks, not months. And that you start with your real operation, not an empty demo.

6. Is it built for forwarders?

A generic ERP or CRM holds contacts and invoices, but it doesn’t speak the language of freight forwarding: files, BLs, transshipments, demurrage, customs. Software built for forwarders understands your operation out of the box.

7. Who helps you when something breaks?

Onboarding and support from people who know your operation, in your language, is the difference between fixing it in minutes and opening a ticket no one answers.

The checklist in one line

Real integrations · multimodal on one map · margin and VeriFactu · data in the EU that you can take with you · onboarding in weeks · built for forwarders · human support.

Rowan Cargo was built to this list, with real forwarders. If you want to run this checklist past your candidate with us in the room, book a demo.