What matters when choosing an ERP for equipment rental?

For rental businesses one point decides before all others: your central unit is not the item with a stock level but the individual machine over time. An excavator is not „three in stock“, it is with customer A from Tuesday to Friday, then two days in the workshop and available from the week after. Any system that calculates availability as a quantity rather than a calendar gives systematically false commitments in rental. Business Central cannot do this as standard, it needs an extension. The real selection question is therefore: which parts of your business belong in that extension, and which stay in the standard where they survive updates.

Which question comes before all others?

How high is your rental share of revenue, and what does the rest look like? Most rental businesses are mixed businesses: rental, sale of new and used machines, service, spare parts, consumables and transport. Often all of it appears on one invoice.

That is exactly where many selection processes fail. A pure rental solution covers trade poorly, a pure trading system covers rental poorly. Anyone discovering the mixed character only during implementation builds the missing half afterwards as a special solution. So ask in every demo for a document on which rental, sale and service appear together, with correct tax and correct margin per line.

Where selection in rental most often fails

• Availability is checked as stock. The system reports „available“ because the machine is held in the warehouse, and overlooks the reservation four weeks out. Test this in the demo with a real overlap, not with a free machine.
• The return is just a goods receipt. Condition, damage, cleaning, operating hours and readiness to re-hire all arise right here. Anyone not capturing them later has no basis for maintenance, damage billing and utilisation figures.
• The pricing logic is more complex than assumed. Daily, weekly and monthly rates, tiers, minimum hire periods, part days, seasonal surcharges, framework agreements per customer. Anyone mapping this afterwards ends up with prices that form in the dispatcher's head.
• Sub-hire is missing from the picture. When your own fleet is fully booked, machines are hired in. That is a purchase that hangs off a rental contract, and it decides the margin of the job. Many systems only know their own stock.

Which criteria genuinely carry?

The rental object as a unit of its own. With serial number, location, operating hours, maintenance history, acquisition value and residual book value. Everything later hangs off it: dispatch, maintenance, utilisation and the question of when a machine is sold rather than hired out again.

An availability calendar that allows real dispatch. Not just a display but a tool: rebook, move, provide a replacement machine, schedule transport. In rental, dispatch is the workstation where the money is earned.

Maintenance by operating hours, not by calendar. A machine with 900 hours in a quarter needs a different rhythm from one with 90. If maintenance hangs off the calendar, you service either too early or too late, and both cost.

Utilisation as a figure, not an estimate. What share of the fleet was on hire in the quarter, which machines stood still, which were permanently in repair? That figure decides investment, and it can only be kept if rental, return and workshop run in the same system.

The general approach with criteria and checklist: ERP selection: criteria, approach and checklist

Industry solution or standard with an extension?

The honest answer depends on your rental share. If it is low, hire periods short and the pricing logic simple, a lean add-on on the standard carries it and you keep the full trading and service scope of Business Central. If rental dominates your business, with maintenance by operating hours, sub-hire and framework agreements, a specialised solution is the straighter route.

What holds in both cases: every customisation must be built as an extension that does not touch the core. Business Central gets a major version twice a year in the cloud, and rental logic sitting in the core becomes a topic with every wave.

And regardless of the product, the data foundation decides. A fleet whose serial numbers, locations and operating hours today live in three spreadsheets and one person's head will not become orderly by itself through any system. That work falls due before the project, or more expensively during it.

Why this is so often underestimated: Why does automation fail on data quality?