Reading the Summer Edition: what to act on and what to ignore

Twice a year Shopify publishes several hundred changes at once, grouped by theme, each with a sentence and an illustration. It is a genuinely useful changelog wrapped in a genuinely effective piece of marketing, and the two jobs pull in different directions. Volume is the point of the marketing; it is the enemy of the changelog.

The way through it is to read with a question rather than a highlighter: what decision am I currently making, and did anything in here change it? A merchant mid-way through scoping a theme rebuild has a different Edition to read than one whose problem is EU shipping. Almost everything else is context you will absorb naturally when it becomes relevant.

The second habit worth having: separate shipped from announced. Items marked early access, developer preview or "coming soon" are commitments, and a commitment is planning information, not build information. Scoping a project around a preview means the project inherits somebody else’s release schedule.

Horizon and the theme block foundation. The headline is ten new themes; the substance is the design foundation underneath them, built around theme blocks rather than fixed sections. This is the item most likely to change something already on your roadmap, because the boundary between "the merchandising team can build that" and "that is a developer ticket" has moved. If you scoped a theme rebuild three months ago on the assumption that every new layout needs a developer, re-read the scope.

Duties collection in checkout, on all plans. Previously a Plus-shaped capability, now available more broadly, alongside the option to include duties in displayed prices. If you ship cross-border and your customers currently meet a courier invoice on the doorstep, this is the single cheapest improvement in the Edition — and it fixes a genuine repeat-purchase problem rather than an aesthetic one.

Markets for B2B, on Plus. Multi-market catalogues for wholesale, with a "View as" preview. Anyone running one B2B store per region because catalogues could not vary by market should reconsider the structure before renewing that arrangement for another year.

Web performance reports in the admin. Page-level Core Web Vitals, from your own traffic, in the place your team already looks. Third-party tooling has offered this for years and most merchants never installed it. Now there is no gap between noticing the site is slow and knowing which template is responsible.

Polaris as one web-component UI system. Across admin, checkout and customer account extensions. If you build apps or commission them, this is the item with the longest tail: a shared component system is the difference between an extension that looks like Shopify and one that looks like an app.

A faster developer inner loop. Local development without tunnels, extension work without a deploy on every change. Unglamorous, and it compounds — most of the cost of extension work is the loop between a change and seeing it.

Plenty in the Edition is real engineering that has no business in your next quarter.

AI theme and block generation. Describe a block, get a block. It is a fair prototyping tool and we would not put its output into a production theme without a developer reading every line — generated markup you did not design is exactly the debt that makes a theme unmaintainable three agencies later. Use it to explore a layout, then build the layout properly.

Checkout in Roblox, stablecoin payments. Both are genuinely interesting and both are answers to questions almost no mid-market merchant is asking. If you sell to an audience inside Roblox you already knew that. Nobody should be adding a crypto payment method because a changelog mentioned one.

Storefront Web Components and the next-generation developer platform. Early, and promising. The web components idea — embed commerce with HTML snippets — is the sort of thing that quietly changes what a brochure site can do. Watch it; do not stake a launch on it.

The Sidekick expansions. Better, broader, in twenty languages. Try it, because it costs nothing to try, and do not restructure any process around it yet.

The Edition carries performance claims — a checkout that loads meaningfully faster, an admin loading around a third faster. These are Shopify’s own measurements of Shopify’s own products, published in a marketing document. That does not make them false; it makes them unverifiable by you.

The useful way to treat a vendor figure is as a direction to check against your own data. If checkout is faster, that shows up in your funnel, and you have the numbers. If the admin is faster, your team notices without being told. Putting a vendor’s percentage into a business case is how a project ends up defended by a number nobody on your side can reproduce.

The same goes for the counts. Shopify Payments arriving in sixteen more countries is a precise, checkable claim that matters only if one of the sixteen is yours — and the Edition names them, so read the list rather than the total. Same for the new carriers and the additional Klarna markets.

Read three or four of these in a row and the shape becomes predictable. The platform steadily absorbs things merchants used to buy apps for — duties, store credit, discount logic, review of your own performance data — and steadily moves customisation out of theme code and into blocks, extensions and functions with defined boundaries. Both directions are good news if you are building on the platform and bad news for any store whose competitive advantage was a clever hack in checkout.liquid.

The practical consequence is that the right posture is not "adopt everything". It is to keep the store close to platform defaults so that when the platform ships the thing you were about to pay for, you can simply use it. Every custom workaround you carry is a feature you will have to migrate off later.

We scope [Shopify builds](/services/build) with that in mind: fewer apps, fewer bespoke mechanisms, more of the store expressed in the parts of the platform Shopify is actively improving. An Edition is easiest to read when most of it is something you can just switch on.

• Shopify store development
• Theme architecture: settings, blocks and the limits of each
• Duties at checkout, and the post-purchase surprise