Shopify Customer Account API is dropping its last tie to Checkout Classic, and any headless storefront that read it for cart recovery breaks in October 2026. On July 6, 2026, Shopify confirmed that API version 2026-10 removes the Customer.lastIncompleteCheckout field and the entire Checkout type subtree. If your logged-in account UI still queries either one, the query fails the day you upgrade rather than returning less data.
What Shopify is removing
Version 2026-10 deletes Customer.lastIncompleteCheckout and the whole Checkout type, including CheckoutLineItem, CheckoutLineItemConnection, AppliedGiftCard, AvailableShippingRates and ShippingRate. The changelog entry is tagged Action Required, which is Shopify's signal that an affected query hard-fails rather than degrades. One detail matters more than the removal itself. The field was already deprecated and has been returning null, so the schema is being cleaned up long after the behaviour changed. Any recovery flow reading that field has been quietly returning nothing for months, not breaking in October. This is the deprecation catching up to a behaviour that already shipped. These types are the last remnants of the Checkout Classic object graph, the pre-cart checkout model Shopify has been retiring across its APIs for years. Removing the connection and edge types alongside the field means there is no partial query left to fall back on. After the upgrade you cannot ask for a line item, an applied gift card or a shipping rate off that subtree, because the subtree no longer exists in the schema.
Customer Account API vs Storefront API: where cart state lives now
Live and incomplete cart state belongs to the Storefront API cart, not the Customer Account API. Shopify's guidance is blunt: there is no replacement field inside the Customer Account API. For active cart or checkout state you use Storefront API cart flows, and for purchase history you use the Customer.orders connection. The mental model is cleaner than the one it replaces. The Customer Account API answers who the buyer is and what they have already bought. The Storefront cart answers what is in the bag right now. lastIncompleteCheckout blurred that boundary by exposing a stale checkout snapshot through the identity API, and the blur is exactly what Shopify is deleting.
Why it matters for premium studios in Asia
The teams most exposed are the ones that built the most ambitious logged-in experiences. A common pattern on headless Shopify Plus was a "resume your order" panel in the account area, hydrated from lastIncompleteCheckout, so a returning customer saw their half-finished cart on any device. That is the pattern that breaks, and because the field already returns null, it has most likely been showing an empty panel for a while with no bug filed. For a premium storefront in Southeast Asia, where a large share of returning traffic is mobile and moves between devices, a broken cross-device resume is not cosmetic. It is lost revenue on the exact buyers who already intended to purchase. This is why we audit query schemas on a schedule instead of waiting for a version bump to surface the breakage. Our Shopify and Hyva commerce work and our headless checkout guide start from the same rule: never let one vendor field own a revenue-critical flow.
What we would change this quarter
Grep every Customer Account API query for lastIncompleteCheckout or any Checkout field, then rebuild recovery on the Storefront cart before you touch version 2026-10. The migration is not a rename, it is an architecture change. Persist the Storefront cart ID against buyer identity when a customer logs in, so a returning buyer rehydrates the same cart on any device from a source that is not being deprecated. Move purchase-history views onto Customer.orders, which is stable and was always the correct home for them. Pin your Customer Account API version explicitly and do not float to unstable, because a floating version pulls the removal in the moment 2026-10 ships. Then wire abandoned-cart recovery through the channel Shopify actually supports for it. Server-side automation off cart and checkout events is more reliable than reading a client-facing identity field that Shopify has now removed twice over, first in behaviour and now in schema. Add a schema check to your pipeline that fails the build when a query references a removed field, so the breakage surfaces in a pull request instead of at checkout. Do this while 2026-10 is still upcoming, not after a support ticket about a dead resume panel.