Shopify POS / Improvement

The new POS editor
Manage all POS settings on a single screen

Payments, receipts, tips, customer information, and app settings — which previously required jumping between separate settings pages — are now consolidated into the same single editor as Smart grid and Lock screen. With the same split-panel UI as the Online Store editor, editing and previewing happen in the same context.

On this page
  1. What's actually changing (understand it in 30 seconds)
  2. Before vs. the new editor: how settings get consolidated
  3. 5 changes the new editor brings
  4. New behavior around payments
  5. What merchants need to do / rollout
  6. 5 points developers should know
  7. 3 use cases you can apply to your work
  8. A one-line summary you can use in a pitch

1What's actually changing

Previously, the POS settings for payments, receipts, tips, customer information, and apps were split across separate settings pages.
The new POS editorbrings them into a single editor alongside Smart grid / Lock screen / Customer display / Receipts. The layout is organized, and there's less moving between pages.

Before: scattered settings pages

Settings for payments, offline payments, local payments, app extensions, customer information, and receipts were on separate pages, requiring back-and-forth navigation.

New editor: consolidated on one screen

Operate all POS settings from a single navigation. With the same split panel as the Online Store editor, your edits and the preview sit side by side in the same context.

2Before vs. the new editor: how settings get consolidated

Before: moving between pages Payments Offline payments Local payments App extensions Customer information Receipts Smart grid Lock screen Consolidated New POS editor: a single split panel POS editor Payments / Tap to Pay Receipts Tips Customer information Apps / Global settings Preview (keeps context) Shop Pay · Tap to Pay Local payments Receipt settings
The new editor adopts the same layout as the Online Store editor. Changes you make in a subpanel, relative to what you're previewing, are kept in the same context, so it's hard to lose track of what you're currently editing.

35 changes coming to the new editor

Consolidation

1. One editor, one navigation

Payments / Offline payments / Local payments / App extensions / Customer information / Receipt settings now live inside the POS editor alongside Smart grid, Lock screen, Customer display, and Receipts.

Payments

2. A cleaner payments experience

Toggle payment methods on/off with a visibility toggle right where you're designing checkout. Shop Pay, Tap to Pay, and Local payments show their setup status inline, and per-entity settings deep-link to the relevant admin surface.

Accessibility

3. Global settings up front

Staff attribution, required checkout information, and customer receipt choices are grouped into a "Global settings" section for quick access.

Apps

4. Revamped app management

When you enable an app in the editor, its POS blocks and action extensions are activated in a single step. A second trip to settings is no longer needed.

UI

5. New split-panel navigation

Uses the same layout as the Online Store editor. Changes you make in a subpanel stay in the same context as what you're previewing.

4New payment behaviors

TargetBehavior in the new editor
Turning payment methods on/off In place Switch from the visibility toggle right on the screen where you're designing checkout
Shop Pay / Tap to Pay / Local payments Inline Shows setup status in place
Per-entity settings To the relevant admin surfaceDeep linkGuided by
Global settings Staff attribution, required checkout info, and customer receipt selection all placed together
Enabling apps Activate POS blocks + action extensions at the same time in one step
The supported countries and plans, the specific launch date, and the range of target stores arenot stated in the article. It only says it "rolls out automatically over the coming weeks."

5What merchants need to do / rollout

1

Action required: none

The updated editor will roll out automatically over the coming weeks.

2

Existing permissions stay the same

Your current permission settings apply as-is. No new permissions need to be granted.

3

The same staff have access

Staff who can currently manage payment providers or POS settings can use the new editor with the same access rights.

Migration work, reconfiguration, and permission reviews are allunnecessary. After the rollout, only the editor's appearance changes; what you can do stays the same as before.

65 points engineers should keep in mind

1. Automatic, phased rollout

"Rolls out automatically over the coming weeks." Because it isn't a simultaneous switch, there can be a period where the new and old editors coexist from store to store. It's safest to write manuals and support procedures assuming both UIs.

2. The permission model is unchanged

It targets staff who "can manage payment providers" and "can manage POS settings," and their access rights are the same. No new permission scopes are added. There's no need to revisit your role design.

3. Reorganized information architecture

Settings that were scattered are consolidated into a single editor's split panels. Staff procedure docs and screenshots need updating because the navigation changes. A new grouping called Global settings is added.

4. App activation in one step

Enabling an app in the editor activates POS blocks and action extensions at the same time. App developers should review their UX on the assumption that "extensions are enabled in bulk through this flow."

5. Inline status display + deep links

For Shop Pay, Tap to Pay, and local payment methods,the setup status is visible inline, so missing settings are caught early. Fine-grained, per-entity settings deep-link to the relevant admin screen, creating a division of roles where "the editor gives the overview and the admin gives the details."

73 use cases you can apply to your work

USE CASE 1

Rebuild the "POS settings manual" for store staff around a single screen

Challenge
The old manual spans multiple settings pages, so the steps are long and store staff can't reach the setting they're looking for.
Approach
Using the new POS editor's split panels as the baseline, restructure the procedure docs and screenshots along the editor's sections such as "Payments," "Receipts," and "Global settings."
Result
Explanations for moving between pages disappear and the steps get shorter. This lowers the burden of onboarding new hires and of help-desk inquiries.
Technical note
Because the rollout is automatic and phased, the new and old UIs can coexist during the transition. For the time being, documenting both UIs prevents anything from slipping through.
USE CASE 2

Speed up payment setup verification when launching a new POS

Challenge
When building out a POS for a new store, it's hard to tell which of Shop Pay, Tap to Pay, or local payment methods are still unconfigured, so missing settings tend to surface right before opening.
Approach
Use the new editor'sinline setup status displayto check the state of each payment method on the spot while designing checkout. For details, deep links take you to the relevant admin page.
Impact
With "an overview at a glance in the editor, details in the admin," you make fewer round trips to verify and avoid gaps in pre-opening checks.
Technical notes
Per-entity settings live in the admin, so for final confirmation open the deep link destination and lock down the state.
USE CASE 3

Make POS app rollout easier with "one-step activation"

Challenge
Even after installing a POS app, activating block and action extensions is a separate task, so it's easy to forget and have the features not appear in store.
Approach
Building on a flow where enabling an app in the new editor activates POS blocks and action extensions at the same time, the multi-store rollout process is simplified to "just turn it on in the editor."
Impact
Duplicate setup work and missed activations go away, making app rollout across stores faster and more uniform.
Technical notes
For your own or partner POS apps, verify in advance that extensions display as expected under this bulk activation flow.

8One-line summary you can use in pitches

"POS settings for payments, receipts, tips, customer info, and apps are consolidated into a single split-panel editor.
With the same feel as the Online Store editor, payment status shows inline and apps activate in one step.
Rolls out automatically with no work required, and existing permissions stay as they are."