How to Automate Qashier
Qashier automates the counter itself: QashierPOS inventory and employee management on the terminal, QashierPay for cards and local wallets, Treats payment-linked loyalty, and QashierHQ as the web back office for reports, payouts and multiple outlets. Aggregator commission statements, bank settlement and supplier prices still need an agent like WebRun.
Qashier put the till, the card reader and the loyalty card in one box
Qashier is a smart point of sale out of Singapore, sold across Southeast Asia as a SuperTerminal: an all-in-one Android device with its own touchscreen and receipt printer, standing where a cash register used to. QashierXS is the compact one, QashierX2 the dual-screen one, and QashierPOS is the software on both.
The businesses on it are the ones you walk past: a bubble tea kiosk, a hair salon, a bakery, a minimart, and the small chains that grew out of one of those.
What sits inside it is every transaction and how it was paid for, the item list and what is left of it, the staff who clocked in, and the customers earning points on Treats.
At that size the terminal is not one system among several. It is the record of the day.
Every payment type pays out on its own timetable
A counter in Kuala Lumpur or Singapore takes money in six different ways before lunch. Cash, a card, a QR payment, GrabPay, Touch 'n Go, a voucher from a campaign somebody ran in March.
The terminal records all of that as one day's takings. The bank does not. Card money arrives net of a fee on one cycle, each wallet on another, and a delivery order later still, minus commission and whatever adjustments the platform decided on.
So somebody works backwards. Open the bank, find Tuesday's credits, work out which provider each belongs to, subtract the fees, find the gap. Somebody opens the delivery partner portal to see why a payout is light.
Then the ordinary things: the wholesaler's price this week against last week's, the roster against who actually clocked in, last night's reviews.
It is an hour a day of nothing but reading other people's screens.
QashierHQ reports what came through Qashier
Qashier covers more of this than most counters have switched on, and it is worth exhausting first.
Inventory management tracks stock automatically, raises alerts, moves items between outlets with transfers, and syncs with Shopify and WooCommerce so the shelf and the online listing agree. Employee management runs clock in and clock out, schedules, access controls and commission rates and tiers. QashierPay is built into the terminal, taking cards and the local wallets from one device instead of four, and Treats is payment-linked loyalty on top of it: a customer paying with a linked card earns points with no app to download and no card to lose. Behind all of it, QashierHQ is the web back office, holding sales reports, transaction history, payouts and multi-outlet performance in a browser rather than on the terminal. GrabFood and foodpanda orders arrive on the same system, with menus synced.
That is a lot of counter for one box.
All of it describes what came through Qashier. What an aggregator took out before paying you, what the wholesaler charges this week, what actually cleared into the business account, and what a customer wrote last night are other companies' screens, behind logins that belong to you.
Yesterday's tenders can be matched to yesterday's payouts
That hour of working backwards is the first thing to go. Every portal it depends on can be read overnight and set out on one page.
Yesterday's sales by payment type out of QashierHQ set against what actually cleared into the bank, so a wallet or a scheme that came up short is named that morning instead of at the end of a quarter.
The delivery partner's payout statement read line by line against the orders Qashier recorded, so a commission adjustment or an order that never got paid for becomes a query while the platform still holds the record.
The buying side reads the same way. This week's price at the cash and carry, checked against the one before it, so a rise stands out on its own, with availability beside it.
Then the ones nobody gets to. Treats members who have not been back in two months, with an offer written and waiting for a person to send. Reviews from the map listing and the delivery apps in one place, since a bad week shows there first. Clock-in records set against the roster, so an outlet that ran short on Saturday is a fact rather than a feeling.
Nobody has to work backwards from the bank
None of that is a skill. It is a set of logins opened in order, read carefully and written down in one place, and the business already has every password.
WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens QashierHQ, reads yesterday's sales by tender, employee and outlet, then opens the bank, a delivery partner portal, a wholesaler account or the review listings, and hands back one short list: what did not clear, what was short, what changed.
It runs on your schedule in your own private environment, and any run can be watched and stopped. Ordering stock, messaging a customer, answering a review in public or raising a dispute is prepared and waits for you.
The workflows below are already built, and each one names what it opens.
Questions people ask
Will it raise a dispute with a payment provider?
No. It finds the reversal or the light payout on the provider's portal, matches it to the transaction Qashier recorded, and puts the evidence in front of you. Raising a dispute is a claim made in your business's name, so a person makes it.
Do we need to take the terminal out of service for this?
No. The agent works in a browser, signed in to QashierHQ the way you would from a laptop, so the terminal keeps serving throughout. Nothing is installed on it and staff notice no difference while a run is happening.
We only want it reading, not editing. Is that configurable?
Yes, and read-only is the default. Most workflows read Qashier and write their findings somewhere else, into a sheet or a message. Anything that would edit a product, a price or a stock count is drafted for approval rather than applied.
12 ready-made Qashier workflows
Each one names the apps it touches and the exact steps it takes. Open one to read what it will do, then turn it on.
Want one of these running on your own Qashier?
Show WebRun the process once and it will run it on schedule, in your own private browser environment.


