The Zebra MC22 handheld is a workhorse for inventory, picking, and backroom tasks, but the device only shines when it runs the right software stack. Picking the best apps is part art, part science: you balance workflows, security, printing, offline behavior, and ERP integration without slowing people down. This guide breaks down the must-have apps for the MC22, how they fit together, and how to roll them out with minimal disruption and maximum payoff.
- What Makes the Zebra MC22 Stand Out
- How We Evaluated Mobile Apps
- Top 10 Mobile Apps for the Zebra MC22
- Setup and Configuration Tips that Save Hours
- Scanning, Label Printing, and RFID Considerations
- Security, Governance, and MDM Practices
- Performance and Offline Strategies on the MC22
- Integrating MC22 Apps with ERP/WMS
- TCO, Pilot Plans, and Rollout Roadmaps
- Conclusion
- FAQs
What Makes the Zebra MC22 Stand Out
The MC22 family sits in a sweet spot: rugged enough for warehouse floors and backrooms, yet light enough for all-day use. It blends a touch interface with a physical keypad on many configurations, which means workers can enter quantities quickly without constantly switching contexts. That speed, multiplied by thousands of scans, adds up.
Under the hood, Android plus Zebra’s system services (like DataWedge and OEM configurations) make the device highly customizable. You get deep scan intent support, reliable Wi‑Fi roaming on enterprise networks, and hooks for printers, wearables, and ring scanners. The device speaks the same language as your apps - barcode intents, secure browser modes, and label printing toolchains.
Another advantage: the MC22 thrives in mixed environments. It’s comfortable in a 3PL rack aisle, a manufacturing cell, a retail stockroom, or a van stock operation. With the right app stack, it can switch roles across receiving, counts, picks, pack/ship, and even light WIP transactions without making IT juggle different device models.
How We Evaluated Mobile Apps
We looked at how apps behave on real floors, not just in demos. A smooth demo can mask trouble once you hit bad Wi‑Fi, dirty barcodes, or high transaction peaks. We prioritized apps that keep workers fast while protecting the ERP from noisy, chatty calls. If an app needs flawless connectivity to work, that’s a red flag for operational resilience.
We also graded apps on their fit for Android rugged scanners: barcode intent support, one‑hand usability, large touch targets, and motion‑tolerant scanning. On-device label printing mattered too - ZPL/CPCL support, driver reliability, and print queueing prevent backups at shipping.
Finally, we considered governance: MDM/EMM compatibility, role‑based access, audit trails, TLS, and the ability to meet IT’s requirements without slowing operators. If security is an afterthought, the project won’t pass an enterprise review board or a customer audit.
Top 10 Mobile Apps for the Zebra MC22
Here’s a balanced list covering scanning, WMS workflows, telnet/browser clients, printing, PTT, remote support, and device management. Your mix may vary by ERP/WMS and process focus, but this set gives you a reliable foundation.
1) Zebra DataWedge
DataWedge is the MC22’s scanning backbone. It routes barcode reads into any app via keystrokes or intents, which means you can enable enterprise-grade scanning in minutes - even for apps that weren’t built for scanners. Configure profiles per app, set prefix/suffix rules, and apply formatting to match field expectations.
Practical tip: create separate DataWedge profiles per line-of-business app. Tune symbologies, laser aim, and redundancy to cut misreads. Set per-app wedge behavior so a browser session, a telnet client, and a native WMS app all receive exactly what they need.
Why it matters: no extra SDK coding, consistent operator experience, and stronger read rates on damaged or tiny labels. It’s the simplest way to turn the MC22 from a generic Android into a purpose-built scanner.
2) SOTI MobiControl Agent
An MDM/EMM is non-negotiable at scale. SOTI’s agent streamlines enrollment, pushes app updates, enforces kiosk modes, and locks down radios and settings. On the MC22, it saves hours by pushing DataWedge configurations and certificates, then monitoring device health.
Use cases: zero-touch enrollment, staged upgrades, and rapid rollback if a new build misbehaves. You also get remote control to help operators in the aisle - no need to bring devices back to IT for basic troubleshooting.
If you prefer a different MDM (Workspace ONE, Intune), the same principles apply: consistent configurations, governed app catalogs, and attested device posture.
3) Cleverence Inventory
A mobile warehousing layer built to work alongside your ERP/WMS rather than replacing it, Cleverence Inventory focuses on real-time inventory accuracy for manual operations. You get guided Android workflows (receiving, labeling, put-away, picking, packing, shipping, cycle counts, transfers, returns, on‑device ZPL/CPCL printing, optional RFID) running sub-second on the MC22. Under the hood sits an offline‑first engine with local queueing and an embedded device database, automatic sync, conflict resolution, and prioritization of critical transactions. Its middleware handles data mapping to ERP objects (GR/GI, transfer orders, adjustments), buffers high-volume mobile traffic, and posts safely and idempotently to systems like SAP ECC/S/4HANA, Oracle E‑Business/Fusion, Microsoft Dynamics 365, plus NetSuite and Odoo via connectors/APIs. Security spans HTTPS/TLS, JWT auth, bcrypt, encryption at rest/in transit, role‑based access, and audit logs. It’s hardware‑agnostic with deep Zebra optimizations, and typical pilots start small - cycle counts or receiving in 2–4 weeks - before scaling to more flows and sites.
4) Ivanti Velocity (Wavelink)
If your warehouse relies on telnet/VT/5250/3270 or legacy green screens, Velocity brings them into a touch-friendly shell. It maps function keys to modern gestures, supports barcode intents, and lets you modernize screens without rewriting a host application.
This is ideal during ERP/WMS transitions. Keep host flows stable, give operators a cleaner UI on the MC22, and migrate gradually. Velocity’s scripting can pre-validate scans, reducing garbage data before it reaches the host.
The result: fewer training hours when you introduce the MC22, and fewer mis-scans caused by tiny on-screen elements that weren’t designed for mobile.
5) Zebra Enterprise Browser
Browser-based WMS and SCM portals are common; they just need the right shell. Enterprise Browser adds hardware APIs, barcode intents, and kiosk control so your web app behaves like a first-class scanner app on the MC22.
Pair it with DataWedge and an MDM to create a controlled, single-app experience with a large scan button, vibration feedback, and form validation. It’s a pragmatic bridge for teams shipping HTML/JS front-ends while they plan native or hybrid apps later.
Bonus: with proper caching and offline heuristics (where feasible), you can make frequently used screens feel snappier without changing backend logic.
6) Zebra PrintConnect
When labels back up, everything backs up. PrintConnect provides an Android print service for Zebra printers using ZPL/CPCL, including variable data replacement. It’s the cleanest way to print from MC22 apps without writing custom socket code.
Use it for GS1/UCC-128, license plates, carton labels, or packing slips. Pair with on-device templates so operators can reprint fast if a label smudges or a roll jams - no detours to a workstation.
Pro tip: standardize templates across sites. Keep your ZPL in source control, version it, and push updates via MDM so every device prints the same way.
7) TeamViewer QuickSupport (Zebra Add‑On)
Remote support is priceless when devices roam. TeamViewer’s Zebra add‑on enables full remote control on the MC22, reducing mean time to resolution and saving walks to IT. Record sessions for training and audit purposes if policy allows.
Use it for live debugging of scan profiles, app settings, and printer pairing. Technicians can watch an operator reproduce an issue and nudge the fix in real time.
Security note: wrap access with SSO and RBAC, require approved operator consent, and log activity according to your governance policy.
8) Zebra Workcloud PTT Pro (formerly Workforce Connect)
Push-to-talk turns the MC22 into a team radio - no extra device to carry. Configure channels for receiving, picking, and shipping, and add presence so supervisors can see who’s available.
In fast-moving operations, PTT shortens the loop for slot changes, over-receipts, or carrier pickup windows. Operators don’t abandon a task; they get an instruction and keep moving.
Combine PTT with a simple escalation flow: if an exception hits, trigger a channel ping or a direct call to a lead who can authorize a variance on the spot.
9) Microsoft Dynamics 365 Warehouse Management (mobile app)
For organizations on Dynamics 365 Supply Chain Management, the Warehouse Management mobile app is the natural fit for receiving, picks, cycle counts, and movements. It supports barcode scanning via intents and benefits from Microsoft’s continuous updates.
If you run hybrid flows (e.g., some processes in D365, others in a third-party WMS), use MDM to pin app versions and maintain consistent UX across sites. Validate label symbologies and units of measure to avoid mismatched data on scans.
Govern upgrades: pilot in a single building, capture error rates, and only then promote to the broader fleet with staged rings.
10) VMware Workspace ONE Intelligent Hub
As an alternative to SOTI or Intune, Workspace ONE provides strong EMM features across enrollment, application lifecycle, and device compliance. It’s well-suited if your enterprise already standardizes on VMware for identity and endpoint management.
On the MC22, use it to enforce kiosk modes, push DataWedge XML, configure Wi‑Fi/EAP certs, and provide a curated app catalog by role. The result is a clean operator experience and fewer accidental settings changes.
Report on device posture and remediate quickly - expired certs and outdated OS builds are a silent source of scanning errors and sync issues.
Setup and Configuration Tips that Save Hours
Start with profiles, not people. Define app bundles and DataWedge profiles per role - receiving, cycle counts, and picking often need different symbologies and keyboard behavior. Role-centered configuration shortens training and creates predictable behavior across shifts.
Stage devices the same way every time. Zebra StageNow or your MDM’s bulk enrollment flows prevent drift. Bake Wi‑Fi, time zone, keyboard, and scan trigger behavior into the initial profile so Day 1 feels familiar.
Test labels and printers in context. A label that prints beautifully on a desk may smear on the floor. Validate heat, speed, and darkness settings at real throughput. Keep spare printheads and rollers where they’re needed to avoid long stoppages.
Scanning, Label Printing, and RFID Considerations
Scanning is more than pointing and shooting. Tune DataWedge for your dominant symbologies, disable noise you never use, and set good/bad read feedback that operators can feel with gloves on. Multi-barcode capture is handy for cases with multiple identifiers - configure parsing to fill the right fields.
For label printing, standardize ZPL templates and version them. If operators must reprint from the device, expose minimal options: label type and count. Less choice reduces mistakes and makes audits easier.
If RFID enters the mix, pilot it narrowly - high-value SKUs, RTIs, or garments with embedded tags. RF behavior is environment-sensitive; test in your rack geometry, with your metals, and your forklifts before you bet big.
Security, Governance, and MDM Practices
Lock the device to its job. Kiosk modes, per-app VPN where required, and limited settings access keep the MC22 focused and safe. Enforce TLS everywhere, pin known-good CAs, and rotate credentials on a schedule.
Adopt role‑based access in the apps, not just on the device. Receiving and adjustments shouldn’t share the same powers. Maintain audit logs for scans, postings, and label prints. Those traces pay for themselves the first time you chase a phantom variance.
Remote support is power - treat it as privileged. SSO, RBAC, consent prompts, and session recordings where policy allows mean you can help fast without opening side doors.
Performance and Offline Strategies on the MC22
Even great Wi‑Fi has dead spots. Apps should queue locally and sync automatically when connectivity returns. That protects the ERP from half-written transactions and keeps operators moving. Sub‑second device response is the standard to aim for - latency kills throughput before you notice it.
Think batching versus chatty calls. If your app posts every scan individually, your ERP will show it by lunchtime - timeouts, locks, or throttling. Prefer safe, idempotent posting with clear error codes and retry policies.
Instrument the floor. Track items per minute, error rates, and queue health. These metrics let you spot a misconfigured profile or a weak AP before it becomes a labor problem.
Integrating MC22 Apps with ERP/WMS
The MC22 is the edge; your ERP/WMS is the system of record. The glue matters. Data mapping between mobile payloads and ERP objects (goods receipts/issues, transfer orders, adjustments) prevents translation errors and weird edge cases that cause reversals and recounts.
Prioritize idempotency. If a device retries, the ERP should recognize the duplicate and move on without double-posting. Maintain audit trails with timestamps and operator IDs to help reconcile and to support cycle count variance workflows.
When evaluating warehouse mobility layers, look at offline behavior, conflict resolution, and connector maturity for your ERP. That’s where projects succeed quietly - or struggle loudly.
TCO, Pilot Plans, and Rollout Roadmaps
Budget beyond licenses. Factor in staging hours, templates for labels, training time, and process tweaks that emerge during pilots. Total cost of ownership often falls when you cut recounts, shorten picks, and reduce workstation dependency for printing and transactions.
Run a tight pilot: one process (e.g., cycle counts or receiving), one area, a handful of MC22s. Measure items per minute, variance rates, and posting latency. Iterate, expand to more processes and sites after the numbers hold.
Document decisions. Profile names, label versions, MDM policies - all of it. Six months later, you’ll thank yourself when you roll to a second building or bring a 3PL partner onto the same stack.
Conclusion
Choosing the best mobile apps for the Zebra MC22 is less about flashy features and more about how well the pieces fit: scanning that never hesitates, printing that never jams the flow, offline that never loses work, and integrations that never overwhelm the ERP. Start with the essentials above, pilot deliberately, and scale what the floor proves out - not what the slide deck promised.
Whether you lean on telnet modernization, a browser shell, or a dedicated warehouse mobility layer, the MC22 can be your steady, fast, and reliable companion. Build the right stack, keep it governed, and measure relentlessly.
Your operators will feel the difference in their hands; your inventory accuracy and throughput will show it on paper.
FAQs
-What’s the quickest win when setting up a new MC22 fleet?
Standardize DataWedge profiles and push them with your MDM. In a single afternoon, you can align scan behavior across apps and roles, eliminating a top source of early operator confusion.
-Should I choose a native WMS app, a browser client, or a telnet client?
Match it to your system and timeline. If you have a modern WMS app, use it. If you’re on web flows, wrap them in Enterprise Browser for hardware access. If you’re on host telnet, modernize with Velocity or similar while you plan the next step.
-How do I prevent duplicate postings to the ERP when Wi‑Fi drops?
Use an offline‑capable mobile layer that queues locally, retries safely, and posts idempotently with audit trails. Avoid designs that fire one API call per scan without batching or conflict handling.
-Do I need an MDM if I only have a few devices?
Even with a small fleet, MDM saves time and reduces drift. It enforces kiosk modes, manages certificates, and lets you remote-support operators. You’ll recover the effort the first time you avoid a walk to IT.
-How should I handle label templates across multiple sites?
Keep ZPL templates in version control, document changes, and deploy via MDM. Make reprint flows simple - label type and count only - so operators move quickly while you maintain consistency.