On this page
Why this happens
Earlier API versions could automatically attach newly registered carrier services to the General shipping profile. Shopify removed that side effect for 2026-10. A successful API response now proves registration, not checkout availability.
How to fix it
- Check the API version used by the installer and confirm the carrier service is active, with the expected HTTPS callback URL.
- In Settings → Shipping and delivery, inspect the shipping profile containing the test product, not just General.
- Within the destination shipping zone, add the registered app- or carrier-calculated rate and save. For programmatic configuration, use delivery profile APIs with targeted updates.
- Attempt checkout with a product in that profile and a destination in the configured zone. Inspect the callback logs and returned rates.
- Repeat with products assigned to custom profiles and verify fallback rates are not concealing failures.
Production example
A carrier can be registered successfully while Shopify sends zero callback requests. Before debugging server response times, verify that the product’s shipping zone actually includes the carrier-calculated method.
How to test this
- Register a test service using 2026-10 and confirm the mutation has no userErrors.
- Inspect the profile before adding a method; confirm the service was not attached automatically.
- Add the method to the correct zone and test checkout with a matching product and address.
- Confirm a callback arrives and the expected rate is shown; repeat for a custom profile.
- Simulate a callback error in a safe environment and confirm backup-rate behavior.

