Table of Contents
- Key Highlights:
- Introduction
- Smarter analytics and safer experimentation
- Rollouts and A/B testing for safer launches
- Automation gets more capable and safer: Flow and Sidekick
- Checkout, payments, and tax coverage expand
- Customer accounts, identity, and consent
- POS, in-store, and omnichannel retail operations
- Inventory, transfers, and fulfillment reporting
- Merchandising, product management, and catalog expansion
- Themes, storefront features, and AI-assisted editing
- Developer platform changes and migration deadlines
- Finance, Balance, and Capital enhancements
- Governance, security, and admin controls
- Action checklist: what merchants should do now
- FAQ
Key Highlights:
- Shopify shipped a broad set of product updates across Admin, POS, Analytics, Payments, Customer Accounts, Apps, and Developer tooling — with several platform changes requiring merchant action (notably Scripts and legacy custom apps deprecation).
- Major themes: deeper analytics and experimentation (new chart types, cumulative metrics, Rollouts), richer automation and AI in admin (Flow and Sidekick enhancements), retail-first POS and fulfillment improvements, and expanded payments and international tax capabilities.
- Merchants should prioritize migrations (Shopify Scripts → Functions; legacy custom apps → Dev Platform), update identity and account flows, and adopt testing tools (Rollouts, Flow test runs, Sidekick) to safely roll out experiences.
Introduction
Shopify’s latest changelog reads like a product sprint across every corner of commerce operations. Over the past months the platform delivered more than a hundred improvements and features — from new analytics visualizations and A/B testing for storefront and checkout experiences to POS hardware reliability and payments expansions such as USDC on Base. The collection includes operational tooling for inventory and transfers, developer-facing platform changes, and several deprecations that require merchant planning.
These updates reflect a clear push: give merchants more control over experimentation, richer operational observability, and tighter automation while consolidating commerce plumbing — payments, taxes, identity, and fulfillment — to reduce friction across omnichannel operations. For merchants the news is practical: better ways to measure, test, and automate; new capabilities to expand catalogs and markets; plus a set of migrations to schedule into your roadmap.
The sections below synthesize the most important changes, show real-world examples of how teams can use them, and provide an action checklist so you can turn announcements into improvements that move the business.
Smarter analytics and safer experimentation
Shopify bolstered analytics and introduced tools to test and roll out changes with more confidence.
What’s new
- Two new chart types in Analytics: scatter plots (compare two metrics across a dimension) and radar charts (compare multiple metrics at a glance).
- Cumulative view for time-series metrics so running totals are available with targets and prior-period comparisons.
- Annotations that surface store events directly on charts (product changes, theme deploys, app installs).
- Data-driven insights and automated insights on the Analytics dashboard (trends, streaks, top performers).
- Set and track targets with visual gauges on dashboards.
- Minute-level, real-time controls for fine-grained monitoring and Live View support in the new analytics experience.
- Flexible “Top items” reporting and the ability to use metafields as dimensions and filters.
- Benchmark comparisons removal note (Compare to Benchmarks toggle removed on May 19, 2026) — plan reporting adjustments if you relied on that feature.
Why this matters Visualization variety and event annotations let teams connect changes to outcomes faster. Scatter plots are useful when you need to see the relationship between two variables (e.g., average order value vs. sessions by traffic source). Radar charts provide a compact view of multiple KPIs across channels or product families, which helps merchandising teams compare performance at a glance.
Annotations reduce the blind spot between operations and outcomes. When a spike or drop hits the dashboard you no longer have to cross-reference release notes and deploy timelines; the event marker is there.
Real-world example A growing DTC brand uses scatter plots to map marketing spend per channel (x-axis) against new customer acquisition (y-axis) by campaign. They spot a cluster of high‑spend but low‑new‑customer campaigns and reallocate budget. Simultaneously, the analytics annotations show a theme tweak rolled the week the cluster emerged, leading them to test the theme change with an A/B using Rollouts.
Practical actions
- Add annotations to regular release and marketing calendars so every push is automatically visible in Analytics.
- Build dashboard cards using scatter plots and radar charts for executive and merchandising reviews.
- Replace any reliance on the soon‑removed benchmark toggle with internal baseline reports or cohort comparisons.
Rollouts and A/B testing for safer launches
Shopify extended experimentation beyond code: admins can now schedule, publish, and A/B test new themes, checkout, and customer account configurations through Rollouts.
What’s new
- Use Rollouts to launch, gradually release, or A/B test new themes and checkout/customer-account experiences.
- Schedule theme changes and set automatic rollback windows.
Why this matters Themes and checkout flows are high‑impact changes. Rollouts gives control to test with real shoppers, mitigate risk with gradual releases, and capture comparative performance. This is particularly useful for time‑bound promotions, localization experiments across Markets, and validating UX changes.
Real-world example A retailer prepares a new checkout experience optimized for France and wants to test different address input flows. They use Rollouts to show variant A to 10% of French shoppers and variant B to another 10%, tracking conversion rate and cart abandonment. Once data favors a variant, they schedule a full rollout.
Practical actions
- Create an experiment plan for major UI changes and use Rollouts to run controlled tests.
- Combine Rollouts with Analytics annotations and target metrics to measure lift.
- Keep a rollback strategy in every rollout: schedule checkpoints and automated reversible windows.
Automation gets more capable and safer: Flow and Sidekick
Shopify shipped significant Flow and Sidekick upgrades that reduce manual operations risk and accelerate automation creation.
What’s new
- Flow: new actions to fetch analytics (via ShopifyQL), market data, article data, inventory transfer triggers, and more. Flow now supports test runs, workflow version history, and preview/test events.
- Flow: new triggers (discounts, disputes, fulfillment order splits) and actions to pull workflow-run data, inventory items, etc.
- Flow now adopts newer GraphQL Admin API versions periodically (notable versions: 2026-01, 2025-10, 2025-07, etc.), bringing metaobject and metafield improvements.
- Sidekick: generate Flow automations with natural language, create test events, create customers and companies, write ShopifyQL queries for payments and performance, generate interactive checklists, and propose proactive business recommendations.
Why this matters Flow plus Sidekick decreases dependence on developers for routine automations. Test runs and workflow histories reduce the risk of accidental rules causing operational errors. Pulling analytics data directly into Flow via ShopifyQL enables data-driven triggers (e.g., “when inventory for product X drops below threshold and the product’s sell-through rate is below Y, trigger reorder”).
Real-world example A merchant uses Sidekick to generate an inventory-reorder Flow: Sidekick creates the workflow; the merchant runs a test run to confirm the logic; then the Flow triggers a purchase-order creation action when stock dips below a market-specific threshold and predicted demand is rising.
Practical actions
- Use Flow test runs and Sidekick generation for sensitive automations that touch inventory or refunds.
- Consolidate ad hoc scripts into Flow actions where possible to get audit trails and rollbacks.
- Track Flow API versioning and test flows when Shopify upgrades Admin API versions.
Checkout, payments, and tax coverage expand
Shopify expanded payment methods, visibility into payouts, and tax automation — with clear merchant-facing improvements and new crypto support.
What’s new
- USDC on Base now available as a payment option for guest checkout and Shop Pay.
- Apple Pay available in Shop Pay checkout; Google Pay available in Checkout Kit and mobile app storefronts.
- Local payment method expansion in more countries and new payment methods for France (Klarna, Bancontact, iDEAL, etc.).
- Shopify Payments: clearer payout balance naming and reserve info; payout exports include Bank Reference and Payout ID for easier matching.
- VAT number validation in checkout for EU/UK merchants to automate reverse charge exemptions.
- Shopify Tax expanded to Canada and now supports California’s embedded battery fee and other local rules.
- Pay-in-Full credit payment options behavior changes for Shopify Credit; Capital remittance changes in Texas; Capital launches in multiple European countries.
Why this matters Payment choice affects conversion. Adding local methods and accelerated checkout buttons reduces friction for global buyers. USDC support gives merchants another option to accept stablecoin payments, useful for certain buyer segments and marketplaces. Improved payout exports and clearer balances simplify reconciliation for finance teams.
Real-world example A French merchant adds iDEAL and Klarna to increase conversion in the Benelux region and introduces Shop Pay with Apple Pay for returning customers on mobile. They also enable VAT number validation to automatically apply reverse charge for B2B orders.
Practical actions
- Review checkout payment options by market and enable local methods where conversion gains justify the fees.
- Configure payout exports and reconcile bank deposits using the new Bank Reference and Payout ID fields.
- Work with tax advisors to enable Shopify Tax coverage for new jurisdictions like Canada and set VAT validation for EU/UK flows if you sell B2B.
Customer accounts, identity, and consent
Shopify improved identity flows, marketing consent capture, and account customization while deprecating legacy account types.
What’s new
- Merchants can unlink customers from their custom OIDC identity provider in Admin (fixes “sign-in method doesn't match this account” errors without contacting Support).
- Refreshable and customizable sign-in page with a two‑column layout, brand imagery, and editor controls.
- Social sign-in options available (Google, Facebook) and Sign in with Shop expanded.
- Collect marketing consent on sign-in pages and account components; consent settings extend checkout consent to sign-in with preselected regions.
- Legacy customer accounts deprecated — merchants should upgrade to the current accounts system.
Why this matters Identity coherence matters for retention and support. The ability to unlink problematic identity ties reduces friction for customers and support tickets. Collecting consent at sign-in increases the reach of marketing while complying with privacy laws and reduces unsubscribe friction downstream.
Real-world example An enterprise using a custom OIDC provider finds a set of customers failing to sign in after a password migration. The admin unlinks the affected customers so they can use the new identity provider login and avoid a support ticket backlog.
Practical actions
- Audit all customers who authenticate via custom identity providers and plan unlink workflows where needed.
- Migrate legacy customer accounts to the modern account system to keep receiving feature updates and avoid future support gaps.
- Update account sign-in pages with brand language and clear consent choices to improve opt‑in rates.
POS, in-store, and omnichannel retail operations
Shopify added hardware resilience and richer workflows to POS and POS Editor, addressing the needs of multi-location retailers and fast-moving stores.
What’s new
- Multi-location pickup in POS: create pickup orders for any pickup-enabled location.
- POS Hub connects tablets to hardware over wired USB to eliminate Bluetooth dropouts.
- Create pickup orders in POS, fulfill transfers from POS, and print packing slips for inventory transfers.
- Offline checkout per device setting and mid-session cash counts for better register control.
- Quick sale available globally, with change‑due calculators and Tip support.
- POS Editor consolidates settings and now supports Smart Grid edits and screen settings.
- Subscriptions available in POS and returns/refunds UX improvements.
- Keyboard shortcuts, inline search suggestions, and scanning discount QR codes.
Why this matters Physical retail benefits from reduced hardware friction and faster in-store workflows. POS Hub solves a common complaint: unreliable Bluetooth disconnects in busy retail environments. Multi-location pickup and transfer fulfillment improvements make omnichannel order routing smoother.
Real-world example A regional retailer with five stores uses multi-location pickup and transfer fulfillment: a customer places an order online for same‑day pickup; POS creates a transfer from multiple locations automatically when stock is insufficient at the pickup store; POS staff fulfill and hand the order to the customer using Shop-generated QR codes.
Practical actions
- Test POS Hub setups in your busiest stores to confirm hardware reliability over USB.
- Train staff on new POS shortcuts and the new returns/refunds flow to speed service.
- Enable offline checkout per device for remote selling situations like pop-ups, and log offline events for audit.
Inventory, transfers, and fulfillment reporting
Shopify improved inventory visibility and transfer workflows for multi-site operations and third-party fulfillment.
What’s new
- Track inventory at locations not active for selling or fulfillment (better internal visibility).
- Bulk CSV importing for inventory transfers and greater flexibility editing shipment line items at any stage.
- Inter-location transfers reporting with new reports for Transfers & Shipments (shipped, received, accepted, rejected).
- New “Bin name” column for location-level picking; improved adjustment history and audit trails for inventory changes.
- FedEx duties prepaid labels and expanded fulfillment partners for Shopify Fulfillment Network.
Why this matters Accurate inventory across many locations is core to omnichannel retail. The improvements reduce overselling, make bulk transfer workflows efficient, and give operations teams the audit trails needed for inventory reconciliation.
Real-world example A 3PL-enabled merchant runs weekly bulk CSV upload transfers to push stock to regional hubs before peak season; they use the new inter-location reports to confirm shipments and reconcile against warehouse receipts.
Practical actions
- Add bin names to variants to speed picking and reduce mispicks.
- Use bulk CSV transfers for recurring large shipments and validate with the new transfer reports.
- Enable inventory tracking at non-fulfillment locations where back-office stock holds need visibility.
Merchandising, product management, and catalog expansion
Shopify added more granular publishing controls and catalog expansion mechanisms that reduce inventory risk.
What’s new
- Product variant publishing: publish/unpublish individual variants by channel and catalog.
- Product Network and Shopify Collective expansions let retailers import supplier products without holding inventory. Collective now supports discovery globally and public price lists; suppliers can earn Verified Tracking badges.
- New Unlisted product status and increased variant limit to 2,048 per product.
- Compare multiple metrics on one chart, set compare controls, and set compare-at prices inside Catalogs.
Why this matters Variant-level control and unlisted product types support complex merchandising — pre-launch pages, limited drops, and region-specific variants. Collective and Product Network let retailers scale product assortments without inventory, lowering operational capital risk.
Real-world example A boutique retailer imports a slow-moving supplier line into its storefront via Shopify Collective and adjusts retail prices locally. They only publish the variants that fit their curated collection, keeping the storefront clean while testing demand.
Practical actions
- Use Product Variant Publishing to test new colors/sizes per market before a full rollout.
- If expanding catalog with Collective, ensure suppliers maintain tracking coverage to earn Verified Tracking badges — it increases discoverability.
- Consider Unlisted product status for private drops or direct URL access campaigns.
Themes, storefront features, and AI-assisted editing
Shopify continued investing in theme tools and AI assistance to speed creative iterations.
What’s new
- Improvements to the theme editor navigation and code editor; ability to create and edit resources in the theme editor (products, collections, markets, metaobjects).
- AI block generation now available for Theme Store themes; Sidekick can customize theme elements in real time and generate images in the file picker.
- Posts replaces Updates with richer shoppable content and Shop integration improvements.
Why this matters Teams can iterate on visual design faster and incorporate AI into creative workflows. Creating resources directly in the theme editor reduces context switching and accelerates launch cycles.
Real-world example A retailer uses Sidekick to create an AI-generated product hero block and fine-tunes the block using prompts. The preview shows live in the editor, then Rollouts tests the new hero against the existing one for conversion lift.
Practical actions
- Use AI block generation for prototype hero sections, then A/B test with Rollouts.
- Consolidate content creation by leveraging theme-editor resource capabilities and Sidekick image generation to shorten launch timelines.
Developer platform changes and migration deadlines
Shopify announced several deprecations and developer-facing changes that require planning.
What’s new and critical
- Shopify Scripts deprecation: as of April 15, 2026 you cannot edit or publish Scripts; execution ends June 30, 2026. Migrate to Shopify Functions or a public app.
- Legacy custom apps cannot be created after January 1, 2026; the Dev Platform (Dev Dashboard) now replaces admin-based app creation.
- Flow and apps adopt newer GraphQL Admin API versions; developers must test integrations against new versions.
- Dev Platform and new app tools (Dev Dashboard) are available to build and manage apps.
Why this matters Scripts often enforce complex pricing, shipping, and discount logic for Plus merchants. Functions become the migration path but can require reimplementation. Legacy custom apps’ sunset affects stores that rely on ad hoc custom apps created in admin. Both shifts have concrete deadlines.
Migration checklist
- Inventory all Scripts and custom apps. Prioritize Scripts that impact checkout pricing, gifting, or shipping and map them to equivalent Functions or public app solutions.
- Build a migration roadmap: audit logic, test in a sandbox, and run A/B/rollout experiments to validate parity.
- Move custom app development to the Dev Platform. Create dev stores, migrate code, and reissue app credentials.
- Use Flow test runs and Sidekick to ease workflow conversions.
Real-world example A large retailer with custom Scripts that applied wholesale discounts during checkout plans a phased migration: export Script logic, implement equivalent functionality using Shopify Functions for the most critical flows, test with Rollouts, and schedule the final cutover before the June 30, 2026 execution end date.
Practical actions
- Start Script-to-Functions migration immediately if you have Scripts. Prioritize based on business risk.
- For legacy custom apps, plan dev work on the Dev Platform and ensure you have reproduced required scopes and webhooks.
- Use Flow and Sidekick to document automations and preserve operational context.
Finance, Balance, and Capital enhancements
Shopify extended merchant finance tooling in Balance, Capital, and payouts.
What’s new
- Shopify Balance: new mobile redesign, domestic wire transfers, automated transfers for payouts, create Balance cards for staff, auto-lock staff balance/credit cards.
- Faster reconciliation with payout exports that include Bank Reference and Payout ID.
- Shopify Capital expansions: launches in France, Spain, Netherlands, Ireland; Capital Flex in the US. Capital remittance now collects in all US states and remittance collection changes in Texas.
- Shopify Credit updates: dispute workflow improvements and increased rewards cap.
Why this matters Automated transfers and card controls give finance teams tools for cashflow planning and T&E governance. Capital expansion provides financing options in more countries. Better payout reconciliation reduces accounting overhead.
Real-world example A mid-size e‑commerce business sets up automated Balance transfers to split each payout 20% to taxes, 50% to operations, and 30% to a replenishment account — reducing manual transfers and reconciliation work.
Practical actions
- Adopt automated payout splitting in Balance to simplify bookkeeping.
- Review Capital and Credit eligibility and the remittance rules in your state/country.
- Train finance users on new card controls and auto-lock dates.
Governance, security, and admin controls
Shopify added compliance and admin features for organizations and teams.
What’s new
- Export users, roles, groups, and activity logs in CSV for audits and compliance.
- Track app activity and permissions from Settings and see where apps are active.
- New default settings for marketing pixel data sharing and pixel controls.
- Billing delegatable permissions for organization-enabled core merchants.
Why this matters These features make audits and security reviews easier while enabling governance over app and pixel usage.
Practical actions
- Schedule periodic exports of user activity logs for compliance and SOX-style audits.
- Review app permissions and enforcement policies quarterly to ensure least-privilege access.
- Consolidate marketing pixel settings and update privacy policies to reflect new consent choices.
Action checklist: what merchants should do now
- Audit critical platform dependencies
- List Shopify Scripts and custom apps. Create migration timelines with developers.
- Plan migrations with deadlines
- Scripts editing ends April 15, 2026; execution ends June 30, 2026. Legacy custom app creation stops Jan 1, 2026.
- Start testing and rollout hygiene
- Use Rollouts for theme and checkout changes; annotate analytics with deployment events.
- Automations and safety nets
- Build Flow workflows with test runs; use Sidekick to generate and document workflows.
- Payments and tax configuration
- Reconcile payout exports using Payout ID and Bank Reference; enable VAT validation where required; add local payment methods for targeted markets.
- POS and hardware plan
- Pilot POS Hub in busy stores; enable multi-location pickup and train staff on new POS flows.
- Inventory operations
- Add bin names, begin inter-location reporting, and use bulk CSV transfers for large shipments.
- Privacy and consent
- Update sign-in and forms to collect marketing consent; check pixel sharing default behavior.
- Use analytics to measure impact
- Add scatter plots and radar charts to dashboards; set targets and use cumulative views for campaign tracking.
FAQ
Q: I use Shopify Scripts — what timeline and migration path should I follow? A: Editing and publishing Scripts ended April 15, 2026; Script execution ends June 30, 2026. Map each Script’s business logic to Shopify Functions or a public app. Prioritize Scripts that affect checkout pricing, shipping, or discounts. Implement and test Functions in a dev store and use Rollouts or staged releases to validate parity before the execution end date.
Q: What happens to legacy custom apps I created in admin? A: You will not be able to create legacy custom apps after January 1, 2026. Migrate development to the Dev Platform (Dev Dashboard), recreate app functionality as a new app, and reconfigure scopes and webhooks. Test thoroughly and rotate credentials where necessary.
Q: How do I fix the “sign-in method doesn’t match this account” error? A: For merchants using a custom OIDC identity provider, Admin now allows you to unlink a customer from the custom identity provider. This resolves mismatches without contacting Shopify Support. After unlinking, the customer can sign in with the correct method and you can guide them to update their credentials.
Q: I operate in multiple countries — what tax changes require immediate attention? A: Shopify Tax expanded to Canada and supports new local rules (e.g., California battery fee). EU/UK merchants can enable VAT number validation at checkout to automate reverse-charge treatment. Check your Markets settings and tax registration status; enable tax features in Shopify Tax and verify that reported liabilities match local filings.
Q: How should I use Rollouts and analytics together? A: Use Rollouts to create controlled experiments (A/B split or gradual rollouts). Add annotations to Analytics for every Rollout change. Track the target metrics (conversion rate, AOV, checkout completion) and use the new chart types (scatter for correlation, radar for multi-metric comparison) to evaluate impact before a full launch.
Q: What does the Verified Tracking badge in Shopify Collective do? A: Suppliers with consistent carrier tracking coverage across orders can earn a Verified Tracking badge. The badge increases discoverability to retailers on Shopify Collective, improving trust for cross-store catalog imports. Suppliers should ensure tracking coverage and carrier reliability to qualify.
Q: Are there new reconciliation fields for payouts? A: Yes. Payout exports now include Bank Reference and order transaction exports include Payout ID, making it easier to match Shopify Payments payouts with bank deposits.
Q: How will Sidekick and Flow help my operations team? A: Sidekick can generate Flow automations, build analytics queries, create test events, and propose proactive recommendations. Flow now supports test runs, workflow version histories, and more native actions. Together they let non-developers create and test automated workflows safely, reducing manual work and operational errors.
Q: Should I be concerned about benchmark comparisons removal in Analytics? A: The Compare to Benchmarks toggle was removed (May 19, 2026). If you relied on benchmark comparisons, replace them with cohort, prior-period, or internally defined baseline comparisons using the new Analytics tools. Use cumulative metrics and targets to replicate trend benchmarking.
Q: How do I prepare for the payments and checkout changes like USDC and local payment methods? A: Review payment method adoption by market and test checkout flows. USDC on Base offers an alternative for certain buyer segments; enable it where it makes sense. For local payment methods, add them in the Admin for countries where they are supported and run test checkouts to verify UX and reconciliation.
Q: Where can I find the new reports for transfers and shipments? A: Inter‑location Transfers Reporting and Transfers & Shipments reports are available in Analytics > Reports. Use these to track shipped, received, accepted, and rejected transfer events; filter and export CSVs for reconciliation.
Q: How do I ensure my theme changes are reversible? A: Use Rollouts to schedule staged releases and set automatic rollback windows for theme and checkout changes. Maintain a release log with analytics annotations and set targets that must be met for a change to proceed to full rollout.
Q: What’s the impact of the increased variant limit to 2,048? A: You can now create up to 2,048 variants per product (up from 100), enabling complex product matrices. Keep catalog performance and storefront UX in mind; use variant-level publishing to only surface necessary variants per market or channel.
Q: How should I approach app permissions and pixel data settings? A: Review the new default for marketing pixel data sharing and limit pixel access to tools driving results. Use app activity and permission tracking in Settings to audit where apps are active and revoke permissions for unused or risky apps.
Q: Where should I start if I sell wholesale or run B2B? A: B2B features are now available on non‑Plus plans, and several enhancements exist: company profiles, payment terms, volume pricing, ACH for B2B, and more. Enable B2B features in Admin, test B2B checkout flows including Apple Pay support, and validate tax/duty handling for B2B in Managed Markets.
Q: What immediate POS upgrades are worth testing? A: Pilot POS Hub in a high-transaction store to verify hardware stability. Enable multi-location pickup and transfer fulfillment if you operate multiple stores. Test the new returns/refund workflow and Smart Grid customizations to speed staff operations.
Q: How do I keep track of all these changes? A: Create a cross-functional product-readiness calendar. Map platform-deprecation dates and feature launches to merchant workflows. Use analytics annotations to link releases to outcomes and maintain a backlog for configuration updates, staff training, and developer migration tasks.
If you need, I can produce:
- A prioritized migration plan for Scripts and custom apps specific to your store.
- A rollout/experiment playbook mapped to your highest-traffic pages and checkout flows.
- A tailored inventory and POS checklist to pilot POS Hub and multi‑location pickup in your busiest stores.
Which would you like first: a migration roadmap for Scripts → Functions, or a hands-on Rollouts and experimentation playbook tailored to your product pages?
