Bookings
Create, change, cancel, check in and review schedules in one workflow.
Connect bookings, customers, staff, sales and store settings. Customers book on mobile while operators manage today’s work from anywhere.

A booking should connect to the customer record, daily operations and the resulting sale.
Create, change, cancel, check in and review schedules in one workflow.
Manage customer history, employees, login accounts and permissions with clear boundaries.
Prioritize the bookings, orders, treatments and statuses that need action now.
Review payments, refunds, receivables and end-of-day closeout against transaction evidence.
We use real product screens, kept at their original proportions. Customer-facing multilingual booking is already part of the beta.
See operating status and essential numbers first, then open detail when you need it.
Handle requests, schedules, check-in and no-shows inside the operating workflow.
Customer, team and closeout work do not have to live in separate tools.

The customer-facing booking flow is multilingual. Merchant UI localization is being expanded separately.
Bookings, customers, staff and closeout stay connected while industry-specific workflows are added where needed.
Operate around providers, treatments, booking policies and customer history.
Beta supportedConnect room and time operations with customer QR ordering where applicable.
Beta supportedExtend consultation, booking and customer records around the service workflow.
ExpandingClasses, attendance and member operations are being added on top of the shared customer and booking model.
In developmentWhen a store chooses to publish its customer page, service information and booking requests can be offered in Korean, English, Japanese and Chinese.
FLOVI is designed around the same operating flow across phones, tablets and PCs.
FLOVI separates operator roles and avoids mixing customer data, financial detail and operational records without a reason.
Separate owner, manager, staff and accounting responsibilities and permissions.
Customer-facing public services are designed to appear only when the store enables them.
We do not present estimates as revenue or hide the product’s beta status.
Tell us how you run your business today and what you want to improve. We will review the fit before following up.
Not yet. Access is currently invitation-based Closed Beta. Contact us about adoption or beta participation and we will follow up.
Customer-facing booking and information pages are designed for Korean, English, Japanese and Chinese. Operator UI localization will expand separately.
FLOVI’s operating experience is not built around dedicated hardware. It is designed for phones, tablets and PCs.
Public pricing is not being published while the product is in Closed Beta. We plan to publish clear plans after product and plan-policy validation.