Carry real service choices into a valid appointment.
A nail appointment is rarely just a service name and an empty time. Removal, repairs, length, design, or another choice can change duration, informational value, or who can deliver the service. The current ilinara build can be evaluated as one connected path from those choices to current availability and appointment creation.
Customers pay the salon. ilinara does not process salon-customer appointment payments.
Start with the service that creates the most questions.
A fixed label can hide materially different work. If a choice changes appointment time, displayed value, professional capability, or a required resource, resolve that choice before availability is shown.
The useful question is not whether every service needs options. It is whether the few appointment-changing decisions are visible to the guest and the salon before a time is chosen.
Define the smallest complete base service.
Map each option and its duration, value, capability, or resource effect.
Resolve appointment-changing choices before availability.
Repeat the complete configuration at review and appointment creation.
Configuration, availability, and creation stay connected.
The current evaluation flow sends one salon-authored configuration forward: configure the service, choose a suitable professional, request current availability, review the result, then create or request the appointment under the salon's current policy.
A displayed time is not a reservation. Appointment creation rechecks the selected time and returns the actual confirmed, requested, or changed state.
Configure
Choose a capable professional
Check current availability
Review
Create or recover
Use a fit boundary instead of a feature wall.
This approach is relevant when the hard part is carrying detailed service choices into current availability and a recoverable direct-booking path.
Customers pay the salon. ilinara does not process salon-customer appointment payments.
Evaluate configurable services, no-account booking, secure management, and recovery states.
Record POS, stock, payroll, commission, deposits, marketplace discovery, and production integrations as outside the current claim.
What this page does not claim.
These boundaries keep the product's current scope explicit.
General availability, production deployment, uptime, or support response times
Prices, plan names, trials, discounts, or a production billing catalogue
Customer outcomes, testimonials, rankings, reviews, or ratings