2026-10 and later, carrierServiceCreate registers the carrier service but does not add its rates to the General shipping profile. A successful API response is not proof that checkout can offer the service. Add its carrier-calculated rate to the appropriate shipping profile and zone, then test checkout with a real qualifying address.On this page
Why an old integration suddenly appears broken
Shopify announced this breaking change June 26, 2026, for the October 1 API release. Older versions automatically attached newly created active carrier services to eligible General profile zones. That convenience also made carrier setup unpredictable: an app install or update could change a merchant’s available shipping rates. Newer versions separate registration from rate configuration.
This affects GraphQL carrierServiceCreate and REST POST /admin/api/{version}/carrier_services.json. Shopify staff also confirmed in a July 2026 developer-forum discussion that carrierServiceUpdate no longer re-adds a removed service on 2026-10, addressing an older surprising behavior.
Diagnose the missing rate in the right order
First check the API version actually used by the app, not just the app’s latest deployment version. Confirm the carrier service exists and is active. Then inspect the merchant’s shipping profile and the shipping zone matching the test destination. Is the app-provided carrier-calculated rate explicitly configured there? If not, Shopify may never request the app’s callback, so debugging callback JSON or response latency will not help.
Next confirm that the products in the cart belong to the profile and that the destination qualifies for its zone. Test the shipping setup in the store’s admin rather than assuming a rate in one market or zone is available everywhere.
Make rate attachment an explicit onboarding step
After registering the carrier service, either guide the merchant to add the carrier-calculated rate in the appropriate shipping profile in Shopify admin (Shopify’s recommended route), or use supported delivery-profile APIs when your app owns that configuration. Do not silently create rates in every zone: shipping rules are a merchant decision and may vary by product and destination.
For existing stores, migration should be idempotent. Detect the current rate setup before adding anything. Avoid duplicate rates when an app reconnects, a callback URL changes, or onboarding is repeated. Keep a clear merchant-facing status: service registered, shipping profile configured, and checkout verified are three different milestones.
Watch the Markets shipping migration too
Shopify is also transitioning merchant-owned shipping configuration toward Markets. The carrier service is the rate provider; the merchant’s shipping configuration determines where that rate is offered. Do not treat an API-created service as a universal rate. Validate against the store’s current shipping model and use the supported admin setup for that store.
How to test this
- On a development store using API 2026-10, create an active carrier service and confirm its ID is returned.
- Before adding a rate, use a qualifying cart and address to observe that the service is not automatically available.
- Add its carrier-calculated rate to the correct profile and zone, then retry the same cart and address.
- Confirm the callback is requested and that the returned rates appear; test a nonqualifying zone and a product in another profile.
- Re-run onboarding and update the service; ensure neither operation creates duplicate rate definitions.

