Skip to content
Youssef Alouani
← Projects

Flagship · Osoul · live

Osoul: recommendations and dynamic pricing

Dish and beverage recommendations, pairings and meal-completion promos in the Guest App, plus event-based dynamic menu pricing, on one menu data model.

Part of the Osoul platform case study.

Problem

In a fine-dining room the waiter suggests the starter, the wine and the dessert. When guests order from their phone at the table, those suggestions disappear, and so does part of the ticket. Osoul’s recommendations bring them back in the Guest App: guided ordering journeys help guests discover the menu, raising the check and their satisfaction, and their navigation data shows the restaurant what to improve on the menu and in the kitchen.

Constraints

  • Menus are not catalogues: dishes have options, add-ons and pairings that change by service and by season.
  • Few signals per guest: most diners visit a handful of times, so suggestions cannot rely on long histories; for loyal guests, their history is used to lead them to parts of the menu they have not tried.
  • Never pushy: a suggestion that feels like an ad lowers trust in the whole menu.
  • Measurable: the point is the average ticket, so every surface has to be attributable.

Architecture

Osoul recommendationsMenu data (dishes, beverages, options and pairings) and the guest's current order and history feed the recommendation service. It produces three surfaces in the Guest App: complete your meal, more like your favourites, and pairings and drinks on a dish page.DataMenu datadishes · drinks · optionsCurrent orderwhat is in the cartGuest historyfavouritesServiceRecommendation servicepairings · completion · similarityGuest AppComplete your mealMore like your favouritesPairings · drinks
Diagram source (Mermaid)
flowchart TB
  menu[Menu data · dishes, drinks, options] --> svc[Recommendation service]
  cart[Current order] --> svc
  history[Guest history · favourites] --> svc
  svc --> complete[Complete your meal]
  svc --> similar[More like your favourites]
  svc --> pairings[Pairings · drinks to go with it]
Osoul Guest App home: Start ordering, quick actions for the dish recommender, physical menu and reporting an issue, and Picked For You recommendations with Complete your meal and More like your favourites filters
Picked for you: complete the meal, or more like the guest's favourites.
Osoul Guest App item page: the selection with a beverage add-on and item total, dish pairings, drinks to go with it, and Add to cart
On a dish page: pairings and drinks to go with it.

Dynamic pricing

Recommendations raise the ticket; dynamic pricing adjusts prices automatically by event and season. Pricing rules are attached to the menu and triggered by events such as the time of service, occupancy or a special night, and they feed meal-completion promos so a guest sees an offer at the moment it matters.

Key decisions

  1. Model the menu for recommendations first. A flat list of dishes can only recommend “popular”. Pairings, courses and beverage links are part of the menu data, so the service can reason about what completes a meal.
  2. Recommend in context, not on a separate page. Suggestions appear where the decision happens: on the home screen as “complete your meal”, and on a dish page as pairings and drinks to go with it.
  3. Start from the order, then the guest. The current order is the strongest signal at the table; favourites refine it for returning guests.
  4. Price by event, not by hand. Dynamic pricing applies time- and event-based rules (a quiet service, a match night, a set menu) to the same menu model, so promos and recommendations always show the price the guest will pay.

Results

Numbers to come.

Stack and links