Shopify Editions "Compass" Just Dropped — Here's What Hydrogen Developers Need to Do
Shopify's Summer 2026 Edition landed Tuesday. Codename "Compass." 65 product updates.
Most of the headlines are about Sidekick 2.0 and B2B. Those matter for merchants.
This post is for the developers staring at the Storefront API changelog and calculating what breaks before October.
The One Number That Matters: October 2026
Shopify updated the Storefront API to version 2026-07. It introduces breaking changes to cart and product query structures that affect every headless build — Hydrogen, Next.js Commerce, Nuxt, or custom.
The old 2024-10 API version sunsets in October 2026. That's a five-month runway.
If you're running Hydrogen, you get codemods and a guided migration. If you're on a custom framework, you're on your own — and agency estimates for remediation land between $8,000 and $40,000 depending on storefront complexity.
Five months sounds like a lot. It isn't. Not when you factor in testing, staging deploys, and the fact that your cart logic is probably the most fragile part of the stack.
What Actually Broke in Storefront API 2026-07
1. Discount Fields Overhaul
This is the biggest structural change. Three things shifted:
-
cart.discountAllocationsis gone. Usecart.lines[].discountAllocations(lineLevelOnly: false)for product discounts andcart.deliveryGroups[].discountAllocationsfor shipping discounts. -
cartDiscountAllocation.discountApplicationis replaced bysourceDiscountApplication. The old field had a long-standing bug wherevaluereturned the per-line allocated amount instead of the configured discount amount. A $10 fixed discount allocated as $4 to one line showedvalue: $4. The new field returns the correct configured amount. Use GraphQL fragments for type-specific fields. -
cart.discountApplicationsis new. Lists all discounts (product, shipping, order) currently applied to the cart. Cleaner than the old allocation-based approach.
If your storefront has any custom discount logic — tiered pricing, BOGO, market-specific discounts — this is where you'll spend the most time.
2. Cart Warnings for Buyer Location
New PRODUCT_UNAVAILABLE_IN_BUYER_LOCATION warning code in the Cart object. If you sell across markets with different product availability, your cart now emits warnings when a product can't ship to the buyer's location. Your frontend needs to handle these gracefully instead of silently hiding products.
3. Cart Delivery Option Warnings
The Cart object now exposes CartWarning for unavailable delivery options. This lets you notify buyers and prompt for reselection when their chosen delivery method isn't available — useful for mixed-ship orders.
4. Removed Fields
DraftOrderLineItem.grams— deprecated for 8 years, finally removed. UseLineItem.weightinstead (now available in the public Admin API with value + unit).PRIVATEandPUBLIC_READmetaobject enums — removed. Update to the current access control model.
5. New Checkout & Accounts Configuration API
Unified branding across checkout, customer accounts, and sign-in pages. Shared settings, surface overrides, direct color settings, and Markets support. If you've been stitching together checkout branding with CSS hacks, this replaces that cleanly.
B2B: Shopify Closes the Wholesale Gap
For developers building B2B storefronts on Hydrogen, this release is significant:
- Net-30/60/90 payment terms natively in Shopify Payments, with automated AR aging reports. Eliminates third-party apps like Apruve or Behalf for many use cases.
- Company-level price lists with tiered volume rules, supporting up to 500 distinct company profiles.
- Purchase order number capture at checkout with PO validation logic — configurable without custom code.
- Draft order automation via Flow — wholesale reps can trigger quote-to-order workflows from CRM events. Salesforce and HubSpot triggers shipping in Q3.
- B2B-specific storefront permissions — wholesale catalog and pricing remain fully gated from DTC traffic without a separate store instance.
If you're building Hydrogen B2B storefronts, the new createHydrogenContext helper and the Hydrogen Cookbook's B2B recipe just became much more relevant.
Sidekick 2.0: Less Relevant for Developers, But Worth Knowing
Sidekick now plugs into live inventory data, Shopify Payments transaction flows, and 3PL connectors (ShipBob, Flexport, FBA). It can answer questions like "Why did my conversion rate drop 12% last Tuesday?" by cross-referencing session behavior, payment declines, and shipping estimate changes.
Not directly a developer concern — but it means merchants will expect their storefront data to be clean and structured enough for AI reasoning. Sparse metafields and inconsistent product data = invisible to Sidekick.
The Remediation Math
Here's the honest cost breakdown for different storefront types:
| Build Type | Migration Path | Estimated Cost |
|---|---|---|
| Hydrogen (latest) | Codemods + guided migration | $0–$2,000 (internal dev time) |
| Hydrogen (older versions) | Upgrade + codemods + testing | $2,000–$8,000 |
| Custom Next.js Commerce | Manual API migration + cart rewrite | $8,000–$25,000 |
| Custom Nuxt/headless | Manual migration + discount logic rebuild | $15,000–$40,000 |
| Hydrogen + heavy custom Functions | Functions audit + cart + checkout | $5,000–$15,000 |
The discount fields overhaul alone touches cart, checkout, and every place your storefront displays pricing. If you have custom discount stacking logic, that's where the hours pile up.
What Hydrogen Developers Should Do This Week
1. Pin your API version and audit.
Check which API version your Hydrogen storefront is pinning:
grep -r "apiVersion" app/
If you're on 2024-10, you have until October. If you're on 2025-01 or later, the discount changes are already live in your dev environment.
2. Test discount logic against 2026-07.
npx shopify hydrogen dev --api-version 2026-07
Walk through every discount scenario: percentage, fixed amount, BOGO, tiered, market-specific. Check that your cart renders allocations correctly.
3. Run the Hydrogen codemods.
npx shopify hydrogen upgrade
Shopify ships codemods for Hydrogen users. They handle most of the structural field renames. They won't fix custom discount logic — that's on you.
4. Check your metafield usage.
If you're using PRIVATE or PUBLIC_READ metaobject enums, replace them before 2026-07 goes stable on July 1.
5. Review B2B readiness.
If you're building B2B storefronts, read the Hydrogen Cookbook B2B recipe — it's been updated for the new net terms and PO capture APIs.
The Bottom Line
Shopify Editions Compass is a platform redefinition disguised as a feature drop. The Storefront API 2026-07 changes are real, the October deadline is firm, and the remediation cost for custom builds is significant.
Hydrogen users get the smoothest path — codemods, guided migration, and a framework that ships changes aligned with Shopify's own API cadence. That's the argument for building on the platform's own stack.
Five months. Plan accordingly.
Need This Migration Done Right?
The Weaverse team ships Hydrogen storefronts under production load — not demos, not tutorials. We've handled Storefront API migrations, custom Functions ports, and B2B builds from scratch.
If your store needs the 2026-07 migration and you don't want to learn discount field restructuring the hard way, talk to us →
Sources
- Shopify Editions Summer 2026 — shopify.com/editions
- Shopify Developer Changelog — shopify.dev/changelog
- Storefront API 2026-07 breaking changes — shopify.dev/changelog
- E-Commerce Times: Shopify Editions Summer 2026
- Shopify API Versioning — shopify.dev/docs/api/usage/versioning
- Hydrogen Updates — hydrogen.shopify.dev/updates
- Hydrogen Cookbook — hydrogen.shopify.dev/cookbook



