TL;DR — The blog went quiet in April; Shopify did not. The June 17 Editions drop (officially "Spring '26," even though half the coverage calls it Summer) removed the approval gate from UCP agent registration, gave agentic storefronts their own page in admin, and previewed a multi-source collection model that replaces the smart/custom split in API 2026-07. And the one with a hard deadline attached: Shopify Scripts stops executing June 30 — eleven days from now. If you still have a Plus store leaning on Scripts, that is no longer a migration project, it is a countdown.
The theme
Two months of changelog in one sitting, and the shape is clear: the agentic checkout line is now open to anyone. In January, UCP was an architecture post and a short list of launch partners. As of June 17 it is a self-serve registration form and a public MCP endpoint. Around it, Shopify shipped the supporting surfaces a merchant actually needs — a place in admin to see which AI channels rank your products, customizable llms.txt files, Sidekick extensions for the apps you already run. One housekeeping note on naming before the entries: the official page is shopify.com/editions/spring2026. Third-party recaps almost universally say "Summer '26 Editions," and editions/summer2026 is a 404. Cite the real one.
1. UCP registration goes self-serve (original)
Overview
The Universal Commerce Protocol — the Google-and-Shopify-led standard for agents that discover merchants, build carts, and complete checkouts — dropped its approval gate. Any developer can now register an agent profile in the Developer Dashboard and start calling the public MCP endpoint. When the architecture post landed in January, the interesting question was whether this would stay a walled garden for Etsy, Target, Walmart, and Wayfair-sized partners. June 17 answered it: the same rails, open to whoever fills in the form.
Technical
The agent-side stack, per shopify.dev/docs/agents: the UCP CLI installs via npm install -g @shopify/ucp-cli (Node 18+), and the MCP surface splits into Global Catalog (cross-merchant search), Storefront Catalog (single merchant), Cart, Checkout, and Order servers — the last with a get_order tool plus webhooks for fulfillment, refunds, and returns. Trust tiers key rate limits and capability access to your agent profile, published at a well-known URL. On the merchant side, profiles live at /.well-known/ucp, capabilities use reverse-domain naming (dev.ucp.shopping.*), and checkout runs as a state machine — incomplete, requires_escalation, ready_for_complete — so an agent knows exactly when a human needs to step in. A multi-merchant Universal Cart API is in early access. The Spring '26 dev post also shipped an open-source UCP Skill toolkit and Catalog API additions: image search, multi-modal search, product URL resolution, and Shop sign-in.
Takeaway
If you build for merchants, register an agent profile now even if you have no agent to ship — the trust-tier system means account age and behavior history will likely matter, and the exploration cost is an afternoon. If you run a store, the work is upstream of the protocol: agents transact against the catalog data you already publish, so every normalization pass you make this quarter compounds when this traffic arrives.
2. Agentic storefronts get an admin surface (original)
Overview
Two smaller ships that matter together. Since May 11, agentic storefronts have a dedicated page under Sales channels → Agentic in admin — per-channel ranking data and query-level visibility into which AI queries surface your products, across ChatGPT, Google AI Mode/Gemini, Microsoft Copilot, and Meta. And since May 28, /llms.txt, /llms-full.txt, and /agents.md are customizable per store. Editions layered Shopify Catalog on top: product data auto-syndicated to AI channels, with checkout embedding into surfaces like Copilot and Meta ads.
Technical
The Agentic page is the first place a merchant can see AI-channel demand as data rather than anecdote — which queries you rank for, per channel, with product-feed recommendations attached. Treat the customizable llms.txt the way you treat structured data: a controlled surface you audit, version, and test, since it is now part of how agents read your store. On the Catalog claim — Shopify's editions page says syndicated data "drives 2x more conversion in AI chats." That is Shopify's number from Shopify's funnel; I have not seen the methodology, and neither have you. The direction is plausible, the multiplier is marketing until someone outside Shopify reproduces it.
Takeaway
Add the Agentic page to whatever weekly reporting ritual you already run. Volume will be small for most stores this year; what matters is the trend line and which queries you rank on, because that tells you what the models think your store sells. If the queries look wrong, that is a catalog-data bug, and now you have a place to catch it.
3. Collections get a real data model in API 2026-07 (original)
Overview
The smart/custom collection split — one of the oldest constraints in the platform — is being replaced by a source-based model, in developer preview now ahead of the 2026-07 API release. A Collection.sources field returns the one-or-more sources backing a collection: typed inclusion conditions, manual selections, exclusion conditions, shareable app-owned sources, and variant-level membership. One collection can now mix a rule-based source with hand-picked additions and an exclusion list, which previously took an app or a merge job.
Technical
The rollout is non-breaking in 2026-07 — deprecated members remain queryable — with one sharp edge: collections that use new-model-only features are silently filtered out of query results on pre-2026-07 API versions. That is the trap. An app pinned to 2026-04 will not error; it will simply not see collections a merchant built with the new tools, and the merchant will file the bug against your app. Variant-level membership is the other quiet headline: collection membership at the variant level unlocks merchandising cases (colorway-specific collections, size-run filtering) that the product-level model never could.
Takeaway
If you maintain an app that reads collections, schedule the 2026-07 bump this quarter and grep your codebase for anything assuming the smart/custom binary — ruleSet presence checks are the usual suspect. The filtered-results behavior means staying on an old version fails silently, and silent is the expensive kind.
4. Shopify Scripts stops executing June 30 (original)
Overview
Not news to anyone who was paying attention — the timeline was published well in advance — but it belongs in a catch-up post because the final deadline is now eleven days out. Editing and publishing Scripts already ended April 15; execution stops entirely June 30. Every Plus store still leaning on a line-item discount script or a shipping-rate script loses it that day, with no error banner to announce it. Shopify Functions is the replacement, and side-by-side operation is allowed right up to the cutoff.
Technical
The migration path is well-worn at this point: the Scripts customizations report in admin maps what your scripts do, and each maps to a Function API — product discounts, order discounts, shipping customizations, payment customizations. Functions run as WASM with hard instruction limits, so the freeform-Ruby habits of Scripts (calling out to metafields mid-loop, unbounded iteration) need real restructuring — a line-by-line port usually blows the execution budget. Budget real QA time on discount stacking: Functions compose with Shopify's native discount combining rules, which Scripts predated and frequently fought.
Takeaway
If you run or inherit a Plus store, audit for live Scripts today and get the Functions migration scheduled before the 30th — after the cutoff, a script that silently stops firing looks exactly like a pricing bug with no error attached, and you will be diagnosing it from checkout revenue instead of a log line. Sidekick's new app extensions and the rest of the Editions list can wait; this one is about money moving through checkout.
Original sources
- Shopify Editions Spring '26 — Everywhere — 2026-06-17
- Spring '26 Edition for developers — 2026-06-17
- Introducing the Universal Commerce Protocol — 2026-01-11
- Build commerce agents
- A new home for agentic storefronts in your admin — 2026-05-11
- Customize llms.txt, llms-full.txt and agents.md — 2026-05-28
- New collection model and APIs now available
- Shopify Scripts deprecated on June 30, 2026
- Sidekick app extensions available today — 2026-06-17
