TAUFUPOS Book a demo

A POS by a restaurant owner, for restaurant owners

Seat.Cook.Settle.

Taufu POS was built at a counter, not in an office. It knows that a table of eight pays three ways, that the wok and the drinks counter don’t work the same, and that a new hire learns the till on a Saturday lunch. It keeps nothing about your customers, and it keeps going when the shop doesn’t.

Book a demo See how it works ↓
  • Table
    QR
  • Split
    bills
  • Set
    meals
  • Self-
    hosted
  • Owner
    built

How it works

  1. 01Scan & order

    Table QR. No app.

  2. 02Kitchen gets it

    Each station, its own ticket.

  3. 03Served

    Food and drinks, together.

  4. 04Pay

    Split by ticking. Cash or QR.

Why us

The messy bits a normal POS leaves to your staff.

Two of the same drink

Usually TEH C × 2 ??

One sticker for both. Which cup is which?

With Taufu 1/2 2/2

A sticker per cup. “1 of 2 ready” at the pass.

Set meals

Usually SET A ?

The drink is a note. The drinks counter never sees it.

With Taufu SET A PENG +RM5 → 2 PCS

Every part goes to its own station. Add-ons can’t be skipped.

Splitting the bill

Usually

Re-key it all. The kitchen thinks it’s a new order.

With Taufu BILL 2

Tick items to a new bill. The kitchen isn’t touched.

One pot, many dishes

Usually ? MEE5 CCF3 RICE4

Counted per dish. The curry runs out anyway.

With Taufu CURRY · 4 MEE CCF RICE

Count the pot. Every curry dish sells down together.

Your own slips

Usually VENDOR ?

A fixed layout. Every change goes back to the vendor.

With Taufu LOGO QR LOGO

Build it from blocks: logo, lines, QR. Preview, then print.

Design any of them
  • Receipt
  • Kitchen ticket
  • Checklist
  • Sticker
  • Table QR
  • Cancel slip
  • A separate bill for Grab, or any order type
  • Your shop’s real name and address in the preview
  • Delete a design by mistake? The built-in one still prints

Built by a restaurant owner.
Not a software house.

These all happened at our counter. Each one is now a rule in the till.

  1. DRINKS#01
    Before

    A set came with barley. The drinks counter didn’t know: hot or cold?

    Now

    The drink in a set gets its own questions, like hot or cold.

  2. KITCHEN#02
    Before

    Last night’s orders printed in the kitchen the next morning.

    Now

    Old orders never print on their own. Staff decide.

  3. THE PASS#03
    Before

    A paid takeaway disappeared from the screen before the food went out.

    Now

    It stays on the screen until the food is out.

  1. THE PASS#04
    Before

    Food came back, but the runner just pressed “delivered”. Explaining took too long.

    Now

    Send it back with one tap: wrong item, cold, spilled…

  2. COUNTER#05
    Before

    The cashier stood holding the change, waiting for the drawer to open.

    Now

    The cash drawer opens first, then the receipt prints.

  3. TAKEAWAY#06
    Before

    A customer brought their own tiffin and still paid for a box.

    Now

    Tick “own container”. No packaging charge.

Every rule in Taufu has a story like these.

[SHOP NAME], [CITY] · 35 TABLES · 57 DISHES · EVERY ORDER GOES THROUGH TAUFU

Everything else

The rest,
on one ticket.

+Tap any line

TAUFU POS · COUNTER 1
TAUFU POS[SHOP NAME] · [CITY] · 35 TABLES · 57 DISHES
TABLE: YOUDINE IN
CASHIER: [OWNER NAME]

ROUND 1 · BILLS

1Split by ticking items
  • Even 2 of the 3 fish balls
  • Nothing re-keyed, nothing cooked twice
1Combine two bills
  • Every dish keeps its round and its station
  • The pass still knows which bowl came from where
1Move to another table
  • Asked by name: combine into it, or keep separate
1Ready-to-pay mode
  • “Which table is this customer from?”
  • Dims every table that can’t pay and ranks the rest
1Void, never delete
  • Voided with a reason
  • The kitchen gets a CANCEL slip

ROUND 2 · KITCHEN

1A sticker per item
  • Numbered 3/3, printed as it’s made
  • A beep for a station facing the other way
1Recipe notes
  • Teh O, cold, less sweet — in the kitchen’s own 15 ml spoons
  • Dish photos for a crew that reads different scripts
1Set meals split by station
  • Each piece goes to the station that makes it
  • They meet again at the pass
1Sound per screen
  • The pass rings
  • The office doesn’t

ROUND 3 · THE SMALL THINGS

1One scroll, no pages
  • The whole menu with sticky headings
1“10 left” on any dish
  • Counts down and switches off by itself
1Customers order from the table QR
  • A plain web page, in the shop’s two languages
  • No app, no sign-up
1Design your own slips
  • Receipt, kitchen ticket, checklist, sticker
  • Your logo and a QR code on the bill
  • A separate bill for Grab or any order type
  • Preview it before it prints

ROUND 4 · BAD DAYS

1Two tables, same second
  • Both go through
1Customer screen drops
  • Heals itself; the till says so if it stays down
1Phone reloads mid-order
  • The customer’s basket is still there
1Every slip
  • Never reprinted on its own
  • A print log keeps an exact picture of each one
TOTAL · CUSTOMER DATA KEPT
0

No name. No phone number. No login.

ON THE PHONE
dish ids + quantities, 6 h, then gone
ON YOUR SIDE
the order, marked “customer ordered”
TRACKING
no device cookie, ever
SHARED TABLE
never a stranger’s food or money

THANK YOU · COME AGAIN

Who made this

“We run the shop it runs. Every feature came from a bad day at the counter.”
— [OWNER NAME] · OWNER, [SHOP NAME], [CITY]
[PHOTO: the owner at the pass during service]

Come see it at lunch

Bring your
menu.

We key in your dishes. You take the order.

WhatsApp [YOUR NUMBER] [YOUR EMAIL]