XMenu
An in-development restaurant product centered on QR menus, ordering, order tracking, and owner menu and order workflows.
- Problem
- Restaurant menus and orders are often split across disconnected tools, leaving guests, staff, and owners with conflicting information.
- Approach
- The current build uses one business, menu, and order model across guest and owner flows. Kitchen, floor-plan, reservation, workforce, and stock capabilities remain prototype or roadmap work.
The problem in context
Restaurant menus and orders often live in separate tools. Guests need to see what can be ordered, staff need an accurate order, and owners need changes to the menu and order state to appear consistently. When those views disagree, the restaurant has to reconcile the difference by hand.
Who it is for
The current XMenu build focuses on guest and owner workflows: QR menus, ordering, order tracking, and menu and order management. It gives those flows one shared business, menu, and order model.
Kitchen screens, floor plans, reservations, workforce features, stock, and wider reporting remain prototype or roadmap work. They are not presented here as completed capabilities.
What is being tested
The core product decision is to keep guest and owner views on the same underlying menu and order records. The build is testing whether that shared contract stays clear as the supported flows grow.
Current boundary
XMenu is in development. This case study describes the scope that exists now and separates it from the operating capabilities still being designed.
Have something to build?
Email us in Arabic or English, whichever is easier, or call us directly.
Contact detailsDirect contact
- contact@jiwar.io
- +962 7 9174 8028
- Amman, Jordan