Table of Contents
- Key Highlights:
- Introduction
- One Editor, One Navigation: Consolidating scattered settings into a single workspace
- Cleaner payments experience: visibility toggles, inline status, deep links
- Global settings surfaced: staff attribution, required checkout information, and receipt selection
- Updated app management: activate POS blocks and action extensions in one step
- Split-panel navigation: keep changes in context with what you preview
- Offline payments and local payment methods: design checkout behavior with resiliency
- Receipts and customer displays: align branding, privacy, and operational needs
- Permissions, rollout, and admin implications: no new permission changes, automatic rollout
- Best practices: prepare, test, train, document
- Potential limitations and considerations: hardware, third-party apps, regional restrictions
- Comparing the new POS Editor with prior flows and competing systems
- Troubleshooting and practical migration tips
- Practical, real-world examples of the POS Editor in use
- What merchants should watch next
- Where to find help
- FAQ
Key Highlights:
- Shopify consolidated payments, receipts, tips, customer data, and POS apps into a single POS Editor with a split-panel layout, inline payment setup status, and grouped global settings for faster configuration.
- The update streamlines app activation (POS blocks and action extensions enable in one step), improves offline and local payment management, and preserves existing permissions while rolling out automatically.
Introduction
Shopify has redesigned its point-of-sale configuration experience. The new POS Editor replaces a fragmented set of settings pages with a single editor that groups payments, receipts, customer information, apps, and device-specific options in one interface. The redesign introduces a split-panel layout that mirrors the Online Store editor, inline visibility toggles for payment methods, and a Global settings section that brings staff attribution, required checkout fields, and receipt selection closer to where merchants design checkout flows.
This change aims to reduce time spent switching between different admin screens, simplify app activation for checkout behaviors, and help merchants manage omnichannel checkout consistency with fewer clicks. The rollout is automatic; merchants with current permissions for payment providers or POS settings will see the updated editor without further action.
One Editor, One Navigation: Consolidating scattered settings into a single workspace
Merchants configuring checkout, hardware, and POS apps previously navigated multiple admin screens: payment provider settings, receipt templates, customer preferences, app settings, and device-specific options for Smart grid, Customer display, or Lock screen. The POS Editor brings these elements into the same editor pane so configuration stays contextual to the checkout preview.
How this changes workflow
- Centralized access: Payments, offline methods, local payment methods, app extensions, and customer info appear alongside device and receipt settings. Merchants no longer need to memorize where each setting lives.
- Contextual configuration: When modifying checkout UI or toggling payment methods, the preview reflects changes immediately within the editor’s split-panel layout.
- Fewer clicks: Global checkout behaviors—like requiring customer contact information or enabling staff attribution—are available in a single Global settings section.
Practical example A boutique store manager preparing for a seasonal pop-up can now enable a local buy-now-pay-later method and update receipt behavior from a single place while previewing the checkout flow. That eliminates the need to flip between a payment provider page and separate receipt configuration screens.
Why consolidation matters Multiple settings surfaces increase the risk of inconsistent configurations across online and in-person channels. Centralizing control reduces configuration drift, accelerates onboarding for new staff, and simplifies routine updates—like enabling a new payment method for a holiday sale.
Cleaner payments experience: visibility toggles, inline status, deep links
Payment management receives specific attention. The POS Editor introduces visibility toggles for payment methods directly within the checkout design view, displays the setup status of popular payment methods inline (Shop Pay, Tap to Pay, local methods), and provides direct links to entity-level settings when deeper configuration is required.
Visibility toggles where you need them Turning a payment method on or off no longer requires jumping between admin pages. A visibility toggle appears adjacent to the payment method within the editor. That makes it simple to test different payment mixes for different locations or devices and to hide methods that are unavailable in a given market.
Inline setup status and deep linking The editor shows whether a payment method is configured and ready. When a method requires additional configuration—perhaps a missing account connection or a required regional credential—the editor offers a deep link to the precise admin surface to complete setup. That reduces the time spent searching for the correct settings page.
Example scenarios
- A retailer preparing to accept Tap to Pay on iPhone can check the method’s status; if a firmware or profile requirement is missing, the editor links to the admin page to finalize setup.
- A shop that wants to offer Shop Pay in person can confirm that Shop Pay is active and visible in the checkout preview, rather than switching to a separate payment provider page to verify activation.
Operational benefits Immediate visibility of payment availability reduces customer-facing errors at checkout. Staff members can quickly identify whether a payment failure stems from a local configuration or a hardware issue. For multi-location merchants, toggles make it straightforward to enable or disable payment options per location during temporary promotions or local regulations.
Global settings surfaced: staff attribution, required checkout information, and receipt selection
The editor groups global checkout behaviors under a dedicated Global settings section. Merchants gain quicker access to controls that shape how transactions are attributed, what customer information is captured, and how receipts are presented.
Staff attribution and accountability Staff attribution ties sales and tips to specific employees. That information matters for payroll, performance tracking, and compliance with local labor rules. The Global settings section makes it simpler to toggle staff attribution on or off and to define whether staff must be signed in before processing a sale.
Configuring required checkout information Merchants often require contact details or delivery instructions to process orders or support returns. The new Global settings surface lists the required fields at checkout and lets merchants adjust them without leaving the editor. That ensures required fields align with receipts, customer profiles, and fulfillment needs.
Customer receipt selection and options Receipt behavior—including email, SMS, and physical printing—affects customer experience and operations. Merchants can set default receipt preferences, allow customers to select receipt type at checkout, and control which receipt templates apply in which contexts. Grouping these options improves consistency between what staff expect and what customers receive.
Practical implications A restaurant chain can require a phone number for takeout orders while leaving dine-in sales freer of required fields. A clothing retailer can default to email receipts and enable paper receipts only on request. These behaviors are now accessible in one place, reducing the chance of mismatched expectations between locations.
Updated app management: activate POS blocks and action extensions in one step
Shopify has streamlined how apps integrate into the POS experience. Historically, enabling an app might require toggling it on in the apps list and then separately enabling its checkout or POS-specific blocks. The updated POS Editor activates POS blocks and action extensions when an app is enabled in the editor, removing the need for a secondary trip to settings.
What POS blocks and action extensions do
- POS blocks: UI elements that appear within the POS checkout interface—things like loyalty buttons, quick-add modifiers, or customer loyalty points summaries.
- Action extensions: Additional behaviors tied to checkout events—post-sale surveys, loyalty enrollment prompts, or third-party fulfillment triggers.
How the new flow simplifies setup A merchant enabling a loyalty app within the editor sees the app’s POS block appear immediately in the checkout preview and gains the app’s actions without toggling separately in the app settings. That reduces configuration errors where an app appeared enabled but lacked its in-checkout components.
Real-world use case An ice cream shop installs a loyalty app ahead of a summer promotion. Activating the app in the POS Editor adds a “Redeem Points” block to the checkout and a post-sale prompt to collect customer contact information. Staff can test and confirm behavior in the editor before going live.
Developer and partner considerations App developers gain a more predictable user experience. When their extensions appear as soon as merchants enable an app, merchant adoption and satisfaction increase. Partners should still provide clear installation guidance and handle any required external account connections within their own admin flows.
Split-panel navigation: keep changes in context with what you preview
The POS Editor borrows the split-panel layout used by Shopify’s Online Store editor. A primary preview panel displays the checkout or device layout, while a nested sub-panel houses configuration options. Changes made in a sub-panel remain visible in the preview, preserving context and making iterative design faster.
Advantages of split-panel editing
- Context retention: Merchants see the immediate effect of a change without losing sight of the preview.
- Side-by-side comparison: It becomes easier to compare different states—payment enabled vs. disabled, different receipt templates, or alternate customer display layouts.
- Reduced cognitive switching: The interface reduces the need to mentally map settings to outcomes because the preview updates alongside edits.
Example workflow A retailer experimenting with alternative receipt templates can toggle between templates in the sub-panel and instantly see the preview update. That cuts the guesswork from visual design decisions and shortens the feedback loop when preparing hardware or staff training materials.
Offline payments and local payment methods: design checkout behavior with resiliency
Offline payments and local payment methods are crucial for certain merchants: pop-up shops with unreliable internet, markets with region-specific payment options, and events with intermittent connectivity. The POS Editor groups these options in the same workspace as other payment methods and displays their setup and visibility inline.
Offline payments explained Offline payments let merchants record a sale in the POS when the device lacks a network connection. The POS stores the transaction locally and synchronizes it when connectivity returns. The editor lets merchants toggle offline payment visibility, understand which devices and locations can use offline payments, and set policies for when offline transactions are allowed.
Local payment methods and regional considerations Different markets favor different payment rails: buy-now-pay-later services, local mobile wallets, or country-specific gateways. The editor displays local methods alongside global methods with inline indicators that show whether they’re configured for a specific location and device.
Operational example A handcrafted goods vendor selling at weekend markets can enable offline payments for their mobile POS devices. The editor marks the offline method as visible and shows that sales will sync automatically afterward. The vendor can then verify receipt templates and customer info requirements in the same place.
Risk management Offline transactions require careful policy. The editor should be used to control where offline payments are allowed and under what conditions. Merchants should set clear staff protocols for verifying identity and managing refunds for transactions recorded offline.
Receipts and customer displays: align branding, privacy, and operational needs
Receipts are a key moment of customer interaction. They deliver proof of purchase, brand messaging, and contact channels. The POS Editor brings receipt settings alongside customer display and lock screen configuration, enabling merchants to align printed or digital receipts with their in-person checkout flow.
Receipt options consolidated Merchants control default receipt channels (email, SMS, print), choose templates, and allow customers to select receipt types during checkout. With receipt settings adjacent to customer display controls, merchants can ensure that the message shown on the customer-facing hardware matches the content delivered via digital receipts.
Privacy and data capture The editor’s Global settings group required checkout fields alongside receipt selection. That allows merchants to define the minimum customer data captured while keeping receipt preferences consistent. For example, if a merchant requires email for e-receipts, the editor highlights that dependency.
Customer display use cases
- Upselling and cross-sell prompts appear on customer displays; configuring these in the editor ensures the customer-facing messages align with app extensions and receipt content.
- Loyalty balances or payment prompts on the customer-facing screen can be tested in the preview, enabling staff training before rollout.
Example: a cafe chain A café chain can configure the customer display to show loyalty points and a digital tipping prompt while attachments to email receipts promote a newsletter sign-up. Staff sees how prompts appear during the sale and can adjust required fields so customers consent to marketing opt-ins only when appropriate.
Permissions, rollout, and admin implications: no new permission changes, automatic rollout
Shopify is rolling the updated POS Editor out automatically. Existing permission structures remain intact. Staff members who can manage payment providers or POS settings today will see the new editor with the same access.
What administrators should verify
- Permission audit: Confirm which staff roles have the ability to manage payment providers and POS settings. The new editor does not broaden access, but any ability to change payment methods or app blocks remains sensitive and should be limited to trusted personnel.
- Training: Because the interface has changed, staff who configure POS settings should be briefed on where to find legacy controls in the new editor. The split-panel preview and inline toggles reduce friction but still change workflows.
- Location configurations: Multi-location merchants should check that the editor displays location-specific payment methods and that toggles match intended behavior per site.
Rollout cadence and expectations Shopify indicated the editor will roll out automatically over the coming weeks. Admins should expect the interface to appear without manual upgrades. If an organization uses role-based access control or SSO integrations, those systems will continue to govern who can change settings.
Change control recommendations
- Stage changes during low-traffic hours.
- Test edits on a single device or location before widespread deployment.
- Keep a change log for POS configuration alterations to aid troubleshooting and compliance reviews.
Best practices: prepare, test, train, document
Adopting the POS Editor benefits from a few disciplined steps. The following practices minimize downtime and ensure consistent customer experiences.
Prepare a configuration plan Map out which payment methods are required at each location. Account for local payment preference differences and hardware constraints. Decide which apps will be enabled at the POS and whether their blocks or actions require staff workflows or external credentials.
Test in a controlled environment Use a single device or a non-production location to trial edits. Validate offline payments by simulating network loss, and confirm synchronization on reconnection. Verify receipt templates and customer display behavior for typical transaction flows: returns, exchanges, tips, discounts, and multi-item orders.
Train staff on the new editor and checkout behaviors Even when staff do not manage settings, they benefit from understanding how toggles affect checkout behavior. Provide quick reference guides for handling payment errors, toggling receipt preferences, and capturing required customer information.
Document settings and maintain a change log For multi-location operations, keep a central document indicating which payment methods and app blocks are active per site. Track changes, who made them, and when. This aids troubleshooting and supports audits.
Use staged rollouts for major changes When enabling a new payment method or loyalty app, roll it out to a single location first. Observe transaction processing, customer reactions, and staff feedback. If issues appear, revert quickly and adjust the configuration.
Potential limitations and considerations: hardware, third-party apps, regional restrictions
The POS Editor simplifies configuration but does not eliminate technical constraints or regional limitations. Merchants should evaluate edge cases before relying on a single workflow.
Hardware compatibility Tap to Pay requires compatible devices and may be limited by operating system versions or hardware models. Not all registers or mobile devices support Tap to Pay or certain peripheral integrations. Verify device compatibility before enabling a method widely.
Third-party payment providers and custom integrations Merchants using custom or third-party payment gateways should confirm that toggles and inline statuses reflect the actual readiness of external systems. Some custom integrations may still require manual configuration in vendor dashboards or separate admin portals.
Regional availability of Shop Pay and local methods Shop Pay and specific local payment rails are not universally available. The editor displays setup status for these methods, but merchants in unsupported regions will need alternative options. Confirm regional availability before promoting a payment method to customers.
Offline payment risks Offline transactions carry risk: chargebacks, returns, and identity verification challenges increase when connectivity prevents real-time validation. Define staff protocols for large offline sales or high-risk items.
App extension dependencies Some apps require external credentials or account activations outside the Shopify admin. Activating an app in the editor may enable POS blocks and actions, but merchants must ensure all external dependencies—API keys, third-party accounts—are configured.
Timing and rollout discrepancies Because Shopify is rolling the editor out over weeks, some merchants may see the update earlier than others. Organization-wide training should account for staggered appearances across international teams.
Comparing the new POS Editor with prior flows and competing systems
The previous Shopify POS configuration dispersed critical settings across separate admin pages. That approach required more mental mapping and increased the chance of mismatches between payment availability and receipt behavior. Consolidation aligns settings with the preview, enabling faster iteration.
Competitive landscape Other POS vendors provide unified configuration interfaces; some focus on hardware-sales bundling, others on deep third-party marketplace ecosystems. Shopify’s advantage lies in its integration with the broader Shopify ecosystem: online store settings, apps, and fulfillment tools coexist with in-person checkout configuration in a single merchant account.
What this means for merchants
- For merchants already on Shopify, the new editor reduces friction by keeping everything within the same administrative environment.
- Merchants evaluating POS alternatives should consider how closely in-person checkout settings integrate with online storefront tools, apps, and fulfillment systems.
- Organizations relying heavily on custom integrations should audit how those integrations surface within the editor and whether additional vendor configuration is required.
Troubleshooting and practical migration tips
Even with a user-friendly editor, issues can arise. These steps address common scenarios merchants may face after the rollout.
If a payment method appears disabled but should be active
- Check the editor’s inline status for setup requirements. Follow any deep links to finalize configuration.
- Confirm credentials and account connections on the payment provider’s dashboard.
- Verify device compatibility and location-specific settings.
If an app’s block or action doesn’t appear after enabling
- Confirm the app’s permissions and any external account connections.
- Re-open the POS Editor to refresh the preview.
- Check the app developer’s installation instructions for additional steps.
Offline transactions not syncing
- Ensure the POS device has adequate local storage and is running supported firmware.
- Reconnect the device to the internet and confirm synchronization status.
- If synchronization fails, contact Shopify support and provide logs or timestamps for the offline transactions.
Troubleshooting customer display or receipt mismatches
- Verify that receipt template selection and customer display settings are aligned in the Global settings section.
- Test transactions of different types (sales, returns, exchanges) to see if templates react differently.
- Revisit app extensions that affect receipt content or customer display prompts.
When to contact support Open a support ticket if you suspect a backend issue—failed synchronizations that persist, unexpected permission changes, or payment methods that are said to be configured but fail to process transactions. Include device logs, screenshots of the editor status, and timestamps for problem transactions.
Practical, real-world examples of the POS Editor in use
Examples show how the editor benefits different classes of merchants.
Example 1: Independent coffee shop A two-location coffee shop enables Tap to Pay at one kiosk for quick payments while keeping a third-party mobile wallet as a promotional option in only one location. The manager uses visibility toggles to enable Tap to Pay at the kiosk device and a local wallet only at the downtown location. Staff attribution is required to log transactions for tip reporting.
Example 2: Seasonal pop-up clothing boutique A boutique operating a weekend pop-up enables offline payments for their mobile POS devices, activates a loyalty app with a POS block for points redemption, and sets email receipts as the default. The owner tests the loyalty flow in the POS Editor preview and confirms offline sale synchronization before opening the pop-up.
Example 3: Multi-location restaurant chain A midsize restaurant chain centralizes receipt templates and required checkout fields. Corporate configures default email receipts and required phone numbers for takeout orders. Local managers use the POS Editor to tweak local payment methods, such as enabling a regional mobile wallet only at certain sites.
Example 4: Hair salon with appointment workflows A salon integrates a bookings app that adds checkout actions—confirming appointments and collecting deposits. Activating the app in the POS Editor enables the action extension that prompts staff to record appointment details at checkout and prints appointment reminders on the customer receipt.
These examples highlight how diverse merchants can use a unified editor to expedite configuration and reduce operational friction.
What merchants should watch next
The POS Editor centralizes configuration, but ongoing attention to a few areas will maximize value.
Monitor device compatibility and OS updates As Apple and Android release OS updates, Tap to Pay and peripheral integrations may change. Keep devices current and test payment flows after major OS releases.
Track app updates and extension behavior App partners will iterate on POS blocks and action extensions. Subscribe to app update notes and re-test flows when apps push new versions.
Audit permissions regularly Because the editor consolidates powerful settings, periodic permission reviews ensure only authorized staff can change payment methods or receipt templates.
Evaluate analytics and reporting Unified configurations open opportunities to correlate payment method usage, receipt preferences, and customer behavior across channels. Merchants should plan to analyze post-rollout data to assess whether the new editor reduces payment errors or speeds checkout.
Consider additional staff training and documentation A one-time rollout can mask the ongoing training needs of seasonal hires, new locations, or event staff. Keep training materials updated with screenshots and quick steps that reflect the editor’s current UI.
Where to find help
Shopify’s Help Center includes documentation on customizing POS with the POS Editor. When support is necessary, provide detailed context: device model, location, payment method, app names, and relevant timestamps to accelerate diagnosis.
FAQ
Q: Will the POS Editor change who can access payment or POS settings? A: No. Existing permissions remain unchanged. Staff who could manage payment providers or POS settings before the update will retain their access.
Q: Do I need to do anything to get the new editor? A: No manual action is required. Shopify is rolling the updated POS Editor out automatically over a period of weeks.
Q: Can I still enable or disable payment methods per location? A: Yes. Visibility toggles and location-aware settings allow you to manage payment methods for specific locations and devices.
Q: How does the editor show whether a payment method is ready? A: The editor displays inline setup status for methods like Shop Pay, Tap to Pay, and local payment options. If additional configuration is needed, the editor provides deep links to the relevant admin page.
Q: Will enabling an app in the editor automatically enable its POS block and action extensions? A: Yes. Enabling an app in the editor activates its POS block and action extensions in one step, eliminating the need to toggle them separately.
Q: How do offline payments work with the new editor? A: Offline payments can be toggled in the editor. When enabled, transactions made offline are stored locally on the device and synchronized when the device reconnects. Merchants must set policies for offline usage and review staff protocols for risk mitigation.
Q: Is customer data capture and receipt selection managed in the same place? A: Yes. Global settings surface includes required checkout information and customer receipt selection, making it easier to align data capture with receipt behavior.
Q: What if a payment method appears enabled but fails at the point of sale? A: Check the editor for inline status indicators and follow any deep links to finalize setup. Verify device compatibility and connectivity. If issues persist, gather screenshots, timestamps, and device logs and contact Shopify support.
Q: Will the layout affect hardware-specific settings like Customer display and Lock screen? A: These device-specific settings now sit alongside payment and receipt configuration in the POS Editor, preserving the contextual preview while you configure hardware behaviors.
Q: Can I test changes before rolling them out to all locations? A: Yes. Use a single device or a designated test location to validate changes. Staged rollouts are recommended for significant payment or app activations.
Q: Where can I learn more or find step-by-step guidance? A: Shopify’s Help Center includes detailed documentation on customizing POS with the POS Editor. The editor also provides deep links to the admin surfaces required for additional configuration.
Q: What should I do about staff training after the rollout? A: Update internal procedures and training materials to reflect the split-panel layout, inline toggles, and the Global settings section. Provide short, focused training sessions for staff who will manage POS configurations.
Q: Are there any regional limitations to Shop Pay or Tap to Pay that I should consider? A: Yes. Shop Pay and local payment methods may not be available in all regions. The editor reflects availability in its setup status, but merchants should confirm regional support before promoting a payment method to customers.
Q: How can I revert to the old editor if my team prefers it? A: Shopify is rolling the new editor out automatically and has not provided a manual reversion option. If you encounter issues, reach out to Shopify support for assistance and provide detailed context.
Q: Are there additional costs associated with activating apps or payment methods through the POS Editor? A: Enabling an app may still involve subscription fees or third-party processing fees, depending on the app and payment provider. Review the app’s billing and the payment provider’s pricing before enabling.
Q: What are best practices for managing offline transaction risks? A: Restrict offline payments to trusted devices, set maximum offline transaction values, require staff sign-in, and define protocols for verifying identity and handling refunds.
Q: Who should I contact if I see inconsistencies in payment method availability across locations? A: Start by checking the POS Editor’s visibility toggles and location settings. If the issue persists, contact Shopify support with device details, location IDs, and timestamps.
Q: Can I customize receipts differently for online and in-person sales? A: Yes. Receipt templates and defaults can be configured to differ between channels. The POS Editor groups receipt settings for in-person sales, enabling targeted behavior.
Q: Will enabling apps through the editor require developer action? A: Most app activation flows become easier because POS blocks and action extensions enable via the editor. Some apps still require developer-provided credentials or external configuration; follow the app developer’s installation guide.
Q: Does the POS Editor change how taxes or fulfillment are handled? A: The POS Editor centralizes checkout-related settings but does not fundamentally alter tax calculation or fulfillment flows. Ensure tax settings and fulfillment rules remain correctly configured in their respective admin screens.
Q: How do I keep track of changes made in the POS Editor for auditing? A: Maintain a change log with who made edits and when. For larger organizations, enforce change control procedures and limit permission to configure payment and POS settings to authorized personnel.
Q: Will the editor show me which payment methods are supported by specific hardware? A: The editor indicates setup status and visibility for payment methods. For detailed hardware compatibility (e.g., Tap to Pay device support), refer to device documentation or the deep-linked admin surfaces for setup guidance.
Q: Is there any impact on PCI compliance with the new editor? A: The editor organizes payment settings but does not change underlying payment flows. Merchants should continue to follow payment provider guidance and maintain any required PCI-compliant practices for hardware and processing.
Q: Where can app developers find guidance on creating POS blocks and action extensions that work with the new editor? A: App developers should consult Shopify’s developer documentation for POS extensions. Ensuring clear installation flows and handling external credentials will improve merchant adoption.
Q: How can I best prepare for holidays or peak seasons using the POS Editor? A: Map required payment methods for each location, stage tests in a controlled environment, enable promotions or local payment methods where appropriate, and brief staff on expected checkout behavior changes ahead of peak days.
Q: What reporting changes should I expect after consolidating settings with the POS Editor? A: The editor simplifies configuration, which can reduce discrepancies in payment method reporting. Use Shopify’s reporting tools to monitor payment-use trends, reconciliation issues, and the impact of app-enabled checkout behavior.
Q: If I have more questions, how do I contact Shopify support? A: Use the Shopify admin support channels, include relevant screenshots and device or location details, and reference the POS Editor when describing configuration concerns.
This article explains the scope of Shopify’s POS Editor update and provides practical guidance for merchants, administrators, and partners. The editor centralizes critical checkout configuration, reduces friction in enabling payments and apps, and surfaces global behaviors that affect receipts and customer data capture. Merchants should take advantage of the consolidated workflow by preparing a configuration plan, testing changes, and training staff to ensure a smooth transition and improved in-person checkout reliability.
