A POS that keeps selling
Dine-in, takeaway, split bills, and a kitchen display. Offline orders queue locally and sync when the line returns.
Restaurant POS · Purchasing · Accounting
Run the restaurant.
Not the spreadsheets.
MyRest connects the dining room, kitchen, store room, and ledger — with recipes and FIFO costing that make every plate’s margin visible.
Today
MMK 184,500
Orders
42
Avg. bill
4,392
COGS
31.8%
3
Chicken rice
MMK 4,500
2
Beef noodle
MMK 6,000
4
Iced coffee
MMK 3,600
Open shift · Main Branch
POS-01
Built for restaurants
The parts that usually live in separate systems.
Menu items and ingredients are different things. MyRest keeps them connected through recipes, so purchasing, stock, and cost of goods sold describe the same reality.
Recipes connect buy and sell
Sell a burger, consume beef, buns, cheese, and sauce. Theoretical usage becomes real FIFO cost of goods sold.
Stock you can trust
Cost layers, transfers, counts, wastage, and low-stock alerts across every branch.
Purchasing to AP
Purchase order, goods receipt, supplier invoice, payment, and three-way matching without double entry.
Books that stay closed
Auto-posted journals, fiscal periods, trial balance, profit and loss, and branch-level reporting.
Multi-branch by default
One brand, many outlets. Branch-level stock, cash drawers, and reports under one tenant.
The flow
Buy ingredients. Sell plates. Let the ledger follow.
Purchasing and selling are different sides of the restaurant, but they meet in inventory and the general ledger. Receipts open cost layers; sales consume them oldest-first.
Purchase. Supplier invoice → goods receipt → inventory and accounts payable.
Production. Recipes translate a sold menu item into ingredient quantities.
Sale. Revenue, tax, service charge, and tips post with the bill.
Close. FIFO consumption posts COGS. Stock counts explain the variance.
Double-entry view
Goods receipt
Dr Inventory Cr GRNI
Supplier invoice
Dr GRNI + Input VAT
Cr Accounts Payable
Paid sale
Dr Cash / Discounts
Cr Revenue + Tax + Service + Tips
Recipe consumption
Dr Cost of Goods Sold
Cr Inventory (FIFO layers)Financial and stock posting runs in one database transaction. Corrections are reversals, not edits.
Offline-first POS
The internet drops. Service does not.
The POS installs as a PWA, keeps the menu and tables locally, queues orders in IndexedDB, and prints receipts and kitchen tickets through PrintMe on the same PC. When the connection returns, orders sync with idempotency keys and receive official invoice numbers.