Shopify Updates September 2026: What Actually Matters for Merchants

Key takeaways

• Meta joined Agentic Storefronts on September 8, and your products were shared with it by default. The same day Meta launched Muse, a consumer agent that shops and pays on the user’s behalf. Eligible US-selling stores have direct checkout switched on already.
• Meta’s direct checkout does not fire your browser pixels. Orders are attributed to Meta in your admin, but third-party attribution tags never run. Server-side events are the only way to see them.
• October 1 is the next deadline cluster. Script tag API writes start failing, apps with extensions on API 2025-07 or earlier can no longer be updated, and API version 2026-10 ships. Ask your app vendors now.
• The August 26 checkout upgrade is still costing stores reported conversions. The busiest merchant threads of the month are about Meta and Google showing fewer purchases than Shopify.
• Variants can carry up to 20 barcodes. GTIN, EAN, ASIN, ISBN, UPC and custom codes on one variant, scannable at POS, importable by CSV.

Here are the Shopify updates for September 2026, ranked by what actually matters for a merchant rather than dumped as a flat changelog. August was about a deadline that broke conversion tracking on most stores. September is about a new sales channel that turned itself on the day Meta launched its Muse shopping agent, and about the next set of cutoffs that arrive on October 1.

We publish this mid-month so you can act while it matters, and update it at month-end if anything significant lands.

Related reading: last month’s Shopify updates (August 2026).

At a glance: the September 2026 release notes in one table

Update	Who it affects	Why it matters	What to do
Meta added to Agentic Storefronts (Sep 8)	Stores selling to US customers	Products shared by default, direct checkout on by default	Review the toggles, check what agents can read
Meta Muse launched (Sep 8)	Every merchant, strategically	A consumer agent that shops and pays inside the app	Fix product data before the traffic arrives
October 1 deadline cluster	Everyone with older apps	Script tag writes fail, old extensions freeze, 2026-10 ships	Ask app vendors for their migration date
Multiple barcodes per variant (Sep 8)	Ops, wholesale, marketplace sellers	Up to 20 codes per variant, any of them scannable at POS	Import supplier and channel codes via CSV
Shopify acquires Tailwind Labs (Sep 9)	Developers, headless stores	Signals investment in custom storefront tooling	Nothing, unless you were about to buy Tailwind Plus
Multi-currency payouts in AU and FR (Sep 11)	Advanced and Plus on Shopify Payments	Get paid in the currency you sell in	Add payout accounts under Settings > Payments
WhatsApp consent at checkout (Sep 10)	Marketers	Build a WhatsApp list at the point of purchase	Turn it on in Checkout settings
Abandoned online cart visible in POS (Sep 3)	Retail on POS	Staff can finish a sale the customer started online	Grant the permission to the right POS roles
Persistent cart on mobile POS (Sep 14)	Retail on POS	One tap to the cart from any screen on phones	Update to POS 11.15
Discounts Allocator preview ends (Sep 29)	Developers	Apps still declaring the target fail to deploy	Move to the Discount Function API
Events contract changes (Sep 16)	Developers	New webhook system changes shape before going stable	Refactor before 2026-10
Admin login outage (Sep 15)	Everyone	Roughly four hours of failed logins	Nothing, resolved

The 3 September updates worth your time first

If you read nothing else this month:

1. Open Sales channels > Agentic and look at the Meta row. It was created for you, with product sharing and direct checkout switched on. Decide whether you want both, and know that a Meta checkout does not fire the tags your attribution runs on.
2. Send your app vendors one question before October 1: what is your script tag migration date? From that day, apps can no longer add or change script tags, and apps with older checkout extensions cannot be updated at all.
3. Reconcile Meta and Google against Shopify for the two weeks after August 26. If the gap is bigger than it was in July, you lost server-side purchase events in the checkout upgrade and your bidding is running on bad data.

1. Meta in Shopify Agentic Storefronts: what changed on September 8

What changed. On September 8, Shopify added Meta as an AI channel inside Agentic Storefronts. The changelog entry is three sentences long, and the second one is the important one: your products are shared with Meta by default through Shopify Catalog.

The timing was not a coincidence. Meta launched Muse the same day, a personal agent that connects to a user’s email, calendar, payments and shopping, and completes tasks rather than answering questions.¹ It runs on the web, in iOS and Android apps, and inside WhatsApp, with a free tier and paid plans at $20 and $100 a month. It is US-only for now. Shopify’s own account on launch day was that merchants were already live in Muse: when a user asks it to buy something, it searches Shopify Catalog and can complete the purchase inside the app without ever opening your store.²

Who is in. According to Shopify’s help documentation, the Meta channel applies to stores that sell to customers in the United States, have the Facebook and Instagram by Meta channel installed with product syncing on, have products eligible for Shopify Catalog, have completed the Terms of Service, Privacy and Return policies under Settings > Policies, and have accepted the Agentic Storefronts supplemental terms.³ If that describes you, purchasing through Meta’s direct checkout is active by default. Stores on the Agentic plan are the exception: direct checkout is off by default there.

What is not supported. Subscriptions, product bundles, customizable products and B2B-only products cannot be sold through Meta’s direct checkout. If an order needs information Meta cannot supply, the shopper is sent to your store with the cart intact.

Why merchants care. This is a sales channel with real distribution behind it. Muse is Meta’s consumer bet, and it can pay. For stores in Shopify Catalog, the order goes through Shopify’s direct checkout and your normal payment processing. For stores that are not, Muse buys the way a shopper would, in its own browser with a Stripe Link virtual card, and Shop Pay support for that path is listed as coming soon.¹

The catch is measurement. Orders placed on Meta surfaces are attributed to Meta and show up in your admin like any other channel, but third-party analytics pixels do not fire on Meta’s direct checkout.³ Your Meta pixel, your Google tag, your GTM container: none of it runs, because the checkout never happens in a browser you control. Shopify says server-to-server pixels are supported, so the checkout started and completed events can reach a CAPI-style integration. If your attribution is browser-only, these sales will look like they came from nowhere.

There are no channel fees. You pay your standard payment processing rate and nothing else.

What to do.

1. Go to Sales channels > Agentic and click Meta. You will see two toggles: Shopify Catalog access and Direct checkout.
2. Leave Catalog access on. Being discoverable costs you nothing.
3. Keep direct checkout on only if you can see those orders in your attribution. The test is Events Manager: filter for server-side purchase events and check whether a Meta-attributed order from your admin appears there. If it does not, either fix the server-side integration or turn direct checkout off until you have.
4. Run the free Shopify Catalog data audit to see what an agent finds when it reads your products. Thin titles and missing variant attributes are the reason an agent picks a competitor, and Muse does not browse your homepage.

For the wider context on how Shopify has been rolling these channels out since December, read our Agentic Storefronts guide. If the audit turns up gaps, the Fudge store editor rewrites titles, attributes and metafields across the catalog from a prompt.

2. What happens to Shopify apps on October 1, 2026?

Three things happen on October 1, and none of them is new news. They are now two weeks away, and each one hits a different layer of your store.

Script tag API writes start failing. As covered in August, apps can no longer create or update storefront script tags from October 1, and on March 1, 2027 Shopify stops injecting them entirely.⁴ From a merchant’s side, the symptom is an older app that can no longer update its storefront widget, and a vendor that has been quiet about migration.

Apps with older checkout extensions freeze. Any app that still contains a checkout UI or customer account UI extension on API version 2025-07 or earlier can no longer be updated at all after October 1.⁵ The app keeps running, but its developer cannot ship a fix to any part of it until the extensions move to 2025-10 or later, which means the Polaris web components migration.

API version 2026-10 ships. The October release recalculates taxes when a shipping address is updated and removes the legacy Checkout types from the Customer Account API, among other breaking changes.⁶ The same version line carries the new Events system, the barcodes connection, and the countryCode field on customer addresses. Two weeks later, on October 16, API version 2025-10 is retired.

Why merchants care. You do not run any of these commands. Your apps do. The failure mode for each one is the one you saw in June with Scripts and in August with additional scripts: nothing errors, something just stops. The only defence a merchant has is to ask.

What to do. Send one message to each app vendor whose product touches your storefront or checkout: “Does your app use script tags, and are your extensions on API 2025-10 or later?” A vendor that answers in a sentence is fine. A vendor that does not answer is your list of apps to replace before BFCM. Our checkout extensibility guide explains what each extension surface can and cannot do if you need to evaluate a replacement.

3. The August 26 hangover: three platforms, three different numbers

What is happening. Two weeks after the Thank you and Order status page upgrade on non-Plus stores, the most active merchant threads of the month are about Meta reporting fewer purchases than Shopify, Google reporting a different number again, and merchants trying to work out whether sales fell or measurement did.⁷ The migration steps are in last month’s post; this is what two weeks of threads have added.

The clearest explanation came from a merchant on the day itself: “The store didn’t stop selling. The receipt page stopped talking to Meta.”

Four causes, and most affected stores have more than one:

• Purchase events fired from additional scripts on the order status page are gone, and nothing replaced them.
• Conversions API integrations that read from a legacy source (older Elevar or Triple Whale setups, custom scripts) lost their data feed, so the server side went quiet too.
• Browser pixels kept firing on some stores, and Meta’s deduplication masked the gap for a week or more.
• Timezone mismatches between the Shopify and Meta accounts made day-level comparisons look wrong even where the events were fine.

The damage is in the bidding. Smart Bidding and Advantage+ react to a fake conversion drop faster than any human notices it, and the missed conversions never backfill.

What to do. Reconnect Meta through the native channel under Customer Events, set data sharing to Enhanced or Maximum, and confirm the server-side purchase event is present in Events Manager. Then compare the browser and server event split against July. Our Meta Conversions API guide covers the setup. One caveat from the same fortnight: a heavily replied thread traced Meta purchase events firing on homepage load to a codeless rule in Meta’s Event Setup Tool, not to Shopify.⁸ Not every tracking oddity this month is the upgrade’s fault.

4. Variants now carry up to 20 barcodes

What changed (September 8). Each product variant can now hold up to 20 barcodes, each with an optional type of UPC, EAN, ISBN, GTIN, ASIN or Custom, validated against the format. You manage them on the variant page or in the mobile app, bulk-edit across variants, and import and export through a new Variant Barcodes column in the CSV. The first barcode stays the primary identifier for channels, feeds, labels and third-party apps, so existing data needs no migration.

On the POS side, staff can scan or search any barcode on a variant from POS 11.14 and land on the right product.

Why merchants care. Anyone who buys from more than one supplier, sells on Amazon and in store, or repackages products has been running a spreadsheet of alternate codes on the side. Supplier cartons carry one code, the retail unit another, Amazon expects an ASIN, and your own label printer wants a SKU-based code. Until now, only one of those could live on the variant.

For developers. In API version 2026-10, ProductVariant gains a barcodes connection and the singular barcode field is deprecated.⁹ It still works, but once a variant has a second barcode, a barcode-only reader sees one of them with no hint that others exist. Sending barcodes replaces the whole set, and you cannot set both fields in one input. Shopify has not named a removal date and promises a full API version of notice before it does.

What to do. Export your products, fill the Variant Barcodes column with every code you actually receive or ship under, and re-import. If you use a marketplace connector or a WMS, ask whether it reads the new connection yet, because until it does it will only see the first code.

5. Shopify bought Tailwind Labs

What happened. On September 9, Tailwind Labs, the company behind the Tailwind CSS framework, announced it is joining Shopify.¹⁰ Terms were not disclosed. Tailwind CSS stays MIT-licensed and the same team continues to maintain it. The paid products, Tailwind Plus and ui.sh, are closed to new sign-ups; existing customers keep access.

The backstory: in January, Tailwind’s founder said revenue was down close to 80% and documentation traffic down about 40% from early 2023, because AI coding tools generate Tailwind code without anyone visiting the docs the paid products sat next to.¹⁰ Tailwind is installed more than 110 million times a week and had become infrastructure without a business model. Shopify, which calls Tailwind a load-bearing part of its own stack, gave it one.

Why merchants care. In the short term, nothing changes. Liquid themes such as Horizon and Dawn do not use Tailwind, Hydrogen storefronts can keep using it or not, and Polaris is unaffected. If you were about to buy Tailwind Plus for a custom build, you now cannot.

In the longer term, this is Shopify hiring the team that defines how a large share of the web writes front-end code, at the same time as it pushes custom and headless storefronts as a growth line. Shopify wants to own the tooling for stores that outgrow the theme editor, not just the stores that stay in it.

What to do. Nothing this month. If you are planning a custom storefront for 2027, our Hydrogen guide covers what the stack looks like today.

6. Money: multi-currency payouts reach Australia and France

What changed (September 11). Eligible Shopify Payments merchants on Advanced and Plus plans in Australia and France can now receive payouts in multiple currencies. Australian stores can be paid in 13 currencies, to an Australian bank account or to accounts in the US, New Zealand, UK, Canada or the eurozone. French stores get 18, with EUR as the default and other currencies routed to additional bank accounts.

Why merchants care. If you sell in USD or GBP from Sydney or Paris, you have been paying a conversion spread on every payout to bring the money home. Getting paid in the currency you sold in, into an account in that currency, removes the spread and lets you pay suppliers and ad platforms without converting twice. This follows the July removal of the eight-currency cap and is part of the same cross-border push that brought Managed Markets to Canada and the UK.

What to do. Under Settings > Payments > Shopify Payments > Manage > Payout accounts, add a bank account per currency you sell in meaningful volume, then assign payouts. Compare the result against your current conversion cost for a month before moving ad spend accounts over. If Markets is where your international pricing lives, our Shopify Markets setup guide covers the settings that feed into this.

7. Marketing: WhatsApp consent at checkout

What changed (September 10). Checkout can now collect WhatsApp marketing consent, the fourth piece of a chain that started in June with consent management, continued in July with WhatsApp campaigns in Shopify Messaging, and added Forms in August.

Why merchants care. The checkout opt-in is the one that builds a list, because it catches people at the moment they have already decided to trust you with an order. For stores in markets where WhatsApp is the default messaging app, this is now a complete native loop: capture at checkout, send campaigns from Shopify, no third-party tool.

What to do. Turn it on under Checkout settings. If you already run SMS opt-in at checkout, watch the combined opt-in rate for a few weeks, since two consent prompts in a row can depress both.

8. Retail: POS 11.14 and 11.15

Three things landed for stores that sell in person.

Staff can see an identified customer’s online cart. From POS 11.14, when staff look up a customer who has an abandoned online checkout, they can pull those items into the in-store cart and close the sale. It needs an explicit permission: View abandoned checkouts, under Settings > Users > Roles, in the POS role’s Customers section. The customer has to be identified with an email, and only the cart contents are shown, not browsing history.

A connectivity indicator on POS Home (September 1) shows whether the device is online before staff start a sale, replacing a status buried in the side navigation.

A persistent cart button on phones. POS 11.15 (September 14) replaces the cart tab and the go-to-cart bar with a button that follows staff across Home, Products, Orders and Search, showing item count and running total. It also confirms when a discount, customer, staff assignment or fee is added.

What to do. The online-cart feature is the one worth setting up. Grant the permission to floor staff roles, then tell them it exists. The reminder from August still stands: Liquid receipt templates are converted automatically on January 1, 2027, so build the replacement in the receipt editor while both can run side by side.

9. What Shopify told investors about AI traffic

What happened. At the Goldman Sachs Communacopia conference on September 10, CFO Jeff Hoffmeister and head of growth Archie Abrams gave the first conversion and landing-page numbers Shopify has put on agent-driven discovery.¹¹ Searches that start in an LLM are 2.5 times more likely to land directly on a product page than traditional search, and shoppers who reach a merchant’s site through LLM discovery convert at roughly 80% higher rates. Hoffmeister said Shopify is only six to nine months into seeing that traffic at any real volume. Abrams listed the platforms Shopify has made itself accessible to: ChatGPT, Claude, Lovable, Manus, Replit and Groq.

Why merchants care. The two numbers describe the same thing from opposite ends. An agent skips your homepage and your collection page and drops the shopper on a product page, because it already did the comparing. That shopper converts better because they arrive decided. The product page is now the landing page, and the product data is what the agent compared.

What to do. Segment your analytics by referrer for chatgpt.com, perplexity.ai, claude.ai, copilot.microsoft.com and gemini.google.com, and look at the landing pages rather than the volume. Then read answer engine optimization for Shopify for what those product pages need to contain.

10. Other new Shopify features in September 2026, in brief

• Storefronts advertise UCP version 2026-08-25 (September 4) in their discovery profiles at /.well-known/ucp. Capabilities are unchanged, only the version negotiation. Our UCP readiness guide explains what the endpoint does.
• Hydrogen developer preview update (September 2): variant links land on the named variant, a cart refresh action to reconcile client state, and auto-generated local HTTPS certificates for testing customer account login.
• A paymentInstrumentSendAddEmail mutation (September 3, API 2026-10) emails a customer a link to add a payment method to a subscription contract, order or draft order themselves. Previously that was only possible when a method was already on file.
• Customer address APIs accept countryCode (September 8, Customer Account API 2026-10). The old territoryCode field is deprecated but not removed.
• Shopify CLI 4.8 creates and deletes dev stores from the terminal (September 9), with a new cap of 250 development stores per organization. Organizations already above it keep their limit.
• Theme CLI 3.83.x and older lose password-protected dev flows on October 1. The theme commands, and app dev for apps with theme app extensions, need CLI 3.84 or later on password-protected stores.
• Shopify is moving its mobile apps from React Native to native Swift and Kotlin (September 10). Shop is done, rebuilt and shipped in twelve weeks, and the Shopify admin app ships later this year.¹² The stated reason is that coding agents removed the cost of building twice.
• An admin login outage on September 15 ran from 09:19 to 13:20 UTC and affected Admin, POS and Support.¹³ Shopify classed it as minor. Its first public status update came at 09:49 UTC, half an hour after the window it later said the problem began.

What merchants are talking about

Three themes dominated the community this window:

• The tracking reconciliation problem is the conversation. The August 26 aftermath threads are the most active on the merchant forum this month, and the tone has shifted from “how do I migrate” to “which of these three numbers is real.” None of them has a reply from Shopify staff.
• Nobody can find the agent orders yet. Merchants are asking whether anyone has seen an AI-referred order in their analytics, and the honest answers are a trickle of ChatGPT and Perplexity referrals with very few orders clearly attributable.¹⁴ One merchant checked 15 storefronts and found 11 serving an llms.txt and a UCP endpoint nobody had created, with the MCP endpoints resolving to myshopify.com subdomains, which means agent catalog queries never show in a custom-domain log. The practical consensus is to fix structured product data and legal pages first, because exclusions are silent and there is no admin warning.
• Developers had a rough fortnight. The Partner Dashboard showed zero earnings from September 5 until Shopify confirmed a data sync issue on September 8 and recovered the data on the 9th, with actual payouts unaffected.¹⁵ Shopify also posted an update on App Store review authenticity after removing reviews it judged inauthentic, and developers pushed back on the lack of an appeal path. And the migration to expiring access tokens, mandatory for every public app from January 1, 2027, has a failure mode where a lost HTTP response during the exchange orphans the install; Shopify staff said they will make the exchange more resilient.

Payout holds remain the sharpest recurring merchant complaint, unchanged from August. A steady trickle of threads describe funds held with no self-serve route to a human.

September updates ranked by merchant impact

Priority	Update	Effort	Urgency	Who it’s most for
1	Review the Meta toggles under Sales channels > Agentic	Low	Now	Stores selling to US customers
2	Reconcile Meta and Google against Shopify since Aug 26	Medium	Now	Every non-Plus store running ads
3	Ask app vendors about script tags and extension versions	Low	Before Oct 1	Everyone
4	Audit product data for agent readability	Medium	Now	Everyone
5	Add supplier and channel barcodes to variants	Low	Soon	Multi-supplier, marketplace sellers
6	Set up multi-currency payouts	Low	Soon	AU and FR on Advanced or Plus
7	Grant the abandoned-checkout permission in POS	Low	Soon	Retail
8	Turn on WhatsApp consent at checkout	Low	Soon	Stores in WhatsApp-first markets
9	Remove the Discounts Allocator target	Low	Before Sep 29	Developers
10	Refactor for the Events contract changes	Medium	This week	Developers

What to do this month: a checklist by store type

If you’re a DTC brand on a non-Plus plan:

• Open Sales channels > Agentic > Meta. Decide on direct checkout, and confirm your server-side events can see those orders.
• Pull Meta, Google and Shopify purchase counts for August 12 to 26 and August 27 to September 10. If the gap widened, fix the server-side event before touching bids.
• Message every app vendor about script tags and extension API versions before October 1.

If you sell cross-border:

• Australian and French stores on Advanced or Plus: set up per-currency payout accounts and compare against your current conversion cost.
• If you use Managed Markets, note that Meta’s direct checkout is US-only for now, so your international pricing is unaffected.

If you run retail or POS:

• Update to POS 11.15, grant View abandoned checkouts to floor roles, and tell staff it exists.
• Import alternate barcodes for anything you receive under a supplier code.
• Rebuild any Liquid receipt template before the January 1, 2027 conversion.

If you’re a developer or run headless:

• Refactor Events handlers for the September 16 contract changes: fields_changed becomes an object with added, updated and removed buckets, delete events no longer cascade, and parent trigger paths need an explicit .* wildcard.¹⁶
• Remove any purchase.discounts-allocator.run target before September 29 or shopify app deploy fails outright.
• Replace script tags with app embed blocks or web pixels before the October 1 write freeze, and move checkout and customer-account extensions to API 2025-10 or later.
• Read barcodes instead of barcode when you move to 2026-10.

Shopify developer updates and the deadline list

Events is going stable. Shopify’s next-generation webhook system, in developer preview since spring, becomes stable in API version 2026-10.¹⁶ Before that, the contract changes on September 16: fields_changed moves from an array to an object with added, updated and removed buckets, delete operations produce a single delete event instead of cascading child updates, parent trigger paths require .*, and the redundant shopify-event-id and shopify-resource-id headers are removed. Developer reaction on the forum was unusually warm for a breaking change, because the granular triggers replace a lot of polling.

The Discounts Allocator Function API is gone. The developer preview ended on September 10 with the removal effective September 29. The register and unregister mutations are removed from the unstable API, registered functions were unregistered automatically, and any app still declaring the purchase.discounts-allocator.run target fails to deploy with an API-not-found error. Shopify’s position is that native discount controls, including stacking multiple product discounts on a line, cover most of what the allocator was used for. Migrate to the Discount Function API.

The deadline digest, in date order: September 16 (Events contract changes take effect), September 29 (Discounts Allocator removal), October 1 (API 2026-10 released; script tag create and update calls start failing; apps with checkout or customer-account extensions on API 2025-07 or earlier can no longer be updated; theme CLI 3.83.x and older lose password-protected dev flows), October 15 (the card deposit endpoint requires a Shopify-issued mTLS certificate), October 16 (API version 2025-10 retired), December 1 (Built for Shopify authentication requirements for returns and subscription apps), January 1, 2027 (expiring offline access tokens required for all public apps; POS Liquid receipt templates converted automatically), January 16, 2027 (API version 2026-01 retired), March 1, 2027 (script tags stop running on storefronts).

Where Shopify is heading

August’s theme was Shopify removing custom code from its critical path. September’s is Shopify adding distribution merchants did not ask for. Meta became a sales channel for eligible stores with a changelog entry rather than an opt-in flow, and the products were shared before most merchants read the entry. That is a pattern now: four AI channels switched on together in March, WebMCP tools appeared on every Liquid storefront in August, Meta this month.

It is consistent with what the CFO told investors the same week. Shopify’s pitch is that it is the one admin that connects a merchant to every agent platform at once, and the value of that pitch grows with every channel it turns on by default. Each new surface makes the platform more useful to the merchant with good product data and more dangerous to the one without, because the agent compares catalog fields.

The Tailwind acquisition is the other half. Default channels bring the traffic; custom storefront tooling is where Shopify wants the stores that outgrow the theme editor to stay. Between them sits a store owner whose job in September is unglamorous: check a toggle, reconcile three numbers, send an email to a few app vendors, and fix the product data an agent is already reading. The rest can wait until October.

FAQ

Footnotes

1. TechCrunch: Meta debuts its Muse AI agent, September 8, 2026. Pricing, platforms, US availability, and the Stripe Link and Shop Pay details are from Meta’s launch coverage, not from Shopify. ↩ ↩²

2. Shopify on X, September 8, 2026. ↩

3. Shopify Help Center: Selling on Meta through Agentic Storefronts. Eligibility, default settings, unsupported product types, pixel behaviour and fees are as documented on September 15, 2026. Check the page before planning around it. ↩ ↩²

4. Shopify developer changelog: Online store script tags deprecation, August 24, 2026. ↩

5. The October 1 cutoff for apps with extensions on API 2025-07 or earlier is stated in the Shopify AI Toolkit for upgrading extensions to Polaris web components changelog entry, June 11, 2026. ↩

6. Shopify API release notes, version 2026-10 and the API versioning schedule. Events, barcodes and countryCode are announced in separate changelog entries linked elsewhere in this post. ↩

7. Shopify Community: Meta reporting fewer purchases than Shopify after the Aug 26 checkout upgrade, August 26 to September 14, 2026, and the two-weeks-after retrospective, September 9, 2026. Some replies in the retrospective are from app vendors. ↩

8. Shopify Community: Meta purchase event fires on homepage load with no purchase, September 7 to 10, 2026. The thread identifies the rule as the likely cause; no confirmed resolution had been posted at the time of writing. ↩

9. Shopify developer changelog: Variants now support multiple barcodes, September 8, 2026. ↩

10. Tailwind Labs: Tailwind is joining Shopify, September 9, 2026. The revenue and documentation traffic figures are from the founder’s January 2026 statements as reported by DevClass; terms of the acquisition were not disclosed. ↩ ↩²

11. Shopify at the Goldman Sachs Communacopia and Technology Conference, September 10, 2026. The 2.5x and 80% figures are Shopify’s own and were not broken down by merchant size or category. ↩

12. Shopify Engineering: Native is now the future of mobile at Shopify, September 10, 2026. ↩

13. Shopify Status: Shopify Admins are experiencing degraded performance, September 15, 2026. ↩

14. Shopify Community: Has anyone actually seen AI-referred orders in their analytics yet?, September 14, 2026, and Your store already serves an llms.txt and a UCP endpoint you did not create, September 10, 2026. The author of the 15-storefront thread co-founded an attribution app. ↩

15. Shopify Developer Community: Earnings not showing correctly in Partners Dashboard, September 6 to 9, 2026. ↩

16. Shopify Developer Community: Upcoming changes to Events, September 9, 2026. ↩ ↩²