Rentiva v4.64.0 — Commission Rate Overrides (Vendor & Vehicle) and Tier Configuration

Admins can now override the commission rate per vendor or per vehicle, and configure the volume-discount tier thresholds directly from the admin panel — closing the last three previously UI-less layers of the commission rate hierarchy. Also includes three commission-accuracy fixes and a schema migration guard found during release verification.

New

• Vendor-level commission rate override. Set a fixed commission rate for an individual vendor from that vendor's detail page in Vendor Management — no need to touch every vehicle they list.
• Vehicle-level commission rate override. Set a fixed commission rate for an individual vehicle from a new "Commission Rate Override" box on the vehicle edit screen. This is the most specific layer — it takes priority over the vendor's rate, volume-discount tier, and the platform-wide rate.
• Editable volume-discount tiers. The three tiers that automatically discount a high-volume vendor's rate (based on trailing 30-day cleared revenue) can now be edited directly from the Commission tab, instead of only via direct database edits. See the Commission Rate Configuration guide for how the full 4-layer hierarchy resolves.

Fixes

• The vehicle-level override above is now actually applied to real bookings. The underlying resolver logic already existed but was never connected to live checkout processing.
• Refund commission clawbacks now use the rate the vendor was originally credited at, instead of whatever rate happens to be active on the day of the refund — a rate change between payment and refund no longer silently alters the refund math.
• The vendor dashboard's "last 7 days" revenue figures could show artificially low or negative numbers, because a commission credit that clears 7+ days after it's created could never land inside a rolling 7-day window while a same-day refund always could. A new internal timestamp now tracks when a credit actually cleared.
• The dashboard's revenue_7d metric had the same balance-lookup key mismatch that was fixed for the other Financial Summary cards in v4.63.2.
• Schema migration guard. Found during release verification (before this ZIP was published): a database schema-version constant hadn't been bumped alongside the new column that powers the 7-day revenue fix above, which would have silently prevented existing installations from ever receiving it. Fixed and verified against a simulated real upgrade before release.