Skip to content
ASTRO
Continue with email

Hosted booking software · Reviewed Oct 26, 2026

ReturnOS

Hosted booking and property-management software with a direct-booking site.

At a glance

Runs on
ReturnOS's servers, at your-name.my4u.travel or your own domain
Plans
Free ($0 + 1.5% of each direct or OTA booking) to Complete ($114 a month + 0.75%)
OTA sync
Channex, included on every plan, or an existing Smoobu account; iCal as a fallback
Data export
A ZIP of JSON and CSV files with a checksum manifest, on every plan
Try it
Free plan for one unit; 14-day trial of the paid monthly plans
A unit's guest page on ReturnOS: photo gallery, property name and Direct booking label
A unit's guest page in ASTRO's ReturnOS evaluation account. The banner across the top appears only in the evaluation.
On this page
  1. 01What it is
  2. 02What a guest sees
  3. 03What you see when a booking lands
  4. 04What you own
  5. 05Keep your Airbnb and VRBO listings
  6. 06Payments
  7. 07AI features
  8. 08Who it suits
  9. 09What it does well
  10. 10Things to plan for
  11. 11Owner Portability Baseline
  12. 12Reported, not scored
  13. 13Stated exclusions
  14. 14What it costs
  15. 15About this review

What it is

ReturnOS is hosted booking and property-management software for short-term rental hosts. It runs in your browser: you don't install anything or host a website yourself.

One account covers your properties and units, rates and availability, a direct-booking site (or a booking page you embed on a site you already have), distribution to Airbnb, VRBO and Booking.com, guest messaging, payments through your own Stripe account, and a local compliance check.

Who makes it. ReturnOS, Inc. is a Delaware corporation run from Vienna, Austria. The product is new to the U.S. market.

What ASTRO looked at. ASTRO set up a real one-bedroom condo in Biloxi, Mississippi, in a fresh U.S. evaluation account, made a booking with a fictional guest, and exported the account. ReturnOS runs evaluation accounts with live card payments and OTA connections switched off. It also offers Stripe test mode there, but ASTRO did not run a card through it, so payments and OTA connections were not tested.

What a guest sees

Each unit gets its own page on your ReturnOS address (your-name.my4u.travel), or on your own domain with the Website Kit.

How a guest books:

  1. Read the pagePhotos, description, capacity, amenities and house rules.
  2. Pick datesLive availability and the price per night.
  3. Choose a rateThe total, with the cancellation and payment terms for each rate.
  4. Check outPayment into your own Stripe account.

ASTRO saw every step up to checkout, which the evaluation account stops before payment. For dates one day out, the only rate offered was non-refundable, paid in full, with the note that flexible cancellation was no longer available that close to check-in. That follows from the default terms (see Things to plan for).

What you see when a booking lands

Bookings, phone bookings you add by hand and OTA reservations all land in one Bookings list, and block their dates on the calendar.

From the control center you can:

  • filter bookings by property, unit, channel, payment state and dates, and see booked and upcoming revenue
  • open a booking for its dates, guests, value, reference and payment status
  • add a reservation by hand, marked unpaid, paid outside ReturnOS, or sent a payment link
  • let ReturnOS queue the host notice, the guest's booking confirmation and their guest-access message
  • generate a private iCal feed of your direct bookings for another calendar
The Bookings list in the ReturnOS control center: filters, booked and upcoming revenue, and two upcoming direct bookings
The Bookings list in ASTRO's evaluation account, with its two fictional test bookings.

What you own

ReturnOS's Exit & Portability Standard is part of its U.S. Host Terms, and the export sits on your Account & Billing page from day one, on every plan, including the free one.

What the export ASTRO generated contained:

Format
A ZIP of JSON and CSV files, each listed in a manifest with its SHA-256 checksum
Listing
Title, descriptions, facts, amenities, house rules and the photo list, in order
Photos
Uploaded originals as files; linked photos as their addresses
Bookings
The reservation, a future-booking handoff file and its payment status
Website
A map of every page address, for redirects

Upload your photos. ReturnOS takes photos either as an upload from your phone or computer or as a pasted image address. An uploaded photo comes back in the export as the original file; a linked one comes back only as its address, so keep those originals wherever you host them.

Bringing an ASTRO profile with you. ReturnOS's setup offers to import an ASTRO owner pack. In a round trip ReturnOS ran on Oct 17, 2026, which ASTRO checked against the checksums, the property's address, capacity, rooms, all 32 photos, their order and their alt text came back unchanged. The import arrives paused and publishes nothing until you confirm it.

What you can take with you, item by item, is in the Owner Portability Baseline below.

Keep your Airbnb and VRBO listings

A direct site sits alongside your OTA listings; it doesn't replace them. ReturnOS distributes to the OTAs through a channel manager, Channex, or an existing Smoobu account, which keeps bookings, rates and availability in step.

Channex comes with every plan, Free included: full rate and availability sync for supported channels, with no separate subscription and no per-unit or per-channel charge. ReturnOS confirmed this to ASTRO in writing on Oct 30, 2026. A channel manager you already pay for under your own agreement, such as Smoobu, keeps its own charges.

Without a channel manager it falls back to iCal, which ReturnOS syncs about every three hours. That's normal for iCal, but it leaves a window where the same night can be booked twice. If you rely on the OTAs, use the channel-manager connection.

OTA connections are switched off in the evaluation account, so ASTRO did not test them.

Payments

Guests pay through your own connected Stripe account. ReturnOS's Host Terms state guest funds settle to that account and are not pooled by ReturnOS. The evaluation account takes no live card payments, and ASTRO did not run a card through its Stripe test mode, so ASTRO did not see a payment go through.

The payment schedule set during setup:

  • a 20% deposit at booking, with the balance due 30 days before arrival and charged automatically
  • flexible deposits and automated balance collection on the paid plans, per ReturnOS's pricing page
  • for supported OTA bookings, ReturnOS states you can collect the guest payment into your own Stripe account instead of waiting for the OTA payout (Booking.com first)

AI features

  • Dynamic pricing starts in Shadow Mode: it suggests, and you decide. Every night shows its reasons, with a floor based on your costs. On a new account it labels early suggestions low-confidence. Turning automatic pricing off doesn't undo prices already sent to a channel, and ReturnOS says so.
  • Clarissa, the owner assistant, can read your account but can't change it. It answered ASTRO's questions about pricing decisions and about leaving ReturnOS from the stored data and the exit standard. One question opened a support case without asking first.
  • Agentic Booking lets AI assistants quote and hand off bookings for your property on the paid plans. It carries its own fee (see What it costs). ASTRO did not test it.

Who it suits

A good fit if you:

  • want a direct-booking site and a booking system without running WordPress or hiring someone to build it
  • want one place for bookings, channel sync, guest messages and payments
  • like to see what pricing and messaging automation would do before you switch it on
  • already have your property on ASTRO and want to bring it with you

Probably not the right fit if you:

  • want every guest-facing detail on your own server
  • have one property and low volume, where a percentage of each booking outweighs a flat price
  • need OTA sync without a channel manager

What it does well

  • One system instead of several. Booking site, calendar, bookings, channel sync, guest messages and payments sit in one account, with no website to run yourself.
  • You stay in control of automation. Pricing and guest automation start in Shadow Mode, where you see the suggestion and its reasons before anything changes.
  • A compliance gate that works. A property can't go live until ReturnOS has a local rules pack for your city. For Biloxi it listed the permits, the local-contact rule, tax registrations and zoning districts.
  • Guests pay you directly. Payments go into your own Stripe account, not through a pooled account.
  • Leaving is straightforward. No exit fee, and an export of JSON and CSV files on every plan.

Things to plan for

  • Set and confirm your cancellation terms. The standard policy is free cancellation until 30 days before arrival, with a non-refundable rate closer in, and a 20%/80% payment split. ReturnOS stores it only after you confirm it under Payments, Payment schedule. Change the terms if your OTA listings are more generous, or guests will see different terms in different places.
  • The contract. ReturnOS caps its liability at the greater of 12 months of fees or $1,000, and the Terms' status line says independent U.S. counsel review is "not represented".

Owner Portability Baseline

ASTRO's Owner Portability Baseline v1 asks what you keep if you ever change software. Each line comes from an export ASTRO ran itself or the maker's published terms; “Plan for this” marks a step worth taking early.

  1. B1
    Owner-created content and original media files, plus a complete URL map for redirects

    Yes. Your listing text, house rules, photos and every page address come with you. Uploaded photos come back as the original files.

  2. B2
    The domain: it stays with the owner, or a published transfer process exists

    Yes. Your domain stays yours. The my4u.travel address is ReturnOS's.

  3. B3
    Reservations, past and future, including payment status for future bookings (paid, balance due, deposits held)

    Not tested. A future booking came out with its status, amount and payment status. ASTRO did not create paid, part-paid or past bookings in the evaluation account.

  4. B4
    OTA references: channel listing IDs and reservation confirmation codes

    Not tested. The booking's own reference came with it. OTA connections are switched off in the evaluation account.

    ReturnOS states: ReturnOS states its export carries channel listing IDs and reservation confirmation codes, without channel credentials.

  5. B5
    Guest records together with consent evidence (scope, policy version, source, timestamp)

    Not tested. Guest records come with you, linked to their stays. A booking you enter yourself records no guest consent, and the guest checkout that would was not open to test.

    ReturnOS states: ReturnOS states guest-stay consent evidence collected in the Host context is exported with the guest records.

  6. B6
    Full message history, including guest replies

    Not tested. Automated messages for a booking come out as records. ASTRO could not test message text or guest replies.

    ReturnOS states: ReturnOS states its export carries stored inbound and outbound message text, linked to the reservation.

  7. B7
    Pricing and configuration in readable form: rate plans, pricing rules, minimum stays, fees, taxes, automations

    Yes. Rates, minimum stays, fees, the payment schedule and your confirmed cancellation policy come out readable. Confirm the policy first: until you do, it isn't stored.

  8. B8
    Guest-facing links on the provider's own domains keep working, or redirect, for a stated window after exit

    Yes. Guests' booking links keep working until 45 days after your last guest leaves.

  9. B9
    No exit fee, and a documented exit process with a stated timeline

    Yes. No exit fee, and at least 45 days to export after a paid plan ends.

  10. B10
    Open formats (CSV or JSON) with a manifest of every file

    Yes. Everything comes out as JSON and CSV, with a manifest that checks every file.

How we tested: method and evidence, item by item
  1. B1. Owner-created content and original media files, plus a complete URL map for redirects

    Yes. The export carried the title, short and full descriptions, facts, amenities, house rules and the photo list in order, plus a URL transition map of every page on the ReturnOS address. In the re-test, a photo uploaded through Listing content came back in the export as a file, byte-identical to the original (same SHA-256). Photos added as image addresses export as those addresses, marked as external references.

    Evidence: ASTRO-run Exit & Portability export (standard v1.2) from ASTRO's ReturnOS evaluation account, after a fictional-guest booking, Oct 22, 2026; ASTRO-run re-test export from the same account after a photo upload and a second fictional booking, Oct 23, 2026: properties/, media/ and website/url-transition-map.*.

  2. B2. The domain: it stays with the owner, or a published transfer process exists

    Yes. ReturnOS does not register Host domains; a connected domain stays with the owner's registrar and can be repointed at any time. The your-name.my4u.travel address is ReturnOS's and does not transfer.

    Evidence: The Website Kit page in the evaluation account and the export README, Oct 22, 2026.

  3. B3. Reservations, past and future, including payment status for future bookings (paid, balance due, deposits held)

    Not tested. The fictional future booking exported with its status, dates, guests, currency and total, in the reservations file, a future-booking handoff file and a payment-status file (unpaid, no payment records). The evaluation account takes no live card payments, and ASTRO did not run a card through the Stripe test mode it offers, so no paid or deposit state was created; the account held no past stay.

    Evidence: ASTRO-run Exit & Portability export (standard v1.2) from ASTRO's ReturnOS evaluation account, after a fictional-guest booking, Oct 22, 2026: reservations/.

  4. B4. OTA references: channel listing IDs and reservation confirmation codes

    Not tested. The export has files for channel listing IDs and reservation confirmation codes. With no OTA connected, the unit file was empty and the reservation carried only its ReturnOS reference.

    Evidence: ASTRO-run Exit & Portability export (standard v1.2) from ASTRO's ReturnOS evaluation account, after a fictional-guest booking, Oct 22, 2026: distribution/.

  5. B5. Guest records together with consent evidence (scope, policy version, source, timestamp)

    Not tested. The export linked the fictional guest to the stay and the reservation. It held no consent rows with scope, policy version, source and timestamp: a host-entered booking collects no guest consent, and the evaluation account stops the guest checkout before it would.

    Evidence: ASTRO-run Exit & Portability export (standard v1.2) from ASTRO's ReturnOS evaluation account, after a fictional-guest booking, Oct 22, 2026: consent/.

  6. B6. Full message history, including guest replies

    Not tested. The three automated messages queued for the booking (host notice, booking confirmation, guest access) exported as records with type, recipient, status and timestamps, without message text. The evaluation account sends only to the signed-in user, so no guest reply could be produced, and the complete message history file was empty.

    Evidence: ASTRO-run Exit & Portability export (standard v1.2) from ASTRO's ReturnOS evaluation account, after a fictional-guest booking, Oct 22, 2026: communications/.

  7. B7. Pricing and configuration in readable form: rate plans, pricing rules, minimum stays, fees, taxes, automations

    Yes. The rate plan, minimum stay, cleaning fee, pricing profile, tax context, deposit and balance schedule, and messaging settings exported as readable JSON and CSV. ReturnOS stores the cancellation policy only once the host confirms it, so it exported empty until ASTRO confirmed it on Oct 26, 2026 under Payments, Payment schedule. The next export carried it as text, as a structured rule (free cancellation until 30 days before arrival, then no refund; non-refundable rate, no refund) and with the time it was confirmed.

    Evidence: ASTRO-run Exit & Portability export (standard v1.2) from ASTRO's ReturnOS evaluation account, after a fictional-guest booking, Oct 22, 2026; ASTRO-run re-test export from the same account after a photo upload and a second fictional booking, Oct 23, 2026; ASTRO-run re-test export from the same account after confirming the cancellation policy, Oct 26, 2026: pricing/, workflow/ and properties/.

  8. B8. Guest-facing links on the provider's own domains keep working, or redirect, for a stated window after exit

    Yes. Existing signed Guest Access and Manage Booking links for confirmed reservations stay available through the last relevant departure plus 45 days.

    Evidence: ReturnOS U.S. Host Terms, version US v12 (15 Oct 2026), §18, read by ASTRO on Oct 22, 2026

  9. B9. No exit fee, and a documented exit process with a stated timeline

    Yes. "ReturnOS does not charge the Host an exit, termination or portability fee." The Exit & Portability Standard v1.2 is incorporated, and self-service export stays available for at least 45 days after a paid subscription ends, unless the owner deletes the account earlier.

    Evidence: ReturnOS U.S. Host Terms, version US v12 (15 Oct 2026), §18, read by ASTRO on Oct 22, 2026

  10. B10. Open formats (CSV or JSON) with a manifest of every file

    Yes. The three exports held 53, 56 and 56 files: JSON and CSV data, plus the uploaded photo in the later two. Each manifest lists every file with size and SHA-256; ASTRO recomputed them all and every one matched, with none missing or unlisted.

    Evidence: ASTRO-run Exit & Portability export (standard v1.2) from ASTRO's ReturnOS evaluation account, after a fictional-guest booking, Oct 22, 2026; ASTRO-run re-test export from the same account after a photo upload and a second fictional booking, Oct 23, 2026; ASTRO-run re-test export from the same account after confirming the cancellation policy, Oct 26, 2026: manifest.json.

Reported, not scored

OTA integration and calendar sync

Distribution runs through Channex, or an existing Smoobu account; without either, iCal syncs about every three hours. Channex is included on every plan, with no per-unit or per-channel charge (ReturnOS, in writing, Oct 30, 2026). Not tested: OTA connections are switched off in the evaluation account.

Onboarding

Two-factor sign-in is required before the dashboard. Plan, host profile and tax details come before the first property; no EIN was needed. Bedrooms, beds and amenities are picked from lists. An AI listing draft took about half a minute and was faithful apart from one invented detail. An existing Smoobu or Lodgify account connects read-only first, with a separate switch-over.

AI, and where the owner stays in control

Dynamic pricing and guest automation start in Shadow Mode, which suggests without acting; paid plans move them to Guarded Live, which acts within limits you set. Clarissa can read the account but not change it.

Compliance handling

A property stays locked until ReturnOS has a local rules pack for its city and the owner supplies their own permit documents. For Biloxi the pack listed permits, the local-contact rule, tax registrations and zoning districts, and treated the fire inspection as conditional, which matches the city ordinance.

Pricing and terms

Free carries a 1.5% fee on each direct or qualifying OTA booking, on the pre-tax booking amount, with no cap; paid plans 0.75%, capped at $300 per property per subscription year on annual billing only, and uncapped on monthly billing (ReturnOS, in writing, Oct 30, 2026). Paid subscriptions renew until cancelled and are not refunded mid-period. The Host Terms allow a January price list and an April inflation adjustment of up to 5% a year. Prices are in the costs section below.

Stated exclusions

  • Credential-vault secrets, API and OAuth tokens, security keys, session tokens and the security-bearing parts of guest-access links.
  • ReturnOS's application source code, engines, interfaces and platform IP.
  • 4U Network-wide consent that is not scoped to the Host.

What it costs

Pricing as of Oct 22, 2026

$0 a month + 1.5% a booking, no cap
Free plan
$51 to $114 a month + 0.75%
Paid plans
$339 setup + $22 a month
Website Kit

A monthly plan plus a percentage of each booking. Prices are ReturnOS's U.S. pricing, in USD before sales tax, matching the catalogue in ASTRO's evaluation account.

The percentage applies to direct bookings and to qualifying OTA bookings alike, on the booking amount before tax. On Free it is 1.5% with no cap; on paid monthly plans it is 0.75% with no cap. ReturnOS confirmed this to ASTRO in writing on Oct 30, 2026.

Annual billing gives two months free and caps the 0.75% at $300 per property per subscription year. Through Dec 31, 2026, ReturnOS states a first annual year is charged at nine monthly rates.

The included booking site on your-name.my4u.travel, and an embed on a site you already have, cost nothing extra on any plan. The Full Website Kit is the generated full site, with your own domain.

Agentic Booking: a 15% success fee on accommodation revenue for bookings that come through a verified AI quote or handoff, on paid plans. It replaces the 0.75% on those bookings and sits outside the annual cap. A plain link to your booking page is a direct booking and isn't charged at 15%.

On top: Stripe's card fees, and add-ons if you use them: Guest Compliance $30 a month, Cleaning $17 a month, Operations $39 a month.

Plans (monthly billing, per month)
PlanFirst unitEach extra unitPer booking
Free$01 unit only1.5%
Automation$51$200.75%
Revenue$61$300.75%
Automation + Revenue$112$500.75%
Complete$114$410.75%
Full Website Kit (optional, any plan)
ItemUSD
Setup, one time$339
Hosting, first unit$22 a month
Each extra unit$9 a month

Sources: ReturnOS U.S. pricing · ReturnOS U.S. Host Terms

About this review

  • Reviewed: Oct 26, 2026
  • Version tested: ReturnOS U.S. evaluation account (Free plan), Exit & Portability Standard v1.2, export generator 1.5.1; U.S. Host Terms US v12
  • Affiliation: No affiliation or commercial interest connects ReturnOS to ASTRO or its principals.
  • ReturnOS, Inc.'s part: ReturnOS was offered the same factual-accuracy check as every software maker. The scored export is ASTRO's own.
  • Evidence: An export ASTRO ran itself, on a disposable install with fictional data.

Reviews cover portability and terms, not uptime or support.