How to Manage Every Shopify POS Device from a Single Dashboard: Visibility, Security, and Best Practices

Table of Contents

1. Key Highlights:
2. Introduction
3. What the Devices view shows and why it matters
4. Accessing Devices and minimum requirements
5. Inventory vs. control: when to use Devices and when to use MDM
6. Day-to-day workflows enabled by centralized device visibility
7. Security controls and permission governance
8. Onboarding new POS hardware: a step-by-step checklist
9. Version management and update strategies
10. Handling lost or stolen devices: practical steps
11. Multi-location considerations and pop-up operations
12. Troubleshooting common device problems
13. Real-world scenarios: three examples
14. Policies, metrics, and KPIs to run a healthier POS fleet
15. Integrations and automation to reduce manual work
16. Preparing for audits and compliance reviews
17. Cost-benefit considerations for MDM adoption
18. Recommended device naming and tagging conventions
19. Retiring and recycling POS hardware
20. Practical checklist for the first 30 days of adopting the Devices view
21. When to escalate to Shopify support or your MDM vendor
22. Closing operational advice
23. FAQ

Key Highlights:

• Shopify’s Devices view now lists every tablet, phone, card reader, and mobile POS running POS 11.9 or higher, giving merchants centralized visibility into device status and app versions.
• Administrators can remotely log devices out or remove access (requires staff permissions); businesses with multiple locations should pair this with mobile device management (MDM) for version control and policy enforcement.

Introduction

Retail operations depend on reliable point-of-sale hardware: tablets that process transactions, card readers that accept payments, and phones used at pop-up stands. Fragmented device management contributes to downtime, inconsistent customer experiences, and security gaps. Shopify’s expanded Devices view in the POS channel addresses that by presenting every active POS device in a single, searchable list. That visibility shortens the time it takes to detect problems, standardize software versions, and react to security incidents such as lost or stolen hardware.

This article walks through the Devices view capabilities, explains how to use its security controls, and lays out practical policies and workflows to keep a fleet of POS devices secure, compliant, and up to date. Real-world examples illustrate how teams reduce outages and speed incident response. Actionable checklists, onboarding steps, and a thorough FAQ finish the guide so retail managers, IT leads, and operations teams can implement immediate improvements.

What the Devices view shows and why it matters

The Devices view in Shopify’s POS channel aggregates every registered POS endpoint running Shopify POS 11.9 or newer. At a glance, administrators can:

• See which devices are online or offline.
• Identify the installed POS app version on each device.
• Recognize device types (tablet, phone, card reader, mobile POS).
• Take security actions such as remotely logging a device out or removing its access completely (staff permission required).

Why this matters: a centralized inventory reduces ambiguity. When a store reports a payment failure, an admin no longer asks staff to read back device details. They can open Devices, filter for the store or device type, and determine whether the device is offline, running an out-of-date app, or flagged for removal. That saves time and reduces ticket escalation.

Visibility also supports compliance. Payment card industry (PCI) rules and internal audit requirements expect merchants to know where payment-processing devices are and to demonstrate controls over access. A single source of truth helps meet those obligations while providing the factual basis for incident reports.

Accessing Devices and minimum requirements

To reach the Devices list, open the POS channel in the Shopify admin and select Devices. Two practical constraints matter:

• Only devices running Shopify POS 11.9 or higher will appear in the list.
• Device removal and certain controls require staff permissions configured under Settings > Users.

Practical implications:

• Before rolling this into a fleet management workflow, confirm that all devices are updated to POS 11.9+. Devices on older versions will not be visible and thus remain blind spots.
• Review staff roles. Restrict device removal to trusted administrators. A removal control is powerful; used incorrectly it can cause a device to lose access during a busy shift.

Common reasons a device might not appear:

• The installed POS version predates 11.9.
• The device has never successfully registered to the Shopify account.
• Network problems are preventing synchronization.

Inventory vs. control: when to use Devices and when to use MDM

The Devices view provides a unified inventory and immediate security actions, but it is not a substitute for a full mobile device management (MDM) platform for multi-site retailers. MDM platforms provide features that extend beyond inventory:

• Enforcing OS and app update policies across thousands of endpoints.
• Remote wipe if data must be purged.
• Configuration profiles, VPN settings, and Wi-Fi provisioning by location.
• App distribution and silent updates.
• Geofencing and enforcement of physical location constraints.
• Detailed telemetry and compliance reporting.

Use Devices for rapid operational visibility and quick remediation. Pair Devices with MDM for policy enforcement at scale. For single-store or very small multi-location businesses, Devices might be sufficient on its own; for larger or regulated operations, MDM is essential.

Example: a regional fashion chain uses Devices to spot a cluster of tablets in one store that are still on an older POS build. The operations manager then uses their MDM console to push the updated POS app to that location and enforce automatic updates going forward. The combination of Shopify Devices for awareness and the MDM for enforcement reduces the window of exposure.

Day-to-day workflows enabled by centralized device visibility

Operational procedures change when device information is centralized.

Shift startup checks:

• Confirm each POS device in the store is online and running the current app version.
• Verify the card reader is paired and that the payment terminal shows connectivity.
• Remotely log out any devices found to be assigned to the wrong location or staff member.

Incident response (lost or stolen device):

• Immediately log the device out through Devices to invalidate the session.
• Use staff permission controls to remove the device’s access from the account.
• If the device stores customer data or was used to process payments while not present, escalate to IT and compliance, and consider remote wipe via MDM if available.

Routine audits:

• Monthly review of Devices to identify outdated app versions, devices offline for extended periods, or devices assigned to staff who no longer work for the company.
• Reconcile Devices against physical asset inventory to detect missing devices.

Software rollout and testing:

• Use Devices to monitor adoption rates after a POS update. If a subset of devices does not update, investigate network constraints, MDM rules, or user actions that may have prevented the update.

A concrete flow for handling a nonresponsive checkout during a busy period:

1. Tier 1 associates report that a checkout tablet is not processing payments.
2. The operations lead opens Shopify admin > POS > Devices and confirms the device is offline and running an older app version.
3. The lead either instructs on-device troubleshooting steps (reboot, reconnect Wi-Fi) or ejects the device from the session and assigns a spare tablet.
4. If the device was recently updated or exhibits repeated failures, the lead flags it for full diagnostic or replacement.

Security controls and permission governance

Device logout and removal are effective tools, but they must live in a governance framework to avoid accidental service disruption or compromised security.

Recommended role model:

• Device administration role: full access to Devices, required to perform remote logout and removal. Limit membership to IT, operations managers, or senior store managers.
• Standard staff role: ability to use POS on assigned devices but no device removal privileges.
• Audit-only role: ability to view Devices and logs for compliance reviews, without control capability.

Permissions to check in Settings > Users:

• Who can remove devices?
• Who can add or assign devices to a location?
• Who can modify staff accounts that interact with devices?

Device removal should be limited because removing a device entirely could disrupt a store mid-shift if misused. A better pattern: enable remote logout for immediate deauthorization and reserve full removal for confirmed lost/stolen hardware or permanent retirement.

A recommended five-step policy for device incidents:

1. Identify: Use Devices to verify the device status and last activity.
2. Deauthorize: Log the device out remotely to block access immediately.
3. Revoke and rotate: Disable or rotate the staff credentials used on the device if they are believed to be compromised.
4. Remove: If the device is lost, stolen, or being retired, remove access permanently (requires authorized persona).
5. Document: Record the incident in an asset and security log for audits.

Onboarding new POS hardware: a step-by-step checklist

Standardizing onboarding reduces configuration drift and improves uptime. The following checklist gives a repeatable process:

Pre-setup (IT or operations):

• Register the device serial number and asset tag in the asset management database.
• Create or designate a staff user account for initial setup.
• Prepare Wi-Fi credentials and any VPN or proxy details for secure networks.

Initial setup on device:

1. Update device OS to the latest stable release supported by the hardware.
2. Install the Shopify POS app and ensure it is version 11.9 or higher.
3. Sign into the Shopify POS with the designated setup account.
4. Name the device using a consistent convention: [StoreCode]-[DeviceType]-[Number] (e.g., NYC01-TAB-01).
5. Assign the device to the correct store/location within Shopify.
6. Pair the card reader and test a simulated payment or use test mode if available.
7. Verify the device appears in Shopify admin > POS > Devices.
8. Enroll the device in your MDM solution for policy enforcement, if applicable.
9. Document the device registration details, including assigned staff, asset tag, and device serial.

Naming conventions are easy to overlook but save hours during troubleshooting. Include store code, device type, and a unique number. Example: "SFO-002-REGISTER" or "POPUP-LA-TAB1" for a temporary event device.

Version management and update strategies

App version visibility is one of the most compelling operational features. Version drift — where some devices run older POS builds while others are current — leads to inconsistent behavior across stores. Use Devices to:

• Identify devices on older versions.
• Prioritize updates for devices that handle payments or high traffic.
• Confirm rollouts after scheduled maintenance windows.

Update strategies:

• Staged rollout: update a subset of devices first, verify stability, then push to the remainder.
• Maintenance windows: define times when updates and reboots are acceptable (outside peak hours).
• Auto-update policy via MDM: where possible, configure silent updates to avoid missed installations.

When an update causes issues:

• Roll back affected devices to the previous stable build if possible, or reassign checkout tasks to unaffected devices.
• Record the affected versions and symptoms to create a rollback plan for future releases.

Example: a cafe chain notices that a new POS build introduces a card reader pairing bug. By using Devices, the technical lead quickly finds that only two stores have updated. They instruct those stores to revert or switch to a backup device while a fix is developed, minimizing disruption.

Handling lost or stolen devices: practical steps

Stolen hardware is a material risk for retail. Payment devices can contain sensitive session tokens, cached user credentials, or customer information. A rapid, staged response minimizes exposure.

Immediate actions:

• Use Devices to remotely log out the missing device to invalidate the session.
• Remove device access if recovery is unlikely. Confirm that the person executing removal has the appropriate staff permission.
• Change passwords and rotate API keys or other credentials that may have been stored on the device.
• If the merchant uses MDM, initiate a remote wipe to remove stored data and credentials.
• Notify the payment processor and, if applicable, affected customers in accordance with breach policies.

Follow-up steps:

• File an incident report in your security log with timestamps and actions taken.
• Evaluate whether additional devices were impacted, looking for odd logins or suspicious transactions.
• Reassess the device lifecycle and asset tagging to reduce the chance of loss recurrence (for example, hardware locks or tracking stickers).
• If data exposure is possible, escalate to legal and compliance teams for notification obligations.

Practical tip: accumulate evidence quickly. Screenshots of the Devices list showing the device’s last seen time, location, and app version support insurance claims and police reports.

Multi-location considerations and pop-up operations

Managing devices across multiple locations multiplies complexity. The Devices view centralizes visibility but also requires policies tailored to distributed environments.

Inventory alignment:

• Maintain a master inventory mapping each device to a store, including serial number and MDM enrollment status.
• Run reconciliation monthly to catch orphaned devices assigned to closed stores or deactivated staff.

Temporary operations (pop-ups, events):

• Use naming conventions that include the event code and dates, e.g., "POPUP-COMA-20260625-TAB1".
• Prepare temporary Wi-Fi provisioning that restricts access to event-specific networks and limit device privileges for short-term staff.
• After the event, use Devices to deauthorize and either reassign or remove devices promptly.

Cross-location theft detection:

• Devices that move between locations unexpectedly will appear in Devices and MDM logs. If a tablet assigned to Store A shows activity from Store B, investigate staff assignments and asset transfers.

Scaling tip: for a chain with dozens or hundreds of locations, integrate device inventory with your broader IT asset management (ITAM) system. Use APIs or daily exports from Shopify to keep records synchronized.

Troubleshooting common device problems

The Devices view helps identify problems, but resolving them requires a combination of local troubleshooting and backend checks. Here are common issues and troubleshooting steps.

Device not showing up in Devices:

• Confirm POS app is version 11.9 or higher.
• Check the device’s network connection and that it can reach Shopify services.
• Verify the device has successfully signed into the correct Shopify account.
• Reinstall or update the POS app and retry.

Device offline but physically present:

• Examine local Wi-Fi and network health; reboot the device and the network gateway.
• Confirm the device is not in airplane mode or restricted by an OS-level firewall.
• If the device is on an older OS that has background services restricted, update the OS.

Card reader pairing failures:

• Ensure the POS app and card reader firmware are both up to date.
• Verify Bluetooth permissions and that no other device is connected to the reader.
• Restart both the POS device and the card reader; re-pair and test.

Slow or lagging transactions:

• Test the network throughput at the store; consider a wired connection for fixed terminals.
• Check for background processes on the device that might consume CPU or network.
• If only one device is slow, remove any experimental apps or settings that could interfere.

If problems persist after standard troubleshooting, capture logs (if available), document each step taken, and escalate to Shopify support and your MDM vendor with timestamps and device identifiers.

Real-world scenarios: three examples

Example 1 — Regional grocery chain A regional grocery chain with 35 stores used the Devices view to discover that 12 devices at a single distribution hub were still running an older POS build after a partial rollout. The operations director paused further updates, used MDM to push the correct build, and issued a short staff training on new checkout flows. The chain reduced payment exceptions by 47% in the following month.

Example 2 — Coffee shop with multiple kiosks A coffee concept with four kiosks per venue used Devices to centralize device status checks during morning rush. When a card terminal at a busy kiosk failed, managers logged the terminal out remotely and switched payments to a backup tablet within 90 seconds, avoiding long lines. The chain adopted a spare-device policy and decreased average checkout downtime from 9 minutes to under 2 minutes.

Example 3 — Pop-up retail and asset tracking A fashion retailer running weekend pop-ups relied on naming conventions and Devices to track devices. After a pop-up, two devices were missing from inventory. Devices showed they had last checked in at the event location but not again. With MDM remote wipe and logged removal in Devices, the retailer mitigated risk and updated internal procedures to include mandatory check-in scans before staff leave the event.

These scenarios illustrate measurable benefits: fewer payment errors, faster incident response, and better postmortem reporting.

Policies, metrics, and KPIs to run a healthier POS fleet

Operationalizing device management requires measurable objectives.

Key policies to implement:

• Device lifecycle policy: define procurement, deployment, maintenance, decommission steps.
• Least privilege access model: who can perform device removal, who can view devices, and who can enroll devices.
• Incident response playbook for lost or stolen devices.
• Update policy: how frequently devices must be updated and what constitutes an emergency patch.

KPIs to track:

• Percentage of devices running the latest POS app version.
• Average time to remediate device incidents (from report to resolution).
• Device uptime per store or region.
• Number of devices offline for more than 24/48 hours.
• Time between device registration and MDM enrollment.

Reporting cadence:

• Daily: high-level dashboard for offline devices and critical issues.
• Weekly: version distribution and remediation progress.
• Monthly: audit report for decommissioned and unaccounted-for assets.

These metrics create a feedback loop that shows whether operations and IT are improving device reliability and security.

Integrations and automation to reduce manual work

Automation reduces human error and accelerates response times. Common integrations:

• MDM integration for silent app updates and remote wipe.
• ITAM system synchronization to maintain one source of truth for asset status and lifecycle.
• Ticketing system integration to create service tickets automatically when a device goes offline or experiences repeated failures.
• Alerting: configure notifications for devices that go offline unexpectedly, run older app versions, or show anomalous behavior.

Use automation carefully. Not every change should be automatic; for example, avoid automated device removal without human verification. Automate detection and ticket creation, but reserve destructive actions for authorized personnel.

Preparing for audits and compliance reviews

Shopify's Devices view supports audit readiness by supplying evidence of device inventory, app versions, and actions taken (logout or removal). Prepare for audits by:

• Retaining logs of device actions and staff permissions changes.
• Keeping a documented update and decommissioning history.
• Demonstrating least privilege access and periodic review of staff roles.
• Showing reconciliation between physical assets and Devices listings.

Auditors often seek proof of control over payment terminals. Provide screenshots or exports from the Devices view that show device names, last seen timestamps, and assigned locations, backed by your asset inventory and incident logs.

Cost-benefit considerations for MDM adoption

MDM systems come with licensing and operational costs, but they deliver benefits that typically justify the investment for larger merchants.

Cost drivers:

• Number of devices enrolled.
• Required features (remote wipe, geofencing, app distribution).
• Integration and maintenance overhead.

Benefits:

• Reduced manual updates and inconsistent configurations.
• Faster incident response through remote wipe and enforced encryption.
• Simplified onboarding and decommissioning.

Decision criteria:

• If your business operates more than a handful of locations or has strict compliance needs, MDM is high ROI.
• If device turnover is high (seasonal staff, frequent pop-ups), MDM decreases friction and improves security posture.

Recommended device naming and tagging conventions

Consistent metadata makes Devices and ITAM more usable.

Sample convention:

• Format: [Region/StoreCode]-[DeviceType]-[SequentialNumber]-[UseCase]
• Example: "NYC02-TAB-03-REGISTER" or "LA-POPUP-01-MOBILITY"

Include tags for:

• Assigned staff or role (if fixed).
• MDM enrollment status.
• Purchase date and warranty expiry.
• Retirement date or scheduled replacement.

Tagging supports quick filtering in Devices and speeds root cause analysis during incidents.

Retiring and recycling POS hardware

When hardware reaches end-of-life, follow a controlled process:

1. Document the device in the decommissioning register.
2. Remove the device from Shopify Devices and the MDM console.
3. Perform a remote wipe (MDM) or factory reset and remove any stored credentials.
4. Physically log and track the device for recycling or resale.
5. Update asset inventory and reconcile financial records.

If a device will be redeployed at a new location, re-enroll it in MDM, rename it according to the naming convention, and verify connectivity before assigning it to staff.

Practical checklist for the first 30 days of adopting the Devices view

Day 1–7:

• Update all devices to POS 11.9+ and confirm they appear in Devices.
• Set permissions for device removal and audit viewers.
• Establish naming conventions and retroactively rename devices for clarity.

Day 8–14:

• Enroll devices in MDM if not already done.
• Identify devices on older app versions and schedule a staged update.
• Create a lightweight incident response playbook for device loss/theft scenarios.

Day 15–30:

• Run a full inventory reconciliation between Devices and physical assets.
• Measure baseline KPIs (percentage on latest app, average remediation time).
• Train store managers on how to report device issues and how the Devices list works.

After day 30: iterate. Review policies quarterly and refine thresholds and automation rules.

When to escalate to Shopify support or your MDM vendor

Escalate to Shopify support if:

• A device running POS 11.9+ appears inconsistent with Shopify’s expected behavior (e.g., cannot register or authenticate).
• You encounter account-level anomalies where multiple devices log out inexplicably.
• You suspect a platform-level outage.

Escalate to the MDM vendor if:

• Enrollment failures occur at scale.
• Remote wipe or automated update operations fail on a subset of devices.
• Device sensors or telemetry required for geofencing and location tracking show anomalies.

Always capture logs, timestamps, and device identifiers before escalation to reduce troubleshooting time.

Closing operational advice

Centralized device visibility changes how retail operations manage risk and uptime. Treat the Devices view as the operational heartbeat for your stores. Use it for daily checks, incident response, and audit preparation. Combine it with MDM for enforcement at scale and with a disciplined governance model that restricts destructive actions to authorized personnel.

Consistent naming, regular reconciliation, and clear escalation paths turn the Devices list from a passive inventory into a strategic tool that reduces downtime and tightens security.

FAQ

Q: What devices will appear in Shopify’s Devices view? A: Only devices running Shopify POS version 11.9 or higher appear. This includes tablets, phones, card readers, and other mobile POS devices that have been registered and are connected to your Shopify account.

Q: How do I access the Devices view? A: Open the Shopify admin, select the POS channel, and choose Devices. The list is accessible to users with permissions to view the POS channel; removal actions require elevated staff permissions set in Settings > Users.

Q: Can I remotely remove a lost or stolen device? A: Yes. Devices can be remotely logged out and removed from your account. Removal is restricted to staff roles with the appropriate permissions. For additional action, use your MDM solution to perform remote wipe if available.

Q: My device is not showing up — what should I check first? A: Confirm the POS app is at least version 11.9, verify the device has an active network connection, and ensure the device has been signed into the correct Shopify account. If the POS version is older, update the app and try again.

Q: Should my business use MDM alongside Shopify Devices? A: For single-location or very small operations, Devices may suffice for inventory and basic control. Multi-location businesses, high device counts, and regulated industries should adopt an MDM to enforce updates, perform remote wipe, and apply configuration profiles at scale.

Q: Who should have permission to remove devices? A: Limit removal permissions to a small group of trusted administrators, such as IT leads or senior operations managers. Remote logout can be more widely assigned for quick deauthorization without full device removal.

Q: How should I name and tag devices? A: Use a convention that includes store code, device type, and a unique identifier, e.g., "SFO-001-TAB-REGISTER". Add tags for MDM enrollment status, assigned staff, purchase date, and warranty expiry.

Q: What immediate steps should I take when a device is stolen? A: Remotely log out the device in Shopify Devices, remove access if recovery is unlikely, initiate a remote wipe via MDM if available, rotate any credentials potentially exposed, and file an incident report with timestamps and actions taken.

Q: How often should I audit the Devices list? A: Conduct a basic check daily for critical issues and a detailed audit monthly to reconcile Devices with physical assets and identify devices offline for extended periods or running outdated app versions.

Q: Can I automate actions based on Devices status? A: Automate detection and alerting (for example, create tickets when a device is offline or on an old version), but reserve automated destructive actions, such as removal, for authorized personnel after verification.

Q: What KPIs should I track to measure device health? A: Track percentage of devices on the latest POS app version, device uptime, average time to remediate incidents, number of devices offline beyond 24/48 hours, and device churn or theft incidents.

Q: Does removing a device from Shopify delete it from my MDM or other systems? A: No. Removing a device from Shopify revokes its access to your Shopify account but does not automatically remove it from MDM or IT asset management systems. Coordinate removal across systems as part of your decommission workflow.

Q: Where can I find more technical steps for managing devices? A: Use the Shopify Help resources and your MDM vendor documentation for detailed, platform-specific instructions. Maintain an internal runbook that reflects your organization’s policies and the exact steps for remote logout, removal, and wiping devices.

Q: What’s the best practice for pop-ups and temporary deployments? A: Use a naming convention that includes event code and dates, preconfigure Wi-Fi and security settings, enroll devices in MDM with temporary profiles where possible, and deauthorize or remove devices promptly after the event.

Q: How do I prepare for audits involving POS devices? A: Keep device action logs, show reconciliation between Devices and asset inventory, demonstrate least privilege access, and maintain records of updates, incidents, and decommissions. Provide auditors with consistent screenshots or exports of the Devices list and asset registers.

Q: What mistakes should be avoided when using Devices? A: Avoid granting wide permissions for device removal, neglecting MDM enrollment for distributed fleets, failing to name devices consistently, and postponing updates that create version drift across your fleet.

Q: How quickly should I expect to remediate device issues using Devices? A: Many incidents can be mitigated within minutes—remote logout and reassignment of a spare device can restore service quickly. Track your own average remediation time to set and meet operational targets.

Q: Will Devices tell me the physical location of a device? A: Devices show the store or location assignment and last-seen status. For more precise location telemetry, combine Devices with MDM solutions that support geofencing and GPS reporting.

Q: Are there costs associated with using Devices? A: Devices is a feature in Shopify admin. Costs mainly arise from complementary services like MDM licensing and internal staffing to manage the program. Evaluate MDM costs against savings from reduced downtime and improved security.

Q: What should be included in my 30-day rollout plan for Devices? A: Update devices to POS 11.9+, set permissions, standardize naming, enroll devices in MDM, reconcile inventory, and train staff on reporting and incident procedures. Measure baseline KPIs and iterate.

Q: Who should be on the device incident response team? A: At minimum, include IT/technical lead, an operations manager for the affected store(s), the security/compliance contact for breach evaluation, and someone with the authority to remove devices in Shopify and MDM.

Q: If a device keeps going offline, what deeper checks should I run? A: Test store network reliability, examine device logs and MDM telemetry, check for OS-level issues interrupting background services, and rule out environmental factors like power management settings or cellular signal reliability.

Q: Can I restrict which devices can process payments? A: Configure permissions and device assignments in Shopify and enforce policies with MDM to limit payment processing to approved, compliant devices. Use role-based access and physical controls to reduce unauthorized usage.

Q: How do I handle a device being repurposed between stores? A: Reassign the device within Shopify Devices, update the device name and tags to reflect the new location, and ensure MDM and asset inventory records are updated. If location-specific settings differ (Wi-Fi, VPN), confirm configuration is correct before the device returns to service.

Q: Where can I escalate if I suspect account-wide issues with devices? A: If you observe multiple devices failing or account-wide authentication problems, open a support case with Shopify and include device IDs, timestamps, and any error messages. Coordinate with your MDM vendor if enrollment or wipe actions are failing concurrently.

Q: Will Devices show devices used in guest checkout or non-staff accounts? A: Devices registers hardware running the Shopify POS app tied to your Shopify account. Guest or non-staff activity would not appear as a separate device unless it runs the POS app and signs into your account.

Q: Any final operational tips before I start using Devices? A: Start small—update and enroll a pilot group of devices, refine your naming convention and policies, and then scale. Use Devices for monitoring and incident response and rely on an MDM for enforcement at scale. Keep documentation and incident logs current so every device action is auditable and repeatable.