Equipment Rental ERP
Monday morning, the yard is still wet and the phone will not sit still. A bricklayer wants the six-metre platform for Wednesday. A contractor asks whether the mixer that left on Friday is back yet. The driver is at the door, key in hand, waiting for the address of the eight o'clock drop. At the counter someone opens the notebook, the WhatsApp group and a spreadsheet that was half updated on Saturday. The platform looks free on paper and taken in a message. Nobody invented a number. Each person wrote down what they saw, in the place they had in front of them.
That hour is when a rental company finds out whether its records can survive the day. The customer does not want a speech about process. They want a yes or a no, a delivery time, and a price that will not change when the machine comes home. If the answer takes too long, they call the next yard. If the answer is wrong, the trouble returns on Thursday, when two sites are waiting for the same generator.
People who have lived with this for years have already tried everything. A hardback book, a whiteboard, a spreadsheet with colours, a group chat with the driver, a folder of contracts in a drawer. Each of those works while the company still fits inside two people's heads. The squeeze starts when a third person serves a customer the first person had already promised, and nobody hears about it in time.
What people mean when they ask for a system
When an owner says they need an ERP, they are rarely shopping for a label. They want to stop answering in the dark. They want to see what is in the yard, what is on site, what is in the workshop and what has already been billed. They want the contract, the handover and the invoice to tell the same story. The name on the box matters less than that conversation at the counter.
Renting equipment is not a sale that ends at the till. The machine leaves, stays out for days or months, and comes back dirty, sometimes dented, sometimes with more hours on the clock than the contract allowed. The money does not finish on the way out. There is a deposit, a daily rate, extra hours, fuel, haulage, a part that was replaced, and a settlement on return. A system built for a shop counter, which only knows how to sell and write stock off, leaves half of that life outside.
So the system that fits this trade follows the equipment as something that comes back, not as goods that disappear. It keeps who has the piece, since when, until when, at which address, at what price, and in what condition it should return. If that card does not exist, the rest is polite guesswork.
A record that is actually useful
A price list is not a record. A real record says what that mixer is: internal number, make, year, capacity, whether it needs an operator, whether it fits in the pickup, what voltage the generator wants, how high the platform goes, what load the scaffold will take. It also says the state of it today. Ready, reserved, on site, in the workshop, waiting for a part, written off.
Without that detail, the counter sells what it cannot deliver. The customer asks for a 20 cfm compressor and gets a 10, because both sat on the same spreadsheet row under the same nickname. The job stops, the truck turns around, and the argument about who got it wrong eats the rest of the afternoon. A decent record stops that conversation before it starts.
A photo helps, a serial number helps, and the short note the mechanic left helps most of all. "Leaks oil on start" written on the card is worth more than a meeting. The person covering Saturday morning was not in the workshop on Thursday. They need to read what the other person saw, without phoning anyone.
A hold, a contract, and what was actually agreed
Holding a machine is not the same as renting it. The customer asks on Tuesday whether the platform is free on Thursday. Today's answer does not lock the equipment for later unless someone writes the hold down with a name, a date and a deadline to confirm. Without that, the next call takes the same machine, and on Thursday both of them are at the gate.
The contract is where the agreement stops living in memory. Period, daily rate, collection time, who picks up, who delivers, the deposit, what happens if it runs late, what happens if it breaks through misuse. It can be short. It has to be the same text the driver and the bookkeeper will read. A contract in a drawer and a different note on WhatsApp is an invitation to a row.
Some yards close the deal in a hurry, out in the yard, with the customer already late. The system does not need to be a ceremony. It needs the contract to come out fast, with the equipment details already filled in, and to keep a copy that does not depend on the phone of whoever answered. When the customer comes back in twenty days, a different person may be at the counter. The agreement still has to be there.
Where the machine actually is
A rental fleet spends the day scattered. Part of it sleeps in the yard. Part of it is on site, sometimes in the next town. Part of it is on the truck, between a delivery and a collection. Part of it is in pieces in the workshop, waiting for a seal the supplier said would arrive tomorrow. Asking how many mixers we own, without asking how many are free today, is a sum that helps nobody.
A useful view shows availability by date, not only the total count. If the platform comes back Friday afternoon, it is not free to leave Friday morning. If the service takes two days, those two days are not on the rental board. It sounds obvious when you say it like that. On paper, people forget, because the rush pushes an "I think it will be fine".
The delivery address is part of the whereabouts too. The driver should not depend on a forty-second voice note to find the site. Street, number, a landmark, the name of the person receiving it and a phone number belong on the same job as the machine. When that fails, the daily rate starts running while the equipment sits on the wrong pavement, and the customer thinks the delay belongs to the yard. Usually it does.
The workshop, the hour meter, and the part nobody wrote down
Rental equipment works in someone else's hands. It comes back with dried concrete, a bald tyre, a taped power lead, an hour meter that moved further than the contract said. The workshop sees that first. If the note stays in the mechanic's notebook, the counter keeps offering the machine as if it were ready.
A plain record already changes the day: it came into the workshop, why, when it should be out, it left, what was replaced. It does not need to become an engineering paper. It needs to stop the platform with the failing sensor going out again on Monday. A customer who receives a bad machine once thinks twice before calling again. A late repair costs less than that doubt.
Hours and mileage, when the equipment has them, take the argument out of the return. The number on the way out and the number on the way back, written on the same contract, turn "they used it too much" into a figure. Without the number, it is an opinion. An opinion at the counter, with a tired customer and a dirty machine between you, rarely ends well.
Deposits, extra days, haulage and the bill on the way back
Rental money does not fit in a single sale. A deposit comes in. The daily rate runs. Sometimes an hourly rate runs. Haulage out, haulage back, fuel, an operator, an accessory that left with the machine and was not in the list price. On return there is damage, a clean-up, an extra day because the site ran late. Anyone who closes that from memory at the end of the month leaves money on the table, or charges something that was never agreed. Both paths spoil the relationship.
The bookkeeper needs to read the contract without phoning the person who took the order. If the daily rate is there, if the deposit was cash or a transfer, if the haulage was already paid, the invoice goes out without a surprise. The customer needs to recognise the bill too. Nothing annoys people more than a line nobody explained. The system does not replace the conversation. It stops the conversation from getting lost.
Some yards mix the rental till with the workshop till and with the purchase of the next machine. At month end the owner knows money came in and does not know whether the operation made anything. Separating the rentals from the rest, even in a simple view, shows which machine pays for its own repairs and which one only occupies yard space. That sum, done once a month with numbers you trust, changes the decision to buy the next one.
The counter, the driver and the Saturday message
Three people meet the same customer over one rental. The person who sold it, the person who delivered it, the person who takes it back. If each of them has their own version, the customer notices. The driver arrives without the lead that was promised. The counter charges a day the salesperson had waived "just this once". The person on returns cannot find the deposit. None of that is bad will. It is information that did not travel with the machine.
Saturday is worse, because the crew is smaller and the work is not. The message lands on the phone of someone who is off. On Monday nobody reopens that chat. The hold dies halfway, or worse, it stays alive only for the customer. One place to write it down, which the person on duty can also open, takes that ghost out of the week.
This is not about watching staff. It is about letting a new person serve a customer without borrowing the memory of the old one. A yard that only works when the owner is at the counter is not in control. It is on permanent duty. A decent system gives the Sunday back.
When the spreadsheet stops being enough
The spreadsheet is honest at the start. One sheet of equipment, one sheet of contracts, a colour filter. With twenty items and one person at the counter, it saves the day. The trouble arrives slowly. Someone sorts a column and loses a row. Two people open the file at once. The version in the email is not the version on the desktop. A year of history becomes a heavy file nobody opens, afraid of breaking it.
Then the nicknames start. Mixer 4 becomes "the yellow one" on one sheet and "MX-04" on another. The utilisation report lies, because half the rows do not speak to the other half. The owner feels the company grew and the view shrank. That is the point where insisting on the spreadsheet costs more than changing tools.
Changing does not have to be a year-long project. It has to carry the equipment list, the open contracts and the deposit balances. The rest, the old history, can stay filed for lookup. Anyone who tries to migrate ten years of mess on day one gives up in the second week and goes back to the old file. Better to start with what is out on the road now.
A week when the answer lives in one place
Picture the same Monday, six months on, once the habit is there. The phone rings. The person at the counter looks up the six-metre platform, sees it coming back Wednesday morning from a site across town, with a service booked for the afternoon. They offer Thursday, delivery at seven, and leave the hold in the caller's name, to be confirmed by Tuesday. In the morning the driver opens the day's run and finds the address, the contact and what has to travel with the machine. Nobody shouts across the yard to check.
On return, the hour meter from the way out is on the contract. The difference becomes a line on the bill, next to an extra day the customer had already mentioned. The deposit comes back without a hunt for the receipt. The workshop receives the machine with the counter's note: split hose, customer told. None of that is magic. It is the same information, written once, read by the person who needs it.
At the end of the week the owner looks at what is out, what comes back in the next few days, and what has been sitting still for too long. They decide whether to buy another platform or whether the one in the workshop deserves the expensive part. The decision comes from a number, not from a guess over lunch.
What stays as people's work
No system knows whether a customer returns equipment clean, or whether a particular site has a name for losing accessories. That lives with the person who serves them. The program keeps the note if someone writes it. If nobody writes it, the card stays quiet. The tool does not replace the mechanic's eye or the feel of negotiating a late return with an old customer.
A setup nobody uses is no help either. If the counter closes the contract in the system and the driver still works from paper, the company has two records, and the worse one wins. The right start is dull and small: every machine that leaves, leaves through there. Every machine that comes back, comes back through there. An exception becomes a hole the same day, not "we'll enter it later".
An afternoon of practice, with the yard's own machines, is worth more than a thick manual. The person needs to find the platform, open the contract and see the deposit without asking for help. If those three moves are easy, they learn the rest in the week. If they are hard, they are back on WhatsApp before the coffee cools.
A reference for people who rent out equipment
People looking for a system built for this trade, rather than a shop system or a factory system with a rental sticker on it, find companies that grew up around hiring equipment out. The contract with a period, the whereabouts of the machine, the workshop and the settlement on return are in the shape of the product, not hidden in a module you switch on later.
In Brazil, one reference of that kind is Locazap. It is an equipment rental ERP, shaped around the routine of lending a machine out and getting it back with the bill closed. You can see how the company works at https://locazap.com.br. Look at it with the counter's question in mind: does this show where the machine is, what was agreed, and what still needs to be charged?
Where to start without turning the company upside down
Do not start with the pretty report. Start with the list of what is out today. Customer name, equipment, date it left, date it should come back, price and deposit. If that list is not trustworthy, no chart will save the week. Build it first, even if it is short. Twenty open contracts done properly are worth more than two hundred doubtful rows.
Then pick the pain. If the pain is the same machine promised twice, start with holds and availability. If the pain is a fight on return, start with the contract and the hour meter. If the pain is a surprise invoice, start with what the bookkeeper can see. Trying to cure all three on the same day is the classic way to cure none of them.
And agree one rule with the crew, said out loud: if it is not in the system, it was not agreed. The first fortnight will have grumbling. There will be old contracts still outside. There will be exceptions. Write the exception down and bring it in the same day. At the end of the month the Monday phone still rings. The difference is that the answer no longer depends on who remembers.
More guides are listed on the articles page.