What is self-checkout kiosk software?
Self-checkout kiosk software is the application that lets a shopper scan, bag and pay for their own purchases at an unattended terminal, with a store attendant stepping in only for exceptions. It reads barcodes and QR codes, looks up prices and promotions from the store's product master, verifies each bagged item against a weighing scale, applies loyalty and coupons, takes payment by card, UPI, wallet or cash, prints the receipt and records the sale in the point-of-sale and inventory systems as if a cashier had rung it up. It also decides when a human is needed: an age-restricted item, a weight mismatch, a price override, a voided line. Those decisions, and the way the attendant is called, are what separate a working self-checkout from a slow one.
AtashiTech writes this software as a native Windows application for the checkout hardware you choose, and integrates the scanner, scale, payment terminal, cash recycler and receipt printer built into it. It belongs to our range of kiosk and self-service solutions. We do not manufacture the checkout unit itself.
Lanes are staffed for the peak and idle for the rest
A checkout lane costs the same to run whether one shopper or thirty pass through it in an hour. Stores pay for that gap every day.
The old way
At seven in the evening a shopper with a bottle of milk and a loaf stands behind two full trolleys. Three lanes are open because that is how many cashiers are on shift; the other four sit dark. The cashier scans, asks about a loyalty card, asks about a carry bag, waits for the card machine, counts change, and calls a supervisor for the customer who wants to return one item from yesterday. The queue moves at the speed of the slowest basket in it.
Opening more lanes means hiring for the evening peak and carrying the cost at eleven in the morning. Meanwhile the store's own data lives in three places: the POS knows what sold, the loyalty system knows who bought it, and the inventory system finds out overnight. Age-restricted items are checked when the cashier remembers, and shrink at the till is discovered at the stock count rather than at the moment it happens.
The AtashiTech way
Self-checkout kiosk software moves the short-basket shopper out of the cashier's queue. A shopper scans each item, places it in the bagging area, where the scale confirms the weight matches the product, scans a loyalty card or enters a mobile number, applies a coupon, and pays by tapping a card or scanning a UPI QR code. The receipt prints and the sale posts to the POS and inventory systems immediately. One attendant oversees several units from a tablet, and is called only when the software flags something it should not decide alone.
The store keeps its lanes for full trolleys and complicated transactions, and reallocates staff from scanning to the shop floor. Because the application runs as a Windows executable with a local mirror of the product master, a checkout does not stop selling when the store's connection to head office drops.
How it works
Four stages from the first scan to the exit gate. Every stage has a defined exception path so the attendant knows exactly why they were called.
Scan and bag
The shopper scans each barcode or QR code on the fixed or handheld scanner. Loose produce is weighed on the scale and chosen from a picture menu with a PLU search. Each item goes into the bagging area, where the security scale checks that the added weight matches the item just scanned.
Identify and apply offers
A loyalty card scan or mobile number pulls the shopper's points and personalised offers. Promotions from the product master, multibuys, bundle prices, and scanned coupon codes are applied and shown line by line so the shopper can see what changed the total.
Pay
Card payments go to the payment terminal, UPI payments through a dynamic QR code on screen, wallets through their own QR, and cash into a note and coin recycler that returns change. The software waits for the terminal or gateway confirmation before it closes the sale.
Receipt, exceptions, exit
The receipt prints, or is sent by SMS if the shopper prefers. Where the sale included an age-restricted item, a weight mismatch or a void, the attendant is alerted on their tablet and clears it with their own login. The receipt QR can open an exit gate.
Core features
The feature set is designed for grocery and general retail, and the same build serves a pharmacy or a department store with a different configuration.
Barcode, QR and PLU lookup
Fixed and handheld scanners read retail barcodes and QR codes; loose items are found through a picture menu or a PLU code. Prices come from the store's product master, mirrored locally.
Weighing-scale validation
The bagging scale confirms each scanned item's expected weight, and the produce scale weighs loose goods for pricing. Tolerances are set per product category so bread does not trigger what a bottle does.
Card, UPI, wallet and cash
Payment terminals for cards, dynamic UPI QR codes, wallet QR codes and a cash recycler for notes and coins. Card data stays on the terminal; the kiosk application never handles it.
Age-verification workflow
Products flagged as age-restricted pause the sale until an attendant confirms the shopper's age at the unit or from the tablet. The check is logged with the attendant's identity.
Loyalty scan and redemption
Card or mobile-number lookup against your loyalty platform, points earned and redeemed on the sale, and member offers applied automatically to eligible lines.
Coupons and promotions
Multibuys, bundle pricing, percentage and value discounts from the product master, plus scanned or typed coupon codes, each shown as its own line on screen and on the receipt.
Attendant alerts
One attendant supervises several units from a tablet that shows each unit's state and the reason it needs attention. Interventions require the attendant's login and are recorded.
POS and inventory integration
Every sale posts to the POS as a completed transaction and to the inventory system as a stock movement, so the store's numbers do not depend on an overnight batch.
Hardware and integrations
A self-checkout unit carries more peripherals than any other kiosk we build. The software drives each one through the vendor's SDK or OPOS driver, locally, with no cloud dependency in the payment path other than the gateway itself.
Peripheral and system matrix
Retail hardware is standardised more than most kiosk hardware, which is why brand names appear here. If your store already owns a different make, it is assessed during scoping rather than ruled out.
| Category | Examples integrated | Interface | Offline behaviour |
|---|---|---|---|
| Barcode and QR scanners | Datalogic Magellan fixed scanner-scales; handheld USB scanners | OPOS driver or vendor SDK, USB | Fully local |
| Weighing scales | Mettler-Toledo and DIGI produce and bagging scales | Serial (RS-232) via vendor SDK | Fully local |
| Card payment terminals | Pine Labs terminals; other terminals via Razorpay-style gateway integration | Terminal SDK over USB or LAN | Needs the terminal's own connectivity |
| UPI and wallets | Dynamic UPI QR rendered on screen; wallet QR | Payment gateway API over HTTPS | Needs connectivity; falls back to card or cash |
| Cash handling | JCM and CPI note and coin recyclers | Vendor cash SDK, USB or serial | Fully local; float reconciled at day end |
| Receipt printers | Epson TM-series thermal printers | OPOS driver, USB or LAN | Fully local |
| POS and inventory | Your POS; NexCommerce or NexERP for catalogue and stock | REST API, with a local product-master mirror | Sales queue locally and post when the link returns |
| Loyalty | Your loyalty platform | REST API | Earn is queued; redemption needs connectivity |
The payment gateway and loyalty connectors are built by our integration team; the kiosk application itself comes from our kiosk application development practice, which also handles the Windows lockdown so the unit cannot be used for anything but checkout.
Retail formats that use self-checkout kiosk software
Basket size, item mix and the number of regulated products decide how a format configures the software; the build is the same.
Supermarkets and hypermarkets
The classic case: high volume, a long tail of loose produce, and evening peaks. Units are grouped in banks of four to six under one attendant, produce is handled through the picture menu, and the scale tolerances are tuned per category to keep interventions low without weakening the check.
Convenience and forecourt stores
Small baskets, long hours and a single member of staff who may be outside on the forecourt. A self-checkout unit here is less about queue length and more about keeping the store serving when the one employee is busy, with age-restricted tobacco and alcohol lines routed to attendant approval.
Pharmacies and health stores
Over-the-counter lines can be sold unattended while scheduled products are blocked or routed to a pharmacist's approval. The receipt carries batch and expiry data when the product master holds it, which pharmacies need for returns.
Department stores and malls
Fashion and general merchandise use hang-tag barcodes rather than weighed items, so the bagging scale is often replaced by a security-tag detacher workflow and a receipt QR that opens the exit gate. Service desks in the same stores frequently pair this with our queue management kiosk for returns and alterations.
Campus, canteen and staff stores
Stores inside corporate campuses, hospitals and universities sell to a known population. Payment can be tied to an employee or student card, and the same badge that enters the building through our visitor management kiosk or an ESS card can identify the shopper at checkout.
Quick-service food retail
Cafes and bakeries with packaged goods run a hybrid: packaged items go through self-checkout, prepared food through a menu-driven flow. For a full restaurant journey with modifiers and a kitchen display, the better fit is our food ordering kiosk.
Deployment, offline operation, AMC and remote management
A checkout that stops selling costs more per minute than any other kiosk in this catalogue, so the operational design is conservative by intent.
Deployment
Installation is a Windows package on each unit plus the attendant application on a tablet. The product master, price and promotion rules are pulled from your POS or from NexCommerce into a local mirror, and refreshed on a schedule you set. We configure scale tolerances, restricted-product categories, payment methods and receipt layout per store, and a chain keeps one master configuration with per-store overrides. Go-live is usually one bank of units in one store, watched by our team and yours through the first weekend, before the rollout continues.
Offline operation
Scanning, weighing, pricing, cash payment and receipt printing are entirely local and continue during an outage. Card payments depend on the terminal's own link, which is often separate from the store's data connection, and UPI needs the gateway to be reachable; when it is not, the screen offers card or cash instead of failing silently. Completed sales queue locally and post to the POS and inventory systems when the connection returns, in order, with their original timestamps.
Annual maintenance contract
Retail changes constantly: new promotions, new product categories, a new payment method, a replaced scanner. The AMC through our consulting and AMC support service covers those changes and the software updates that follow Windows and driver releases, with a support route for store operations. Its terms are set per customer and are not published.
Remote management
A chain wants to know which units are selling, which have a paper-out or a cash-recycler fault, and whether the morning's price file reached every store, without ringing each one. Self-checkout kiosk software reports to our centralized kiosk management platform, which raises those alerts, pushes configuration and promotional screens to every unit, and lets a technician pull logs or restart the application remotely. Practical notes on running self-service estates are on the blog.
Plan a self-checkout pilot
Tell us your format, the POS and loyalty systems you run, the payment methods your shoppers use, and which checkout hardware you have or intend to buy. We will define the exception rules with your store operations team, confirm the integrations, and quote the engagement. Start on the contact page; we do not publish prices because store configurations differ too much for a list to be honest.