Help / FAQ

Rental OS Help

A short guide to the core Rental OS flow: organization, equipment, clients, bookings, availability, handover, and plan access.

Start

These terms set the context for working in Setvio.

What is the organization context?

The organization context connects equipment, clients, bookings, team, plan, and settings for the active rental house or production house.

Open operations

What is Rental OS?

Rental OS is the operational part of Setvio for rental teams: inventory, clients, bookings, availability, and handover.

Rental OS

How is Rental OS different from Production OS?

Rental OS handles equipment, clients, bookings, availability, and handover. Production OS handles projects, roles, crew, and project requests.

How it works

Booking vs project request

A project request is demand coming from a project. A booking is the real rental record with client, dates, gear, and operational statuses.

Bookings

Rental basics

The minimum needed for the first self-serve flow: equipment, client, booking, and availability review.

How do I add equipment?

Add an item manually in Equipment or start with import. Name, category, and day price are enough for the first booking.

Equipment

How do I import equipment?

Download the CSV template, upload your file, check mapping and validation, then import valid rows.

Import equipment

How do I add a client?

Go to Clients and add a contact. You can also quick-add a client while creating a booking.

Clients

How do I create a booking?

In Bookings, choose the client, dates, and equipment. The booking starts as pending, and availability blocks only after confirm.

Create booking

Booking statuses

The status tells you where a booking is in the flow and whether availability is already blocked.

oczekuje

The booking exists but is not confirmed yet. Availability is not reserved.

potwierdzona

The booking was confirmed. Availability is reserved for the booking dates.

do-przygotowania

The booking is confirmed and waiting for set preparation.

gotowe-do-odbioru

The set is prepared and can be checked out to the client.

wydane

Gear was checked out to the client and is outside the warehouse.

czesciowo-zwrocone

Some gear has returned or needs review. Check the checklist and item issues.

zwrocone

Gear has returned and the booking is operationally closed.

anulowane

The booking was canceled. Linked availability blocks should be released.

problem

The flow needs manual review, usually because of a conflict, missing item, damage, or incomplete return.

Availability

Availability is blocked only by a concrete block source, not by merely adding gear to a draft.

When is gear only in a booking?

After booking creation, gear exists only in booking_items. That shows the planned reservation, but it does not block availability by itself.

Bookings

When is availability reserved?

Availability is reserved after booking confirmation. Confirm creates booking-linked availability blocks for the booking dates.

Availability

What is preflight?

Preflight checks dates, items, and conflicts. It is a safety check before confirm, not an equipment reservation.

Bookings

What should I do with a conflict?

Check preflight, review the colliding bookings or manual blocks, then decide: change dates, swap gear, or do not confirm the booking.

Availability

Handover

Handover guides warehouse work from set preparation through return and issue review.

Prepare

Prepare builds a checklist from internal booking_items and marks the set as needing preparation.

Ready

Ready means the set is ready for pickup. It is an operational step and does not change availability blocks.

Checkout

Checkout marks gear as issued to the client. Availability blocks still come from the confirmed booking.

Return

Return records the return, condition, missing items, and damage. After review, the booking can move to history.

Damaged / missing

Record damaged/missing on items in checklist view. The issue remains for manual review before the flow is closed.

Bookings

Plans / access

Plan and role decide which operational actions are enabled.

Free / Beta

Free/Beta can limit equipment, members, or operations. Locked states show the scope of the active package.

Pricing

Pro

Pro unlocks a broader Rental OS and organization operations scope. Check pricing or the organization plan page for details.

Plan

Staff / member limitations

Staff can handle some operations, but confirm/cancel and plan changes may require owner/admin. Member usually has view or limited access.

Plan

Ask owner/admin

If you see a lock, ask an owner or admin to change the plan, change your role, or perform the action for you.

Contact support

Trust / beta

The beta is ready for controlled use, while some operations still require owner or support involvement.

How does Setvio handle data?

We explain which data can enter an organization in Setvio, how to contact us about data, and what not to put into staging/demo without consent.

Privacy

What are the usage terms?

Terms explain early access, responsibility for data entered into the system, beta availability, and how to contact us about issues.

Terms

What are the beta limits?

Review what remains manual or incomplete in beta: billing, mobile web, PDF/protocols, barcode, and discovery surfaces.

Beta limits

Contact

When the flow is unclear or you need a plan change, contact is the quickest path.

How do I contact support?

Use the Contact page. For plan questions include plan context, and for bookings include the booking reference.

Contact support