Android device management for retail

Keep every checkout in view.

See which terminals need attention, keep kiosks on their store apps, and roll out Android updates by location.

14-day trial · No credit card required

Example workflow Store 08 / Checkout 03

Device activity

  1. Terminal offlineLast seen at 09:40
  2. Back onlineStore Wi-Fi restored
  3. App version verifiedPOS app · v4.8

What is mobile device management for retail?

Mobile device management (MDM) for retail lets IT enroll, configure and monitor the devices used in its stores. With LimaxLock, a checkout can run a single POS app while an associate handheld runs several approved apps. IT can manage both by store or region.

Explore mobile device management

Manage retail POS terminals, kiosks and handhelds

A checkout terminal, a customer kiosk and an associate handheld need different rules. Each gets its own profile, managed from the same console.

POS and checkout terminalsSingle-app kiosk

Countertop and mobile POS devices boot straight into the point-of-sale app and relaunch it after every restart.

  • Home, recents, status bar and settings blocked
  • App updates assigned to the store group
  • Managed Wi-Fi pushed and locked
Explore POS device management
Self-checkout and self-service kiosksSingle-app or web kiosk

Customer-operated screens stay on the ordering or checkout flow, with nothing else on the device reachable.

  • Kiosk app relaunches automatically on boot
  • Web kiosks limited to approved URLs
  • Schedule kiosk restarts outside trading hours
Explore kiosk lockdown software
Store associate handheldsMulti-app kiosk

Shared handhelds carry only the stock, price-check, task and messaging apps the role needs.

  • Approved work apps only, nothing personal
  • Camera, Bluetooth and USB set per profile
  • Live location and last-seen for lost devices
Explore rugged device management
Price checkers, catalogues and signageWeb kiosk

In-aisle tablets and screens run one web page or app full-screen, with the browser controls locked.

  • Browsing restricted to your whitelist
  • Address bar and navigation hidden
  • Content changed remotely from the console
Explore the secure kiosk browser

Remote app management for retail stores

How to update a POS app across store locations

Start with a group of spare terminals. Deploy the approved POS app from Managed Google Play or distribute your private APK. On a connected terminal, verify the installed version and run a test checkout with the scanner and receipt printer.

Apply the update to the next store group when the pilot passes. For a terminal that was offline, check its installed version after it reconnects. See Android app deployment and updates for the available controls, or follow the store-by-store POS update guide.

Security & compliance

Kiosk lockdown and security for retail devices

Set app, password and update policies before handing a device to staff or customers.

LimaxLock manages the device, not the payment. It does not process card data and is not a PCI DSS certification; its lockdown and restriction policies help you keep store devices inside the controls your own PCI programme defines.

  • Checkout devices locked to one app

    OS-level kiosk lockdown stops browsing, games and personal apps on devices that sit next to customer and payment workflows.

  • No unapproved software

    Only approved apps install. Unknown sources, sideloading and app-store access are blocked by policy.

  • Lost or stolen device response

    Review the last reported location if available. When the device connects, use the appropriate lock or wipe command.

  • Password and update policy

    Enforce device password rules and defer system updates by up to 30 days to avoid changes during peak trading.

Try it on one checkout.

Choose one spare device per model. Record its Android build, enrollment method and store app version, then run these checks before expanding to a store group.

Mark each check as you complete it

Record the result for each model, including time to first checkout and any peripheral that needs manual setup. For help reviewing compatibility and planning a multi-store rollout, book a retail demo.

Test this checklist in a free trial

Roll out Android MDM across retail stores

Once the pilot passes, use the same profile for the next store and check that its devices report the expected app version.

  1. Create a store profile

    Choose the kiosk mode, the POS and store apps, the restrictions and the store Wi-Fi.

  2. Enroll the devices

    Scan a QR code during setup or use zero-touch so devices enroll on first boot.

  3. Group by store

    Assign devices to store and region groups so the right profile and apps arrive automatically.

  4. Monitor and update

    Watch status per store, push app updates and recover faulty devices with remote commands.

QR code or Android zero-touch enrollment?

Use QR enrollment when someone can scan the setup code on each terminal. For a larger shipment, check zero-touch eligibility with your reseller before ordering. Assign the enrollment configuration before first boot, then confirm a sample device receives its store profile, Wi-Fi settings and checkout app. See Android device enrollment and the new-store enrollment checklist.

For your rollout team.

Design a self-service kiosk experienceManage store apps and updatesTroubleshoot an offline Android POS terminalRestrict a kiosk to approved websitesRead LimaxLock user reviews on Google Play
FAQ

Retail device management FAQ

What is retail device management?

Retail device management is the central control of the Android devices used in stores, including POS terminals, self-checkout kiosks, price checkers and associate handhelds. An MDM platform such as LimaxLock enrolls each device, locks it to its store app, deploys updates and reports its status, so every store runs the same configuration.

How do I investigate an offline checkout terminal?

Open the store group, find the terminal and check its last-seen time. Ask the store to confirm power and network connectivity. Once the terminal reconnects, sync its policy and verify the installed POS app version before returning it to service.

How do I lock an Android tablet to a POS app?

Enroll the tablet in LimaxLock and apply a single-app kiosk profile that names your POS app. The tablet boots into that app, the home and recents keys, status bar and settings are blocked, and the app relaunches after a restart. Only an administrator can take the device out of kiosk mode.

Can I update the POS app on every store device at once?

Yes. Select the app and the device group in the console and deploy. The install runs silently on every device in the group, approved apps auto-update, and private in-house APKs are deployed the same way as Managed Google Play apps.

Does LimaxLock work with self-checkout kiosks?

For compatible Android kiosks, use single-app mode for a checkout app or web kiosk mode for an approved ordering site. During the pilot, verify enrollment, checkout peripherals and app relaunch on the exact model you deploy.

How do I manage devices across multiple store locations?

Group devices by store and region in the console. Each group gets its own profile, apps and Wi-Fi, and the dashboard shows online, offline and needs-attention counts per location. A change can be applied to a single store or rolled out to every store at once.

Is LimaxLock PCI DSS compliant?

LimaxLock is device management software and does not store, process or transmit card data, so it is not itself a PCI DSS certification. It helps retailers apply device controls that a PCI programme typically calls for, such as locking devices to approved apps, blocking unapproved software and enforcing passwords.

What happens when a store device is lost or stolen?

Check the device’s last reported location if available. Select it in the console and issue a lock or wipe according to your incident policy. Confirm the command result when the device is online.

Bring your first checkout online.

Use the 14-day trial to test your POS app, peripherals and store policies on a spare Android terminal.