Has there been any changes in the last few months regarding carrierServiceUpdate?
Recently, running this mutation will re-add the app to the general shipping profile, it didn’t appear to exhibit this behaviour last year, and there have been no updates to the documentation suggesting so either.
Hey @Min_Liu! You’re right that carrierServiceUpdate re-adds your app to the General shipping profile. I reproduced this on a test store (API version 2026-04). I confirmed it’s not specific to sending active: true and a name-only or callbackUrl-only update triggers it too, as long as the carrier service is active. Each re-add creates a fresh method definition with a new ID rather than restoring the merchant’s previous configuration.
Starting with API version 2026-10, carrier services will no longer be automatically added to the default shipping profile. I verified this on the unstable API: after removing a carrier service from the General profile and running carrierServiceUpdate, it was not re-added. From 2026-10, your app will need to explicitly place the carrier-calculated rate in a shipping profile, either by directing the merchant to add it in the Shopify admin or by using the delivery profile APIs.
The changelog is written in terms of carrierServiceCreate, but the change also covers carrierServiceUpdate and the re-adding case, which is your exact scenario.
On current supported versions (2026-07 and earlier), there’s no workaround that keeps the service usable. active: false avoids the re-add but removes the service from checkout. Only the app that created the carrier service can update it, so delegating to another app isn’t an option either - I hope this clears things up for you!
Hi Donal,
Thanks for confirming, yes i re-ran this with previous API versions as well and it exhibits the same behaviour too, however when we ran this in Dec last year, i could swear that it didn’t do this. I’m thinking perhaps something has changed unexpectedly that wasn’t documented?