beginner
shop-rentals
overview
walk-in

Shop Rentals Overview

An end-to-end rental operating system for brick-and-mortar bike and scooter shops — walk-ins at the counter, online bookings via embed widget, waivers, refunds, gift cards, and damage tracking

Levy Fleets TeamMay 7, 20267 min read

Shop Rentals turns Levy Fleets into a complete operating system for a brick-and-mortar bike or scooter rental shop. If your shop currently runs on FareHarbor, Booqable, or a paper clipboard plus a spreadsheet, this is the module that replaces all of that.

What it includes

  • A counter Desk showing today's pickups, returns, and assignment queue
  • A walk-in POS wizard that takes a customer from search to active rental in five steps
  • A public booking page — your own branded URL for customers to reserve online
  • An embeddable widget — a single <script> tag that adds a "Book a rental" button to your existing website
  • Per-rental waivers with a typed-name signature flow that customers complete on their own phone
  • Add-ons — helmets, locks, child seats, delivery, insurance — sold alongside the rental with bookable inventory
  • Gift cards issued and redeemed at checkout
  • Damage logging at return time, with photo URLs and per-incident charges
  • A service log per vehicle — maintenance, damage, out-of-service events
  • Refunds that respect the same accounting discipline as our shared-mobility module: every refund is recorded against the reservation, never directly against the wallet

Who it's for

Shop Rentals is for owned-fleet rental operators — typically bike shops, e-scooter rental kiosks, and resort concessionaires. The audience is distinct from the shared-mobility (Car Sharing) audience that uses unlock codes, GPS tracking, and zone-based pickup.

If your business is "a customer rents a specific bike for a known time window from a known counter," Shop Rentals is the right module. If your business is "the customer unlocks any nearby vehicle via the app and rides it," use Car Sharing instead.

How it relates to Advanced Bookings

Advanced Bookings covers the model-level inventory primitives Shop Rentals is built on — pricing tiers, deposits, free-cancellation windows, capacity caps. If you want to understand the underlying reservation model, read that overview first. Shop Rentals layers an opinionated bike-shop UX on top.

The five surfaces you'll spend time on

  1. The Desk at /dashboard/shop-rentals — your home base. KPI tiles, today's manifest, assignment queue, and shortcuts to common counter actions.
  2. Walk-in at /dashboard/shop-rentals/walk-in — the iPad-friendly checkout flow for customers walking through the door.
  3. Bookings at /dashboard/shop-rentals/bookings — search, filter, and drill into any reservation.
  4. Calendar at /dashboard/shop-rentals/calendar — month grid showing every reservation and out-of-service block.
  5. Public Booking at /dashboard/shop-rentals/public — configure your customer-facing booking page and embed snippet.

Setup checklist

Before you take your first booking, complete the setup guide:

  1. Create a pickup location for your shop
  2. Define vehicle models and add vehicles with serial numbers
  3. Set inventory caps — how many of each model you'll allow per location
  4. Configure a pricing tier with hourly/daily/weekly rates and deposit amounts
  5. Create an agreement template — your rental waiver
  6. Add add-ons if you sell helmets, locks, or accessories
  7. (Optional) Enable the public booking page and copy the embed snippet onto your website

Once that's done, your shop is ready to take walk-ins and online bookings.

What's not in Shop Rentals (yet)

  • Stripe Elements card capture inside the walk-in wizard — for now you attach a card to the customer profile via the operator-driven SetupIntent flow before charging. End-to-end at-the-counter card capture is on the roadmap.
  • OTA distribution (Viator, GetYourGuide, Expedia) — explicitly out of scope. Shop Rentals targets direct bookings via your own site.
  • Multi-location operating hours UI — the schema supports per-location hours and blackouts; the configuration UI is a fast-follow.
  • SMS reminders to customers — email confirmations work today; SMS is queued.

These gaps are documented in the internal FareHarbor parity scorecard and on the public roadmap.

Where to next