Choosing Your POS Devices for Multi-Location Retail

Choosing POS hardware for a multi-location retail business involves more than picking a screen size and a price point. The device platform you choose affects how your team interacts with customers, which peripherals you can use, and, perhaps less apparent, how much control you have over when software updates reach your stores.

This guide focuses on the tablet platform decision (iPad vs Android) and update management, not peripherals like card readers, printers, or scanners, which work with both platforms through the POS Hub. The first half helps you evaluate iPad and Android for your POS fleet, including a meaningful operational difference between the two that’s often overlooked. The second half walks through a simple, repeatable process for rolling out Shopify POS updates safely across all your locations.

Choosing your POS devices

iPad and Android both work with Shopify POS

Shopify POS runs on iPads and Android tablets. Both platforms support the same core features and the same peripherals through the Shopify POS Hub: card readers, receipt printers, barcode scanners, and cash drawers. The differences are in device management, update control, and cost.

iPad offers a narrower product line, which can simplify standardization when you want every location running the same hardware. Apple Business Manager provides a streamlined MDM enrollment path, and declarative device management (DDM) on iOS 17.2+ lets you lock devices to a specific app version (version pinning) per device group.

Android tablets cover a wider price range and offer native USB-C connectivity for wired peripheral connections. Managed Google Play lets you delay individual app updates by up to 90 days per app, giving you a clear testing window before any update reaches your fleet. Android also supports direct USB connections to peripherals without requiring a hub.

The best choice depends on what your team already uses, what your MDM supports, and how much flexibility you need on device cost. Check the POS compatibility page for current supported models on both platforms.

The update control difference between iPad and Android

This is worth understanding before you commit to a hardware platform, because it directly affects how you manage Shopify POS updates day to day.

On Android, your MDM can set Shopify POS to “Postpone” mode for any device group, which holds the current version for up to 90 days. When you’re ready, you switch that group to “Default” and the update rolls out. It’s straightforward, per-app, per-group control.

On iOS (17.2 and later), Apple’s declarative app management gives you precise version control. Through Apple Business Manager and a DDM-capable MDM, you can pin devices to a specific app version and block auto-update prompts entirely. When a version is pinned, the device ignores all automatic update checks until you change the configuration.

Jamf and Iru (formerly Kandji) support declarative app management with version pinning today. If you use a different MDM vendor, check with them to confirm support for this capability. Both device-based and user-based licensing through Apple Business Manager support version pinning.

The distinction between OS updates and app updates still matters. MDM vendors sometimes talk about “delaying updates for 90 days” when referring to operating system updates (iOS itself). App version control through declarative app management is a separate capability. Make sure your MDM configuration addresses both.

The main difference is the setup path: iOS uses Apple Business Manager, while Android uses Managed Google Play. Both achieve the same result: controlled, phased rollouts per device group.

Both platforms now offer strong update control when paired with MDM. If you’re evaluating hardware, factor in the broader differences (peripheral compatibility, device cost, staff familiarity) rather than update control alone. Switching platforms after you’ve deployed dozens of devices is expensive and disruptive, so the right choice is the one that fits your overall operational needs.

One more thing to plan for: New devices

By default, a new device installs the latest version of Shopify POS from the App Store or Google Play. With MDM and declarative app management on iOS (17.2 or later), your MDM’s app configuration can specify a target version for new enrollments, so new devices should match the rest of your fleet. On Android, Managed Google Play offers similar control. Without MDM, plan for new devices to arrive on the latest version and validate accordingly.

The complete Shopify POS hardware bundle.

Rolling out POS updates safely

Regardless of whether you choose iPad or Android, the principle is the same: test on a small group first, verify your workflows, and then roll out to everyone else.

Why phased rollouts matter

Every version of Shopify POS goes through extensive testing before release. But every retailer’s environment is different. Your specific card readers, receipt printers, POS UI extensions, and daily workflows might interact with a new version in ways that general testing can’t predict.

A phased rollout lets you catch those issues on a few devices before they affect every register in your fleet. It’s a small investment of time that protects your entire operation.

That said, the goal is always to end up on the latest version. Running old versions means missing bug fixes and security patches, and you’ll start seeing in-app prompts if your version falls too far behind. You can follow what’s in each new release through the Retail Release Roundup, which is updated every two weeks.

Payment Terminals and POS Hubs also receive periodic firmware updates. Terminal updates typically install automatically overnight when connected to power and Wi-Fi. For POS Hub, check for updates in device settings. Keeping all devices on the latest firmware is important. Updates include security patches, performance improvements, and compatibility fixes that ensure your terminals and hubs continue to work reliably with the POS app. Build firmware checks into your regular device management routine alongside POS app updates so your entire hardware stack stays current.

Step 1: Set up your device groups

Start with two groups in your MDM:

• Test devices: One to three devices that represent your typical store setup. If you can, choose devices at different types of locations, such as a busy store, a quieter one, and a mall location, so you’re testing in varied real-world conditions.
• All other devices: Your remaining fleet.

If you manage devices across many locations and want an extra layer of safety, you can add a middle group: a few devices at select locations, so no single store is fully on the new version until you’re confident. This way, if something goes wrong during testing, every location still has working devices on the previous version.

Step 2: Configure your update settings

On iOS (17.2 and later with declarative app management):

1. Pin your test group to the new version via your MDM’s declarative app configuration
2. Keep all other groups pinned to the current version
3. When your test group validates the new version, update the version pin for the next group
4. Repeat until all groups are on the new version

If your MDM doesn’t yet support declarative app management, use the on/off toggle approach: enable automatic updates for test groups, disable for others, and toggle per group as you validate.

On Android:

1. Set your test group to “Default” or “High Priority” in Managed Google Play settings
2. Set all other groups to “Postpone”
3. When your test group validates the new version, switch the next group from “Postpone” to “Default”

Contact your MDM vendor for platform-specific configuration steps.

Step 3: Test before you roll out

When your test devices receive the new version, have staff at your test locations run through this checklist before you enable updates for everyone else. It should take about 10 minutes during a quiet period.

Update validation checklist:

• Process a card payment (verify card reader connects and payment completes)
• Process a cash sale (verify cash drawer opens)
• Process a return
• Apply a discount
• Print a receipt
• Scan a barcode
• Open each POS UI extension you use (verify they load and function correctly)
• Check any third-party app integrations (loyalty programs, inventory systems, etc.)

If everything works, roll out to the next group. If anything breaks, stop the rollout, and contact Shopify Support or the extension developer before updating more devices.

Step 4: Time it right

A few practical scheduling tips:

• Update during off-hours. Configure your MDM to push updates overnight or before stores open. A device that starts updating during the lunch rush can cause problems at the register.
• Account for time zones. If you have locations across multiple regions, stagger your rollout so each store receives updates during its local off-hours.
• Give store managers a heads-up. Before you push an update, let managers know what’s changing and ask them to process a quick test sale the next morning.
• Stay current before busy periods. Start testing new versions two to three weeks before Black Friday or other peak sales periods. Aim to have all devices on the same tested version before the rush begins.

What to do if something goes wrong

Rolling back to a previous version of POS isn’t supported. The App Store and Google Play don’t allow reverting to older versions of any app. This is standard across all mobile apps.

If you find a problem during your phased rollout:

1. Stop the rollout. Don’t enable updates for any more groups.
2. Report the issue. Contact Shopify Support with the device model, OS version, and POS version number.
3. Submit diagnostic logs. In the POS app, go to … > Support > Report a Bug to send logs from the affected device.
4. Wait for the fix. The standard approach is to fix forward with a patch release.

This is exactly why phased testing matters. If you catch a problem on three test devices, the rest of your fleet stays on the working version while the fix is developed.

Making your decision

Here’s a quick comparison to help frame the hardware choice:

• Peripheral support: iPad: Full via POS Hub. Android: Full via POS Hub + native USB-C.
• App update control: iPad: Version pinning per group (iOS 17.2+ with DDM). Android: Delay up to 90 days per app.
• Device cost: iPad: Narrower range, higher floor. Android: Wider range of price points.
• MDM enrollment: iPad: Apple Business Manager. Android: Managed Google Play.

Neither choice is wrong. Both platforms support the same Shopify POS peripherals. iPad simplifies standardization with a narrower product line. Android offers more flexibility on device cost and native USB-C connectivity. The best choice depends on what your team already uses, what your MDM supports, and your budget.

Whichever platform you choose, pairing it with MDM and a phased rollout process is the safety net that lets you stay current without risking every register at once.

Next steps

• Check Shopify’s hardware compatibility page to verify your devices and peripherals work in your region
• Follow the Retail Release Roundup to see what’s in each new version of Shopify POS