Shopify's quarterly Admin API versions usually pass without merchants noticing, because most breaking changes throw an error somewhere a developer eventually sees. Version 2026-10, which became the stable release on October 1, has one change that does the opposite: it removes a step silently, so a store can lose shipping rates at checkout with nothing in any log to say why. Four more changes in the same release touch order taxes, headless checkout, discounts and inventory. None of them require you to do anything if your store never calls the Admin API directly — but if an app, script or custom integration does, this is the week to check it.
Shopify's Admin API 2026-10 went stable on October 1, 2026. The change most likely to cost you a sale: creating a carrier service no longer automatically adds its rates to the store's General shipping profile, so checkout can show zero shipping options with no error anywhere. Four more breaking changes affect order tax recalculation, a removed headless-checkout field, the legacy PriceRule discount type, and an inventory error code. If your store runs entirely on Shopify's own checkout, theme and unmodified apps, you are not at risk today — but any custom app, freight integration or discount tool that gets updated to target 2026-10 inherits all five changes the moment it does.
What actually changed on October 1
Shopify ships a new Admin API version every quarter and keeps the previous three supported, so most merchants never read a release note. 2026-10 is worth reading because of what it removes rather than what it adds: 28 breaking changes in total, including 23 outright removals, spread across shipping, orders, customer accounts, discounts and inventory. Five of them have a realistic chance of affecting a working store.
| Change | What breaks | Who is affected |
|---|---|---|
| Carrier service auto-add removed | A newly created carrier service no longer appears in the General shipping profile, so checkout can show no rates from it, with no error logged | Freight apps, multi-carrier shipping apps, custom checkout-rate integrations |
| Order address edits recalculate tax | Updating an order's shipping address through the API now triggers a live tax recalculation instead of leaving the original tax untouched | Fraud-review tools, address-correction apps, 3PL sync scripts that edit addresses post-order |
Customer.lastIncompleteCheckout removed | The field and the entire Checkout type subtree reachable through it are deleted; any query referencing it now fails | Headless storefronts and custom account pages built before the Storefront API cart migration |
PriceRule type family removed | The legacy discount object and its mutations no longer exist in the schema | Older discount apps and B2B pricing tools that never moved to the Discount API |
ITEM_NOT_STOCKED_AT_LOCATION removed | Inventory can be adjusted at any location without this error firing, since inventory is now adjustable at any location by default | Apps that specifically catch this error to block or flag location mismatches |
The carrier service change, in detail — because it fails silently
Before 2026-10, creating a carrier service through the Admin API automatically added it to the store's General shipping profile, so its rates were live at checkout the moment the integration finished running. Shopify's own changelog states the change plainly: carrier services will no longer be automatically added to the default shipping profile. As of 2026-10, that linking step is gone. The carrier service is created successfully, the API call returns no error, and the rate simply never reaches a customer, because nothing points a shipping profile at it.
Most API deprecations fail loudly: a query throws, a field comes back null, a webhook stops firing. This one does not. The mutation that creates the carrier service still succeeds. The failure shows up two steps downstream, at checkout, as an absence rather than an error — which is exactly the kind of break that monitoring built to watch for 4xx and 5xx responses will not catch.
The fix is a single extra step: after creating the carrier service, add its rate to the relevant shipping profile either manually in the Shopify admin or programmatically through the shipping profile APIs. The work is small. Finding out you need to do it before a customer does is the part worth twenty minutes this week.
Who actually needs to act this week
Most stores are not touching any of this. The risk is concentrated in a handful of setups, which makes the audit fast if you know what to look for.
| Store setup | Risk | What to check |
|---|---|---|
| Default theme, Shopify Shipping or calculated rates only, no custom carrier integration | Low | Confirm Settings > Shipping and delivery still shows rates for every profile you expect |
| Freight quoting tool, regional courier plugin, or international duties calculator that creates carrier services via the API | High | Re-run the integration in a development store on 2026-10 and check whether the new carrier service shows rates at checkout afterward |
| Headless storefront (Hydrogen or a custom frontend) built before mid-2026 | Medium | Search the codebase for lastIncompleteCheckout and move to Customer.orders or a Storefront API cart |
| B2B or wholesale store on an older discount or pricing tool | Medium | Ask the vendor directly whether the app has migrated off PriceRule to the Discount API |
| Fraud-review, address-correction or 3PL sync app that edits order addresses after the fact | Low to medium | Confirm the app and your tax setup expect the live recalculation, so tax isn't adjusted twice |
A 20-minute audit before Black Friday
- Check every shipping profile. In Settings > Shipping and delivery, confirm each profile still lists rates for the carriers customers expect to see.
- Find your API-calling apps. In the Shopify admin's app list, note which installed apps touch shipping, discounts, inventory or order addresses, and when each was last updated.
- Ask vendors directly. For any app updated in the last month, ask whether that update targeted 2026-10 and, if so, whether it accounts for the carrier-service change.
- Test in a development store. Create a carrier service the way your integration does, then check whether its rate appears in a shipping profile without a manual step.
- Grep custom code. Search any theme, app or script you maintain for
PriceRule,lastIncompleteCheckoutandITEM_NOT_STOCKED_AT_LOCATION. - Place one real test order. Walk it through to the shipping step and confirm the rates a customer would actually be shown.
Run this before traffic peaks, not during it. A missing shipping rate at 2pm on a Tuesday is a support ticket. The same gap on Black Friday is a day of lost checkouts nobody notices until the weekly report.
If you are still on an older API version
Nothing forces you onto 2026-10 today. Shopify supports the last several quarterly versions at once, so an app built against 2026-01 or 2026-04 keeps its current behaviour, carrier auto-add included, for roughly a year before that version is retired. The part that catches stores out is indirect: you do not choose when this becomes relevant. Your shipping app's developer does, the day they ship an update that targets 2026-10, and that update note rarely mentions a shipping-profile behaviour change buried under thirty others. Checking which API version each of your critical apps currently targets, and watching for their next update, is cheaper than discovering the change after it ships.
This is the kind of audit that tends to fall through the cracks between a merchant who doesn't read API changelogs and a theme developer who was never told to. It is also routine work for Shopify development partners who track platform versioning as part of ongoing support, rather than only when a store owner notices checkout looks wrong. If your team doesn't have anyone watching Shopify's quarterly release notes, that gap is worth closing before the next one ships in January, not after.
Frequently asked questions
What exactly changed in Shopify's Admin API 2026-10?
Five breaking changes matter most: creating a carrier service no longer automatically adds its rates to the General shipping profile; updating an order's shipping address now triggers a live tax recalculation; the Customer.lastIncompleteCheckout field and its Checkout type subtree are removed; the legacy PriceRule object and its mutations are gone; and the ITEM_NOT_STOCKED_AT_LOCATION inventory error no longer fires. The version became stable on October 1, 2026.
Why does checkout show no shipping rates after I create a carrier service?
Before API 2026-10, creating a carrier service automatically added it to your store's General shipping profile, so its rates showed at checkout immediately. As of 2026-10, that automatic step is gone. The carrier service exists, but nothing points a shipping profile at it, so checkout shows no rates from it and no error is logged anywhere, because nothing actually failed. Someone has to add the rate to a profile manually in the admin or through the shipping profile APIs.
Do I need to upgrade to API version 2026-10 right away?
Not immediately. Shopify supports the last four quarterly API versions, so apps built against an older version keep working for roughly a year before that version is sunset. The risk is indirect: any app, theme extension or custom integration you or a vendor upgrades to 2026-10 inherits these changes the moment it does, often without a release note anyone reads. Audit now rather than waiting for the forced migration.
What happens to apps still running on an older API version?
They keep the old behaviour, including the automatic carrier-to-shipping-profile link, until the app itself is updated to target 2026-10 or an older version it depends on is sunset. That is exactly why this is easy to miss: the break doesn't happen on a date you control, it happens on whatever date your app vendor ships their next update, which you may not be told about.
Does this affect Liquid themes or only custom apps?
Standard themes that only render shipping options Shopify's checkout already calculated are not directly affected. The risk sits in anything that calls the Admin API to create or manage carrier services, edit order addresses, reference PriceRule, or read Customer.lastIncompleteCheckout: custom apps, freight and multi-carrier shipping apps, B2B pricing tools, headless storefronts and internal scripts.
What should I check before Black Friday?
Run the audit before traffic peaks, not during it. Confirm every shipping profile still lists rates for the carriers you expect, check whether your shipping and discount apps have been updated to 2026-10 recently, search any custom code for the removed fields and types named above, and place one real test order through to the shipping step to see the rates a customer would actually see.
The takeaway
Most Shopify API versions pass quietly because their breaking changes announce themselves with an error. 2026-10's carrier-service change does the opposite: it removes an automatic step and leaves no trace of having done so, which means the first signal most stores will get is a drop in checkout completion nobody has connected to a platform update. The audit above takes less time than writing the support ticket that follows if you skip it. Run it against your shipping, discount and inventory integrations this week, while Q4 traffic is still ramping rather than already at the register.