Shopify 2026-10: carrier services no longer automatic

A silent but critical change

Starting with version 2026-10 of Shopify's GraphQL Admin API, Shopify has introduced a change that directly affects anyone who develops or manages shipping integrations. Registering a carrier service no longer automatically adds it to the store's General shipping profile.

This is a behavioral change, not a visible error: no warning messages appear, and no error codes are returned. The rates calculated by the carrier simply stop showing up at checkout until they are explicitly linked to a shipping profile.

How it used to work

In API versions prior to 2026-10, the flow was straightforward:

• The carrier service was created via API
• Rates were automatically propagated to the shipping zones of the General profile
• The checkout immediately displayed the calculated shipping options

For years, this automatic behavior simplified the development of shipping apps and custom integrations, reducing the number of steps needed to bring a working solution into production.

What changes with version 2026-10

With the new version, the flow stops halfway through. The carrier service is created correctly, but it is not linked to any shipping profile. In practice, this means shipping rates are not shown to the customer at checkout, with no system warning of any issue.

This type of breaking change is particularly tricky because:

• It doesn't generate errors during the API call
• It doesn't block the carrier service creation process
• It only becomes apparent downstream, when the merchant or end customer notices the missing shipping options

Who is affected

The impact specifically concerns:

• Shipping apps that use the carrierServiceCreate mutation via GraphQL
• REST integrations that make POST /admin/api/{version}/carrier_services.json calls
• Custom solutions implementing dynamically calculated carrier rate logic

Any system relying on the previous automatic behavior needs to be reviewed before migrating.

How to prepare for the migration

Before updating integrations to version 2026-10, a targeted audit is necessary:

• Review every integration that creates carrier services, whether via GraphQL or REST
• After creating the carrier service, explicitly add the rates to the correct shipping profile
• Use the shipping profile APIs to manage this association programmatically, or guide the merchant through manual completion via Shopify Admin
• Test the entire end-to-end flow, from service creation through to the actual display of rates at checkout

It's not enough to check that the API call returns a successful response: testing must include visual confirmation of the rates in the store's checkout.

Timeline and previous versions

API versions prior to 2026-10 retain the automatic behavior until their natural sunset. This means existing integrations will keep working as before until the migration is carried out, but the window to act should be used now, before the migration becomes mandatory.

Why you should act now

For anyone managing Shopify Plus stores with real-time shipping rate calculations, this kind of audit is not optional. An integration that works correctly today can stop displaying shipping rates after the migration, with no technical warning sign, directly impacting conversions and the checkout experience.

Those who rely on external developers to manage the technical side of their store can check the terms for Shopify developer pricing to plan a shipping integration audit ahead of the migration to 2026-10.

Planning ahead to verify every carrier service, run end-to-end checkout testing, and update shipping profile association logic is the only way to avoid unexpected disruptions in production.