Solo-built a restaurant ordering system. Need feedback.

Been building a project for the past few months.

It started as a system for restaurants, coffee shops, and food stalls. Main idea is simple: let customers scan a QR code, order from their phone, and send the order straight to a kitchen display. It also has admin tools, order tracking, analytics, and multi-tenant support.

I’m not positioning it as a POS replacement. More like an ordering layer that can work alongside an existing POS.

While building it, I also explored a food-court style use case. Instead of each table having a different QR, every table can use the same entry point. A customer scans once, opens a centralized portal, can switch language, browse all stalls, and order from multiple stalls in one flow. On the backend, each stall still gets its own kitchen ticket, while the customer sees one live tracking view on their phone. I also added the idea of saving “usuals” for faster repeat orders.

I’m posting here because I want blunt feedback from other Filipino devs/builders.

A few questions:

• Does the “ordering infrastructure layer” positioning make sense, or does it sound too vague/weak?
• Is the centralized food-court flow actually a real pain point right now in PH venues?
• Any glaring technical or business red flags you see (especially with Firebase at scale)?
• If you were looking at this as a product/startup, what would you question first?

Already shared the customer POV on some subreddit 2 weeks ago. Now looking for deeper technical/product roast here.

If anyone wants to look at it, I can drop the repo/demo link in the comments.