Freight Forwarding ERP
What a freight forwarding ERP has to do that a general ERP doesn’t
A forwarding ERP has to carry one job all the way through: the price you quoted, the booking it became, the paperwork that moved the goods, the supplier bills that arrive weeks after you invoiced, and what the shipment actually earned. Most general business systems model a shipment as a sales order, and that one assumption is where the re-keying, the missing paperwork and the flattering margin come from.
Six things it has to get right
None of these are unusual requests in forwarding. They are unusual requests of a system built for manufacturing or retail.
One job, quote to cash
The price you quoted, the booking it became, the costs against it and the invoice you send are the same job — not four records someone re-keys. When a customer asks why the invoice differs from the quote, the answer is on one screen.
The paperwork is the work
A bill of lading, an air waybill, a customs declaration and a delivery order are not attachments to the job. They carry the numbers the job is made of, and they have to come out of the same place those numbers live.
Margin per shipment, not per month
A forwarder does not find out at month end whether the year is working. Each shipment earns or loses, and the figure has to hold up when the supplier bill lands three weeks later and is not what you assumed.
Costs arrive after the invoice
You bill the customer long before the handler, the carrier and the transporter bill you. A system that assumes the purchase comes first will report a profit you have not made yet — the single most common way a forwarder is flattered by its own numbers.
More than one currency on one job
Sold in one currency, bought in two others, reported in a fourth. The rate has to be the rate on the day, and an amount nobody could convert has to be shown as unconverted rather than quietly added at face value.
Your customer wants to look
Where is it, what did it cost, send me the paperwork. Answering that by hand is most of a coordinator’s day, and it is the first thing a forwarder wants back.
Where a general ERP tends to struggle
This is not an argument that general systems are bad — they are very good at what they were built for. It is that a forwarding job has a shape they do not expect.
- A shipment is modelled as a sales order, so the paperwork becomes attachments nobody can report on.
- Buying is expected before selling, so a job invoiced ahead of its supplier bills reads as pure profit until the bills arrive.
- Customs, tax and the local invoice rules of each country are configuration work rather than something the system already knows.
- There is no notion of a job that is operationally finished and financially open — which is the state most shipments are in.
- The fit is built by a consultant, so it is only as durable as the person who built it and the budget that paid for them.
“We’re too small for an ERP”
It is the most common thing we hear, and size is the wrong measure. The question worth asking is how many separate places one shipment is written down. A quote in a spreadsheet, a booking in a messaging thread, the invoice in an accounting package and the costs in an inbox is four — and somebody is keeping all four in step by hand.
Smaller forwarders usually feel that sooner than large ones, because the same person is doing all four. What changes is not headcount, it is that the job stops being re-typed.
Questions people ask
What is an ERP in logistics?
It is the one system a logistics company runs the business on, rather than a separate tool for each part of it. In practice that means quoting, bookings, the paperwork for customs and carriers, the fleet or warehouse the goods pass through, invoicing, and the accounts behind all of it — sharing the same records, so a shipment, its costs and its invoice are the same thing seen from different sides.
What is the difference between freight forwarding software and a freight forwarding ERP?
Forwarding software usually covers operations: quotes, bookings and shipment documents. A forwarding ERP carries the money as well — supplier bills, customer invoices, VAT and the ledger — so the margin on a shipment is a fact the system holds rather than a figure somebody rebuilds in a spreadsheet. The practical test is whether you have to re-enter an invoice into an accounting package afterwards.
Can a general-purpose or open-source ERP be used for freight forwarding?
It can be made to work, and plenty of forwarders have tried. The cost is rarely the licence — it is that a shipment is not a sales order, the paperwork is not an attachment, and the supplier bills arrive after you have invoiced. Each of those is configuration or custom development, and it has to be maintained by whoever built it. A system that already models a job that way starts where that work ends.
Is a shipping ERP the same as a freight forwarding ERP?
Usually the same thing, and sometimes not. People say shipping ERP, shipping ERP system and freight forwarding ERP for one idea: the system a company moving other people’s cargo runs on. Where it differs is at the ends of the chain — a carrier or NVOCC operating its own vessels or containers needs equipment and schedules a forwarder never touches, and a customs broker needs declarations more than it needs freight. If you buy space and sell it on, arrange the paperwork, and carry the cost of the job until the supplier bills land, the forwarding description is the one that fits, whichever phrase you searched for.
How do I choose a freight forwarding ERP?
Five questions answer most of it, and none of them is about the length of the feature list. Does one shipment exist once, from quote to invoice, or is it re-keyed between operations and accounts? Do the documents come out of the job, or are they typed again? Can a supplier bill that arrives three weeks late still be matched to the shipment it belongs to? Does it invoice correctly under the tax rules of the country you invoice from, without a consultant configuring it? And can you get your own data out again if you leave. Ask for one shipment to be taken end to end in a demo rather than a tour of screens — a tour shows what the software has, a job shows what it does.
Does a small or mid-sized forwarder need an ERP?
Size is the wrong question — the question is how many places one shipment is written down. If a job lives in a spreadsheet, a messaging thread and an accounting package, then somebody is keeping those three in step by hand, and that is where the hours and the errors are. Smaller forwarders often feel it sooner than large ones, because the same person is doing all three.
What should a freight forwarding ERP include?
At minimum: quotations that become bookings without re-keying; shipment documents generated from the job rather than typed again; supplier costs matched to the shipment they belong to; invoicing that meets the tax rules of the country you invoice from; and a per-shipment margin you can trust once the late costs have landed. Anything beyond that — fleet, warehouse, courier, a customer portal — depends on what you actually operate.
How long does it take to move off spreadsheets?
The part that takes time is not the software, it is agreeing what your charge codes and customers actually are. Companies that bring a clean customer list and an agreed set of charges are usually quoting in days. The realistic plan is to run new jobs in the system and leave the old ones to close where they are, rather than migrating everything at once.
Forwarding is one of four operations most logistics businesses run. If you also move your own trucks or store your customers’ goods, the wider question is what a logistics ERP has to join up across all of them.
Built for these markets
The tax rules, the customs paperwork and the invoice each country expects are part of the system rather than a configuration project.
See it against one of your own shipments
Take a job you ran last week — the quote, the costs, the invoice — and put it through. It is a faster answer than any demonstration.