RANK: ARamen·Jan 30, 2026

Shoyu Ramen

Mendokoro Ramenba · Makati, Philippines

Headquarters reopened a long-running ramen operation in Salcedo Village known for its thick pork tonkotsu foundation and consistently high demand. The mission is to reassess the classic Shoyu Ramen under current conditions, verify whether the signature depth still hits like it did in earlier years, and determine if execution remains reliable or has drifted into high-variance territory. Secondary intel will cross-check queue control, order-and-pay workflow, seating constraints, and value perception against the bowl’s premium positioning.

Shoyu Ramen

Mission Report

Queue management immediately raised concerns. A cut-in incident occurred while I was waiting behind a large group, and reception handling showed poor awareness of customer flow. This set an unfavorable tone before the meal even began.

This visit carried weight due to history. I have been dining at Mendokoro Makati since around 2018, and the memory of their broth as a benchmark experience set high expectations. Unfortunately, that standard was not met this time.

The Shoyu Ramen underperformed. The broth lacked the depth and impact I remembered, reading flat rather than bold. Noodles arrived overly hard and failed to bind with the soup, creating a disconnected and unsatisfying mouthfeel.

Operationally, the system remains efficient. Ordering and payment are handled before seating, turnover is fast, and service is generally attentive with frequent water refills. Seating is tight, and while serving time stayed under twenty minutes, small details like water preference were overlooked.

Final assessment draws a clear line. While the Shoyu Ramen on this visit was disappointing enough to hesitate on a repeat order, the Tokusei Tsukemen remains elite. Its meaty, umami-heavy dipping sauce and thick noodles still place it firmly in my top five noodle dishes in Metro Manila, keeping Mendokoro relevant despite ramen inconsistency.

Intel: Confirm access routes and operating hours before deployment.

Comments