π Restaurants
A table in Japan, in your language, for your diet β booked in seconds, and guaranteed to hold.
Dinner is where a trip to Japan becomes real β and where visitors hit the hardest walls:
- The language wall β listings and menus with no translation, staff with no common language.
- The booking wall β reservations taken by phone, in Japanese, during business hours.
- The dietary wall β no reliable way to know whether a kitchen can handle halal, vegan or gluten-free needs.
Matsuri Restaurants removes all three at once: multilingual discovery on top of a real reservation engine, running inside the same account you already use for tours and experiences.
Discovery built for visitorsβ
Search works the way a traveler thinks: pick from 23 cuisine types, narrow by area, set a budget on the Β₯βΒ₯Β₯Β₯Β₯ scale, and β critically β filter by dietary need: vegetarian, vegan, halal, gluten-free and more. You can also search by availability first β start from "who has a table tonight?" rather than scrolling listings one by one.
From sushi and ramen to regional specialties β browse by what you are craving, not by what you can pronounce.
Vegetarian, vegan, halal, gluten-free and more β dietary needs are a search filter, not a gamble.
Names, descriptions and addresses localized in six languages, so nothing is lost between you and the kitchen.
Photo galleries and precise geo data on every listing β judge the place and find the door.
In much of Japan, finding verified halal or gluten-free dining still means hours of research. On Matsuri, dietary tags are a search filter, and your specific requests travel with the reservation itself β the restaurant sees them before you arrive.
The booking engine β real inventory, real holdsβ
This is not a contact form that emails a restaurant and hopes. Matsuri runs a genuine table-booking engine: each partner restaurant publishes its bookable hours as time slots, each slot has a capacity, and every confirmation is checked against live availability.
- Time slots
- 30-minute intervals by default, across each restaurant's bookable hours
- Capacity
- A per-slot seat cap set by each restaurant, plus configurable closed weekdays
- Party size
- 1β8 guests per reservation
- Booking window
- Up to 60 days ahead
- Overbooking
- Prevented by design β confirmations run under a database row lock
- Reservation ID
- Every booking gets a unique RSV-YYYYMMDD-XXXXXXXX identifier
The row lock is the detail that matters. When two parties race for the last seats in the same slot, the system serializes the writes: one booking confirms, the other is told immediately that the slot is full. A restaurant on Matsuri can never be double-booked by the platform β which is exactly why restaurants trust it with their real tables.
Every dial belongs to the restaurant: bookable hours, slot interval, per-slot seat caps, closed weekdays, and how far ahead guests may book. Matsuri brings the demand and enforces the rules β the house sets them.
Managing your reservationsβ
Every reservation lives in a "my reservations" view and moves through a clear lifecycle:
pendingβ created, awaiting confirmationconfirmedβ your table is heldcompletedβ you dined; the loop closescancelled/no-showβ the exit states, visible to both sides
You can review upcoming bookings, cancel when plans change, and keep the reservation ID on hand for the restaurant. Because guest details and dietary requests are captured at booking time, there is no awkward moment at the door β the restaurant already knows your party size, your language, and what you can eat.
Two listing modesβ
Not every great restaurant wants to run its inventory through a platform on day one, so Matsuri supports both relationships honestly:
| Mode | Which restaurants | How booking works |
|---|---|---|
| Internal booking | Contracted partner restaurants | Real-time slots, booked and managed inside Matsuri |
| External link | Recommended-only listings | Deep-link to the restaurant's own page on ι£γΉγγ° (Tabelog) and similar services |
Recommended listings keep discovery useful even before a restaurant formally partners β and partner restaurants come aboard through the GCF community, where self-serve GCF Start add-ons include a dedicated restaurant category for listing access.
πͺ Where MTC comes inβ
Dining sits inside the same account graph as everything else on Matsuri. Restaurant activity feeds the platform's ηΈ (En, "connection") economy β the En-Mining referral engine that scores real activity across events, purchases and services in your network. How that engine works, and how εΎ³ (Toku) staking multiplies it, is covered in Mining & Earning.
Today, MTC is spent on event checkouts, tips and crowdfunding contributions. Settling a partner-restaurant bill directly in MTC is a planned expansion, not a live feature β when it ships, the dinner table becomes one more surface where the token circulates.
From the table, the next step is natural: take the culture home with you β that is the Matsuri Shop.