Levy Bookings Overview

Levy Bookings is the booking-funnel layer on top of the Levy Fleets reservation engine. It ships in three surfaces that all read and write the same reservations table, the same pricing tiers, the same agreements, and the same Stripe routing:

1. Hosted booking page at fleets.levyelectric.com/book/{slug} (or your own custom domain).
2. Embeddable JavaScript widget that drops onto Squarespace, Wix, WordPress, Webflow, Shopify, or hand-coded sites with a single <script> tag.
3. iPad POS progressive web app that runs at the counter for walk-in rentals, pickups, and returns.

You can use any one of these surfaces on its own, or run all three at once. A booking taken on the hosted page is the same kind of record as a booking taken on the iPad, and both flow through the same pickup queue, the same waiver, and the same Stripe connected account.

What you can build with Levy Bookings

You do not have to choose one. Most design-partner shops run the hosted page plus the iPad POS, and add the embedded widget once their site is ready.

Booking modes supported

The booking engine supports all of the rental shapes Levy operators sell today:

• Instant hourly — "Right now, 2 hours." Customer pays, walks to shop, scans QR.
• Time-slot — "Saturday 10am pickup, 4-hour rental."
• Multi-day — "Monday morning through Wednesday evening."
• Tour / group — Block N vehicles of one model at a single start time, single payer.
• Recurring tour schedule — "Sunset Tour, every Wed/Fri/Sat at 6pm, 8 vehicles."

Each booking is a single reservation row that follows the existing lifecycle (pending → confirmed → checked_in → active → completed). That means refunds, partner payouts, tax remittance, and IoT unlock all work exactly like they do for any other reservation.

Payments and routing

Levy Bookings uses your subaccount's existing Stripe connected account. Online payments (hosted page and widget) run through Stripe Elements with Apple Pay, Google Pay, and Link enabled. In-person payments (iPad POS) run through Stripe Terminal — either a BBPOS WisePOS E card reader, or Tap to Pay on iPhone with no extra hardware.

Processing fees flow into your existing net-revenue and partner-payout calculations. Nothing about how money lands changes.

What you get out of the box

• A booking page at /book/{slug} the moment you turn on a widget.
• A drop-in <script> snippet that loads in under 100 KB and renders in under 200 ms on a 3G simulation.
• Three starter themes (Light, Dark, Minimal) and eight CSS variables you can override for full brand alignment.
• Promo codes (percent, fixed-amount, free-add-on) with redemption limits and date windows.
• Refundable security deposits via Stripe pre-auth — released automatically on a clean return.
• B2B / corporate accounts with pre-negotiated rates and NET-30 Stripe Invoicing.
• iPad POS with Stripe Terminal, QR-scan-to-assign, pickup queue, return checklist, and offline shell.
• Email + SMS confirmation with an ICS calendar attachment.
• Waiver signing inline (signature pad) — no DocuSign round-trip.

How the surfaces share data

Operator dashboard
  ├── Widgets             — create, theme, embed-code generator
  ├── Promo Codes         — discount, expiry, redemption cap
  ├── Tours               — recurring schedule + RRULE engine
  ├── B2B Accounts        — pre-negotiated rates, NET-30 invoicing
  └── POS                 — pair iPads, see live pickup queue
                                          │
                                          ▼
              ┌─── Hosted page  ─┐
              │                  │
   /book/{slug}     /embed/{slug}     /pos/{slug}
              │                  │
              └─── shared engine ┘
                          ↓
   reservations · pricing_tiers · agreements · stripe (connected acct)

Every change you make in the dashboard — a new promo code, a theme tweak, a new tour departure — is visible immediately across all three surfaces. There is no separate "widget database."

Strategic moat

Other booking platforms (FareHarbor, Peek Pro, Bookeo, Lightspeed Booking) stop at "the customer paid you $80." Levy Bookings keeps going: the same booking issues a QR pickup ticket, assigns a specific vehicle when the customer arrives, unlocks it from the iPad, geofences the return, and auto-charges late fees through the same IoT plumbing every Levy operator already uses. Booking platforms cannot replicate this; the IoT vendors cannot ship a booking funnel as fast as we can.

Related guides

• Getting Started
• Hosted Booking Page
• Embedding the Widget
• Widget Theming
• iPad POS Setup
• iPad POS Workflow
• Tour Scheduling and Recurrence
• Group Bookings
• B2B Corporate Accounts
• Promo Codes and Deposits
• Troubleshooting
• FAQ