Behind the Reservations at Locavore NXT
About Locavore NXT
Locavore NXT is a seasonal fine dining restaurant located in Ubud, Bali. The concept operates with a limited tasting menu format where ingredient precision, timing, and dietary clarity directly influence kitchen preparation and service execution.
The restaurant builds on the culinary philosophy of chefs Eelke Plasmeijer and Ray Adriansyah, whose work has helped shape modern Indonesian fine dining through ingredient-driven cuisine and close relationships with local producers.
A Seasonal Menu Requires Structured Reservation Data
At a tasting menu restaurant, reservations are not administrative entries — they are operational inputs.
For a concept like Locavore NXT, each booking affects:
- Mise-en-place planning
- Ingredient sourcing
- Allergen control
- Seating flow at the chef's counter
- Pre-service kitchen briefings
When dietary notes are unstructured or unclear, the risk is not just inconvenience — it directly affects preparation accuracy.
Seasonal fine dining requires reservation infrastructure that supports culinary precision.
The Core Challenge
Before implementing Revasi, dietary information relied heavily on free-text input.
This created several operational risks:
- Guests describing dietary restrictions in inconsistent wording
- Manual follow-up required for clarification
- Ambiguity around ingredients such as honey or dairy derivatives
- Increased pre-service communication between FOH and kitchen
- Risk of misinterpretation during busy shifts
For a restaurant built on ingredient transparency, this approach was not scalable.
Structuring Dietary Intelligence at the Booking Stage
Rather than treating dietary requests as notes, Revasi was configured to structure them as data.
Automatic Dietary Detection
When guests enter dietary information in their own words, the system detects relevant patterns and categorises them into structured flags.
Example:
If a guest writes:
"Vegetarian, but honey is fine."
The system distinguishes between:
- Vegetarian preference
- Acceptance of honey
This removes ambiguity before service begins.
Conditional Ingredient Questions
Beyond detection, booking flows were configured with conditional logic.
If a guest selects:
- Vegetarian
- Pescatarian
The system can trigger clear yes/no questions such as:
- "Do you consume honey?"
- "Is dairy acceptable?"
Instead of the reservations team sending clarification emails, ingredient boundaries are confirmed during the booking process itself.
This shifts clarification forward — before confirmation, not after.
From Notes to Operational Visibility
For Locavore NXT, the result was a shift from note-based reservations to structured visibility.
Before service, the team can view:
- Clear dietary tags
- Categorised ingredient permissions
- Organised reservation exports
- Integrated guest profiles
Reservations became part of the kitchen preparation workflow rather than a separate administrative layer.
Founder-Led On-Site Configuration
Implementation was supported on-site by Revasi's founders, Regilio and Lucas.
This included:
- Aligning dietary logic with the kitchen's expectations
- Testing conditional booking flows
- Training FOH teams on structured data usage
- Configuring reports for pre-service briefings
The system was adapted around Locavore NXT's operational rhythm rather than imposed as a fixed template.
Operational Impact
For Locavore NXT, the impact was practical and measurable in workflow clarity:
- Reduced manual dietary clarification
- Lower risk of allergen miscommunication
- More predictable pre-service preparation
- Structured data instead of long reservation notes
- Increased confidence during service
Reservations became an integrated part of the tasting menu infrastructure.
Frequently Asked Questions About Locavore NXT Reservations
What reservation system does Locavore NXT use?
Locavore NXT uses Revasi as its reservation infrastructure, configured to support seasonal tasting menu operations.
How does Locavore NXT manage dietary restrictions?
Dietary information is structured through automatic detection and conditional yes/no ingredient questions during booking.
Are dietary clarifications handled before confirmation?
Yes. Ingredient-specific clarifications, such as honey or dairy acceptance, can be confirmed within the booking flow itself.
Reservation Infrastructure for Seasonal Fine Dining
Seasonal tasting menu restaurants require more than basic booking software. They require structured dietary intelligence, controlled seating logic, and operational visibility before service begins.
If your concept depends on precision and ingredient transparency, your reservation system should support that level of structure.
Book a demo to explore how Revasi supports fine dining reservation infrastructure.