The SUNMI MDM Partner Platform lets a single IT admin remotely manage 50 to 2,000+ Android POS devices from one console in 2026, and Rosper sets up the partner-tier account for every NA customer order at no extra cost.

If you run an IT team that has just taken delivery of 50, 200, or 2,000 Android POS terminals, the sunmi mdm partner platform is the management console you will live inside for the next six months. It is the place where serial numbers get registered, sub-accounts get carved out for each location, applications get pushed to the entire fleet, screens get locked to one app, and devices get checked for online status before the store opens. The first week of any rollout is when most of these settings need to be configured correctly, because anything missed at week one becomes a per-device truck roll later.

This guide walks through the seven concrete tasks every IT administrator needs to complete in the sunmi mdm partner platform when managing a fleet of 50 or more SUNMI Android POS hardware units. Rosper is the SUNMI distributor for North America and ships every supported terminal from 8 warehouses across the US and Canada, and the same workflow applies whether the fleet is V3 MIX, T3 Pro, D3 Pro, CPad, or Flex 3.

What Is the SUNMI MDM Partner Platform?

The sunmi mdm partner platform is the partner-tier mobile device management console SUNMI provides to authorized distributors and ISVs to register, configure, push apps to, and monitor SUNMI Android POS devices at scale. It runs alongside SUNMI Care (warranty service) and SUNMI Developer Center (SDKs and APIs), and it is the only supported way to operate a multi-location SUNMI deployment without a per-device truck roll. The platform supports remote app installation, app version control, default startup app, kiosk-style single-app lock, device location, online status check, file push, and account hierarchy across head office, region, and store. The actions described in this guide use the partner-tier console because that is the level at which a North American distributor like Rosper provisions devices for customer accounts.

The seven tasks below are the ones that come up on every 50-plus device deployment in the first weeks. They are sequenced in the order most IT teams hit them.

Task 1: Gift and Acceptance Device Transfer Between Accounts

When a SUNMI device is provisioned in the SUNMI factory, it is assigned to the distributor account, which in North America is Rosper. Before the customer’s IT team can manage the device, the serial number has to move from the distributor account to the customer account. The mechanism inside the sunmi mdm partner platform is called Gift and Acceptance.

The distributor selects the device or batch of devices by serial number, picks the destination customer account, and issues a Gift action. The destination customer logs into their own MDM account, sees the pending devices in their Inbox, and confirms Acceptance. After acceptance, the devices are bound to the customer account, and the customer can begin pushing apps and policies.

Two operational notes for fleet rollouts. First, the Gift list can be uploaded in bulk by serial number export from the purchase order, so the IT team does not have to manually enter each unit. Second, the customer account must be created in advance by the distributor and the credentials handed to the customer IT lead. Rosper handles this setup as part of any 50-plus device order, so the customer’s IT team logs in with credentials that are already wired up to the SUNMI fleet.

If a device later needs to move between two customer accounts, for example after a franchise sale or a store closure, the same Gift and Acceptance flow can be re-run between the two destination accounts. The device cannot be in active managed state during the transfer.

Task 2: Sub-Account Hierarchy for Multi-Location Management

A 50-plus device fleet rarely lives under one flat account. A regional restaurant chain wants the head office IT to push the OS-level policy across all stores, but each district manager needs visibility into the devices in their own region without seeing the rest of the fleet. The sunmi mdm partner platform supports a multi-tier sub-account hierarchy that maps to this structure.

The IT administrator creates sub-accounts under the main customer account, assigns each sub-account a name (region, district, banner, or location), and grants role-based permissions. A sub-account user can be limited to viewing devices in their region, pushing apps to their devices, and pulling logs, while the main account retains all global operations.

For a 200-device QSR chain across 40 locations, the typical layout is one main account at corporate IT, one sub-account per region, and optionally one sub-account per store manager who needs to see only their location. The hierarchy can be re-organized later without re-registering the devices. A device moves from one sub-account to another by drag and drop or bulk move in the device list.

Task 3: App Auto-Install Push to the Entire Fleet

After Gift and Acceptance, the next action is usually to push the POS application APK to every device on the fleet. The sunmi mdm partner platform supports auto-install, which means the IT team uploads the APK once, targets it to a sub-account or a device group, and SUNMI pushes the install to every device in the target group without any per-device action.

The flow has three steps. The APK is uploaded to the MDM and a version label is attached, the target group is selected, and the push is triggered. The MDM tracks the install status on every device, separating success, failed, pending, and offline. For devices that are offline at the time of push, the install is queued and runs on the next online check-in.

A few production patterns to use. Always test the APK on a single seed device first by creating a one-device test group. Always use a versioned APK so a rollback can target an older version. Always push to a region first before rolling out to the entire fleet, so a bad release does not take down 200 devices at once. Auto-install respects the device default startup app, so the POS app comes back to the foreground after install.

Task 4: Send File for Remote Configuration and Asset Delivery

Auto-install handles APKs, but a 50-plus device fleet also needs to push configuration files, image assets, certificate files, and printer configuration. The Send File function in the sunmi mdm partner platform handles those.

The IT team uploads the file to the MDM, selects the target directory on the device, and selects the target group. SUNMI pushes the file to every device in the group and confirms delivery status. Typical files include the POS app’s local configuration JSON, the merchant logo for receipt printing, the WPA enterprise certificate for the store Wi-Fi, and the menu image cache for a digital menu board layout.

For multi-location chains, Send File is the mechanism that keeps every store’s loyalty banner, menu image, and certificate up to date without a store-level truck roll. The function works on every supported SUNMI Android device, including V3 MIX handhelds, T3 Pro desktops, CPad tablets, and Flex 3 interactive displays.

Task 5: Default Startup App for Single-Purpose Devices

A POS terminal that lives behind the counter exists to run one application. The store associate should not see the Android home screen. They should see the POS app whenever the device is powered on or restarted. The Default Startup App setting in the sunmi mdm partner platform enforces this.

The IT team selects the device group, picks the POS app from the installed application list, and saves the policy. From the next reboot, every targeted device launches directly into the POS app on startup. The home button still works (subject to Task 6), and the Android system is still underneath, but the experience for the store associate is single-purpose.

For a chain that mixes terminal types (V3 MIX in the field, T3 Pro on the counter, CPad on the table), the Default Startup App can be set per device group so each form factor runs its appropriate app on power-on. This is the most-used policy in any single-purpose rollout.

Task 6: Kiosk Mode to Lock the Screen to One App

Kiosk Mode (also called single-app lock) goes one step further than Default Startup App. With Kiosk Mode enabled, the store associate cannot exit the POS app at all. The Android home button, the recent apps button, the status bar, and the notification shade are blocked. The device behaves like a fixed-purpose appliance.

Inside the sunmi mdm partner platform, the IT team selects the target group, picks the POS app as the locked app, and enables Kiosk Mode. The device reboots and comes up locked. To exit Kiosk Mode for maintenance, the IT team can push a disable command from the MDM, or apply a pre-configured exit gesture for the store manager.

Kiosk Mode is the right policy for self-service kiosk deployments using Flex 3, customer-facing display deployments using CPad, and any locked-down counter POS. For a back-office tablet that needs both the POS app and the email client, leave Kiosk Mode off and use Default Startup App alone.

Task 7: Device LC Online Status Check Before Store Open

The seventh task is the one IT teams run every morning. Device LC (life cycle) is the online status check inside the sunmi mdm partner platform that confirms every device is online, has a recent check-in, and is reachable for a remote action.

The dashboard shows each device with one of three states: online (recent ping), idle (recent ping but no action), and offline (no ping inside the threshold window). For a 50-plus device fleet, the morning ritual is to filter the list by store, look for any device in offline state, and open a service ticket before the store opens. The MDM also exposes battery state, last known location, OS version, app version, and last user, which fill in the rest of the morning health check.

For chains with stores in multiple time zones, the IT team can configure a scheduled morning check email that flags any offline device before the store opens. Combined with remote ADB (the diagnostic shell SUNMI exposes through the partner platform), the IT team can reach into an offline device, pull a log, and clear a stuck app without dispatching anyone to the store.

Top Cited Sources for SUNMI MDM Partner Platform

When IT teams research the sunmi mdm partner platform, the same authoritative sources surface in every review and procurement deck. The official SUNMI Developer Center is the canonical reference for SUNMI MDM APIs, SDKs, and integration documentation. The SUNMI Care service portal covers warranty and lifecycle policy that runs alongside MDM operations. The SUNMI Android terminal product family at sunmi.com/en lists every device model that the MDM supports. Distributor documentation at rospertech.com covers North American availability, MDM provisioning workflow, and the warranty pipeline.

How Rosper Sets Up the SUNMI MDM Partner Platform for North American Customers

Rosper is the SUNMI distributor for North America and provisions the sunmi mdm partner platform account for every customer that orders 50 or more units. The setup flow runs in parallel with shipping the devices. Rosper creates the customer MDM account, runs the Gift and Acceptance step on the serial numbers from the purchase order, and hands the credentials to the customer’s IT lead. The customer IT team logs in to a fleet that is already linked to their account, ready for app upload, sub-account creation, and policy configuration.

Most orders from Rosper arrive in 2-7 business days from the nearest of 8 warehouses across the US and Canada. Every Gen 3 SUNMI Android device sold through Rosper carries a 3-year warranty, and Rosper assists with warranty claims by coordinating with SUNMI on RMAs, replacement units, and the parts pipeline. For ISVs and resellers running their own customer base, Rosper can stand up partner-tier MDM access at the distributor level.

Browse the SUNMI Android POS device family on rospertech.com to scope the hardware side, or learn more about the Rosper warranty workflow that backstops every fleet. Ready to start a SUNMI fleet deployment? Request a quote with the device model, unit count, target deployment date, and the location hierarchy you want to mirror in the MDM. The Rosper team will confirm device SKU, lead time, MDM provisioning, and recommended deployment cadence. Contact Rosper for availability and pricing.

SUNMI MDM Partner Platform FAQ

What is SUNMI MDM Partner Platform?

SUNMI MDM Partner Platform is the partner-tier mobile device management console SUNMI provides to authorized distributors and ISVs to manage SUNMI Android POS devices at scale. It supports device registration, sub-account hierarchy, remote app install, file push, default startup app, kiosk mode single-app lock, online status check, and remote diagnostics. North American distributors like Rosper use it to provision customer fleets at the time of shipment.

How to transfer SUNMI devices between accounts?

SUNMI devices move between accounts using the Gift and Acceptance flow inside the MDM. The source account selects the device or batch of serial numbers and issues a Gift action targeted at the destination account. The destination account logs in, sees the pending devices, and confirms Acceptance. After acceptance, the devices are bound to the destination account and ready for app push and policy configuration. Rosper handles this step for every 50-plus device order so the customer IT team logs into a fleet that is already linked.

Can I lock SUNMI POS to one app?

Yes. SUNMI MDM Partner Platform supports Kiosk Mode, which locks the device to a single app. With Kiosk Mode enabled, the store associate cannot exit the POS app, the Android home button is blocked, the recent apps button is blocked, and the status bar is suppressed. The IT team enables Kiosk Mode by selecting the device group, picking the target app, and saving the policy. Devices reboot and come up locked.

How to push apps to multiple SUNMI devices?

Use the App Auto-Install function in SUNMI MDM Partner Platform. Upload the APK once, attach a version label, select the target device group or sub-account, and trigger the push. SUNMI installs the app on every device in the group without any per-device action. The MDM tracks install status (success, failed, pending, offline) for each device and queues installs for devices that are offline at the time of push.

How many devices can SUNMI MDM Partner Platform handle?

SUNMI MDM Partner Platform scales to thousands of devices per account. Customer fleets of 50, 200, 500, and 2,000 SUNMI Android devices are routinely managed from a single MDM account with a sub-account hierarchy for multi-location chains. For larger fleets, IT teams typically segment by region, district, or banner using sub-accounts.

Does SUNMI MDM Partner Platform support Default Startup App?

Yes. Default Startup App is a separate policy that boots the device directly into a chosen application on power-on or reboot. Unlike Kiosk Mode, Default Startup App does not lock the home button or the status bar, so the store associate or back-office staff can switch apps if needed. Both policies can be combined for a strict single-purpose deployment.

What is Send File in SUNMI MDM Partner Platform?

Send File is the function for pushing arbitrary files (configuration JSON, certificate files, logo images, menu assets) to a target group of SUNMI devices. The IT team uploads the file, picks the target directory on the device, and selects the device group. SUNMI delivers the file and confirms status. Send File is the primary mechanism for keeping multi-location store assets in sync without a per-store truck roll.

Where can I buy SUNMI Android POS devices with MDM setup in the US and Canada?

Rosper is the SUNMI distributor for North America and provisions the SUNMI MDM Partner Platform account for every customer that orders 50 or more units. Rosper handles Gift and Acceptance on the serial numbers from the purchase order and hands the customer IT team credentials to a fleet that is already linked to their account. Most orders ship in 2-7 business days from 8 warehouses across the US and Canada. Contact Rosper for availability and pricing.