See it
A run through the system
Joe’s Wood-Fired Pizza is the test kitchen we use to show the product. Customers order from the restaurant’s own page. The kitchen runs the board, menu and reports. A counter POS sits on the pass. Drivers work for the restaurant, not for Grubble.
-
1
The restaurant’s ordering page
Each restaurant has its own page at a direct link or QR code. Customers do not need an account. Joe’s is the seeded test kitchen: pizzas, pickup and local delivery, demo payments.
-
2
Signed-in customers
People who already know a restaurant can find it again from /app. This is not a marketplace. Search is for a restaurant you want, not browsing for somewhere new.
-
3
Follow the order
After paying, the customer gets a tracking page. Status updates live as the kitchen accepts, cooks and marks the order ready.
-
4
The counter POS in use
Open counter mode on a tablet or Chromium kiosk at the pass. New tickets chime and land full-screen. Accept them, cook them, mark them ready. Delivery orders move onto the road. A remaining-time bar sits on cooking tickets so the counter can see what is due.
-
5
Kitchen dashboards
Reports show how the restaurant is doing this week. The menu manager is where dishes, prices and sold-out toggles live — changes show on the ordering page immediately.
Reports Menu -
6
The restaurant’s own drivers
Drivers are invited by the restaurant. They go online for that kitchen, pick up, navigate, and mark the drop complete. You drive for this restaurant. You do not work for Grubble. Tonight’s hours, deliveries and tips are the same records the restaurant sees. Grubble keeps the records. It does not employ or pay the driver.