Equipment Rental Management Application

The problem

Renting an asset is not selling it. The same crane, camera body, scaffold tower or party marquee goes out and comes back dozens of times, and every one of those cycles has to answer questions that a sales-oriented system was never built to answer: is this specific unit free between the 14th and the 19th, allowing for the day it takes to clean and inspect it? What is the rate when the customer keeps it for eleven days on a weekly card? How much deposit is held, and how much of it is released after a technician records a scratch on the housing?

Zoho Inventory models stock that leaves and does not come back. Zoho Books models an invoice, not a booking that overlaps another booking. Neither has a concept of a reservation window, a return condition, a security deposit held against a customer, or a late-return penalty. So rental businesses end up running the actual operation on a wall planner or a shared calendar, and using Zoho only to raise the invoice afterwards — which means double-bookings, deposits nobody can account for, and equipment that is out for three weeks before anyone notices.

What ECOSIRE builds

ECOSIRE builds an equipment rental management application inside your own Zoho environment. It is written for your fleet, your rate card and your contract terms. Nothing here is downloadable off the shelf.

Assets, categories and serialised units

A Zoho Creator data model separates the rentable item type from the individual unit. A category holds the rate card and the specification; each physical unit carries its own serial or asset tag, purchase date, current condition grade, service history and location. Bulk consumables that rent by quantity rather than by serial are modelled separately so a booking for twenty chairs does not require twenty records. Where the asset also exists in Zoho Inventory for purchasing and valuation purposes, the Inventory Item is linked by ID through the Inventory REST API so you are not maintaining two catalogues by hand.

Availability and reservations

The availability engine is the core of the build. Bookings are stored as dated reservation lines against a unit or against a category with automatic unit assignment at dispatch. Deluge functions check every proposed booking against existing reservations, maintenance blocks, buffer periods for cleaning, inspection or transport, and any blackout dates you define. Overlaps are rejected at save time rather than discovered later. A Sigma widget renders the calendar — units down the side, dates across the top, colour-coded by state — with drag-to-extend and conflict highlighting, because a standard Creator report cannot express a Gantt-style planner.

Quotes and holds are supported as distinct states: a soft hold expires automatically after a configurable window and releases the unit back to availability through a scheduled Deluge function, so tentative enquiries do not silently sterilise your fleet.

Rate cards and time-based billing

Rates are configured per category and per customer tier: hourly, daily, weekly, monthly, with your own tapering rules — for example, four days billed as a week if that is cheaper for the customer, or a minimum charge period. Add-ons such as delivery, collection, operator time, insurance waiver, fuel and consumables are separate chargeable lines. Extensions and early returns are recalculated against the same rate engine so the price is derived, never typed. The rate logic lives in one Deluge function so a change to your commercial terms is a change in one place.

Invoices are raised in Zoho Books through the Books REST API against the Customer record — either per rental at return, on a periodic cycle for long-term hires, or on a scheduled billing run for open contracts. Where VAT or GST applies, the tax rate and place-of-supply treatment are set on the Books item and the Books organization's tax configuration rather than being recomputed in Creator, so your filings come from Books as they always have. Deposits are handled explicitly: a deposit is recorded against the rental agreement and reflected in Books as a customer advance or retainer, then applied, refunded, or partially forfeited on settlement with the reason recorded.

Check-out, check-in and damage

Dispatch and return are structured processes, not a status flag. At check-out, the application produces the rental agreement PDF from a Creator print template, records the assigned units, captures accessories going out, logs meter or hour readings, and takes signature and condition photographs against the unit record. At check-in, a technician records returned condition, meter delta, missing accessories and any damage, with photographs stored against the return. A damage record can create a chargeable line — repair cost, cleaning fee, replacement of a missing part — which is either deducted from the deposit or invoiced separately in Books, with the customer receiving a settlement statement showing exactly what was withheld and why.

Late returns are detected by a scheduled function that compares expected return dates against actual check-in and applies your late-fee rule automatically, while notifying the account owner.

Maintenance, service and utilisation

Units accumulate usage. Service intervals defined by elapsed days, rental cycles or meter hours raise maintenance tasks and block the unit from booking for the service window. Off-hire, written-off and under-repair units drop out of availability without being deleted, so historic bookings remain intact. Dashboards report utilisation per unit and per category, revenue per asset against its purchase cost, damage frequency, and the units that never move — the report that usually justifies the whole project.

Customer-facing and integration surface

A Zoho Creator portal can give account customers their own view: current hires, expected return dates, historic invoices, and a request form for extensions or new bookings that lands as a reservation request rather than an email. Zoho CRM holds the customer, the opportunity and the account manager, with Deluge and Zoho Flow linking a won deal to a reservation. Zoho Flow handles cross-app automation such as return reminders and post-hire follow-ups. Where you need SMS reminders or a signature service, it is integrated over its REST API from Deluge using your own credentials.

Who it is for

Construction plant and access-equipment hire; audio-visual, camera and event-production rental; scaffolding and formwork; medical equipment hire; party, marquee and furniture rental; tool libraries and equipment-sharing operations; any business where the same asset is billed repeatedly by time rather than sold once.

How delivery works

1. Scoping call. We go through your fleet structure, rate card, deposit and damage policy, contract documents, delivery model and the Zoho applications you already run. We ask for a sample rate card and a sample rental agreement. 2. Fixed quote. You receive a written scope covering the data model, availability rules, rate engine, Books integration, documents and portal, with a fixed price. Work begins only on your approval. 3. Build. ECOSIRE develops the Creator application, the availability and rate engines in Deluge, the Sigma calendar widget, the Books and Inventory integrations and the Flow automations. Typical build time is 2 to 4 weeks depending on scope. 4. Install in a test environment. Deployed to a test Creator environment with a copy of your fleet and sample bookings. You run a full cycle — quote, hold, booking, dispatch, extension, damaged return, deposit settlement — before touching live data. 5. Production go-live. After sign-off, deployment to your production Zoho org, migration of the current fleet, open hires and outstanding deposits, and configuration of user roles and portal access. 6. Support window. A post-go-live support period for defect fixes and configuration adjustment, on the terms stated in your quote.

The application lives in your own Zoho account. Deluge source, widget code and documentation are handed over to you.