Run the day · The fleet, booked out instead of sitting

Equipment rental, quote to return.

The same fleet you already maintain, booked, priced, and billed instead of just installed. This is early access: the resolver, reservations, and utilization tracking are real; the depth is still landing.

Early accessTwo ideas on the roadmap

See the reservation register What's built vs. what isn't

What it is

A rental agreement in Thermal books a piece of equipment out to a customer instead of — or alongside — installing it at a site: a spot cooler, a genset, a chiller, a cooling tower, drawn from the same fleet record the rest of the platform already tracks. The agreement holds the customer, the unit, the term, and a rate resolved automatically at creation — never a stale or hand-typed number.

This is early access: the pricing resolver, the reservation calendar, and the utilization dashboard are real and running, but the module isn't turned on for every org by default and some workflow edges — partial accessory returns, per-customer payment terms — are still landing.

Where rentals sit on the spine.

A rental agreement runs against the same equipment record the rest of Thermal tracks, generates a work order when a unit deploys, returns, or swaps mid-rental, and bills on a recurring cycle.

01Customer
One account. Every site under it.
02Service site
The address, and the branch that covers it.
03Installed equipment
The fleet record a rental books out.
You are here
04Service agreement
A rental can grow into a recurring contract.
05Work order
Deploy, return, and swap generate work orders.
06Invoice
Billed on the rental cycle.

The fleet is the same equipment record the service side of Thermal maintains — a unit generates its own work order when it goes out or comes back, and the invoice runs on the rental cycle.

ThermalDispatchAgreementsEquipment

Illustrative rental reservation register — interface mock, not customer data
Agreement	Asset class	Unit	Term	Rate basis	Status
RT‑114	Spot cooler	EQ‑2211	2026‑08‑01 → 10‑01	Retail · 28-day	Overlapping booking
RT‑116	Genset	EQ‑2305	2026‑08‑10 → 08‑24	Wholesale · 28-day	Deployed
RT‑117	Chiller	EQ‑2320	2026‑09‑01 → 12‑01	Retail · 28-day	Reserved
RT‑118	Cooling tower	EQ‑2331	2026‑07‑20 → 08‑20	Wholesale · 28-day	Return due
RT‑120	Genset	EQ‑2306	2026‑08‑05 → 09‑02	Retail · 28-day	Reserved

Illustrative interface mock — not customer dataExceptions sort first: booking conflicts, units off-return

Real backends, early-access depth.

Six pieces of the rental workflow — genuinely running, but this module is early access end to end, not a finished commercial rental system yet.

Early access

Rate tables, resolved automatically

Build named rate cards — retail or wholesale, by asset class — and the resolver picks the right one at quote time from a fixed priority order: emergency, weekend/holiday, volume, branch, seasonal, project, customer, then the standard list. The rate on the agreement is resolved at creation, never a stale or hand-typed figure.

TodayRate-card priority resolution by asset class
Limit28-day billing cycle; daily/weekly figures are a calculated display only

Early access

Reservations, checked live

Book a future date range against an asset class and Thermal checks every unit in that class live against existing bookings — no separate availability step — with a Gantt-style timeline and a weekly-aggregate view for quoting ahead. If the class is booked out, the check says so before a promise goes to a customer.

TodayLive availability check, Gantt timeline, weekly aggregate

Early access

Utilization, tracked per unit

A fleet-level utilization view shows how hard each asset class is working, so a decision to add or retire a unit is based on actual booked time instead of a gut call. The same view makes it obvious which units are paying for the lot and which are just sitting on it, which is exactly the kind of number a rental decision needs.

TodayFleet utilization dashboard, per asset class

Early access

Retail and wholesale, on the same fleet

Retail day-rate rentals and wholesale contractor rentals share the same fleet and resolver, priced off separate rate cards — the pricing and the relationship differ, not the underlying equipment record. One unit can serve both kinds of customer without a second asset register.

TodayShared fleet, separate retail and wholesale rate cards

Early access

Deploy, return, and swap

Moving a unit out, back, or to a replacement asset mid-rental generates its own work order in the same transaction as the movement — a swap on an active rental doesn't lose the agreement's billing history. The service side of Thermal sees the movement too, because it's the same work-order record.

TodayDeploy/return/swap each generate a work order, same transaction

On the roadmap

Off-rent credits & competitive rate rules

Automatic credits for early returns and rules that react to a competitor's posted rate are a speculative idea on the public roadmap — not built, not scheduled.

PlannedEarly-return credits, competitor rate rules — speculative
Not yetNothing on this row is built or scheduled

What rentals will not do.

Three boundaries that matter most on the page furthest from shipped.

It won't bill by the day or week

The rate a shop actually sets and the resolver prices from is a 28-day figure. Daily and weekly numbers shown are a calculated display only, derived from that rate — not separately settable billing periods yet. CSV rate-table import isn't available either.

It won't auto-convert a portal quote into a rental

A reservation is a hold on a unit's future availability. Writing the rental agreement itself — customer, term, resolved rate — is still a separate step once the unit actually goes out; the quote-to-rental auto-convert path isn't dependable yet.

It won't credit an early return or match a competitor

Both are speculative ideas on the public roadmap, not built. A return closes out the agreement and stops the billing cycle; there's no automatic credit or rate-matching logic. See the roadmap for where they sit.

If a capability isn't on this page, assume it isn't built. We'd rather lose a deal on a missing feature than win one on a sentence that turns out to be aspirational.

What rentals touch.

A rental runs on the same fleet, work-order, and invoice records the service side of Thermal uses.

Reads from

EquipmentThe fleet record a rental books out.
InventoryAccessories and consumables on the rental.
DispatchDeploy/return/swap generate work orders.

Writes to

InvoicingBilled on the recurring rental cycle.
DispatchMovement work orders land here.
Customer portalCustomers see their rental history.

Sits beside

Service agreementsA rental can grow into a recurring contract.
Quoting & proposalsQuote-to-rental starts here.
The whole platformTwelve pages, one spine.

Questions a fleet owner asks.

The ones that come up when a shop is deciding whether to run rentals at all.

Is rentals a finished, general-availability feature?

No — it's early access. The rate resolver, reservation calendar, and utilization dashboard are real and running, but the module isn't on for every organization by default and some workflow edges are still landing.

Can I bill a rental by the day or week instead of a 28-day cycle?

How does a reservation become a billed rental?

A reservation is a hold on a unit's future availability, checked live against existing bookings. It can link to a rental agreement, but writing the agreement itself — customer, term, resolved rate — is still a separate step once the unit actually goes out, and the quote-to-rental auto-convert path isn't dependable yet. That gap is stated plainly because it changes how you plan the workflow.

Does Thermal automatically credit an early return or react to competitor pricing?

No — both are speculative ideas on the public roadmap, not built or scheduled. Today, a return closes out the agreement and stops the billing cycle; there's no automatic credit or rate-matching logic, so a shop shouldn't price an agreement as if there were.

Does a rental run against the same equipment I already maintain?

Yes — the rental fleet is the same equipment record the rest of Thermal tracks, not a separate rental-only system. A unit generates its own work order when it deploys, returns, or swaps mid-term, and its service history stays on the unit the whole time.

See where rentals stands today.

An honest walkthrough of what's built, what's early access, and what's still roadmap — no rental is priced on a promise here.

Book a demo Explore the platform