How store selection works across the dashboard

RocketCheckout is organized around the merchant workspace and the currently selected store. The sidebar store selector is the source of truth for store-scoped pages. When you switch stores, the page should refetch data for the new store without requiring a full browser reload.

All Stores view

All Stores is an overview mode. It should summarize the merchant workspace, show cross-store health, and help the user choose a store before doing store-specific work. It should not silently pick a random store for actions that belong to one storefront.

Selected-store view

When a store is selected, pages such as Analytics, Performance, SEO, Recovery, Checkout Testing, and Signals should load data for that store. Store-specific pages can deep-link to an ID route, but the sidebar selector should still drive the visible store context.

What to expect when switching stores

• The sidebar name changes immediately
• Store health enters a loading state while new store data is fetched
• Page cards, charts, and lists refetch for the selected store
• Empty-state notices should only appear after the database confirms there is no data
• Skeleton loaders should match the final page shape so the page does not flash the wrong state

If the wrong data appears

Confirm the URL, selected store, and store health card all point to the same store. If one area updates but another stays grey or stale, the page likely has a stale local fetch and should be refreshed or reported to support.