Shops & minimarts
Barcodes, stock that moves as it sells, stocktakes that show the gap, and a cash shift that closes with a variance you can explain. Dollars and riel on the same counter.
All systems
SuiteWright POS
Pre-livePOS for Cambodia — a till that survives a dropped connection, and takes KHQR
Running on the pre-production environment — not yet in production.
A point of sale system for shops, cafés and restaurants in Cambodia. The till keeps taking sales through a dropped connection and cannot charge the same customer twice when it reconnects, KHQR and PayWay land in your own bank account rather than ours, and dollars and riel are handled together the way every counter here already works.
A till has one job and one enemy: hesitation. The second enemy is the network. When a cashier taps “charge” and the connection dies, the honest question is whether the sale went through — and the only acceptable answers are that it was held safely, and that pressing the button again cannot charge twice.
So a sale rung up during an outage is kept on the terminal and sent when the line comes back, and every checkout, void and return carries a request id the till generates, which the server treats as the same operation rather than a new one. The second half is the part worth paying attention to: plenty of tills queue a sale, and rather fewer can promise that the retry after a dropped connection does not become a second charge on somebody’s account.
There is a boundary and it is better said than discovered. The terminal needs to have reached the server at least once since it was opened, because the catalogue is loaded rather than stored on the device. A connection that drops in the middle of a shift is handled; a terminal switched on cold with no internet is not, yet.
The other thing worth saying plainly is where the money goes. KHQR and PayWay run on your own merchant account, so the customer scans and the takings are in your bank — not held by us and passed on afterwards. Each company’s credentials are encrypted and resolved per sale, so an owner with several companies keeps them apart properly rather than sharing one account and untangling it later. And money is decimal arithmetic; floats are not allowed near a total — which is the unglamorous reason the drawer agrees with the report at the end of the day.
When the connection goes, the counter does not
A till has one job and one enemy: hesitation. When a cashier taps charge and the connection dies, the honest question is whether the sale went through. Here it is held on the terminal and sent when the network returns — and because the till stamps every sale with its own id, pressing the button again returns the sale that already happened rather than taking the money twice. That second half is the part most tills get wrong.
- A sale rung up during an outage is queued and replayed automatically
- The same id means a retry can never become a second charge
- Honest limit — the terminal needs to have reached the server once since it was last opened
They scan, and the money is already yours
Bakong KHQR and ABA PayWay at the counter, on your own merchant account — the customer scans, and the money goes to your bank rather than through us and back later. Each company's credentials are held encrypted and resolved per sale, so a group running several companies is not sharing one account between them.
- Bakong KHQR, and ABA PayWay with push-to-terminal
- Your own merchant account per company, credentials encrypted at rest
- Cash, card and QR all settle onto the same sale and the same day's report
A café is not a shop with tables
Selling a latte is not selling a tin of milk. It has modifiers, it comes off a recipe that draws down beans and milk as it sells, it belongs to a table, and somebody behind the machine needs to know to make it. All four are here rather than approximated with product variants.
- Modifiers for how a drink or dish is actually made
- Recipes, so selling an item moves the ingredients it used
- Tables, and a prep queue the kitchen works from
What it replaces
The jobs that eat the week
- Writing sales in a book when the internet is down, and typing them in laterThe till holds the sale through the outage and sends it when the line is back
- A customer charged twice because the cashier pressed the button againA retry is recognised as the same sale, not a second one
- Cash-up arguments because a total was a few riel outExact arithmetic on every line, so the drawer matches the report
- A drawer counted onto a scrap of paper and reconciled from memoryA cash shift opened and closed in the till, with the variance shown
- Ringing each branch to ask what they sold todayEvery outlet's takings in one place, as they happen
- Stock counts that are already wrong by the time they are finishedStock that moves as sales do, per outlet, with stocktakes that show the gap
Why it's built this way
The decisions that matter
The dropped connection, answered properly
Most tills claim to work offline. What matters is what happens on the way back: a sale that reached the server before the line dropped must not be charged again when the till retries. Every sale carries an id the terminal generates, and the server returns the original result for a repeat rather than creating a second sale. So the cashier can press charge again without thinking about it — which is the only instruction a busy counter will actually follow.
We never touch your takings
KHQR and PayWay run on your own merchant account, not a platform account that pays out later. The customer scans, and the money is in your bank. Each company's credentials are encrypted at rest and resolved per sale, so a group running several companies keeps them genuinely separate rather than sharing one account and reconciling afterwards.
Dollars and riel, the way the counter already works
Cambodian retail runs on two currencies at once, and most imported software treats that as an edge case to be configured around. Both are handled here at a rate you control, so prices, change and the day's report all agree without a calculator on the counter.
A complete till, not a sales screen
The demo is always the sale. The day is everything around it — opening a shift and counting the drawer, a return, a gift card, a stocktake that disagrees with the system, a supplier delivery, the end-of-day variance. Those are here, which is the difference between software you sell on and software that survives a month.
More than one outlet, more than one company
Stock and takings are tracked per outlet and roll up together, and the system is built for owners running more than one company rather than assuming one business per account. Nobody consolidates spreadsheets at the end of the day.
Money is decimal, never a float
Totals, discounts and tax are exact arithmetic. It is the least interesting sentence on this page and the reason the drawer agrees with the report — rounding drift is a bug you only find at cash-up, by which point nobody can tell you where it came from.
Who it is for
One platform, four kinds of institution
Cafés & restaurants
Modifiers, recipes that draw down ingredients as drinks sell, table management and a prep queue for whoever is behind the machine.
Multi-outlet groups
Several branches, and often several companies. Stock and takings per outlet rolling up together, with an owner's app for checking the day from anywhere.
Market & mobile traders
Where the connection is the least reliable thing you own. The till holds the sale through the outage and cannot double-charge on the way back.
What's inside
Module by module
Selling & checkout
The till itself — ring up, discount, split payment, void and return, with an offline queue for a dropped connection and an id per sale so a retry cannot charge twice.
Payments at the counter
Cash, card, Bakong KHQR and ABA PayWay with push-to-terminal, on your own merchant credentials, held encrypted and resolved per sale.
Dollars & riel
Two currencies on one counter, at rates you set per company, so pricing, change and reporting agree.
Products & catalogue
Products, categories, barcodes and suppliers — the catalogue the counter actually sells from.
Modifiers & recipes
How a drink or dish is made, and what selling it draws down from stock, so a café's ingredients move as its sales do.
Tables & kitchen queue
Table management and a prep queue, so an order reaches whoever is making it without a shout across the room.
Stock & stocktakes
Stock per outlet that moves as sales do, with counting sessions that show the variance against what the system believed.
Suppliers & purchasing
Purchase from suppliers so stock arrives in the system rather than being adjusted in afterwards.
Pricing & promotions
Price tiers and promotion rules applied at the till, rather than a cashier doing arithmetic in their head.
Gift cards & loyalty
Gift cards issued and redeemed as a balance, and loyalty points earned against the customer on the sale.
Customers
Customer records attached to sales, so a return, a loyalty balance or a receipt reprint has somebody to belong to.
Cash shifts & end of day
Open a shift, count the drawer, close it and see the variance — the ritual every counter already performs, in the system instead of on paper.
Receipts & numbering
Printed receipts and gapless document numbering, which is the part an auditor asks about.
Reporting & dashboards
Sales, stock and takings by outlet and by day, pulled without asking anyone to assemble it.
Roles & permissions
Who may discount, void or open the drawer — set per role rather than shared with a manager's PIN.
Audit log
What changed, and who changed it — including the voids and discounts that are worth being able to look up later.
The owner's app
A read-only companion for iOS and Android for checking the day's numbers from somewhere other than the shop.
Questions
Frequently asked
Does it really keep working when the internet goes down?
Through a dropped connection, yes — and we would rather be precise than have you find the edge on a bad morning. A sale rung up while the line is down is held on the terminal and sent when it returns, and because the till stamps every sale with its own id, a retry returns the original sale rather than charging again. The limit is the start: the terminal needs to have reached the server at least once since it was opened, because the product list is loaded from the server rather than stored on the device. So a connection that drops mid-shift is handled; a terminal switched on with no internet at all is not, and that is the honest boundary today. One other thing worth knowing: a queued sale can still be rejected when it replays — if the shift was closed or the stock ran out — and those are kept for the cashier to review rather than disappearing.
Can customers pay by KHQR?
Yes. Bakong KHQR and ABA PayWay are supported at the counter, and PayWay can push the amount to the terminal. The important part is whose account it lands in: each company uses its own merchant credentials, held encrypted, so the money goes to your bank rather than through us and out again later. Cash, card and QR all settle onto the same sale and the same day's report.
Does it handle dollars and riel?
Yes, and it is treated as normal rather than as an exception. Both currencies work on the same counter at a rate you set per company, so prices, change and the day's reporting agree without anyone reaching for a calculator.
Does it work for a restaurant or café, not just a shop?
Yes. There are modifiers for how a drink or dish is made, recipes so selling an item draws down its ingredients, table management, and a prep queue for the kitchen — four separate things rather than product variants pretending.
We have several branches. Does it handle that?
Yes — it is built for businesses running more than one outlet, and more than one company. Stock and takings are tracked per outlet and roll up together, so nobody has to consolidate spreadsheets at the end of the day, and the owner's app shows the day from anywhere.
How much does it cost?
There is a 30-day trial on the full system, with no crippled free tier — when the trial ends you choose a plan. Pricing after that depends on how many outlets and tills you run. Cambodian businesses pay by ABA PayWay or KHQR; we are not open for signup outside Cambodia yet, and would rather say so than take an order we cannot serve. Tell us your setup and you will get a straight number.
Is SuiteWright POS available yet?
It is pre-live — built, deployed and running on our pre-production environment, but not yet in production and not yet serving a real shop. That is a deliberate distinction rather than a soft launch. Get in touch to see it running or to talk about being an early pilot — pilots still shape what ships.
How it is licensed
A subscription, starting with a 30-day trial
SuiteWright POS is multi-tenant software you subscribe to, not a one-off build. Every new workspace starts on a free 30-day trial of the Pro plan. There is no permanently free tier — when the trial ends you move to a paid plan or the workspace is suspended, with your data kept intact for a grace period so subscribing brings it back.
- 30 days
- Free trial on the Pro plan
- No free tier
- A paid plan after the trial, or suspension
- KHQR & cards
- Bakong KHQR and ABA PayWay locally, cards internationally
Not open for signup yet. SuiteWright POS is Pre-live — running on the pre-production environment, not in production for any customer, so there is no trial to start today. Ask for a demo and we will tell you when signup opens.
See SuiteWright POS on your own data
A demo runs through your actual workflow rather than a scripted tour — bring the awkward parts.