Markets / Improvement (Admin)

The Markets graph has been redesigned
A view that lets you grasp your market setup at a glance

Without opening and navigating each market's page, you can check product counts, discount counts, and inheritance from parent markets right on the graph. You can now read the overall picture of your setup at a glance.

What's on this page
  1. What's actually changing (understand it in 30 seconds)
  2. Illustration of the redesigned graph
  3. Two new points
  4. Before vs. after the redesign
  5. Assumptions and scope covered
  6. How to use it (3 steps)
  7. 5 points developers should know
  8. 3 use cases you can apply to your work
  9. A one-line summary you can use in a pitch

1What's actually changing

Until now, to check things like how many products were in a market or what a submarket inherited from its parent, you needed toopen and navigate each market's page one by one.you needed to
With this redesign, all of that can now be read at a glance on the Markets graph. now.

Before: opening and navigating pages

Even just to check product counts, you had to go into each individual market page. Inheritance had to be traced in your head.

After the redesign: see everything at a glance on the graph

Each node shows product images, product counts, and discount counts. Parent-child inheritance is also clear from the graph's connections.

2Illustration of the redesigned graph

Parent market 320 products 4 discounts EU market 320 products · 2 discounts Inherited: pricing US market 180 products · 1 discount Customized: currency APAC market 95 products · 0 discounts Inherited: pricing Each node shows the product image, product count, and discount count, plus inherited/customized labels, so you can grasp the setup at a glance
MarketsWhat it is: a Shopify feature for managing sales settings such as pricing, currency, and eligible products by country or region in one place. Submarkets can inherit their parent market's settings and override (customize) only the parts you need. This redesign makes theinherited and overridden status visible.

3Two new highlights

New

① A redesigned graph

Each node now carries aproduct image, and shows theproduct countanddiscount count. The result is a clearer visual map that lets you follow the setup at a glance.

New

② An all-markets summary panel

For each market, you can review theinherited settingsand thecustomized settingsin one place. No need to dig into individual pages.

4Before vs. after the redesign

ItemBeforeRedesigned graph
Checking product counts Individual pages Open each market to check Node display At a glance on the graph
Checking discount counts Checked individually Node display Shown on each node
Product image Text-focused Product images Shown on the node
Grasping inheritance / customization Tracing it in your head Checking by moving between parent and child Aggregated panel See inheritance vs. overrides in one place
Category Improvement / Admin

5Assumptions & documented scope

You're using Markets

This applies to stores running markets (and parent/child market structures). It's a UI (admin display) improvement.

Supported plans & availability

Whether there are supported plans or a phased rollout isnot documented. Check the actual display in Markets in the admin.

This release improves the display (graph / aggregated panel); any mention of API changes or new settings themselves isnot documented. See the Markets graph view in the help documentation for details.

6How to use it (3 steps)

1

Open Settings > Markets

From "Settings" in the admin, go to Markets.

2

Review the whole setup in graph view

Get an at-a-glance view of the structure via each node's product images, product counts, and discount counts.

3

Check inheritance in the aggregated panel

Check inheritance vs. customization per market in one place.

Without opening individual market pages, you can use just the graph and aggregated panel to see where how many products and discounts apply, and which settings come from the parent.

75 points developers should keep in mind

1. This is a "display" improvement

It's a revamp of the visualization layer, not the setting values themselves. Read it on the assumption that existing market settings and inheritance logic are unchanged.

2. Inheritance = parent, override = difference

The aggregated panel distinguishes "inherited from parent" from "market-specific customization." Useful as a starting point for auditing settings.

API ?

3. No mention of API/data specifications

How product and discount counts are aggregated, and how to retrieve them via the Admin API, are, in this article,not documented. If you automate this, you'll need to verify separately.

4. Product images are cues on the node

The product images on each node improve visibility into what kinds of products belong to that market. Useful as a first-pass check for inspection and inventory.

5. The real value is reduced operational workload

It eliminates the need to "open each page just to check the number of products" or "trace inheritance in your head."The more markets a store has, the greater the reduction in verification cost. It speeds up reviews, handovers, and audits.

8Three use cases you can apply to your work

USE CASE 1

Complete a "configuration audit" for multi-country stores in a short time

Challenge
You operate multiple markets and submarkets, and taking inventory of each market's product count, discounts, and inheritance status takes time every time.
Approach
Use the redesigned graph and the aggregation panel to audit each node's product count, discount count, and inheritance vs. customization at a glance.
Impact
No need to visit individual pages, shortening the time required for configuration reviews. Catch missing settings and unintended overrides early.
Technical note
You can read whether something is "parent inheritance" or a "market-specific override" as a difference, so it's useful for checking gaps between design intent and implementation.
USE CASE 2

Speed up understanding the structure for new members and handovers

Challenge
When responsibilities change or operations are handed over, there's a learning cost to understanding the existing market structure.
Approach
Share the graph view to explain parent-child relationships, product distribution, and how discounts apply all at once, visually.
Impact
Fewer misunderstandings than explaining verbally or with spreadsheets, leading to faster ramp-up.
Technical note
Nodes with product images serve as intuitive markers for "what's in which market," reducing the need for verbal supplements.
USE CASE 3

Inspect "where discounts apply" before and after a campaign

Challenge
Before a sale, you want to quickly check how many discounts apply to which markets and whether anything is missing.
Approach
Look at the discount count on each node in the graph to check at a glance whether discounts are placed as intended.
Impact
Catch forgotten or excessive discounts before launch, reducing the risk of lost opportunities and over-discounting.
Technical note
The discount count is a metric on the node. The actual discount details and application conditions are expected to be checked individually (this article does not cover detailed specifications).

9A one-line summary you can use in proposals

"The Markets graph has been redesigned, so you can now seeeach node's product images, product count, and discount countand
inheritance vs. customizationat a glance in the aggregation panel.
No more visiting individual pages,speeding up configuration audits, handovers, and campaign checks for multi-country stores."