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 operationsHelp / FAQ
A short guide to the core Rental OS flow: organization, equipment, clients, bookings, availability, handover, and plan access.
These terms set the context for working in Setvio.
The organization context connects equipment, clients, bookings, team, plan, and settings for the active rental house or production house.
Open operationsRental OS is the operational part of Setvio for rental teams: inventory, clients, bookings, availability, and handover.
Rental OSRental OS handles equipment, clients, bookings, availability, and handover. Production OS handles projects, roles, crew, and project requests.
How it worksA project request is demand coming from a project. A booking is the real rental record with client, dates, gear, and operational statuses.
BookingsThe minimum needed for the first self-serve flow: equipment, client, booking, and availability review.
Add an item manually in Equipment or start with import. Name, category, and day price are enough for the first booking.
EquipmentDownload the CSV template, upload your file, check mapping and validation, then import valid rows.
Import equipmentGo to Clients and add a contact. You can also quick-add a client while creating a booking.
ClientsIn Bookings, choose the client, dates, and equipment. The booking starts as pending, and availability blocks only after confirm.
Create bookingThe status tells you where a booking is in the flow and whether availability is already blocked.
oczekujeThe booking exists but is not confirmed yet. Availability is not reserved.
potwierdzonaThe booking was confirmed. Availability is reserved for the booking dates.
do-przygotowaniaThe booking is confirmed and waiting for set preparation.
gotowe-do-odbioruThe set is prepared and can be checked out to the client.
wydaneGear was checked out to the client and is outside the warehouse.
czesciowo-zwroconeSome gear has returned or needs review. Check the checklist and item issues.
zwroconeGear has returned and the booking is operationally closed.
anulowaneThe booking was canceled. Linked availability blocks should be released.
problemThe flow needs manual review, usually because of a conflict, missing item, damage, or incomplete return.
Availability is blocked only by a concrete block source, not by merely adding gear to a draft.
After booking creation, gear exists only in booking_items. That shows the planned reservation, but it does not block availability by itself.
BookingsAvailability is reserved after booking confirmation. Confirm creates booking-linked availability blocks for the booking dates.
AvailabilityPreflight checks dates, items, and conflicts. It is a safety check before confirm, not an equipment reservation.
BookingsCheck preflight, review the colliding bookings or manual blocks, then decide: change dates, swap gear, or do not confirm the booking.
AvailabilityHandover guides warehouse work from set preparation through return and issue review.
Prepare builds a checklist from internal booking_items and marks the set as needing preparation.
Ready means the set is ready for pickup. It is an operational step and does not change availability blocks.
Checkout marks gear as issued to the client. Availability blocks still come from the confirmed booking.
Return records the return, condition, missing items, and damage. After review, the booking can move to history.
Record damaged/missing on items in checklist view. The issue remains for manual review before the flow is closed.
BookingsPlan and role decide which operational actions are enabled.
Free/Beta can limit equipment, members, or operations. Locked states show the scope of the active package.
PricingPro unlocks a broader Rental OS and organization operations scope. Check pricing or the organization plan page for details.
PlanStaff can handle some operations, but confirm/cancel and plan changes may require owner/admin. Member usually has view or limited access.
PlanIf you see a lock, ask an owner or admin to change the plan, change your role, or perform the action for you.
Contact supportThe beta is ready for controlled use, while some operations still require owner or support involvement.
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.
PrivacyTerms explain early access, responsibility for data entered into the system, beta availability, and how to contact us about issues.
TermsReview what remains manual or incomplete in beta: billing, mobile web, PDF/protocols, barcode, and discovery surfaces.
Beta limitsWhen the flow is unclear or you need a plan change, contact is the quickest path.
Use the Contact page. For plan questions include plan context, and for bookings include the booking reference.
Contact support