Parpkin
Customer ordering and restaurant operations in one application, with branch-specific menus, payments, staff tools and loyalty.
One restaurant, different branches
Parpkin connects the customer ordering experience with the work behind the counter. Customers browse a branch's menu and place orders. Staff manage menus, orders, payments, customer loyalty and promotions.
The branch is a core part of the application. It determines which menu a customer sees and which orders a staff member can manage. That context follows the order through the system.
Building around branch access
The stack is TanStack Start, React and TypeScript, with Drizzle and Postgres for persistence. Better Auth manages restaurant organizations and staff access. oRPC provides typed API contracts between the interface and server.
I derive staff branch access on the server. Customer branch selection scopes the menu and cart, while staff permissions govern the restaurant portal. Both sides use the same underlying menu records.
Hubtel integrations support checkout and SMS. Menu images live in Cloudflare R2, with authorized, short-lived upload URLs so the browser can upload directly to storage.
The result is a connected workflow between the menu staff maintain and the food customers order.