Availability by date range
Per-unit availability calendars with turnaround time, overlapping-booking prevention and stock that is reserved for a period rather than decremented.
Rental software development for equipment, vehicles, products and rental e-commerce. Availability by date range, rental pricing tiers, deposits, returns and damage handling built into the transaction — because a rental that is modelled as a sale will fail on the second booking of the same item.
Selling moves an item once. Renting moves it out and back, repeatedly, and the software has to know where it is on every date in between.
Per-unit availability calendars with turnaround time, overlapping-booking prevention and stock that is reserved for a period rather than decremented.
Daily, weekly and monthly tiers, seasonal rates, long-hire discounts and minimum periods computed on the range the customer actually picked.
Security deposits, pre-authorisations, rental agreements, late fees and the return workflow that closes the hire and frees the unit.
Serial numbers, maintenance windows, damage records and unit history, so a machine out for service is out of the availability pool automatically.
A storefront where picking dates comes before adding to cart, built headless over a commerce platform so the rental rules stay in one place.
Usually not in pricing. Usually in knowing what is actually free next Tuesday.
The website, the depot and the phone each answer differently about the same week.
Two hires overlap by a day because the turnaround time was never modelled.
A standard e-commerce platform was used as-is, and rental dates were bolted on as a custom field.
Nobody can say which deposit is still held, and disputes are settled from memory.
A unit is booked while it is in the workshop, and the customer finds out on collection day.
Weekly and monthly rates are quoted over the phone and rarely match the website.
A React storefront for rental commerce: date ranges, availability and returns built into the transaction rather than bolted beside it.
Read the case study →The same availability engine applied to property: units, nights, pricing rules and operations across many operators.
Read the case study →Yes, if the rental rules are built into the commerce layer rather than the theme. The catalogue, pricing and order model carry the date range, and the storefront reads them over GraphQL. That is exactly the shape of the Dcey build.
They are handled at the gateway, tied to the rental record. The deposit is authorised at booking and captured or released at return, so the finance side matches the physical side without a manual reconciliation.
Yes — most rental businesses sell as well as hire. The same platform can carry both, with rental attributes on the products that need them and a normal checkout for the ones that do not.
Tell me what you are trying to build, automate or scale. You get a straight answer on fit within a day — and a name to call if it is not me.