Platform / Feature Preview

Customer accounts get a refresh
The "single column" layout and how extensions appear are changing

A visual refresh that improves consistency across navigation, layout, and devices. You can preview and test your own Shopify Extensions on the new layout right now. The preview period runs until June 12, 2026.

On this page
  1. What's changing (understand it in 30 seconds)
  2. The 3 changes, illustrated
  3. Extension width: inline and full-page behavior
  4. Improved visibility for order extensions (mobile)
  5. Compatibility and schedule for existing targets
  6. How to start the preview
  7. 5 key points for developers
  8. 3 use cases you can apply to your work
  9. A one-line summary you can use in proposals

1What's changing

Customer accounts get a visual refresh.
Consistency across navigation, layout, and devices is improved, and native pages become a single column shared across desktop and mobile .
Along with this, the display width and appearance of extensions (Shopify Extensions) also change, soa period to test your own extensions before merchants go liveis provided.

Single-column layout

Native pages are unified into the same single column on desktop and mobile. Navigation is also simplified.

Extension display width changes

inline extensions are rendered at a narrower width than before. full-page extensions can choose between a narrow, native-compliant width or a wider width that prioritizes data volume.

Order extensions stand out

order action extensions become easier to see, and order summary extensions are no longer hidden behind "tap to view" on mobile.

2The 3 changes, illustrated

① Unified single column desktop mobile = ② Extension width changes Before: wide Narrow ③ Order extensions move to the front summary action Shown without tapping
All three are a refresh of the "look (layout)," andall existing extension targets are already mapped to the new layout. However, since the display width changes, you're encouraged to check that your extension doesn't break under the new layout.

3Extension width: how inline and full-page behave

inline extensions

Rendered at a narrower width than before

Compared to the previous wide layout, inline extensions embedded within a native page render at a narrower page width . If your layout assumes a wide width, be sure to check it.

full-page extensions

Choose narrow or wide

Full-page extensions can choose to adopt the native-page-aligned mobile-first narrow layout , or, for data-heavy content, expand to a wide layout .

full-page: narrow (matches native) For simple content full-page: wide (data-heavy)

4Better visibility for order extensions (mobile)

Extension typeBeforeNew layout
order action extensions Tended to get buried More prominent Easier for customers to find and use
order summary extensions Required a tap to show on mobile No tap needed Shown without being hidden
Features you've built around orders (reordering, return requests, shipment tracking, etc.)become easier for customers to notice on mobile, too. The benefit is greatest for extensions whose discoverability directly drives usage.

5Existing target compatibility and schedule

All targets remain supported

All current extension targets are mapped to the new design, preserving compatibility. You can check the extension-target support for each page in the documentation (extension targets by page).

6/12

Preview available until 2026/6/12

The feature preview is available until June 12, 2026. Testing now lets you get a head start on any adjustments needed before it's officially released to merchants.

to merchants'No official release (general availability) date is given. The article only states that "ideally, you should test these design updates before they're rolled out to merchants." The specific GA timeline needs to be confirmed separately.

6How to start the preview

1

Open the documentation

Start the feature preview by following the guidance in the official documentation.

2

Test your extensions in the new layout

Verify that inline, full-page, and order-related extensions display correctly with the new widths and placement.

3

Share feedback

You can post questions and feedback in the Shopify community. Surface any needed adjustments before the full rollout.

75 key points for developers

1. Native pages move to a single column

Desktop and mobile are unified into the same single column, and navigation is simplified. Implementations that rely on layout assumptions (such as side-by-side arrangements) may be affected.

2. inline extensions become narrower

They render at a narrower page width than the previous wide layout. Use the preview to check that fixed-width or wide-oriented UIs don't wrap or overflow.

narrow wide

3. full-page lets you choose the width

You can choose narrow, which matches native pages, or wide, for data-heavy content. Use wide for tables and dashboards and narrow for informational content, depending on the nature of the content.

4. Order-related extensions get more exposure

order action becomes more prominent, and order summary is no longer hidden behind a tap on mobile. With this increased exposure in mind, there's room to redesign your copy, CTAs, and amount of information.

5. Existing targets stay compatible, but "now is the time to test"

All current extension targets are mapped to the new layout and continue to be supported. However, the preview runs until 2026/6/12. By validating before the rollout to merchants, you can get ahead of any needed adjustments. As for any mention of a GA date or API/Webhook specifications, the article provides none.

83 use cases you can put to work

USE CASE 1

Do a full review of your customer account extensions "before they go live"

Challenge
It's unclear whether inline and full-page extensions will break in the new single-column, narrow-width layout. Problems that surface after the rollout to merchants have a big impact.
Approach
During the preview period through 2026/6/12, test every extension target on the new layout and identify wrapping, overflow, and width-dependent styles.
Outcome
You can finish fixes before the full release and bring the risk of broken display during migration close to zero.
Technical note
inline renders at a narrower width than before. full-page lets you choose narrow or wide, so revisit your declarations based on the content.
summary action
USE CASE 2

Make the most of the "improved discoverability" of order-related extensions

Challenge
order action / order summary extensions for reordering, returns, shipment tracking, and the like are buried behind a tap on mobile, so usage doesn't grow.
Approach
Redesign your copy, CTAs, and displayed information around the new behavior, where order action is more prominent and order summary appears without a tap.
Outcome
Customers can discover and use features more easily, which can be expected to boost usage of reorder and self-service extensions.
Technical notes
Tuned the above-the-fold information density on the assumption that mobile's "tap to reveal" goes away. The visibility improvement is behavior explicitly stated in the article.
USE CASE 3

Optimize the full-page extension layout based on the nature of the content

Challenge
Cramming data-heavy admin full-page extensions into the narrow native width hurts scannability. Conversely, widening informational content makes it feel padded out.
Approach
Choose the wide layout for data-heavy content like tables and dashboards, and the native-style narrow layout for simple informational content.
Result
With the width best suited to the content, you secure readability while keeping a UX consistent with native pages.
Technical notes
Decide the width on the premise of the behavior described in the article: full-page extensions can choose mobile-first narrow or wide.

9A one-line summary you can use in a pitch

"Customer accounts revamped into a desktop/mobile-sharedsingle column.
Inline extensions get narrower, full-page extensions choose narrow/wide, and order extensions stand out even on mobile.
All targets stay backward-compatible, but it's safest to verify for layout breakage during the preview period through 2026/6/12."