Shared booking core
Pricing, availability, validation, lock handling, confirmations, and recovery stay in one engine instead of drifting across cloned sites.
Product Surface
Pellines is not selling isolated brochure pages. The product is the system underneath: one booking engine, a tenant-safe public web layer, and an operator surface that can launch real partner businesses without route or identity leakage.
Pricing, availability, validation, lock handling, confirmations, and recovery stay in one engine instead of drifting across cloned sites.
Domains, SEO, legal pages, support channels, and property context can change per tenant without leaking one partner’s identity into the platform root.
The platform keeps auth, routing, and recovery flows strict enough that launches stay narrow instead of reopening legacy debt everywhere.
The app is aligned to the same platform logic for operator access, release handling, and field execution rather than acting like a separate consumer product.
Delivery Rules
Public acquisition and tenant storytelling stay separated.
Partner websites reuse one engine instead of forking logic per brand.
Operational rollout can happen without reintroducing Flor-root assumptions.
Review the commercial model, check partner fit, or send the live brief directly to Pellines.