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. On September 21, Shop Pay checkout switched on inside Muse for eligible stores selling to the US, Canada and Mexico.
• Any browser agent can now check out on your store. From September 28, WebMCP covers checkout: an agent in the shopper’s browser can read the checkout, change the address or delivery option, and submit the order with a saved Shop Pay card once the shopper confirms. It is on for every eligible store, with no setting.
• 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.
• Your conversion rate changed on September 21, and your traffic did not. Shopify changed how Analytics counts sessions: bots are filtered out by default, sessions no longer split at midnight UTC, and some sessions without a pageview now count. Orders and sales are untouched.
• October 1 brought the next deadline cluster. Script tag API writes now fail, apps with extensions on API 2025-07 or earlier can no longer be updated, and API version 2026-10 is stable. An app vendor who went quiet in September is the one to check.
• 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.
• The admin got a new look, and variants got more barcodes. The redesign has been rolling out since September 15, with a collapsible side navigation and Sidekick floating on every page. Variants carry up to 20 barcodes, and return windows can now differ by product.

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.

Update (September 30): it did. The second half of the month is where the agent story became a checkout story: on September 21 Shop Pay checkout switched on inside Meta’s Muse, and on September 28 Shopify opened checkout to any browser-based AI agent through WebMCP, on by default with no setting to review. The same fortnight changed how Analytics counts sessions, so conversion rates moved without orders moving, and rolled a redesigned admin out to every store. Return window overrides, tax on return shipping fees, a redesigned Payouts page and POS 11.16 are all in the late-September section below.

Prefer to watch? Here are the biggest September changes in 5 minutes:

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
Shop Pay checkout inside Muse (Sep 21)	Stores selling to US, CA, MX	Muse completes purchases with Shop Pay, on by default	Same toggles as the Meta channel
WebMCP reaches checkout (Sep 28)	Every merchant	Browser agents can read, edit and submit a checkout	Run an agent through a test order
Analytics session measurement (Sep 21)	Anyone who reads a conversion rate	Bots filtered, sessions redefined, rates shift	Re-baseline from Sep 21, do not compare across it
Admin new look (Sep 15)	Everyone	New navigation, Sidekick floating on every page	Nothing, there is no way back
Return window overrides (Sep 29)	Anyone with a returns policy	Different windows per collection, product or variant	Set rules under Settings > Policies
Tax on return shipping fees (from Oct 23)	US stores on Shopify Tax	Return shipping fees taxed automatically	Retire manual workarounds before Oct 23
Payouts page redesign (Sep 16)	Everyone on Shopify Payments	One view of every payout, grouped by day	Check your bank reconciliation still works
Category metafields in Analytics (Sep 28)	Anyone who builds reports	Group sales by colour, material, fit or any metaobject	Finish categorizing the catalog
POS 11.16 (Sep 28)	Retail on POS Pro	Local delivery orders and scheduled stock counts in POS	Update, grant the permissions

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, and since September 21 Muse pays through Shop Pay on eligible stores. Decide whether you want both, and know that a Meta checkout does not fire the tags your attribution runs on.
2. Run a browser agent through a test order on your own checkout. Since September 28, any agent in the shopper’s browser can read, edit and submit your checkout with Shop Pay, on by default. Watch where the order lands in your reports and whether your delivery and discount rules hold.
3. Reconcile Meta and Google against Shopify for the two weeks after August 26, then re-baseline your conversion rate from September 21. The first tells you whether you lost server-side purchase events in the checkout upgrade. The second is Shopify changing how it counts sessions, which moved conversion rates on every store without moving a single order.

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.

Since we published, the Shop Pay path arrived. On September 21, Shopify CEO Tobi Lütke announced that Shopify is “partnering deeply with Muse to enable agentic checkout with Shop Pay on all Shopify stores”, and Muse began completing purchases through Shop Pay on eligible stores rather than through its own virtual card.⁴ Shopify’s help documentation now lists stores selling to Canada and Mexico alongside the United States as eligible for Meta’s direct checkout, with purchasing on by default.³ The contrast was deliberate: Amazon had barred Muse from its site the day before, citing credential and privacy risk, and Shopify’s stock rose about 7% on September 22 as analysts read the deal as Shopify becoming the checkout layer for agents.⁴ The measurement caveat above is unchanged. A purchase completed inside Muse is attributed to Meta in your admin and does not run your browser pixels.

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 happened on October 1, and none of them was new news. Each one hits a different layer of your store.

Script tag API writes now fail. 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 is stable. It went to release candidate on September 26 and stable on October 1. The 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. If you did not ask before the date, ask now. 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, and since October 1 the failure is already live: a script-tag widget cannot be updated, and an app with old extensions cannot ship a fix to any part of itself. 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.

Since we published, a second reason for a moving conversion rate arrived, and it is unrelated to the first. On September 21, Shopify changed how Analytics counts sessions, which shifts conversion rate, add-to-cart rate and bounce rate on every store without touching orders. If your Shopify conversion rate moved in the last ten days of September, separate the two: the August 26 problem shows up as a gap between Shopify and your ad platforms, while the September 21 change shows up inside Shopify’s own reports with sales unchanged. The late-September section covers what moved and why.

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.

Late September: what landed after we published

The back half of the month was busier than the front, and the biggest item of September arrived in it.

Any browser agent can now check out on your store

What changed (September 28). Shopify extended WebMCP to checkout.¹⁵ WebMCP is the set of tools every Liquid storefront has exposed to browser-based agents since August 5: search the catalog, edit the cart, open checkout. From September 28 there are four more: navigate_to_storefront, get_checkout, update_checkout and complete_checkout. An agent running in the shopper’s browser can read the checkout that is open in the tab, change the shipping address or delivery option, and submit the order once the shopper confirms. It cannot change line items, and it cannot enter new card details. Payment runs only through a saved Shop Pay card or an existing Shop Pay approval. The tools live inside the checkout page and use the same state as the checkout the shopper sees, so there is no new API, nothing to install, and no setting. It is on for every eligible store.

The same day, Instinct, a texting-based personal agent whose founder says 35% of its users shop with it, announced that its users can discover products across Shopify stores and check out with Shop Pay in one conversation.¹⁵ A week earlier, Muse had got the same path.

Why merchants care. This is the line Shopify has been drawing since December, and it has now been drawn all the way to the order. An agent that reaches your store in the shopper’s browser no longer stops at the cart. The guardrails are real: the shopper has to approve the order and total, and if the total changes the agent has to ask again. But the practical consequences land on the merchant. Your delivery options, address rules and discount logic are now being driven by software that reads field labels, not by a person reading your page. Shopify’s own guidance to agent builders is to treat merchant and third-party text in the checkout as data rather than instructions, because it may contain prompt-injection attempts, which tells you how early this is. And as of the end of September, Shopify’s documentation does not say whether a merchant can switch off individual checkout tools.¹⁵

The strategic contrast is the point. Amazon barred Muse from its site on September 20. Shopify made every one of its stores purchasable by an agent eight days later and called it a feature.

What to do.

1. Run a test order through an agent yourself. Any browser-based agent that supports WebMCP will do. Watch which address and delivery option it picks, whether your discount logic holds, and where the order appears in your reports.
2. Check Shop Pay is enabled and that the saved-card experience works, because that is the only payment path an agent can use.
3. Re-read your delivery option names, checkout copy and product data as instructions a machine will follow. An ambiguous delivery name or a missing variant attribute is now a checkout failure, not just an SEO problem. The catalog data audit is the fastest way to see what an agent sees.

Your conversion rate changed on September 21, your traffic did not

What changed (September 21 to 23). Shopify changed how Analytics measures sessions, rolling out over three days.¹⁶ Three things moved. Sessions are now based on continued activity instead of ending at midnight UTC, so a visitor browsing across midnight is one session rather than two. Some sessions without a pageview now count, such as a customer who goes straight to checkout from a cart link. And identified bot sessions are filtered out of session-based reports by default, with a Human or bot session filter where you want them back. Nine metrics are affected: sessions, conversion rate, add-to-cart rate, reached checkout rate, checkout conversion rate, bounce rate, pageviews per session, online store visitors and searches. Orders, sales, customer counts and average order value are untouched.

Why merchants care. Conversion rate is orders divided by sessions, and the denominator just changed. A store with a lot of bot traffic saw sessions fall and conversion rate rise; a store with a lot of cart-link checkouts saw the opposite. Neither is a change in the business. The trap is comparison: Shopify says historical data is not reprocessed, but it is displayed differently once bots are filtered, and bot classification only exists for sessions from October 7, 2025 onwards, so even the same filter does not make before and after directly comparable.¹⁶ Any dashboard, agency report or bonus target that quotes a Shopify conversion rate has a step change in it dated September 21.

What to do. Annotate September 21 in every report that uses sessions, and compare periods on either side of it separately for a few weeks. If you report conversion rate to anyone, tell them now rather than in the November review. And keep the two September measurement stories apart: the August 26 upgrade shows up as a gap between Shopify and your ad platforms; this one shows up inside Shopify’s own numbers with sales unchanged.

The admin has a new look

What changed (September 15, rolling out gradually). Shopify redesigned the admin: new colour, type, spacing and icons, with search, notifications and the store picker moved into a side navigation that collapses to give the page more room.¹⁷ Sidekick moved out of its side panel into a floating chat at the bottom of every page, with short questions answered in place and longer tasks expanding into the panel. Apps built on Admin UI extensions and App Home UI extensions pick up the new styling automatically; everything else gets a Polaris 2.0 release candidate, published September 24, and Built for Shopify apps have until May 1, 2027 to match the new look.¹⁷

Why merchants care. It is the screen you spend your working day in, and it moved. The merchant forum’s reaction was the usual mix, with the loudest thread titled “New UI is really bad” listing the dark sidebar, the empty space on the Orders page, extra clicks and Sidekick taking permanent room, and asking for a way back.¹⁷ There is none documented, and no staff reply on the thread at the time of writing. The design intent is clear enough: Sidekick is now on every page because Shopify wants it to be the first thing you reach for.

What to do. Nothing, other than expect your apps to look slightly out of place for a while. If an app’s embedded pages look broken rather than merely old, that is its developer’s Polaris migration, not your store.

Return windows can now differ by product

What changed (September 29). Return window overrides let you set a different return period, by market, for specific collections, products or variants.¹⁸ If an item matches more than one override, the shortest window applies. Final-sale items stay non-returnable regardless. Anything not covered by an override falls back to the market’s window, then to your default.

Why merchants care. Seasonal stock, clearance lines and hygiene products have always needed a different policy from the rest of the catalog, and until now the only native tool was the all-or-nothing final-sale flag. This arrives in time for BFCM, which is when you most want a 14-day window on the doorbusters and 90 days on everything else.

What to do. Settings > Policies > Return and cancellation rules, pick the market, then add overrides by collection. Check the self-serve returns page afterwards, because customers see the window that applies to each item.

Tax on US return shipping fees, from October 23

What changed (announced September 25). For stores on Shopify Tax or Tax Platform, return shipping fees on US orders will be taxed like any other shipping charge from October 23.¹⁹ The estimated tax appears when you create the return, the final amount is recorded when you process it, and it flows into your tax reports. Existing shipping tax settings carry over: if shipping is untaxed in a state, return shipping stays untaxed there. Restocking fees, handling fees and non-US returns are out of scope.

Why merchants care. If you have been under-collecting, this fixes it without you doing anything. If you built a workaround to collect or reconcile that tax yourself, it will now double count.

What to do. Find any manual return-tax process in your accounting and retire it before October 23. Otherwise nothing.

Money and reporting: Payouts, installments, duties, and metafields in Analytics

Payouts page (September 16). The redesigned Payouts page lists payouts on the left with the selected one’s breakdown beside it, groups paid and pending by date, and makes failed payouts easier to trace.²⁰ It rolls out gradually on web and mobile. The first merchant thread about it complains that grouping by day hides individual deposits and slows bank reconciliation, because banks post them one at a time.²⁰ If you reconcile against bank lines, check the new view before month-end close.

Shop Pay Installments across business entities (September 22). Stores operating multiple business entities in the US, Canada or the UK can now turn on Shop Pay Installments for each of them, not just the primary one, from the Shopify Payments settings.²⁰

Shipping and duty costs in profit reports (September 23). Profitability data now includes duties and other shipping costs when both apply to the same order, and handles mixed currencies better.²⁰ Expect the “Average profit margin by market” and “Profit margin by order” reports to move for cross-border orders. Together with the September 21 session change, this is the second analytics step change in the same week; date both.

Category and metaobject fields in Analytics (September 28). The attributes you set when categorizing a product, such as colour, material, fit, fabric or size, now appear in Analytics as dimensions and filters, and so do fields from metaobjects referenced by a metafield on a product, variant, customer or order, such as a designer’s country, a warranty term or a loyalty tier.²⁰ They work in Reports, Explore and the query editor. This is the first time a sales report can be grouped by colour without an export, and it is only as good as your categorization: if the catalog is half-categorized, half the report is blank. Categorizing a large catalog by hand is exactly the job the Fudge store editor does from a prompt.

Retail: POS 11.16

Two things landed for stores that sell in person, both on POS Pro and both in POS 11.16 on September 28.²¹

Local delivery orders from POS. Staff can add items to the cart, choose local delivery at checkout and create the order on the same delivery setup you manage in admin, instead of the notes-and-tags workaround. It needs local delivery configured for the location and two permissions: Create shipping and delivery orders, and Fulfill shipping, pickup, and delivery orders.

Scheduled stock counts. Counts created in admin for a location can now be completed in POS by staff with the inventory permission, scanning or keying quantities, then submitted to admin for review and approval with discrepancies shown.

What to do. Update to 11.16, grant the permissions to floor roles, and if you run pre-BFCM counts, schedule them from admin so the results land in one place.

Also in late September, in brief

• Shop moved to shop.com (September 29). Shopify bought the domain from Market America, announced September 28, and shop.app links redirect.²² Update bios and ads when convenient.
• Two short outages. Third-party monitors logged admin pages going blank for merchants worldwide from about 14:15 to 14:31 UTC on September 25, with no incident posted on Shopify’s status page, and a single-region outage in Australia of just under three hours from 01:44 UTC on September 26.²³ No merchant action.
• The EU legal guarantee notice became mandatory on September 27. Not a Shopify change, but it hit Shopify stores: every seller of physical goods to EU consumers must now show the harmonised notice before the order is placed, and the forum thread on it is about non-Plus plans not being able to put it in checkout. See what merchants are talking about below.
• Rollouts got a clearer setup (September 22). Shopify’s native launch and A/B testing tool now asks whether you are planning a launch, a timed event or an experiment, lets one rollout change theme, checkout and customer account pages together, shows the traffic split, and flags conflicting settings before you schedule. Worth a look before you stage BFCM changes; our conversion testing guide covers how to size a test.
• A new Dev Dashboard (September 25): apps, client stores, development stores and collaborator stores in one place, with revenue, installs and API health per app, and logs kept for 30 days.²⁴ The merchant-side version landed the same day: if you run custom apps, the Developer Dashboard now shows their API request volume, error rates, webhook health and a filterable log of every request, which is the first time a store owner could see a custom app misbehaving before it broke something.
• Polaris 2.0 release candidate (September 24) aligns embedded app pages with the new admin; Built for Shopify apps have until May 1, 2027.¹⁷
• 2026-10 went to release candidate on September 26 and stable on October 1.
• Token migration got safer (September 29): an app migrating to expiring access tokens without a user session can retry a lost exchange with the original token for up to seven days and receive the same token pair, which closes the orphaned-install failure developers were reporting mid-month.²⁴
• Packed product dimensions can be managed through the Admin GraphQL API, and existing app subscriptions can be moved to Shopify App Pricing (both September 29).
• App intents reached discount apps (September 30), and Sidekick can invoke app intents from extensions that declare no tools (September 28).
• Flow extensions got fewer breaking changes and auto-updating runtime URLs (September 25), and lifecycle callbacks accept relative paths (September 29).
• Inventory shipments accept a canceled reason on receive (September 17), market hierarchies are queryable, and Shopify Payments exposes per-fee details and a currency-conversion transaction type (September 23).
• The Customer Account API drops lastIncompleteCheckout and the Checkout subtree in 2026-10 (September 25), with no replacement.
• AI Toolkit skills were consolidated into a single shopify skill (September 25); the old per-area skills are deprecated.²⁴
• UI extensions over the 64 KB bundle limit can request an exception through a new form, with the minified bundle and build metafile attached.

What merchants are talking about

Four themes dominated the community this month:

• The tracking reconciliation problem is the conversation, and it got a second layer. The August 26 aftermath threads stayed the most active on the merchant forum, with the tone shifted from “how do I migrate” to “which of these three numbers is real”, and none has a reply from Shopify staff. Then the September 21 session change moved conversion rates inside Shopify itself, so the last week of the month added “did my conversion rate fall or did Shopify change the maths” to the same threads.
• Nobody can find the agent orders yet, and now there will be more of them. 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. With Shop Pay inside Muse and WebMCP reaching checkout, the practical consensus held: fix structured product data and legal pages first, because exclusions are silent and there is no admin warning.
• The new admin and the new Payouts page both got the “give us the old one back” thread. The admin thread lists fonts, empty space, the dark sidebar, extra clicks and Sidekick’s permanent footprint; the Payouts thread is narrower and more practical, because grouping deposits by day broke a bank reconciliation routine.¹⁷²⁰ Neither had a staff reply at the time of writing, and there is no documented way to revert either.
• EU sellers on non-Plus plans could not put a mandatory notice in checkout. From September 27, every seller of physical goods to EU consumers must display the harmonised legal guarantee notice prominently before the order is placed, under Directive (EU) 2024/825.²⁶ Pre-purchase checkout extensions are Plus-only, so the most-replied thread asks Shopify for a native block or an exception for regulatory notices on Basic, Grow and Advanced, and shares the interim answer: the notice on product pages and in the cart, plus a visible link in the header.²⁶

Developers had a quieter fortnight than the first half. The Partner Dashboard earnings sync issue from early September was resolved on the 9th, the Dev Dashboard that replaces much of it shipped on the 25th, and the expiring-token migration threads kept running, now with a seven-day retry window that removes the orphaned-install failure.²⁷²⁴ 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, CA, MX
2	Run a browser agent through a test order on checkout	Low	Now	Everyone
3	Reconcile Meta and Google against Shopify since Aug 26	Medium	Now	Every non-Plus store running ads
4	Re-baseline conversion rate from Sep 21	Low	Now	Anyone reporting a conversion rate
5	Confirm app vendors cleared the Oct 1 cutoffs	Low	Now, Oct 1 past	Everyone
6	Audit product data for agent readability	Medium	Now	Everyone
7	Set return window overrides on seasonal stock	Low	Before BFCM	Anyone with a returns policy
8	Retire manual return-shipping tax workarounds	Low	Before Oct 23	US stores on Shopify Tax
9	Show the EU legal guarantee notice before the order	Low	Now, Sep 27 past	Sellers to EU consumers
10	Add supplier and channel barcodes to variants	Low	Soon	Multi-supplier, marketplace sellers
11	Set up multi-currency payouts	Low	Soon	AU and FR on Advanced or Plus
12	Update POS to 11.16 and grant the new permissions	Low	Soon	Retail
13	Turn on WhatsApp consent at checkout	Low	Soon	Stores in WhatsApp-first markets

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. Muse now pays through Shop Pay there.
• Run a browser agent through a test order on your own checkout and watch where it lands in your reports.
• 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.
• Annotate September 21 in every report that uses sessions, and warn whoever reads your conversion rate.
• If an app vendor never answered the script tag question, check that their storefront widget still updates now that October 1 has passed.
• Set return window overrides on seasonal and clearance collections before BFCM.

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.
• Meta’s direct checkout now covers customers in the US, Canada and Mexico; your other markets are unaffected.
• Selling physical goods to EU consumers: show the harmonised legal guarantee notice before the order is placed. On a non-Plus plan that means product pages, the cart and a visible header link until Shopify offers a checkout block.
• Expect the “Average profit margin by market” report to move now that duties and shipping costs on the same order are both counted.

If you run retail or POS:

• Update to POS 11.16, grant View abandoned checkouts, Create shipping and delivery orders, and the inventory permission to the right roles, and tell staff what is new.
• 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 if you have not already: fields_changed is an object with added, updated and removed buckets, delete events no longer cascade, and parent trigger paths need an explicit .* wildcard.²⁸
• Any purchase.discounts-allocator.run target still in your app has failed shopify app deploy since September 29.
• Script tag writes have failed since October 1; anything not yet on app embed blocks or web pixels is frozen until March 1, 2027, when it stops. Checkout and customer-account extensions must be on API 2025-10 or later to ship any update at all.
• Read barcodes instead of barcode, and drop Customer.lastIncompleteCheckout, when you move to 2026-10.
• If you are migrating to expiring tokens without a user session, retry a lost exchange with the original token within seven days rather than forcing a reinstall.
• Plan the Polaris 2.0 migration for App Home; Built for Shopify apps have until May 1, 2027.

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 Dev Dashboard replaced most of what you used the Partner Dashboard for. The new Dev Dashboard (September 25) puts every app in one sortable list with revenue, installs, distribution status and alerts, merges client, development and collaborator stores into one index, keeps logs for 30 days, and surfaces errors, warnings and deprecated API calls per app.²⁴ Protected-scope requests still go through the Partner Dashboard for now.

Polaris 2.0 is the admin’s new look for your app. The release candidate (September 24) carries the styles that align App Home with the redesigned admin; Admin UI extensions picked them up automatically on September 15. Built for Shopify apps have until May 1, 2027 to update.¹⁷

Token migration is more forgiving. From September 29, an app migrating a non-expiring offline token to an expiring one without a user session can retry a lost exchange with the original token for up to seven days and get the same access and refresh token pair back.²⁴ That is the fix for the orphaned-install failure developers were reporting in mid-September, and it needs no change to existing flows.

The deadline digest, in date order: September 16 (Events contract changes, passed), September 29 (Discounts Allocator removal, passed), October 1 (API 2026-10 released; script tag create and update calls fail; 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; passed), October 15 (the card deposit endpoint requires a Shopify-issued mTLS certificate), October 16 (API version 2025-10 retired), October 23 (tax calculated on US return shipping fees), 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), May 1, 2027 (Built for Shopify apps must match the new admin look in App Home).

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 second half of the month made the thesis explicit. Amazon barred Muse on September 20; Shopify put Shop Pay inside it on September 21 and opened checkout to every browser agent on September 28. One company decided agents are a threat to its relationship with the customer, the other decided they are a channel, and the market priced the difference the next morning. For a merchant the implication is narrower than the headlines: the order can now be placed by software reading your checkout, and the levers you hold are product data, delivery rules and Shop Pay.

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 at the end of September is unglamorous: check a toggle, reconcile three numbers and re-baseline a fourth, run one test order through an agent, and fix the product data an agent is already reading. October has already started with its own list.

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; by October 6 the page listed stores selling to Canada and Mexico as eligible alongside the United States. Check the page before planning around it. ↩ ↩² ↩³

4. Tobi Lütke on X, September 21, 2026, and PYMNTS: Shopify brings Shop Pay checkout to Meta’s Muse AI agent, September 22, 2026. Amazon’s decision to bar Muse on September 20 and the share price move on September 22 are from the same coverage and from 24/7 Wall St; the stock figure is the closing move, not a Shopify statement. ↩ ↩²

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

6. 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. ↩

7. 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. ↩

8. 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. ↩

9. 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. ↩

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

11. 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. ↩ ↩²

12. 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. ↩

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

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

15. TechCrunch: Shopify opens checkout to browser-based AI agents, September 28, 2026, and the WebMCP checkout entry in the Shopify developer changelog, September 28, 2026. Tool names, the Shop Pay-only payment path, the buyer-confirmation requirement and the prompt-injection guidance are from Shopify’s developer documentation as read on September 29; the documentation did not state whether individual checkout tools can be disabled per store. Instinct’s announcement is from Noah Shinn on X, September 28, 2026. ↩ ↩² ↩³

16. Shopify Help Center: Session measurement update and Shopify changelog: Shopify Analytics session measurement improvements, September 21, 2026. The nine affected metrics, the October 7, 2025 bot-classification boundary and the note that historical data is not reprocessed are Shopify’s. ↩ ↩²

17. Shopify changelog: A new look for the Shopify admin, September 15, 2026; Shopify developer changelog: Prepare your app for the Shopify admin’s new look, September 15, 2026; Polaris 2.0 release candidate, September 24, 2026, which states the May 1, 2027 Built for Shopify deadline; and Shopify Community: New UI is really bad, September 2026, which had no staff reply as of October 6. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶

18. Shopify changelog: Return window overrides now available, September 29, 2026. ↩

19. Shopify changelog: Tax is now calculated on return shipping fees, September 25, 2026, and the matching community announcement. ↩

20. Shopify changelog: Payouts page redesign, September 16, 2026; Shopify Community: New Payouts view hides individual deposits; Shop Pay Installments can now be enabled on multiple business entities, September 22, 2026; Improved shipping and duty data in Analytics, September 23, 2026; and Category metafields are now available in Analytics and Use metaobject fields in Analytics reports, both September 28, 2026. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶

21. Shopify changelog: Local delivery orders in Shopify POS and Run stock counts in POS, both September 28, 2026. Both features require POS Pro. ↩

22. Shopify changelog: Shop is now at shop.com, September 29, 2026, and TheDomains: Shopify acquires the domain name Shop.com, September 29, 2026. The price was not disclosed. ↩

23. StatusGator: Shopify outage history. The September 25 admin incident (about 14:15 to 14:31 UTC) and the September 26 Australia incident (01:44 to 04:36 UTC) are third-party monitor records; Shopify did not post a status page incident for the September 25 event. Treat the timings as approximate. ↩

24. Shopify developer blog: The new Dev Dashboard, September 25, 2026; More resilient token exchanges when migrating tokens without a user session, September 29, 2026; and AI Toolkit skills have been consolidated, September 25, 2026. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶

25. 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. ↩

26. Your Europe: The EU legal guarantee notice and GARAN label, which covers Directive (EU) 2024/825 and Implementing Regulation (EU) 2025/1960, applicable from September 27, 2026, and Shopify Community: EU legal guarantee notice, checkout support for non-Plus plans. This is a summary, not legal advice. ↩ ↩²

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

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