Executive summary
- What: Shopify POS can now sign in a new device when a staff member approves the request from a nearby device that is already logged in, over Bluetooth or by QR code.
- Why: Typing account credentials on a sales floor is slow and exposes them in public. Approval based login removes both problems and ties every new device to a named approver.
- Who: Retail operations leads, store managers, and POS administrators running multi location fleets, seasonal staff, or pop-up events.
What changed
Bringing a new POS device online used to mean entering account credentials on that device, usually during a busy trading day. The new flow inverts that. The unprovisioned device advertises a login request, a nearby signed-in device detects it over Bluetooth, and a staff member holding the POS device setup role approves it with their store manager PIN. The new device lands in the correct shop and location with no typing. If Bluetooth is unavailable, a QR code shown on a logged-in device does the same job.
Session duration is the part worth reading carefully. By default an approved device is signed in for the current day only, so hardware pulled out for one event does not stay authenticated afterwards. A Forever option exists but is hidden in POS by default and must be exposed from the POS channel settings. The Allow nearby device log in setting itself ships turned on.
Why it matters
For a Plus merchant running dozens or hundreds of lanes, device provisioning is not an IT footnote. It is queue time. Every minute a lane sits unusable while someone retrieves a password is lost throughput at peak, and the usual workaround, a shared credential kept in the back office, is exactly the practice your security reviewers flag.
This change gives you a cleaner control model. Approval authority becomes a role you grant rather than a secret you distribute, so removing a leaver ends their ability to provision devices without a credential rotation across the estate. The default single day session matters most for activations, markets, and holiday overflow lanes: borrowed hardware expires on its own instead of relying on someone remembering to log it out.
If you are building out a broader retail stack, this pairs naturally with the device and permission hygiene covered in our Shopify POS setup guide for physical retailers.
Role-specific impact
- Marketers: Pop-ups, trunk shows, and activations get easier to staff. A device is provisioned on site in seconds and expires the same evening, lowering the friction of short retail moments.
- Developers: No API surface changed, but session lifetime affects anything built on POS UI extensions or custom staff workflows. Confirm your extensions behave correctly when a session ends mid shift rather than assuming a persistent login.
- Store admins: You own two decisions: who holds the POS device setup role, and whether the Forever duration is visible at all. Treat exposing Forever as a deliberate exception for fixed register hardware, not a default.
Use-case example
Real-world scenario
A footwear brand runs 40 stores and adds six temporary lanes per store for a two week holiday push, so 240 devices need provisioning in a compressed window. Under the old flow each device took roughly four minutes of a manager typing credentials, about 16 hours of management time across the fleet, all during trading hours. Nearby device login runs closer to 30 seconds per device, and because sessions default to today only, the 240 temporary devices deauthenticate on their own rather than lingering after the season.
Implementation checklist
- Audit which staff currently hold the POS device setup role and reduce it to the smallest workable set per location.
- Decide your default session duration policy. Leave Forever hidden unless a specific class of fixed hardware justifies it.
- In your Shopify admin, open Point of Sale, then Settings, then the POS editor, and confirm the Nearby device log in configuration matches that policy.
- Verify store manager PINs are individually assigned rather than shared, since the approval trail is only as useful as the identity behind it.
- Update your store opening runbook and seasonal onboarding material to describe the approval flow instead of credential entry.
- Pilot in one location for a full trading week, then confirm expired sessions behave as expected before rolling out fleet wide.
FAQ
Q: Does this work if our stores do not permit Bluetooth on staff devices?
A: Yes. The QR code path covers the same flow. A device that is already signed in displays the code, the new device scans it, and provisioning completes without any Bluetooth dependency.
Q: Can a staff member approve a device without manager level authority?
A: No. Approval requires the POS device setup role plus a store manager PIN, so the capability is scoped rather than open to any signed-in staff member.
Resources
Securing your Shopify POS setup
Need guidance? Talk to Makro.