Skip to content

Client Installation & Updates

The device app is distributed via a dedicated download page: www.merchantcentral.de/warehouse/download. It is free and license-free – the license resides server-side in BC (Licensing).

Platform Package Update
Windows 10/11 (x64/arm64) MSIX (signed) via .appinstaller Automatic via Windows
Android 7.0+ (API 24+) APK (signed) Notice at startup, manual download

Signature & trust

Windows packages are signed via Azure Trusted Signing (publisher CN=ALTENBRAND Datentechnik GmbH), Android APKs with a dedicated keystore. The download page shows a SHA-256 checksum for each package for integrity verification.


Install on Windows

  1. On the packing station PC, open the download pageInstall Windows.
  2. Run the .appinstaller file → Install.
  3. Start the app and pair it.

SmartScreen notice

On the first downloads, Windows SmartScreen may show a warning until "reputation" has built up. Select More info → Run anyway. The packages are validly signed.

Automatic updates: By installing via .appinstaller, Windows checks for new versions on its own and updates in the background – no store, no manual intervention.


Install on Android

  1. On the handheld/scanner, open the download pageDownload APK.
  2. Allow installation from "unknown sources" once (or roll out via MDM, see below).
  3. Install the APK, start the app and pair it.

Updates: The app reports at startup when a newer version is available and links the download. With MDM distribution, the management system handles the update.

Industrial scanners without Google services

Zebra/AOSP devices without the Play Store are supplied via the direct APK download or via MDM (Intune, Zebra StageNow, Managed Google Play).


Enterprise rollout (MDM)

For many devices, distribution via a mobile device management system is recommended:

  • Windows: MSIX/.appinstaller via Intune.
  • Android: APK via Intune, Zebra StageNow or Managed Google Play.

This way, installation, updates and – for Zebra – the matching DataWedge scanner profile can be rolled out centrally.


First-time device commissioning

  1. Extension & setup present in BC (wizard executed).
  2. Terminal created in BC, Entra Client ID stored in the setup (Terminals).
  3. App installed on the device.
  4. Scan the terminal's QR code in the app (App at a Glance).
  5. Sign in via Microsoft Entra ID – done.

Compatibility

The download page states the minimum version of the BC extension (minExtension) for each app version. Keep the extension and app at compatible versions – when in doubt, update the BC extension first, then the devices.


Next steps