Every freight software website shows you the dashboard. Nobody shows you the boring things that decide whether it works.
We build and run Portus, a freight forwarding ERP, and our own logistics business uses it every day. So take this as a builder's view rather than a neutral one. We are telling you what we had to get right, which is a more useful thing than a feature grid.
Every demo you will sit through is the same demo. A clean dashboard, a job created in forty seconds, a chart with a pleasing upward line. None of it tells you what you need to know, because the systems that fail do not fail at creating a job. They fail three months in, when the office quietly goes back to the spreadsheet for the one thing the system cannot do.
Ask about the exceptions, not the happy path
Anybody can demonstrate a clean shipment. Ask to see a messy one.
- A house bill that has to be split across two containers after the job is already open.
- A charge added after the invoice has gone out.
- A consignee who changes halfway through.
- A job in a currency that is not your base currency, with the rate moving between quotation and invoice.
- A correction to a bill of lading after it has been issued.
If the answer to any of these is that you raise a credit note and start again, you have found where your team will stop using the system.
Check that the money comes from the same place as the operations
The single most common failure in this category is an operations module and an accounts module that each hold their own version of the truth. Selling rate lives in one, buying rate lives in the other, and the profit figure depends on which screen you asked. When we built job financials, the numbers had to be pulled from the same records the accounts module posts against, because two spreadsheets that disagree is precisely the problem the software was meant to remove.
Ask directly: is the profit on this job calculated from the same rows that the ledger posts, or is it a separate figure that is reconciled later? Watch their face.
Ask what it watches while nobody is looking
Demurrage and detention is where a forwarder bleeds money quietly, and it is almost always noticed too late to do anything about it. A system that stores free days is not the same as a system that counts them down and puts the risk somewhere a person will see it without going looking. The distinction sounds small in a demo and is worth real money in a year.
The same test applies to quotations sitting unanswered, vessels arriving tomorrow, and documents missing before a cut-off. Storing the data is table stakes. Surfacing it unprompted is the product.
Search is not a nice-to-have in this industry
Somebody will ring your office knowing one thing: a container number. Or a vessel name and roughly which week. Or the consignee and nothing else. If finding that shipment takes four clicks and a guess, your staff will keep a parallel spreadsheet, and the moment they do, your system is decorative.
The questions that actually separate them
Whose data is it, and how do you get it out
Ask for a full export in a format you can read, today, as part of the trial. Not a report. The data. If that is difficult during the sales process, imagine it during a dispute.
What happens when you stop paying
Read-only access, a final export, or the shutters coming down? Get the answer in the contract rather than in an email from a salesperson who may not work there next year.
How many of your people have to change how they work
Software that requires the whole office to work differently on day one does not get adopted. Software that can be introduced one desk at a time does.
Who fixes it at nine on a Friday night
Not the support hours on the website. Ask who actually answers, in which timezone, and what has happened the last three times somebody needed them urgently.
Can it be changed for you, and what does that cost
Every forwarder does something slightly odd that matters to their business. Ask what a small change costs and how long it takes. The honest answer is sometimes no, which is more useful than a vague yes.
One thing worth more than the feature list
Ask whoever is selling it whether their own company runs on it. Not a customer's company. Theirs. A team that has to live with its own decisions builds different software, because the awkward cases are their Monday morning too.
Real screens from Portus with honest notes on why each one exists, including the ones that started arguments.
See what we built, screen by screen