ShopEyes Radar

Shopify Radar Daily, July 7, 2026: App Developer Radar and Shopify Platform signals

Today's Radar highlights 6 Shopify ecosystem signals across App Developer Radar, Shopify Platform, Storefront & Theme, Conversion, Analytics, Fulfillment, Operations, Best practices.

Short answer

This daily Shopify Radar report highlights the most important Shopify ecosystem signals for 2026-07-07 and converts them into practical owner-assigned actions.

Today's 3 decisions

  1. Search codebases for Customer.lastIncompleteCheckout and Checkout type references; migrate to Cart/Order queries; pin to pre-2026-10 versions until migration is complete.
  2. Migrate shipping and fulfillment integrations to query LineItem.weight. Update unit handling to support the typed Weight object.
  3. Audit headless checkout implementations and migrate new builds to use sso=silent. Update documentation and code examples accordingly.

Actions by role

For merchants

Ask the store owner or developer to review whether "Customer Account API Customer.lastIncompleteCheckout and Checkout types removed in 2026-10" affects checkout, customer accounts, subscriptions, taxes, discounts, or gift cards.

For agencies

Turn urgent Shopify platform changes into client audit checklist items, especially when a deadline or API version appears in the source signal.

For app developers

Check API version, extension, authentication, webhook, and App Store requirement changes before the next release cycle.

Key takeaways

  • App Developer Radar is a visible theme in today's selected signals.
  • Shopify Platform is a visible theme in today's selected signals.
  • Storefront & Theme is a visible theme in today's selected signals.

Signals in this report

88 Urgent Shopify Developer Changelog Official

Customer Account API Customer.lastIncompleteCheckout and Checkout types removed in 2026-10

Customer Account API 2026-10 removes the deprecated Customer.lastIncompleteCheckout field and the entire Checkout type subtree, including CheckoutLineItem, ShippingRate, and AppliedGiftCard.

Why it matters: Headless and customer-account integrations relying on the deprecated checkout subtree will break at the 2026-10 API version cutover. Teams must migrate to the Cart or Order APIs for abandoned-cart and checkout-related data before upgrading.

Action: Search codebases for Customer.lastIncompleteCheckout and Checkout type references; migrate to Cart/Order queries; pin to pre-2026-10 versions until migration is complete.

Act nowchangelogApp Developer RadarShopify PlatformStorefront & Theme Original source
87 Opportunity Shopify Developer Changelog Official

`LineItem.weight` field now available in public Admin API

GraphQL Admin API now exposes a weight field on LineItem (2026-07+), returning a typed Weight object with value and unit, removing the need to convert from REST's grams field.

Why it matters: Eliminates manual grams-to-unit conversions and REST fallbacks. Critical for shipping, fulfillment, and 3PL integrations that need accurate line item weights.

Action: Migrate shipping and fulfillment integrations to query LineItem.weight. Update unit handling to support the typed Weight object.

Act nowchangelogShopify PlatformApp Developer RadarFulfillment Original source
86 Opportunity Shopify Developer Changelog Official

Headless checkout SSO is now documented with sso=silent

Shopify's headless checkout auth docs now use sso=silent as the parameter name instead of logged_in=true. Existing URLs continue to work.

Why it matters: Standardizes terminology for silent SSO from headless storefronts to checkout. Agencies and developers building headless experiences should adopt sso=silent going forward for clarity and future-proofing.

Action: Audit headless checkout implementations and migrate new builds to use sso=silent. Update documentation and code examples accordingly.

Act nowchangelogShopify PlatformStorefront & ThemeApp Developer Radar Original source
86 Opportunity Shopify Developer Changelog Official

Add Tags to Discounts

Starting API version 2026-04, all discount types support tags for labeling, grouping, and organization via the Admin API.

Why it matters: Enables better discount organization, reporting, and automation. Agencies managing complex discount stacks for Plus/Enterprise merchants can now segment and audit discounts programmatically.

Action: Implement tag-based discount management in apps and ERP integrations. Use tags for campaign attribution, internal categorization, and automation rules.

Act nowchangelogShopify PlatformApp Developer RadarConversion Original source
84 Opportunity Shopify Developer Changelog Official

`LineItem.priceAfterAllDiscountsBeforeTaxesSet` field now available

GraphQL Admin API LineItem now includes priceAfterAllDiscountsBeforeTaxesSet, equivalent to REST's current_subtotal_price_set on line items.

Why it matters: Gives GraphQL users access to discounted line item pricing in both shop and presentment currencies, supporting multi-currency reporting and accurate order math without REST fallbacks.

Action: Replace REST current_subtotal_price_set usage with this new GraphQL field. Use in multi-currency financial reports and tax-aware calculations.

EvaluatechangelogShopify PlatformApp Developer RadarAnalytics Original source
83 Opportunity Shopify Developer Changelog Official

New `checkoutToken` field added to the `Order` object

GraphQL Admin API Order object now exposes checkoutToken, matching the REST API's checkout_token field.

Why it matters: Brings parity between GraphQL and REST for retrieving the originating checkout token on orders. Useful for analytics, attribution, and migrating REST-based integrations to GraphQL.

Action: Update GraphQL queries to use checkoutToken. Use for attribution, funnel analysis, and REST-to-GraphQL migration paths.

EvaluatechangelogShopify PlatformApp Developer RadarAnalytics Original source

FAQ

How to interpret this Radar report before acting on the evidence.

What is included in this daily Shopify Radar report?

This daily report summarizes selected Shopify ecosystem signals, source perspective, practical actions, and original source links for the 2026-07-07 reporting period.

How should I use this report?

Start with the short answer and decision list, assign owners for urgent actions, then use the evidence appendix to confirm the original source before implementation.

Is this report official Shopify documentation?

No. It is a ShopEyes synthesis. Use official Shopify sources for platform facts and deadlines, and treat vendor or agency sources as perspective-labeled guidance.