Fleet control
MDM enrollment, kiosk lockdown, remote update windows and device naming rules.
Deployment / delivery boundary
SUNMI POS, Kiosk and MDM Deployment Services
A practical rollout system for SUNMI POS terminals and self-service kiosks: define the device profile, stage a repeatable image with MDM and kiosk policy, prove the critical workflows and release in controlled waves.
Discuss your projectDeployment blueprint / 4 control points
Make every device arrive with the same operational story.
Deployment is more than shipping hardware. It is the handoff between your application, the device policy, local operations and the team that supports the fleet on day 30.
Start a deployment brief1named golden image
4gates before scale
24hpilot feedback loop
∞repeatable waves
Rollout sequence
Four phases, one accountable record.
Each phase leaves a concrete artifact so engineering, operations and procurement can work from the same version.
- 01
Shape the rollout
Name the model, countries, application build, peripherals and acceptance owner. We turn the brief into a deployment profile.
Output: deployment profile + risk log - 02
Stage a golden image
Prepare the app package, device policy, kiosk rules, network defaults and accessory map on a controlled sample set.
Output: signed image + staging checklist - 03
Pilot and observe
Run a small cohort through real workflows. Capture install time, payment and printer paths, recovery steps and operator feedback.
Output: pilot report + go / no-go decision - 04
Release by wave
Lock the approved profile, name each device and ship in measurable waves with a clear rollback path and handover record.
Output: wave manifest + handover pack
What stays visible
Controls that keep rollout conversations honest.
We label what is confirmed, what is conditional and what still needs a decision. That keeps a polished pilot from becoming an accidental promise.
Evidence control
Versioned acceptance records tie every conclusion to a model, firmware, app build and date.
Commercial control
Stock, importer, warranty route and support response are confirmed per country and contract.
Example / deployment profile
A small manifest prevents a large reset.
Use a named profile to keep the app build, device policy and rollout wave together. The values below are illustrative; your project record should carry the exact model, firmware, accessories and owner.
- Golden image is signed and archived
- Rollback package is available offline
- Operator acceptance script is versioned
- Country and service assumptions are written down
deployment.yaml
profile: uw-retail-2026-08
device: SUNMI T2s
android: 13
app: com.acme.checkout@4.8.2
mode: kiosk
mdm: enrolled
printer: builtin-80mm
rollout: pilot -> 25 -> 250Illustrative configuration. Confirm model, firmware, MDM and application ownership before production use.
Before you scale
Questions we close in the first review.
Bring the unknowns forward. A short, specific brief is faster to route than a broad request for “full deployment support.”
01Who owns the application and signing keys?
Your team or named software partner normally owns the package, credentials and release cadence. We document access without taking implied ownership.
02Can you provide MDM and remote support?
MDM enrollment, policy authoring and support routing are scoped per project. The platform, tenant and response expectations must be named before rollout.
03What changes between pilot and production?
Production adds country terms, stock confirmation, serial-number manifest, operator training, service route and a rollback owner. We capture these in the handover pack.
Next action
Bring the workflow. Leave with a rollout record.
Share your target models, app build, countries, quantity and timeline. We will route the right device, integration and deployment conversation.