A register that closes the day in one tap.

The problem

A counter running on a calculator, a notebook and memory loses money quietly. Totals get mistyped, discounts are applied by feel, stock is discovered empty in the middle of a rush, and the closing count never quite matches the drawer.

The owner learns what sold yesterday, if at all. They never learn what is selling right now.

What the system does

• A touch first register with big tiles, category tabs and best seller tags.
• Modifiers and add ons, priced per line.
• Dine in and take out, held orders, and void with a trail.
• PWD and Senior discounts applied by rule, not by feel.
• Cash, GCash, Maya and card, with split payments.
• Stock that deducts per sale, down to recipe level: one latte deducts beans and milk.
• Sold out items flag themselves on the register.
• An end of day Z report with payment breakdown, hourly sales and drawer reconciliation.

How it works

1. 1The cashier taps tiles. The order builds with modifiers and service charge computed.
2. 2Payment is taken in one or more methods, and the drawer knows what to expect.
3. 3Every sale deducts stock immediately, by recipe for drinks and food.
4. 4When an ingredient runs out, the affected products flag 86'd on the grid by themselves.
5. 5At close, one tap produces the Z report: expected cash versus counted, over or short to the peso.
6. 6The owner reads one page and knows the day: gross, net, voids, discounts, top items, peak hours.

Why we built it

The register is the one screen a business touches hundreds of times a day. It should be the easiest software in the building, and the hardest to get wrong.

Industry

Cafes, restaurants and retail

Payments

Cash, GCash, Maya, card, split

Stock

Deducts per sale, recipe aware

Close of day

Z report with drawer reconciliation