PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Feature scope - proposed scope

9flats Clone Features: Built Around the Host

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
03 / Compare routes

9flats vs Omnistu Clone vs Building From Scratch

Where the proposed base sits against the original platform and a from-scratch build. The Omnistu column is proposed scope, confirmed in writing before any work starts; the scratch column is the work you take on yourself.

CapabilityOriginal 9flatsProposed Omnistu baseBuild From Scratch
Apartment and private-room inventoryCompare the inventory model against your scopeRoom types proposed with independent pricing, occupancy and bed configBuilt from zero
Host onboarding and approvalCompare how hosts are vettedProposed: application, moderation queue and per-host commissionHost onboarding to design and build
Calendar integrityCompare how calendar clashes are preventedProposed: validated at request time, room-level sync inside a propertyAvailability integrity to design and build
Pricing rulesCompare the pricing rules hosts can setProposed: seasonal rates, length-of-stay discounts, extra guest charges, couponsPricing engine to design and build
Host payoutsCompare how host payouts workProposed: earnings net of commission, host-requested, operator-reviewedPayout pipeline to design and build
Commission controlCompare who sets the commissionProposed: set by you, globally or per host, stored on each bookingCommission logic and history to design and build
Other inventory typesCompare which inventory types they bookSix more proposed, shipping switched off - cars, tours, boats, events, flights, spacesA second booking model per type to design and build
LanguagesCompare language coverage for your marketsProposed: 15 locales with per-entity content, RTL for Arabic and HebrewInterface strings, then content, then RTL - each a separate effort
Source code ownershipN/AComplete source proposed, no encrypted filesFull ownership (you are building it)
PriceN/AFixed figure, quoted in writing before work startsQuoted per scope

Swipe sideways to see all columns.

01 / Scope areas

Scope areas for this kind of build

The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.

02 / Feature Set by Role

Feature Set by Role

Every capability grouped by who actually touches it - the host listing and getting paid, the guest booking against their calendar, and the operator approving, moderating and settling.

Host Console

  • Rich property profiles with gallery and video
  • Multiple room types with independent pricing
  • Occupancy limits and bed configuration per room
  • Seasonal and date-based rate adjustment

Guest App

  • Search by location, dates, guests, price and amenities
  • Autocomplete on locations and listings, plus map view
  • Sort by price, rating or distance
  • Star rating, check-in windows and house rules

Operator Admin

  • Host approval and listing moderation
  • Granular role and permission system
  • Commission set globally or per host
  • Coupons with usage limits and minimum totals
04 / How It Works

How It Works, End to End

Follow a host from signup to payout - the path that decides whether they list a second property.

Onboard and list

  • A host applies, you approve them in the moderation queue, and they build a listing with gallery, video, room types, occupancy limits, bed configuration, house rules and check-in windows. Commission can be set for that host specifically rather than globally, which is how you give anchor supply a better rate without repricing the marketplace.

The calendar holds

  • Availability is validated at request time against the per-service date tables and existing bookings rather than a cached flag, and room-level synchronization is designed to prevent a clash inside a single property. Where you also sell through OTAs, iCal export keeps external calendars in step.

The host gets paid

  • Commission is written onto the booking at the moment it is made. Earnings accumulate net of that stored rate, the host requests a payout from their dashboard, and you review and complete it in the payout queue. Raising your commission later affects future bookings only; in the proposed design the stored rate is what protects what a host already earned.
  • Step five is the one hosts talk to each other about. A platform that recalculates historical earnings when the operator changes a rate loses its supply base quickly, and it is not recoverable.
05 / Why these

Every Feature Earns Its Place

Nothing here is on the list because it previews well. Each capability exists because leaving it out costs you hosts. The list describes the proposed design; what ships in your build is confirmed in the written scope.

CapabilityWhy it is not optional
Commission stored on the bookingBecause a rate looked up at payout time means raising your commission silently re-prices every historical booking, and no host will trust your reporting again.
Per-host commissionBecause your first twenty hosts are worth more than your hundredth, and you need a way to reward them that does not reprice the whole marketplace.
Room-level synchronizationBecause a property with four room types is four inventories, and a clash inside one property is invisible to a property-level check.
Availability checked at request timeBecause a cached availability flag is how two guests book the same room, and the host is the one who has to turn someone away.
Seasonal and length-of-stay pricingBecause a host who cannot price a peak week or reward a longer booking is being asked to earn less than they do elsewhere.
Deposits and partial paymentBecause deposit-based bookings are normal in short-stay, and demanding the full amount up front loses both hosts and guests.
Host payout queueBecause money moving to a host should have a deliberate, reviewable step, and because a refund after a payout is the question every operator eventually faces.
Per-entity translationBecause a localised shell around listings nobody in that market can read converts nothing, and European city markets are multilingual by default.
Magic-byte upload inspectionBecause hosts upload property documents and photos constantly, and an extension check trusts a filename the uploader controls.

Swipe sideways to see all columns.

06 / Technology

The Technology Behind the Features

None of this is exotic, and that is the point: any competent Laravel developer can maintain it, so you are not dependent on us to keep it running.

07 / Boundaries we state

Boundaries we state in writing for your build

Stated against the feature, not implied away

  • Local payment rails beyond the proposed set. A customization, though gateways sit behind a common interface.
  • Custom OTA or PMS integrations. Scoped and quoted separately.
  • Merchant accounts. Each gateway you enable needs your own account and approval.
  • Listing content. Photography, descriptions and per-locale copy are yours to supply.
08 / FAQ

Frequently Asked Questions

Answers describe the proposed platform design and our delivery approach. Project-specific pricing, timelines and support terms are agreed in writing.

Can I launch as a stays-only marketplace?

Yes, and most operators do, in the proposed design. Six further service types would ship switched off in the admin, which removes them from search, navigation and the host console entirely, so your platform reads as a pure short-stay marketplace. Enabling one later is designed to need no rebuild because they all share the same proposed booking, payment and payout path. The exact module set is confirmed in the written scope.

Can I change the commission rate later?

Yes, in the proposed design - globally or per host, as a percentage or a fixed amount. The rate would be written onto each booking at the moment it is made, so changing it affects future bookings only and never rewrites what a host already earned. That is what keeps historical reporting and payout records defensible.

How does the platform stop double-booking?

In the proposed design, availability is validated at request time against per-service date tables and existing bookings, not read from a cached flag, with room-level synchronization to prevent a clash inside a single property. Where you also sell through OTAs, iCal export is proposed to keep external calendars in step, and a two-way channel manager is available as an add-on. These are proposed controls, to be verified in the delivered build.

How do host payouts work?

In the proposed design, host earnings accumulate net of commission and fees, calculated per booking at the rate stored on that booking. The host requests a payout from their dashboard, you review it in the payout queue and mark it complete once the transfer is made. Bank transfer and PayPal payouts are proposed; the exact rails are confirmed in the written scope.

Which payment gateways are included?

The proposed design covers the major gateway families - cards and wallets through providers such as Stripe and PayPal, regional rails for African and European markets, an offline bank transfer flow with manual admin confirmation, and an internal wallet. The exact set is confirmed in the written scope, and additional local rails are scoped customization.

Can I run this in more than one language?

Yes, in the proposed design - at entity level rather than interface strings alone. Each listing, page and category would carry its own per-locale content, with 15 locales proposed and right-to-left layout for Arabic and Hebrew. Adding a language is designed to be an admin action, not a deployment. The exact locale set is confirmed in the written scope.

09 / More pages

More pages on this build

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by 9flats.
9flats Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to 9flats, and how clients search for it.
9flats and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.

10 / Next step

Discuss your scope by message

Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead