Choosing the software that will run your freight or maritime business is a decision you live with for a decade — and the most expensive mistake is not a missing feature. It is buying for the shape your business has today. Most companies in this industry diversify: the forwarder adds an NVOCC licence, the NVOCC takes a liner agency, the agency opens a depot or a 3PL warehouse. Most software vendors don't cover that journey — and the day you outgrow them, you start a second vendor search with a first system already in the way. This guide is a framework for choosing once.
Generic ERP vs industry-specific
The first fork in the road. A generic ERP (the household names) manages finance and general business superbly, but it does not natively understand a Bill of Lading, an EDI manifest, a container movement, a port disbursement account or a carrier rate contract. To run freight on one, you bolt on point tools and re-key between them — and the seams are where errors and cost hide.
An industry-specific shipping and logistics ERP has those workflows built in: inquiry and quotation, booking, HBL/MBL documentation, EDI, customs filing, operations and freight billing — with a full multi-currency financial ledger of its own underneath, so the operation and the books are one system.
Ask a candidate system to produce a house bill, reconcile it to a master bill, and calculate demurrage on the container — out of the box. If it can't without customisation, it isn't an industry ERP; it's a generic one with your logo on the login screen.
The echelon test: buy for where you're going
Here is the question most buyer's guides skip, and the one that decides whether you'll be repeating this evaluation in three years: how much of the supply chain does the vendor actually cover?
Look at the market honestly and a pattern appears. Freight platforms are built for forwarders — and stop there. Maritime suites are built for ship owners — and stop there. Terminal systems know the yard, generic ERPs know the trader, and none of them know each other. Each vendor serves one echelon of the chain: the cargo owners, the logistics providers, the shipping companies, the ports and terminals, or the maritime assets. Almost nobody covers all five.
That matters because your business will not stay in one echelon. The classic journey in this industry: a company starts as a freight forwarder. Business grows; it takes an NVOCC licence to control its own bills of lading. Then a principal offers a liner agency. Then the container flow justifies an empty depot, and the warehouse becomes a 3PL profit centre. Every one of those steps is natural — and every one of them is a crisis if your software vendor only ever built the forwarding module.
A forwarder buys a forwarding-only platform. Two years later it adds NVOCC — the vendor has nothing, so a second vendor search begins. Now there are two systems, two implementations, two customer masters, and — worst of all — two sets of operational data feeding one accounting close. The finance team becomes a full-time reconciliation department. The second system always costs more than the first, because you pay for it twice: once in licences, and once in the seams.
The defence is simple: evaluate the vendor's full module map before you buy the first module. If freight forwarding, NVOCC, liner and ship agency, container depot, warehousing/3PL, customs, land transport and e-commerce logistics are all modules on one platform — sharing one customer master and one ledger — then diversification is a switch you flip, not a project you procure. See how the five echelons fit together on the industries map.
The module map to demand
Requirements vary by business, but insist on seeing the whole map — the operations you run today and the ones a growing company in your position adds next:
- Freight forwarding — quotation, booking, HBL/MBL, multimodal, billing (see Freight Forwarding Software)
- NVOCC / LCL — own-BL carriage, consolidation, slot and equipment control (see NVOCC Software)
- Liner & ship agency — bookings as agent, container control, PDA/FDA, principal settlement (see Liner Agency and Ship Agency)
- Container depot & terminal — gate and EIR, yard, M&R, CODECO to the lines (see Container Depot Software)
- Warehouse management & 3PL — receiving, inventory, picking, customer-billable events (see Warehouse Management)
- Customs clearance — declarations, EDI to customs, duty management (see Customs Clearance)
- Land transport & e-commerce — dispatch, last-mile, COD, returns (see TMS and Ecommerce Logistics)
- EDI & documents — EDIFACT and ANSI X12, manifests, bills of lading, native and built in
- Multi-currency, multi-branch finance — one ledger under all of the above
You don't have to license it all on day one — you have to know it exists, on the same data model, for the day you need it.
One data model, one finance ledger
The single most important architectural question is whether the platform runs on one data model. When the booking a sales desk creates flows through documentation, customs and operations to the invoice without re-keying — because it is the same record throughout — you get accuracy, speed and a single version of the truth. When each function is a separate module stitched together, you inherit reconciliation work, latency and disputes between "ops" and "finance".
The same logic extends to money. A diversified group — forwarding arm, agency desk, depot, warehouse — should close its books on one financial accounting system, with every business line posting to the same multi-currency ledger and rolling up to per-business P&L. That is only possible when the business lines live on one platform. If each line runs its own system, finance spends every month stitching exports together — and the group never sees one truth. Push hard on both points in evaluation; they are easy to hide behind a slick demo. (Where a corporate ERP must remain the group's system of record, clean integration should be available — but it should be a detail of the deal, not the centre of it.)
Country compliance rails
Freight is local the moment it touches a border. Every market has its own customs gateway, e-invoicing mandate and tax regime — Fasah and ZATCA e-invoicing in Saudi Arabia, ICEGATE and GST in India, TradeNet in Singapore, uCustoms and MyInvois in Malaysia. A platform that treats these as "customisation projects" will bill you for every country you enter; a platform built as country editions switches them on. If you operate in — or plan to enter — more than one market, ask which countries are supported as configuration, not development. See the country coverage map for how that should look.
The best predictor of a successful ERP is not the feature list — it is a real customer in your trade, at your scale, that you can call. Ask for references you can actually speak to, and ask them what went wrong, not just what went right.
Questions to ask every vendor
- Can you run my core operation end to end on one data model — show me the same shipment from quote to invoice?
- Show me your full module map beyond my current business. If I add NVOCC, an agency, a depot or a 3PL warehouse next year — is that a module you switch on, or a second system I buy?
- Will every business line I run post to one financial ledger, with one customer master and per-business P&L?
- Which industry documents and EDI messages are native, and which need configuration or third parties?
- Which countries do you support as configuration — customs gateway, e-invoicing, tax — and which would be a project?
- Do you run multi-branch, multi-currency, multi-country — and can I see it at my scale?
- What does implementation look like, phase by phase, and who does the work?
- How is AI applied — and where does a human stay in control?
- Who owns my data, and is my deployment isolated?
De-risking the implementation
Most ERP disappointment is really implementation disappointment. De-risk it: prefer a phased rollout — one operation or branch first, then expand — over a big-bang go-live; fix the data foundation before migrating; insist on clear milestones and a named team on both sides; and keep the first phase's scope tight enough to prove value fast. Note that the safest phasing of all — go live with one business line, switch on the next when ready — is only available on a platform that has the next line as a module. A vendor confident enough to start small and expand is usually the safer bet than one promising everything at once.
Related reading
- Industries across the supply chain — the five echelons, mapped.
- AI in Logistics & Supply Chain — how AI should factor into the decision.
- What Is a Maritime ERP? — the equivalent question for ship owners and managers.
- Freight & maritime glossary — the terms behind the requirements.