Rental Extensions, Modifications, and Early Returns

Static reservations are rare in real fleets. Customers will ask to extend, shorten, or shift booking windows. This guide defines a predictable decision model that protects utilization, customer trust, and billing accuracy.

Supported Change Types

---

Extension Eligibility Checks

Before approving any extension, run these checks in order:

1. Availability conflict check: Confirm no overlap with confirmed reservations, maintenance blocks, or external calendar events.
2. Financial check: Confirm payment method validity and deposit sufficiency for revised exposure.
3. Policy check: Confirm maximum duration limits and any subaccount-specific extension rules.
4. Risk check: Confirm no unresolved incident, violation hold, or payment delinquency.

If any check fails, deny extension and present alternatives (nearby vehicle, new booking, manual support).

---

Re-Pricing Rules for Extensions

Extension pricing should be recalculated from the original start time through revised end time using your active rate model.

Practical Rules

• Preserve the original base rate structure when possible for transparency.
• Re-evaluate duration boundary transitions (hourly to daily, daily to weekly).
• Apply active dynamic pricing rules only to newly added time unless your policy states otherwise.
• Keep surcharge logic tied to actual usage and check-out readings.

Example

---

Mid-Rental Modifications

When a rental is already active:

• Show updated total estimate before confirmation.
• Notify customer of any additional hold/authorization attempt.
• Log who approved the change (self-service or operator).
• Keep a before/after timeline snapshot for audit and dispute defense.

For failed or offline command paths during the update, follow Smartcar Outage Runbook.

---

Early Returns

Early returns should end the rental cleanly and release inventory quickly.

Recommended Handling

If you offer early-return credits, make them explicit in booking confirmation and receipt text.

---

Reschedules Before Pickup

Reschedules are lower risk than mid-rental changes and should follow clear limits:

• Define cutoff windows (for example, no reschedules within X minutes of pickup).
• Re-run full availability and pricing checks for the new window.
• If new pricing differs, require explicit customer confirmation.
• Preserve the existing reservation ID when possible for cleaner reporting.

---

Operator Overrides and Audit Trail

Manual changes are sometimes necessary for support recovery.

Every override should record:

• Operator user and role
• Original booking window and revised window
• Reason code (customer request, ops recovery, outage, goodwill, etc.)
• Fee waived/applied fields
• Timestamp and source channel

This metadata is essential for chargeback defense and internal QA.

---

Notification Strategy for Changes

Send updates immediately when a change is approved or denied.

See Notifications and Alerts for channel configuration.

---

Edge Cases to Handle Explicitly

• Extension request while vehicle is outside return/service policy area
• Extension request with stale telemetry
• Early return during active incident case
• Repeated extend-by-small-increments behavior (abuse prevention)
• Reservation modification when payment retry is pending

Clear operator playbooks reduce inconsistent decisions.