Lugaw
Visible opening menu family
Boundary: The dated capture and a second public list support the family name, not a complete recipe or economy row.
Karinderya food and menu archive with dated Lugaw, Plain and Goto records, reported customer unlock thresholds, and clear boundaries around recipes, costs and profit claims.
The same capture shows Silog Meals locked at 21 / 100, while multiple current publishers report the requirement as 100 customers. Later category thresholds have publisher agreement but no direct first-party record. An unlock count does not establish ingredient cost, cook time, ticket revenue, or profit.
The 100-customer target has a visible progress capture. Later values are publisher agreement and must be rechecked in the live menu before long-term planning.
| Menu family | Current record | Evidence | Checked | Boundary | Record |
|---|---|---|---|---|---|
| Lugaw | Available at the opening state in current public records | Reported by current sources | 2026-09-02 | This supports an opening category, not every dish or tutorial variation. | Open |
| Silog Meals | 100 customers reported; one dated capture visibly shows 21 / 100 | Reported by current sources | 2026-09-02 | Recheck the live menu because progression requirements can change after updates. | Open |
| Silog Meals 2 | 400 customers reported by multiple current community publishers | Reported by current sources | 2026-09-02 | No current first-party record or independently captured unlock panel was established. | Open |
| Lutong Bahay | 670 customers reported by multiple current community publishers | Reported by current sources | 2026-09-02 | Treat as a navigation lead until the current menu panel is captured directly. | Open |
| Pasta Sosyal | 1,994 customers reported by multiple current community publishers | Reported by current sources | 2026-09-02 | The unusual threshold should be verified in the live current-build menu before planning around it. | Open |
This answers which family becomes available and which visible count appears to control access. A customer threshold can guide the next unlock target, but it says nothing about the cost of cooking one serving.
This would require ingredient quantity per serving, purchase pack size, servings produced, cook time, and received ticket value from the same build. Those comparable rows do not exist yet, so this page does not call any dish “best.”
See known Grocery fieldsRecord the category, visible progress, and current requirement before choosing a target.
Complete customers consistently; do not assume an unlock counter fixes an operational bottleneck.
Capture its visible options without importing values from an older list.
Use current Grocery listings and player-entered recipe quantities; unknown yield stays unknown, never zero.
On September 2, the menu page from Karinderia Codex was inspected for its dated UI captures. Karinderya.pro and a second public menu list were used only to identify agreement on category names and later thresholds. No creator-owned menu table, private server test, or full recipe-economy capture was available.
Current public records show Lugaw as the opening menu family, with Plain and Goto visible as options in a dated capture.
Multiple current publishers report 100 customers, and one dated capture visibly shows progress at 21 / 100. Check the live menu before relying on the threshold after an update.
Current community publishers agree on Silog Meals 2 at 400 customers, Lutong Bahay at 670, and Pasta Sosyal at 1,994. These remain cross-source reports rather than first-party progression data.
No same-version table establishes ingredients used per serving, cooking time, ticket value, and unlock stage for every dish, so a fair profit ranking is not available.
No. Menu progression and recipe economy are separate systems. Reaching a category does not establish its ingredient quantities or net cash per order.