Mobile
Android (Kotlin)
Apps built specifically for Android, with full access to the phone's hardware, background location and company-managed devices.
Used for
- Apps for Android
- Delivery partner apps
- Billing and POS apps
- Field staff apps
POS device management
POS device management for billing and payment terminals running Android
Every billing terminal locked to the apps it needs, set up the same way in every outlet, and updated when the shutters are down.
At a glance
The short version
What it is
Billing terminals locked to your billing and payment apps, with printers and scanners set up and updates held until after closing, in every outlet.
- What you get
- Terminal lockdown
- Peripherals
- Updates and apps
- Fleet view
- How it works
- Store or IT
- Maker's tools or our agent
- Device policy
- Billing app
- 2 more
- Runs on
- POS terminals
- Android Enterprise
- Android
- Admin
- Built with
- Who it's for
- Cost depends on
- Terminal models
- Management route
- Peripherals
How to start
Tell us what you need in your own words. You talk to the developers who would build it and get a written, line-item estimate.
Get a project estimateA billing terminal is a dedicated device, so manage it like one
A POS terminal running Android looks like a phone or tablet with a printer attached, and without management it behaves like one: staff can install games, change the date, turn off updates or leave the billing app. Each of those can stop billing or open a security gap.
Managed as a dedicated device, the terminal shows only the billing app, the payment app and the few tools staff need. Settings are fixed, peripherals are set up the same way everywhere, and head office can see which terminals are online, which app versions they run and which need attention.
How much control is possible depends on the terminal. Some run Android with Google Play services and support Android Enterprise; many run the maker's own build and are managed through the maker's terminal management system or SDK; payment-certified terminals often restrict what outside apps may change. We map this for your models first.
What is included
What we build for POS terminals
Platform: POS terminal
Terminal lockdown
- Kiosk launcher showing only billing, payment and approved tools
- Settings, app installs and developer options blocked for staff
- Manager PIN for a maintenance screen
- Terminal returns to the billing app after a restart
Platform: POS terminal
Peripherals
- Built-in and USB receipt printers set up per outlet
- Barcode scanners and weighing-scale labels read by the billing app
- Customer-facing display and cash drawer settings
- Printer errors reported to the console, where the printer exposes them
Platform: Admin dashboard
Updates and apps
- Billing app releases to a pilot outlet first, then everywhere
- OS and app updates after closing time, where the terminal allows scheduling
- Payment app kept on the version your provider approves
- Rollback to the previous billing app version
Platform: Admin dashboard
Fleet view
- Terminals by outlet with online status and last billing activity
- Lock a missing terminal and flag it as lost
- Swap a faulty terminal and move its settings to the replacement
- Audit reports: which terminal, which app version, which user
How it works
How a POS terminal is brought under management
From the day a terminal reaches an outlet to its daily check-ins.
- Store or IT
Step 1: Terminal received
The serial number is registered against an outlet and a counter in the console.
- Maker's tools or our agent
Step 2: Provisioned
Depending on the model, the terminal is enrolled through the maker's management system or set up with our device-owner app.
- Device policy
Step 3: Apps allowlisted
Only the billing app, the payment app and approved tools can run; the launcher shows nothing else.
- Billing app
Step 4: Peripherals set up
The outlet's printer, scanner, cash drawer and customer display settings are applied and checked with a test bill.
- Console
Step 5: Updates after closing
App and OS updates wait for the maintenance window, after the last bill of the day.
- Head office
Step 6: Remote support
IT sees the terminal's state, pushes a fix or restarts it, and can lock a terminal that goes missing.
- Console
Step 7: Monitoring
Offline terminals, printer errors and outdated versions show up before they stop billing.
Comparison
How management works on different kinds of POS terminal
The terminal decides the route, so we confirm yours before planning features.
| Android terminal with Google Play services | Terminal on the maker's own Android build | Payment-certified terminal | |
|---|---|---|---|
| How it is managed | Android Enterprise, through an EMM or the Android Management API where its policy permits | Our device-owner app, or the maker's terminal management system | Mainly the maker's terminal management system, as the payment provider allows |
| Installing your billing app | Managed Google Play, as a public or private app | Our console or the maker's app store | The maker's or provider's approved channel |
| Kiosk lock | Kiosk mode set in the device policy | Lock task mode from our device-owner app, where allowed | Usually set by the maker; outside changes may be limited |
| OS updates | Can usually be held to a daily maintenance window (Android 8.0 or later) | Delivered by the maker; timing varies | Delivered by the maker, often with the provider's approval |
| What we build | Policies, launcher and console | Device-owner agent, launcher and console | Integration with the maker's tools, plus the fleet view |
Privacy & security
Payments and security, stated plainly
Payment certification stays with the provider
Card payment security depends on your payment provider's certified app and the terminal's own certification, and UPI payments follow your provider's rules. Device management does not make a terminal certified, and we never handle card data.
Only approved apps can run
An allowlist stops unknown apps, one of the simplest ways to reduce malware and misuse at the counter.
Settings staff cannot change
Date, time, network and developer options are fixed, so bills and logs stay trustworthy.
Every action logged
Remote locks, app pushes and setting changes are recorded with who made them and when.
Platforms
Terminals and tools we manage
POS terminals running Android, Android Enterprise devices used at counters, the billing app and the head-office console.
- Point of sale
POS terminals running Android
Countertop and handheld billing terminals running Android-based software, locked to approved billing and payment apps where the terminal maker or supplier allows device-owner or SDK control.
- Mobile
Android Enterprise devices
Android phones, tablets and rugged handhelds with Google Play services, managed through Android Enterprise: company-owned devices as fully managed, dedicated (kiosk) or work-profile devices, and personal phones through a work profile only.
- Mobile
Android app
Apps for Android phones and tablets, tested on budget and mid-range devices and published on Google Play or privately.
- Back office
Admin dashboard
Back-office panels for operations, support and finance teams: orders, users, content, reports and permissions.
Technology
Technology behind managed POS terminals
Native Android code for the launcher and device-owner agent, Android Enterprise APIs where the terminal supports them, and a cloud console for head office.
Device management
Android Device Owner and DPC APIs
Built-in Android APIs that let one trusted app control a company device: kiosk lock, silent app updates and restrictions, even without Google Play.
Used for
- Custom kiosk launchers
- Devices without Google Play
- POS and signage agents
- Silent app updates
Device management
Android Management API
A Google cloud API for device-management products: your console sets the rules, and a Google app on each Android device applies them.
Used for
- Kiosk products for stores
- EMM and MDM products
- Policy-based device fleets
- QR and zero-touch setup
Backend
Node.js
Runs the server side of apps: fast, scalable back ends that power your app, website and integrations.
Used for
- App back ends
- Live order tracking
- Chat and notifications
- Payment processing
Backend
NestJS
A structured way to build back ends on Node.js, so large business systems stay organised, testable and easy to hand over.
Used for
- Business app back ends
- SaaS platforms
- Marketplaces
- Admin panel back ends
Data
PostgreSQL
A reliable database for the records your business runs on: orders, payments, bookings and stock, kept accurate and easy to report on.
Used for
- Orders and customers
- Payments and ledgers
- Stock and inventory
- Bookings
Web
React
Builds interactive screens in the browser, such as dashboards, admin panels and portals, that respond instantly as your team works.
Used for
- Web apps
- Admin panels
- Dashboards
- Customer portals
Cloud & DevOps
Firebase
Ready-made building blocks for mobile apps, such as push notifications, phone OTP login and crash reports, so you launch sooner.
Used for
- Push notifications
- Phone OTP login
- Crash reports
- Real-time updates
Cloud & DevOps
AWS
Cloud hosting for your app, website and data, with data centres in India and room to grow when traffic rises.
Used for
- App hosting
- File and photo storage
- Backups
- Busy sale days
Plain-English glossary
POS device terms, in plain English
- POS terminal
- The device at the counter that runs billing and often takes payments, usually with a built-in printer. Many now run Android, which makes them manageable like other company devices.
- Terminal management system (TMS)
- The terminal maker's own tool for updating and configuring its terminals. On payment terminals it is often the only approved way to change software, so we integrate with it rather than work around it.
- App allowlist
- The list of apps a managed terminal is allowed to run. Everything else is hidden or blocked, so the counter stays a counter.
- Maintenance window
- The hours when updates may install, such as after closing. It keeps an update from stopping billing in the middle of a rush.
- PCI certification
- Security standards for card payments, set by the PCI Security Standards Council. Terminals and payment apps are assessed against them through their makers and providers; managing the device does not change or replace that.
- AOSP build
- A version of Android built from Google's open-source code without Google Play services. Many POS terminals use one, which rules out tools that rely on Google Play and calls for the maker's tools or our own agent.
Product preview
What the terminal and the console look like
Illustrative screens; outlets, versions and numbers are samples.
POS terminal. Staff see only the billing app, the payment app and approved tools; settings and other apps are out of reach without a manager PIN. 
Head-office console. Head office sees each terminal's outlet, status, billing app version and last billing activity, and spots problems before a queue forms. 
Head-office console. One policy per outlet type decides which apps run, which settings are fixed and when updates may install, and shows what each terminal model supports. 
Head-office console. A single terminal's details for support calls: model, versions, printer state and connectivity, with a remote lock that is logged.
Illustrative preview
Sample screens: names, prices and figures are examples, not client data.
Work
A sample retail device build
Device management & kiosk solutions
Illustrative sampleAndroid kiosk and device management platform for retail stores
An illustrative kiosk product for retail chains: locked Android tablets for catalogues and price checks, a staff launcher, and a console to enrol, update and monitor every device.
- Retail
- Device management platform
Runs on
- Android Enterprise
- Admin
- Web app
Built with
- Next.js
- React
- Android (Kotlin)
- NestJS
- PostgreSQL
- +1 more
Cost drivers
What drives the cost of managing POS terminals
Terminal models
Each model has its own Android build, maker tools and peripherals; supporting several multiplies testing.
Management route
Integrating the maker's terminal management system differs from building our own device-owner agent, and some fleets need both.
Peripherals
Printers, scanners, scales, cash drawers and customer displays are tested per model and per outlet format.
Billing app changes
If we also build or adapt the billing app, work on printing, offline billing and payment integration is estimated separately.
Outlets and rollout
Provisioning days, staff briefings and the swap process for faulty terminals scale with the number of outlets.
Estimates are written from your scope, with the effort and assumptions behind each line item.
How pricing worksProcess
How we bring a POS fleet under management
Terminal audit
We list your terminal models, their Android builds, peripherals, payment apps and what the makers allow.
You getTerminal capability sheet
Policy and launcher design
We agree which apps each outlet type runs, what staff may change and when updates install.
You getOutlet policies
Build and test on real terminals
The launcher, agent and console are tested with your printers, scanners and payment app.
You getTested build
Pilot outlet
One outlet runs managed terminals through a busy week, including an overnight update.
You getPilot findings
Rollout and support
Outlets move in batches outside trading hours; we then handle support and new terminal models.
You getSupport plan
Solutions
Related POS and dedicated-device solutions
POS software development
Custom point-of-sale software with offline billing, UPI QR payments, GST invoices, hardware integration and central control for multiple outlets.
Dedicated device (COSU) management
Fleet management for single-purpose Android devices: rugged scanners, delivery handhelds and shift tablets, kept charged, updated and healthy across sites.
Android kiosk mode development
Single-app and multi-app kiosks for Android tablets, phones and terminals: locked ordering, check-in and catalogue apps that customers cannot escape.
Digital signage and Android TV device management
Player apps, a scheduling console and device management for menu boards, promotions and queue screens on signage players and devices running Android TV.
Services
Services involved
The disciplines a project like this draws on.
Android app development
Native Android apps in Kotlin and Jetpack Compose, designed for entry-level phones, patchy networks and the background limits of popular Android brands.
Custom software development
Software shaped around how your business runs, from approvals and inventory to billing and reports, replacing spreadsheets and disconnected tools.
Admin panel development
Back-office dashboards built around your team's daily tasks: order queues, approvals, catalogue management, payouts, reports and audit logs.
API development
Secure, documented REST and GraphQL APIs, plus integrations that connect your apps to payment, logistics, GST, messaging and business systems.
Industries
Who it is for
Industries where this kind of product fits well.
More specific pages
Tailored by industry
POS device management for
FAQ
Frequently asked questions
Does managing the terminals make us PCI compliant?
No, and we do not claim it does. Card payment security depends on your payment provider's certified payment app, the terminal's certification and how your business handles card data. Device management helps around that: only approved apps run, settings are locked and every change is logged. Questions about PCI scope belong with your payment provider or acquiring bank, and we work within the rules they set.
Can you manage terminals supplied by our payment provider?
Often only partly. Terminals supplied by a payment provider are usually managed through the provider's or maker's own system, and the provider decides which outside apps may run. Where they allow a billing app and offer a management API, we connect it to the fleet view and deliver your billing app through their channel. Where they do not, we keep your billing app on separate terminals and manage those fully. We check the provider's terms before planning.
Will updates interrupt billing?
We design so that they should not. Billing app updates go to one pilot outlet first and then to the rest during the maintenance window after closing. OS updates follow the same window where the terminal lets us schedule them; on some maker builds the maker controls the timing, and we tell you which models those are. If an update misbehaves, the console can roll the billing app back to the previous version.
What happens if a terminal is stolen or goes missing?
Head office marks it missing in the console, and the action is recorded with who took it. On a terminal running our device-owner agent, that switches it to a locked message screen so it cannot bill, and it can also be reset remotely to remove the billing app and its data. On terminals managed through the maker's system, we use the lock and reset that system offers. Location is only available if the terminal has location hardware and the policy allows it, and it is used to recover the device, not to track staff.
Can staff still use the camera to scan QR codes or barcodes?
Yes, if the billing or payment app needs it. The policy can keep the camera available to those apps while the rest of the terminal stays locked, so staff scan codes inside the billing flow rather than opening a separate camera app. How narrowly camera access can be limited depends on the Android version and the management route, which we confirm per model.
Can the same console manage our tablets and menu screens too?
Yes. Captain tablets, kitchen displays and menu screens are all dedicated devices with their own policies, and one console can hold them grouped by outlet. Each device type keeps its own lock settings and update window. If you only need terminals managed today, we design the console so other device types can be added later without rebuilding it.
Related
Keep exploring
Next step
Bring your billing terminals under control
Tell us which terminals you use, how many outlets you run and which billing and payment apps they need. We will map what each model allows and send a line-item estimate.