Build rental rate tables

Every rental — retail or contractor — gets priced by the rate resolver, not by whatever a rep types into the quote. Rate tables is where you build the rules the resolver picks from. Set this up before you write your first rental agreement; an empty rate card means there's nothing for the resolver to price against.

Rate cards

A rate card is a named pricing book. Choose New rate card and set:

Name — e.g. "Standard retail 2026."
Audience — Retail or Wholesale. Wholesale cards price contractor/B2B rentals; retail cards price everything else.
Contractor (wholesale cards only) — optionally scope the card to one contractor customer instead of every wholesale account.
Set as default for its audience — the card the resolver falls back to when nothing more specific matches. Each audience needs exactly one default card.

A shop usually needs at least one retail card and, if it rents to contractors, one wholesale card.

The standard list

Once a card exists, add asset classes to it — the base price for each kind of unit you rent out. Choose Add asset class and set:

Asset class — the unit type this rate applies to (e.g. "Chiller — 30-ton").
28-day rate — the anchor rate for one rental cycle. The resolver prices every billing period off its own persisted figure; the card's ratio (if configured) derives Daily and Weekly from this number at rule creation.
Daily / Weekly rates (optional) — real, independently persisted rates for shorter billing periods. They are not display-only calculations and not derived from the 28-day rate unless you leave them to the card's ratio.
Minimum cycles (optional) — the shortest term you'll rent that class for, in 28-day cycles.
Note (optional) — anything worth flagging on the row, e.g. "run-hour metered."

Each period amount is its own stored number: setting a Daily or Weekly figure never changes the 28-day rate or a sibling period, and the resolver, quote preview, and billing all use the figures exactly as saved. Because the amounts are independent, you can build a graduated, non-linear schedule — a longer commitment at a cheaper effective per-day rate than any single ratio would give. For example, $500/day, $2,800/week, and $9,000 per 28-day cycle prices at about $500, $400, and $321 per day respectively: progressively cheaper the longer the rental.

The Daily/Weekly ratios on a rate card are an optional prefill convenience, not the price themselves. When you add an asset class with a ratio configured, Daily and Weekly auto-fill from the 28-day rate unless you type your own figures — anything you type wins, and a rule whose Daily/Weekly differ from the ratio is flagged "out of sync" in the table so hand-priced rows stand out.

Import CSV is not yet available. Add rate rules by hand for now.

How the resolver picks a price

A rental can match more than one rule — a customer-specific deal, a seasonal adjustment, a weekend surcharge, the plain standard list. When more than one applies, the resolver checks them in a fixed order and uses the first match, highest priority first:

Emergency premium
Weekend / holiday
Volume / long-term
Branch location
Seasonal
Project-specific
Customer-specific
Standard list

So a same-day emergency rental always prices off the emergency rule if one exists for that asset class, even if the customer also has a standing customer-specific rate — the more urgent, more specific rule wins. If nothing more specific matches, the rental falls back to the standard list you built above. This is the actual pricing logic the resolver runs at quote time and at every billing event — not a display-only summary.

Wholesale pricing

Contractor/B2B rentals price off a wholesale rate card the same way — same asset-class structure, same resolver, just scoped to the wholesale audience (and optionally to one contractor customer). Build a wholesale card the same way you build a retail one before quoting a contractor rental.

Reference

Who can reach Rate tables — Owners and Office users; Dispatchers and Technicians can't. See Roles & permissions.