Case study · Online ordering
One kitchen board for Uber Eats and direct QR orders
Restaurants that sell on Uber Eats and through their own QR storefront often end up with two (or three) devices at the pass. SmartSignPro connects Uber Eats as a system of record so marketplace tickets and direct orders share one board, one menu, and one status flow.
The problem: too many devices for one line
A typical busy counter stacks a dedicated Uber Eats tablet, a separate screen or phone for QR and phone-ahead orders, and sometimes another terminal for in-person payments. Each device has its own login, sound, and status buttons. Staff glance between screens, miss tickets, and re-key 86s in more than one place.
Menu boards and the kitchen already live in SmartSignPro. Adding Uber Eats as another island of hardware fights that model. The goal is fewer devices, not another app to babysit during the rush.
The approach: SmartSignPro as system of record
With the Uber Eats marketplace connection (included with online ordering), the location menu publishes from Ordering settings. Incoming Uber Eats orders become paid kitchen tickets on the same board and in Pulse next to QR, pickup, and delivery tickets.
- Publish once from SmartSignPro; Uber Eats reflects that menu.
- Marketplace tickets auto-accept and appear as accepted on the board.
- 86 an item or pause the storefront in SmartSignPro; Uber Eats follows.
- Reject or cancel in SmartSignPro notifies Uber. No Stripe refund on marketplace tickets.
What operators gain
1 board
Shared kitchen view for Uber Eats and QR
Fewer tablets
No dedicated Uber tablet required for ticket flow
1 menu
Signage, storefront, and marketplace stay aligned
Teams keep Pulse or the browser kitchen board as the line of truth. That means less counter space, fewer chargers, and less training on marketplace-only UIs. Direct channel orders still settle through Stripe Connect. Uber Eats payouts stay in Uber’s merchant portal.
Operational outcomes depend on volume and staffing. The product design goal is one fulfillment surface, not a second marketplace silo.
How to run this setup
- Enable online ordering and connect Stripe for your branded storefront.
- Under Ordering settings → Connections, connect the Uber Eats store UUID and publish the menu.
- Run the kitchen board in the browser or pair Pulse for the line and in-person payments.
- Train staff that Uber Eats tickets look like other accepted tickets, with marketplace payouts handled in Uber.
Why this is different from Uber Direct
Uber Eats marketplace is customer demand on Uber’s app. SmartSignPro becomes the POS-style system of record for those tickets. Uber Direct is separate: it only dispatches a courier for orders placed on your own SmartSignPro storefront, still paid with Stripe.
Use both when you want marketplace reach plus branded delivery without mixing the products in one settings card.
Ready to drop the extra tablet?
Start a trial, connect Uber Eats under Connections, and keep marketplace and QR tickets on one board.