ERP stands for Enterprise Resource Planning. In a logistics business it means one system where the quotation, the booking, the paperwork, the cost and the invoice are all the same record — so the price you quoted on Monday is the price on the booking, the booking is what the waybill prints from, and the invoice on Friday is built from the costs that actually landed against that job.
That is the whole idea. Everything else is detail.
The name is unhelpful, which is why the question gets asked so often. “Enterprise Resource Planning” was coined for factories, where the resources being planned were machines and raw materials. Nobody in freight talks that way. If the term had been invented for this industry it would have been called something like one record per shipment, and the question would answer itself.
The test for whether you need one
Forget the software for a moment and count something instead: how many times does a single shipment get typed in?
Walk one job through your own business. The customer asks for a price and somebody types the details into a spreadsheet. It is accepted, so somebody types them again into a booking sheet. The waybill is typed a third time. The supplier’s invoice arrives and the cost is typed into another spreadsheet. At month end somebody types the sell side into the accounting package to raise the invoice.
That is five. Five is normal, and five is also the answer to the question. Every one of those five is a chance for a figure to change, and none of them tells you it changed. The most expensive version is not a typo — it is the charge that never made the last hop, so the customer is invoiced for four things when five were spent.
If your answer is one or two, you do not need an ERP. A business doing a handful of shipments a month with one person handling all of them has the whole record in one head, and that is genuinely cheaper than any software. The point at which it stops working is not a shipment count; it is the first time two people need to know the same thing at the same time and ask each other.
What it is not
It is not accounting software. Accounting software knows about invoices and payments. It does not know what a shipment is, so it cannot tell you what one job earned. You can bolt the two together and many businesses do, but then the shipment lives in one system and the money in another, and reconciling them is a monthly job somebody has to be paid to do.
It is not a tracking system. Tracking answers “where is it”. An ERP answers “what did it cost, what did we charge, and did anyone actually pay”. Both are useful and they are not the same product, though the same software often carries both.
It is not the same as supply chain management. This is the comparison people search for most, and the difference is simply whose goods they are. Supply chain management plans the movement of your own stock — what to make, what to hold, when to reorder. A logistics ERP runs the business of moving other people’s goods for a fee. A manufacturer needs the first. A forwarder, a transporter or a courier needs the second. Software sold as one will disappoint you at the other.
What it has to cover to be worth having
A logistics ERP that only handles the operational half leaves you exactly where you started, because the half that hurts is the money. The minimum is:
The job, end to end. Quotation, booking, the documents that go with the mode, delivery, and the invoice — carrying the same reference the whole way, so nobody is matching by customer name and date.
Cost against the job, not against the month. This is the one most systems get wrong and it is the one that decides whether you know your margin. When the supplier’s invoice arrives weeks later, it has to attach to the shipment it belongs to. If it lands in a general expense account, your monthly profit is knowable and your per-job profit never is — and per-job is the number that tells you which customers and which lanes are worth keeping.
More than one currency, with the rate recorded. Cross-border work is quoted in one currency, bought in another and reported in a third. What matters is not that the software converts, but that it records which rate on which date — because an invoice converted at today’s rate rather than the rate on the day of supply is wrong by a percentage nobody notices until an audit.
The tax rules of the countries you actually work in. Not “supports VAT”. A tax invoice has legal contents that differ by country, and the difference between zero-rated, exempt and out-of-scope is three different declarations that all show as nothing on the invoice. Software that treats them as one number will file your returns wrong and look fine doing it.
One place the paperwork lives. Not because filing is interesting, but because a customs entry, a delivery note and a supplier invoice sitting on the shipment are what let anyone answer a customer’s question without ringing three people.
The honest version of the cost
The software is rarely the expensive part. The expensive part is the fortnight where your team enters things twice while the old spreadsheets are still open, and the month after that when somebody has to decide what the standard charge codes are called. Businesses that skip that decision end up with the same charge recorded four ways and reports that cannot be added up.
Anyone selling you an ERP who does not mention this is selling you the fortnight as a surprise.
So: do you need one?
Two questions settle it more reliably than any feature list.
Can you say what last month’s most profitable customer was, without opening a spreadsheet? If not, the information exists in your business and no system is holding it.
When a customer rings about a shipment from six weeks ago, how many people do you ask? If the answer is more than nobody, the record is in people rather than in the business.
Those are the two things an ERP is for. Everything else on the brochure is a consequence of getting those two right.