Type: Developer Guide / Fix · Stage: Optimize · Topic: Carrier Services / Shipping Rates / API 2026-10
On this page
Quick answer
In Shopify Admin API 2026-10, creating an active carrier service no longer automatically adds its rates to the shop’s General shipping profile. Your app can receive a valid carrier-service ID and active: true while checkout shows no rate from that service. Registration and shipping-rate configuration are now separate steps.
After creating the service, explicitly add its carrier/app-calculated rate to the applicable shipping configuration. Shopify recommends guiding merchants through the shipping editor; an app can also configure rates programmatically when it uses the APIs appropriate to the shop’s shipping model.
What changed on October 1, 2026
Shopify announced the change on June 26, 2026. Earlier supported API versions automatically attached newly created active carrier services to eligible zones in the General shipping profile. From 2026-10, both GraphQL carrierServiceCreate and REST carrier-service creation only register the service. Neither automatically adds its rates to the General profile.
That explains a common installation mystery: the same shipping app works on an older integration but shows no rate on a newly connected store. The create request succeeded; the profile setup did not happen.
Separate service registration from checkout visibility
The GraphQL mutation requires write_shipping and registers a callback URL that Shopify can contact for rate calculations. This example is the registration step, not a guarantee that checkout will display rates:
mutation RegisterRates($input: DeliveryCarrierServiceCreateInput!) {
carrierServiceCreate(input: $input) {
carrierService {
id
name
callbackUrl
active
supportsServiceDiscovery
}
userErrors { field message }
}
}
Example variables:
{
"input": {
"name": "Warehouse Rates",
"callbackUrl": "https://rates.example.com/shopify",
"active": true,
"supportsServiceDiscovery": true
}
}
Save the returned service ID and inspect userErrors. Confirm the endpoint can handle Shopify’s rate-request payload and return valid rates. Then separately confirm the service is selected as a rate source for the products and destination being tested.
Make rates visible in the correct shipping configuration
- Identify the shipping model. Shopify is moving merchant-owned shipping configuration toward Markets. Do not assume the legacy delivery-profile APIs describe every shop’s live rates.
- Find the applicable configuration. In Shopify admin, inspect Settings → Shipping and delivery, then the relevant profile or market, shipping zone, fulfillment origin, and product assignment.
- Add the carrier/app-calculated rate. Use the shipping editor to select the installed carrier service as a rate provider. The editor’s labels can differ by shipping model.
- If configuring through an API, detect the model first. The 2026-10 change allows explicit programmatic rate configuration, but legacy merchant-owned delivery-profile writes may be stale or ineffective on market-driven shops.
- Test an actual checkout. A registered callback alone does not prove Shopify requested rates for the cart.
Debug the missing rate in order
| Symptom | First check |
|---|---|
| Service exists, but callback gets no requests | Is the service selected in the applicable shipping configuration? Does the address qualify? |
| Callback is called, but no rate appears | Response format, currency, rate amount, timeout, and logs. |
| Works for one destination only | Market, zone, profile, origin, and product eligibility. |
| Worked on 2026-07, fails on 2026-10 | Installation logic that relied on automatic General-profile attachment. |
Keep registration idempotent. Recreating the service on every retry can produce duplicate providers. Store its ID and distinguish a configuration retry from a registration retry.
Common misunderstanding
“active: true means rates are live.” It means the carrier service is active, not that checkout is configured to request its rates. “A successful create call adds rates everywhere.” Not in 2026-10. “The old deliveryProfileUpdate mutation always fixes it.” Not necessarily on market-driven shipping stores.
How to test this
- On a development store using API 2026-10, create one service and verify its ID, active flag, and callback URL.
- Before adding it to shipping settings, try a relevant checkout and inspect whether the callback is invoked.
- Add the rate to the applicable shipping configuration, then retry the same cart and destination.
- Test two valid destinations, one excluded zone, a product in a different profile, and a mixed cart where applicable.
- Simulate an empty response and temporary callback failure in a controlled environment; inspect logs and checkout behavior.
- Repeat setup and confirm it does not create duplicate services or rates.
Sources and further reading
- Shopify changelog: carrier service change (June 26, 2026)
- Shopify: carrierServiceCreate
- Shopify: market-driven shipping and legacy delivery profiles
- Shopify API 2026-10 release notes
Documentation checked October 21, 2026.

