
What Shopify Spring '26 means for a Dutch online store
On 17 June Shopify released Spring '26 with more than 150 updates, most of them about selling through AI. What you notice of it in the Netherlands, what you can leave alone, and what has to happen to apps before 1 January.
Mostly AI, and mostly for the US
Spring '26 came out on 17 June, with more than 150 updates. Most of it is about selling through AI. Shopify puts your products into ChatGPT, Microsoft Copilot, Google AI Mode, Gemini and Meta through Shopify Catalog, and in some of those the customer can check out right away. For stores that qualify, this is on by default.
For a Dutch online store, that is a letdown. ChatGPT and Copilot require your store to sell to customers in the United States. Only customers in the US see the checkout in Copilot. If you only sell in the Netherlands or the EU, you will notice little of this for now.
The same goes for more of this edition. The new mobile card reader from Verifone can only be ordered in the US and Canada, and payouts in several currencies are available in the US, Hong Kong and Singapore.
What you notice in your checkout
What you do notice in the Netherlands is mostly in the checkout.
- A shorter checkout. Delivery options are easier to compare, the pay button stands out more, and on a phone your customer scrolls less.
- Payment methods in order of likelihood. With Shopify Payments, Shopify puts the payment methods that customer is most likely to use at the top of each checkout.
- VAT numbers checked. With Shopify Tax in the EU and the UK, you ask a business buyer for their VAT number and validate it in the checkout.
- Your brand, set once. You set your logo, colours and typeface once. They then apply to the checkout, the customer account and the sign-in page.
- A minimum or maximum per order. With Checkout Blocks this now works on every plan. If the subtotal falls outside it, the customer cannot check out.
B2B without Plus
Selling to businesses with Shopify B2B used to be mostly a Shopify Plus thing. Since this edition, company profiles, volume pricing and up to three B2B catalogues come at no extra cost on Basic, Grow and Advanced. Not on Starter and Retail. Exactly which B2B features you get still depends on your plan.
Developers get something too. Shopify Functions can now read the billing address and the purchase order number when validating the cart and checkout. That lets you stop, for example, a business order without a purchase order number.
Test first, then go live
With Rollouts you put a new theme, a new checkout configuration or a new customer accounts setup live at a chosen time, or first as an A/B test next to the current version. A theme change no longer has to go live for everyone at once. You first see whether the new version does better.
Discounts get more room as well. You can stack several discounts on the same product, for example a percentage and a fixed amount. And you can make a discount apply only in a particular market.
What changes for apps
In the Edition this is a single line, but Shopify has since attached a firm date to it. Public apps, the apps in the Shopify App Store, must use expiring access tokens before 1 January 2027. An app that does not is removed from the App Store on that day and can no longer be newly installed. From 15 January, stores with such an app see a warning in their admin. From 1 April 2027, the Admin API refuses the old tokens with a 403. Custom apps, built for a single store, are not affected.
An expiring token is valid for one hour. After that you request a new one with a refresh token, and that refresh token is valid for 90 days. Apps built on a Shopify template do this on their own. We build our apps in Laravel, without that template. There you write the refresh yourself.
$token = Http::asForm()->post("https://{$shop->domain}/admin/oauth/access_token", [
'client_id' => config('services.shopify.client_id'),
'client_secret' => config('services.shopify.client_secret'),
'grant_type' => 'refresh_token',
'refresh_token' => $shop->refresh_token,
])->throw()->json();
// Every refresh also returns a new refresh token. If you don't keep it, the old one works for 30 days at most.
$shop->update([
'access_token' => $token['access_token'],
'refresh_token' => $token['refresh_token'],
'token_expires_at' => now()->addSeconds($token['expires_in']),
]);Two things from the documentation that are easy to miss. Refresh one token per store at a time: two workers refreshing the same store at once can invalidate each other's token. In Laravel you do that with a unique job per store. And a 401 on refresh is final. Stop retrying, and have the app authorised again as soon as the store opens it.
Webhooks get more settings too. You can have them fire only when certain fields change, and decide with your own GraphQL query which data they carry. How we process webhooks is in the article under Read more.
Our position
We only switch on a new Shopify feature once we know which problem it solves for you.Remco, CTO at Brandbrand
What you can do now
- Check which AI channels are on. You find them under your sales channels, in Agentic. If you do not sell to the US, it does little for now. Do fill in your terms, privacy policy and refund policy: Copilot requires them.
- If you sell to businesses, look at B2B. On Basic, Grow and Advanced you no longer need Plus for company profiles, volume pricing and a few catalogues.
- Test your next theme. Put a new version live through Rollouts as an A/B test first, rather than for everyone at once.
- Ask how your apps are doing. If your store runs a public app from a smaller developer, ask whether it uses expiring tokens before 1 January. If it still does not by 1 April, it gets no more data from Shopify.




