Shared booking core
Pricing, validation, locks, confirmations, and recovery stay centralized instead of forking per brand.
Pellines // perfect booking systems
Pellines is the booking agency and SaaS layer behind partner hospitality brands: tenant-safe public websites, one centralized reservation engine, and a native-ready operations shell built for fast execution.
Unified engine
01
One booking core across Pellines and every partner surface.
Tenant-safe rollout
24/7
Public websites, payments, maps, and support stay scoped per tenant.
Mobile command
B
Bloomberg-style terminal treatment is now the native mobile rule.
What ships now
Pricing, validation, locks, confirmations, and recovery stay centralized instead of forking per brand.
Mount new public brands on the same tenancy model without leaking Flor defaults back into the platform root.
Pellines runs the platform layer while partners keep their own identity, support, and public storytelling.
The mobile runtime now follows a dark terminal grammar designed for fast operational scanning instead of brochure UX.
Migration discipline
Sell the platform from pellines.com instead of defaulting to one inherited property brochure.
Keep one booking engine and let tenancy decide brand, payment, map, and support context.
Keep partner host routing, legal copy, and install identity aligned so Pellines never falls back to Flor defaults again.
Mobile rule
Flor de los Pellines remains the first partner tenant, not the platform root.
Legacy public-route debt stays outside the new platform homepage and platform sitemap.
Partner tenant routes now mount on the shared engine and can resolve through fallback paths or host-aware rewrites.