POS UI extensions now support reactive storage access
Source: Shopify Dev Changelog
What Changed
Shopify has introduced reactive storage access for POS UI extensions through a new API, shopify.storage.current, available starting in API version 2026-10. This API exposes each storage key as a read-only reactive signal rather than a static value.
Previously, POS UI extension developers could read and write to storage, but there was no built-in mechanism to detect when stored values changed from other extension targets. With shopify.storage.current, developers can now read the current value of a storage key and subscribe to updates whenever that value changes, as long as the change originates from another target of the same extension running on the same POS device.
Writes and removals to storage continue to work as before. No migration steps are required for existing extensions, and current implementations remain fully functional without modification.
Why This Matters for Shopify App Developers
POS UI extensions often span multiple targets within the same checkout or point-of-sale flow, such as a tile, a modal, and a smart grid component. Before this update, keeping these targets in sync with shared state required manual polling or custom event handling, adding complexity and potential for stale data.
Reactive storage access simplifies this by letting extension targets automatically respond to state changes without additional boilerplate. This is particularly relevant for apps that manage cart-level data, customer session details, or configuration settings that multiple extension points need to reflect consistently.
Practical Implications
Developers building or maintaining POS UI extensions should review their current storage handling logic to identify opportunities to replace manual synchronization with reactive signals. Since the API is scoped to targets of the same extension on the same device, cross-device or cross-extension synchronization still requires other approaches. Teams planning new POS extensions should evaluate API version 2026-10 adoption to take advantage of this capability from the outset.