Releasesby Glyph
ShopifyQL returns fields deprecated and replaced with sales reversals fields
In GraphQL Admin API version 2026-04 , several Returns fields in analytics, which can be queried through ShopifyQL , have been deprecated and replaced with renamed versions (e.g., sales_reversals , reversed_quantity ) to better reflect that they capture all order adjustments, including refunds, returns, order edits, and cancellations.
Also shipped Mar 14, 2026Shopify in March 2026 →
Mem0 Platform Skill on skills.sh First skill launch: a dedicated Mem0 skill providing platform API reference...
Mem0 Platform Skill on skills.sh First skill launch: a dedicated Mem0 skill providing platform API reference, quickstart patterns, and integration examples directly inside agent sessions. Available on skills.sh for any compatible AI coding agent.
feldera 0.267.0
- pipeline-manager: fix starting pipeline while clearing storage NATS Input Connector: Bug fix, reliability & test improvements Ci fast fail on job failure
More from Shopify developer platformEvery Shopify developer platform release →
Checkout and Customer Account UI extensions available by default in new development shops
We are ending the developer preview for checkout and customer account UI extensions. With this update: All new development shops on the Shopify Plus plan have access to checkout UI extensions All new development shops on all plans have access to customer account UI extensions All existing development shops will not be affected by this change
Making `fieldDefinitions` optional in `metaobjectDefinitionCreate`
Starting in April 2026, the fieldDefinitions input argument for the metaobjectDefinitionCreate mutation will become optional. This change means that developers will no longer be required to specify fieldDefinitions when creating a new metaobject definition.
Adding `createdAt` and `updatedAt` fields to `MetaobjectDefinition` objects
The createdAt and updatedAt fields will become available on MetaobjectDefinition objects in API version 2026-04
New rejection reason codes in Payments Apps API
The Payments Apps API now provides more granular decline reason codes for rejected payment sessions. Multiple new rejection codes have been added to the PaymentSessionStateRejectedReason enum alongside a new source field, giving payments apps more standardized, actionable ways to communicate to merchants why a payment was declined.
New payment decline codes added to `OrderTransactionErrorCode` enum
We're adding new error codes to the OrderTransactionErrorCode enum to provide more granular detail about the transaction failure. You can use this more detailed response to improve customer interactions. What's new These error codes enable precise identification of transaction issues: | Error Code | Description | |
Clearer standards for app listing images
We've updated requirement 4.4.4 and added a new requirement 4.4.5 for Shopify App Store apps. Requirement 4.4.4 now provides clearer standards for image quality: images should primarily show your app's actual user interface and features. Screenshots must not include desktop backgrounds or browser windows.
POS UI extensions can now run without network access
POS UI extensions can now continue running even when a merchant’s device loses network access. This feature ensures uninterrupted service during connectivity issues. It is especially beneficial for merchants in environments with unreliable internet, such as pop-up shops, outdoor markets, or large retail spaces.
`inventoryTransferDelete` adds `INVALID_STATE` error code for transfers with in-progress product import
Starting in version 2026-07, the inventoryTransferDelete mutation will return a new error code: INVALID_STATE . This error will be returned when a client attempts to delete an inventory transfer while a product import related to that transfer is in progress.