Is the Reservations System Right for You?

Suprata started life as a service-business platform — jobs, dispatch, invoices. Reservations is a different animal sitting alongside all of that. It's built for businesses that rent the same physical thing to different people across a calendar, not for businesses that send a tech to a customer's site to do work.

Turn it on if you need it and you'll save hours of spreadsheet work every month. Turn it on if you don't and you'll just have extra menus to ignore. This article helps you decide.

When you'd use this

The Reservations system is the right tool when all of these are true:

You have a fixed set of physical assets that customers book (slips, sites, cabins, units, equipment).
A customer occupies one of those assets for a defined time window — overnight, by the week, by the month, or seasonal.
Two customers can't use the same asset at the same time, so you have to prevent double-booking.
You bill in patterns that map to occupancy: nightly rates, monthly settlements, deposits up front, utility metering, late fees on overdue balances.

Concretely, that means:

Marinas renting slips (wet, dry, covered, fixed-length) by the night, month, or season.
Campgrounds and RV parks renting sites with hookups (30-amp, 50-amp, full hookup, primitive).
Cabin and cottage rentals — short-term and long-term.
Self-storage operators renting units month-to-month.
Equipment and asset rental where assets have schedules — boats, jet skis, kayaks, trailers, mooring balls.
Mooring fields, dry-stack racks, slip-share programs — anything where the asset is the unit of inventory.

The reservations grid — your central worklist for active and upcoming bookings

When it's the wrong tool

Don't turn on Reservations for these:

One-off service jobs. You send a tech to a customer's address, do work, leave, invoice. That belongs in the Jobs area, not Reservations. Reservations are about the customer coming to your asset; jobs are about you going to the customer.
Pure appointment scheduling. A 30-minute consultation, a haircut, a piano lesson — that's calendar/dispatch territory, not Reservations. Reservations are for booking physical things; appointments are for booking staff time.
Inventory you sell rather than rent. If a customer takes the asset and never gives it back, that's pricelist inventory, not Reservations.
Memberships with no specific slot assigned. If your "members" pay a monthly fee for general access but don't occupy a specific slip or site, set them up as recurring invoices instead of reservations.

How Reservations fit together

Five entities do most of the work — understand these and the rest follows:

Asset Type — a category of bookable thing. "30-amp Pull-Through Site." "Wet Slip 35-foot." "Storage Unit 10x10." Asset types carry default rules: pricing, required documents, default deposit, late-fee policy.
Asset — an individual physical thing of some type. Slip A-12. Site 47. Unit 203. Each asset belongs to one type and (optionally) sits at a coordinate on a property map.
Reservation — one customer booking one or more assets across a date range. Each reservation carries its own deposit, balance, charges, audit-walk findings, and invoices.
Package — an optional bundle of asset + add-ons + services sold as a single unit. "Holiday Weekend 3-Night Premium" is a package. Packages save data entry on common booking shapes.
Map — an optional uploaded image (your aerial photo, marina layout, campground plan) with assets pinned at coordinates. Maps make booking visual.

Around those, the system layers:

Meters for billing electric, water, or sewer dump usage.
Audit walks for periodic property inspections.
Documents required per asset type (insurance certificates, ID, vessel registration).
Late-fee rules and deposit-compliance tracking.
A public waitlist for when you're full.

You don't have to use all of these. Most operators start with asset types, assets, and the booking wizard, then layer on maps and meters once the basics are humming.

The "is it worth it?" gut check

Reservations is the largest and most opinionated area of Suprata. Turning it on means at minimum:

Defining your asset types and entering every asset (a few hours for a small marina, a day for a large RV park).
Walking through the setup wizard (an hour).
Training front-desk staff on the booking wizard (a half day).
Wiring up deposits, late fees, and document requirements to match your actual policies.

If you have fewer than ~10 bookable units and stay 100% full with the same long-term tenants, you can probably get by with recurring invoices and a paper occupancy chart. The Reservations system pays off when:

You turn over inventory frequently (transient bookings, weekend stays).
You have mixed tenancy — some monthly tenants, some weekly, some overnight.
You're already losing time on double-bookings or "is site 12 free Saturday?" phone calls.
You need to bill utilities to tenants based on metered usage.
You need an audit trail of deposits and compliance documents (insurance certs, vessel registrations) for regulatory or insurance reasons.

What it costs to leave it off

If Reservations clearly fits your business and you skip it, here's what you'll end up rebuilding by hand:

A whiteboard or spreadsheet of who's in which slot when. (Reservations has the timeline view.)
A manual deposit log with sticky notes about who's paid and who hasn't. (Reservations has deposit compliance tracking.)
An ad-hoc month-end process where you re-key pro-rated charges by hand. (Reservations runs settlements for you on a schedule.)
A folder full of expiring insurance certificates you have to chase manually. (Reservations sends you alerts when documents are about to lapse.)

Every one of those is a place where small errors pile up quietly until they all show up at month-end.

Common mistakes when deciding

Treating Reservations as "the only way to book anything." It's not. If you also do mobile service work, run Reservations and the Jobs area side-by-side. They're independent.
Turning it on "just to see." Half-configured Reservations creates noise — empty asset types, half-finished maps, deposit rules that don't match policy. If you're not committed to a 1–2 week setup project, leave it off until you are.
Trying to model service appointments as reservations. "I need to book the customer for a 9 AM service call" is a job, not a reservation, even though the word "book" appears. Reservations are about which physical asset is occupied; appointments are about which tech is busy.
Skipping asset types. Every asset must belong to a type. People sometimes try to make every slip its own one-off type. That defeats the purpose — types exist to share defaults across many assets. (See Setting up asset types.)
Underestimating long-stay billing. If you have monthly tenants, settlements, late fees, and proration are essential and complex. Read Long-stay billing and settlements before going live with monthly customers.

Recommended starting path

If after reading this you're confident Reservations fits, follow this order:

Setting up asset types — define your categories first.
Creating your first asset — add one real asset and book it before adding more.
The booking wizard walkthrough — learn the booking flow end-to-end.
Handling deposits — get money handling right before going live.
Add the rest — maps, meters, audit walks, late fees — as needed.