Hospitality / In daily use
BentoPOS
Built for the busiest part of the day.
Orders, kitchen tickets and the details that keep a takeaway moving. Software shaped around the people using it on shift.
One dish.
One change.
Ready to confirm.
Order #042
#042
1 × Vegetable rice
No onions
COLLECTION / COUNTER ORDERThe details belong to the dish.
Staff choose collection or delivery, add dishes and attach changes to the correct line. This example follows a card-at-counter order.
Choose how the order is paid.
The till requires a payment method. Card-at-counter confirmation places the order; Cash and Mixed use a change window. Payment-link orders follow a different, payment-gated path.
A placed order and a kitchen ticket.
After confirmation, the order appears on the board and its kitchen ticket prints. The real system reports unconfirmed or failed printing so staff can recover it.
The business problem
A busy service cannot wait while staff stitch together screens, paper tickets and phone calls.
What we built
A custom point-of-sale system with bilingual menu management, caller identification, kitchen printing and operational reporting.
Where the work stands
Used in a working takeaway, with continued maintenance including clearer menu names and caller-ID recovery work in September 2026.
Technology, with a purpose
- TypeScript
- React
- SQLite
- Thermal printing
Something similar on your mind?
A till, booking flow or internal system built around the way your team actually works.
Discuss a project →