Shopify has updated its App Pricing system with three key changes: public plan limits increased from 4 to 8 and private plans from 10 to 15; no-charge plan testing is now available during app review, in development stores, and via free-marked plans for partner testing; and the App Events API now supports negative values (for credits/adjustments) and fractional values, removing the previous whole-number-only restriction.
Nguồn: https://shopify.dev/changelog/app-pricing-more-plans-no-charge-plan-testing-and-negative-and-fractional-app-events. 8sync News chỉ tóm tắt và dẫn link; bản quyền nội dung thuộc tác giả và nguồn gốc.
Shopify POS UI extensions API version 2026-07 changes how fixed-amount line item discounts work. Previously, apps could pass a total discount for the entire line item and Shopify POS would auto-convert it to a per-unit value. Starting with 2026-07, the value passed is interpreted directly as a per-unit discount — no automatic conversion occurs. For example, passing '5.00' on a quantity-2 line item now results in a $10.00 total discount, not $5.00. Apps on 2026-04 or earlier are unaffected; apps migrating to 2026-07 must update their discount calculations to pass per-unit values explicitly. Percentage discounts are not affected.
Shopify Flow is changing how breaking changes to Action extension configuration fields are handled. Previously, any field mismatch caused runtime validation to fail and prevented requests from reaching partner servers. Now, workflows using older action versions will continue to execute, and Shopify will forward the request to the configured endpoint regardless of schema differences. Developers must update their endpoints to gracefully handle payloads that may have missing required fields, extra legacy fields, or other schema mismatches — using strategies like default values, ignoring unknown fields, or returning clear error responses.
Shopify Flow now dynamically resolves action runtime URLs on every execution instead of hard-coding them at workflow activation time. When an app is redeployed with a changed runtime URL, existing workflows automatically pick up the new URL without merchants needing to re-save or reactivate them. This also applies during local development with shopify app dev. No action is required from developers, but those who relied on the URL remaining fixed until reactivation should be aware of the new behavior.
Shopify is updating its App Store policy 1.3 on honest and transparent review practices. The changes clarify enforcement around incentivized reviews, with consequences including review removal, app demotion or delisting, and Partner account termination. Additionally, Shopify is adjusting its logic to filter out fake and untrusted reviews, so only reviews meeting trust standards will be publicly visible. Developers should use the Reviews API to collect authentic reviews and request reviews only in neutral language without offering any incentives.
Shopify's Customer Account API version 2026-10 removes the deprecated Customer.lastIncompleteCheckout field and the entire Checkout type subtree. The field previously returned null, so this is a cleanup of stale Checkout Classic schema. Developers must update any queries that reference lastIncompleteCheckout or nested Checkout fields before upgrading. There is no direct replacement in the Customer Account API — for active cart/checkout state use Storefront API cart flows, and for purchase history use Customer.orders.
Shopify's Admin GraphQL API version 2026-10 introduces a new enum value, FULFILLMENT_NOT_REQUIRED, for the OrderDisplayFulfillmentStatus field. This value is returned for orders that have no items remaining to fulfill — such as fully cancelled or fully refunded orders — replacing the previously misleading UNFULFILLED status. The change is backward-compatible for integrations that handle unknown enum values gracefully. Developers using exhaustive enum mappings or filtering on UNFULFILLED will need to add handling for the new value when adopting API version 2026-10.
Shopify's Admin GraphQL API 2026-07 release candidate introduces support for MarketRegionSubdivision, enabling Markets to be configured with country-subdivision regions like states and provinces. This is part of market-driven shipping support. Developers should use the new stable country-subdivision region type and avoid the deprecated market.regions field for sub-region membership. Currently, only shipping is supported; other configurations like Discounts, Catalogs, and Theme contextualization are not yet available and will return validation errors if attempted.
Shopify is rolling out mandatory identity verification for Partners who send collaborator access requests to merchant stores. Starting today, verification is optional but will become required in the coming weeks. Verification is handled through Stripe and requires a government-issued photo ID plus a selfie or liveness check. Every user in a partner organization who sends collaborator requests must individually complete verification via the Dev Dashboard.