Point of sale
Multi-unit selling by bag, pyi, viss and kilogram. The cashier sells in the customer's unit while the stock ledger records the base unit.
EBS in daily use
A real deployment, in daily production.
Thun Nay Min rice trading is EBS's own operating business. It runs on the same system EBS sells — every trading day, with real stock, real credit and real cash.
One documented deployment · No invented client names, logos, quotes or figures
2020Operating business since
RiceTrading and distribution
OfflinePOS keeps working through network drops
LocalServer and database stay on-premise
The challenge
Mixed units, credit, and stock in more than one place.
The business buys and sells rice by the bag, pyi, viss and kilogram. Stock moves between branches, and much of the trade runs on credit: a customer takes goods today and pays later.
When those records live in notebooks, chat messages and memory, the owner cannot see the day's position without adding it up by hand. A missed entry becomes an argument at the end of the month, and a conversion mistake follows the stock through every report.
- One product sold in several units, each with its own price
- Credit sales across many customers, paid in parts
- Stock held in more than one location
- Cash counted at the end of a trading session
- Changes that need a traceable record, not a memory
The solution
The same system EBS sells, running the business.
The deployment is not a demo environment. It is an on-premise installation supporting counters, stock, credit and reporting every trading day.
58 mm receipts
A thermal receipt for the customer, and an A4 invoice or PDF copy for the file. Every document comes from the same sale record.
Inventory & stock ledger
Purchases, sales, transfers and adjustments post to one ledger. Low stock is visible before it runs out, not after.
Receivables
Customer ledgers, statements and payment-in records, so credit sales and repayments stay in one place instead of a separate book.
Multi-branch transfers
Stock moves between branches through recorded transfers, with per-branch permission gates deciding who can send and receive.
Cash sessions
Each branch opens and closes its own cash session, so the day's cash is counted against the day's recorded sales.
Roles & audit log
A role × module × action permission matrix, plus an audit log of changes that records who did what and when.
Telegram bot
Daily figures, stock and debts arrive in the owner's Telegram chat, instead of a phone call to the shop or a late-night spreadsheet.
Offline sync
The app shell and local database keep the counter working through network drops; an outbox syncs when the connection returns.
What it proves
Tested by a trading day, not a demo script.
Most software claims are demonstrated once. This deployment is exercised every day the business opens, which makes it the most honest evidence EBS can publish.
It does not prove that the system fits every business. It does prove that it can run a rice trading operation with mixed units, credit and multiple branches — and that the features EBS sells are the features it uses.
- In daily production, not a pilot project
- Built around the local trading model: units, credit, branches
- The product sold to customers is the product EBS runs
- Upgrades and support are exercised by a real business first
In the founder's words
We sell what we run.
Min Khant Paing runs both EBS and Thun Nay Min. The trading business is not a reference customer; it is the place where the product has to work first.
Min Khant Paing
Founder, Emrys Business Solutions
We run our own trading business on the system we sell. Every feature has to survive a real trading day at Thun Nay Min before we put it in front of a customer.
Founder, Emrys Business Solutions
References
Customer references, with permission.
If speaking to a reference would help your evaluation, ask during the discovery call. We will connect you only with that customer's written permission — EBS does not publish names, logos, quotes or figures otherwise.
No invented proof. This page lists one deployment — EBS's own — because it is the one EBS can document in public today. When a customer agrees to be named, their story will be added here on the same terms.
Method
How EBS documents future case studies.
The same method will be used for customer stories, once a customer agrees to be named. Each step exists to keep the numbers traceable and the consent explicit.
Baseline form
Before go-live, record how the process works today: units, documents, closing routine, time spent and the reports the owner actually uses. No results are promised at this stage.
Measured results
After an agreed period, compare against the baseline using reports exported from the system. Every figure has a source transaction behind it, so it can be checked.
Customer approval
The customer reviews the draft and approves every name, figure and quote. They can request changes or anonymity before anything is published.
Until a customer approves a story, EBS publishes capability pages and documentation — not invented case studies. Ask about references
See the system behind the case study.
Book a walkthrough of the modules running at Thun Nay Min, or start with the sector that matches your business.