Equipment rental is not selling stock — it is selling time on an asset that must come back, get inspected, get serviced and go out again. ERPNext core gives you Item, Serial No, Asset, Sales Order, Delivery Note and Maintenance Schedule, but none of them answer the question a hire desk fields fifty times a day: is this 5-tonne excavator actually free from the 14th to the 22nd, and if not, what is the nearest equivalent? A native Sales Order has no reservation window, the Stock Ledger has no concept of an asset that is owned but physically unavailable because it is on hire, rate cards collapse into a single Item Price rather than daily/weekly/monthly tiers with minimum-hire rules, and there is nowhere to record that the unit came back with a cracked screen and forty hours on the meter. Rental firms end up running the real business on a whiteboard and a spreadsheet while ERPNext holds only the invoice.

ECOSIRE builds a proper Frappe application — its own app on the bench, its own module, its own DocTypes — rather than a pile of Custom Fields bolted onto Sales Order. The core is a submittable Rental Contract DocType with a child table of hired units, each line carrying an equipment-unit link (backed by ERPNext Serial No or Asset, your choice at scoping), off-hire and on-hire datetimes, a rate card line and a computed charge. A whitelisted get_availability() method runs the overlap query against every open contract line and blocks a double-booking in validate, so the reservation board and the REST API tell exactly the same truth. Rate cards live in a Rental Rate Card DocType with tiered daily, weekly and monthly rates, minimum hire period, part-day rules, and customer- or contract-specific overrides; pricing resolution is a single server-side function, so the availability board, the quotation and the sales invoice can never diverge. Delivery and pickup become their own Rental Movement documents — out, return, exchange, site transfer — with driver, vehicle, planned window, signature capture and a condition checklist that writes back to the unit.

The technical wiring is deliberately conventional Frappe so your own team can maintain it. Doc events registered in hooks.py on Rental Contract and Rental Movement post the stock and accounting effects: on off-hire the unit's status flips and a Delivery Note or Stock Entry records the physical move; on return the condition checklist decides whether the unit re-enters the available pool or drops to Under Repair and raises an ERPNext Maintenance Visit or Job Card. Damage charges post as additional lines on the rental invoice with their own Item and tax treatment. Scheduler events run the overdue-return sweep, generate periodic hire invoices on long-running contracts, and refresh a nightly utilization snapshot so reports read a materialized table instead of scanning ledgers. Client scripts drive the reservation board — a calendar/Gantt view with drag-to-reserve — but every write goes through the same whitelisted methods any integration would call, so a telematics feed, a driver app or a customer portal inherits identical rules and identical permissions.

Permissions are modelled as real role profiles — Hire Desk, Yard and Logistics, Workshop, Rental Manager, Accounts — with user permissions scoping depot, branch or company so a branch controller sees only their own fleet. Reporting ships as Query and Script Reports plus a rental dashboard: utilization by unit, category and depot (on-hire days over available days, with workshop and off-fleet days excluded honestly rather than flattered), revenue per unit and per category, idle-asset aging, overdue returns, damage recovery and forward committed hire. Everything targets Frappe/ERPNext v15 and v16, is tested on the version you actually run, and ships as a versioned app with migration patches so bench update and bench migrate stay routine.

This is a build-to-order product, not a marketplace download. You request a quotation, we run a scoping call and agree in writing exactly which DocTypes, statuses, rate rules, movement types, integrations and reports belong in the first release, and we build against that scope. Typical delivery is one working week from confirmed scope. We install on a staging site first, run UAT with your hire desk and yard staff, then deploy to production with a documented rollback plan, hand over the git repository, and stay with you through an agreed post-go-live support window.