Developer hub / public basics
SUNMI POS, Kiosk and Android SDK Integration
A public technical library for printer, scanner, peripheral, Android, kiosk, MDM and compatibility work.
Discuss your projectDeveloper hub / public basics
Build with device-specific facts in view.
Browse practical guides for printer, scanner, cash drawer, kiosk, MDM and multi-device compatibility work.
Quickstart lab
See the integration shape before you open the docs.
Small, reference-only snippets for the two device actions developers ask about first. Replace the service names with the interface documented for your target model.
// Confirm the target model and printer service first
val receipt = "ORDER #1042\nTOTAL CNY 128.00\n"
sunmiPrinter.printText(receipt)
sunmiPrinter.lineWrap(3)- CONNECTED / printer service
- TEXT BUFFER / 3 lines
- READY / sample transaction
val intent = Intent("com.sunmi.scanner.ACTION_DATA_CODE_RECEIVED")
intent.putExtra("data", "6921734901042")
registerReceiver(scannerReceiver, intentFilter)- SCAN EVENT / received
- VALUE / 6921734901042
- NEXT / validate in your POS
// Use only after the base and drawer are confirmed
val openSignal = byteArrayOf(0x10, 0x14, 0x00, 0x00, 0x00)
sunmiPrinter.sendRAWData(openSignal)
operatorUi.showDrawerCommandSent()- COMMAND / 5 bytes queued
- HARDWARE / verify physical open
- FALLBACK / show operator retry
The snippet shows the interaction shape only. Verify package visibility, permissions, API version, firmware and peripheral configuration against the named device before shipping.
Android printer integration
Implement a receipt or label print path around SUNMI printing services, then verify the exact printer mode, service version, paper setup and failure behavior.
Built-in printer or named external printer on a selected SUNMI model. The official examples cover different device and printer configurations; do not generalize across the catalog.
Learn more02 / Technical articleScanner Intent and SDK integration
Choose between the SUNMI OS scanner Intent, the camera-based decoding SDK and an infrared scan engine, then normalize data and trigger behavior in the host app.
V2s, V2s PLUS, L2s PRO or another named SUNMI configuration. Scan-head availability, symbologies and output mode must be confirmed for the exact device.
Learn more03 / Technical articleCash drawer and customer display
Connect counter peripherals only after the base, accessory wiring, power path and display topology are named; the official cash-drawer example is limited to supported device configurations.
A named SUNMI counter model, base, cash drawer and customer-facing display. The public cash-drawer example identifies only supported configurations such as the documented T1 case.
Learn more04 / Technical articleKiosk and MDM provisioning checklist
Build a repeatable dedicated-device rollout using SUNMI Kiosk APIs, OEMConfig, the selected MDM and an explicit recovery owner.
K2 or another named SUNMI device with a selected MDM, ownership mode and approved kiosk profile. K2 is documented with Android 7.1, 9 or 13 depending on configuration and batch.
Learn more05 / ArticleExisting POS migration checklist
Map an existing POS, ERP or field workflow onto named SUNMI hardware by separating application behavior, device interfaces, peripherals, payment certification and rollout scope.
Any named SUNMI device and existing POS or ERP application. The migration result belongs to the named application build and peripheral topology, not to a generic product family.
Learn more06 / Technical articleFlutter and React Native integration notes
Keep the cross-platform shell stable by owning a small native Android bridge for SUNMI-specific printing, scanning, display and device-management behavior.
Named SUNMI model, framework version, Android build tools and native bridge implementation. Framework choice does not remove device-specific validation.
Learn more07 / Technical articleMulti-device compatibility matrix
Compare one application build across named SUNMI devices by keeping Android, firmware, peripherals, method and evidence state visible in every row.
V2s, V2s PLUS, P3, L2s PRO, K2 or any additional named devices. A family label is not a compatibility cell.
Learn more08 / ArticleDeployment staging and handover
Turn a signed application, device policy, accessory list and acceptance record into a repeatable staging batch with explicit ownership and rollback.
Named device batch, application package, deployment destination and staging owner. Include country and network topology when TMS or MDM is involved.
Learn moreNo matching results yet.