November 9, 2026 by InsightLeap
You want a Brand Store for your 1P catalog, so you look for it in Vendor Central and come up empty. Then every setup guide you find opens with "log in to Seller Central," which you don't have.
Brand Stores are available to vendors, but they live in a different console behind Brand Registry, which changes both how you set one up and where its numbers end up. This guide covers how a Vendor Central brand reaches the store builder, a condensed build, which Store Insights figures to check and how often, and how to read them next to the Retail Analytics data you already pull.
Brand Stores belong to Amazon Brand Registry, and you build and manage them in the Amazon Ads console at advertising.amazon.com. Vendor Central manages your supply relationship with Amazon, while the Ads console is a separate account with its own users and its own billing, and the store builder sits there next to your Sponsored Brands campaigns.
Two practical consequences:
The store is free to build and keep live, whether or not you run Sponsored Brands, and it also serves as a landing destination for Sponsored Brands campaigns.
Seller-side guides send you to a Stores tab in Seller Central. As a vendor you reach the same builder, with the same templates and the same moderation step, through the Ads console. Store Insights comes with it, so plan on opening the Ads console for store reporting.
The usual first step, "create a seller account," doesn't apply to you. From a 1P-only starting point the path is:
Where this varies by account: if a distributor or agency runs the Vendor Central relationship, the trademark owner still enrolls the brand and adds them as a Brand Registry user. If you run a hybrid account, look under Manage first to see which selling accounts are already connected before you add the vendor one.
The builder works the same way for vendors and sellers, so here is the condensed version:
Before you place ASINs, check them against your on-hand inventory in Retail Analytics and your open POs. A featured ASIN that runs out of stock wastes the traffic you are about to pay to send there.
Keep an eye on the enrollment too. If the brand loses Brand Registry, Amazon deactivates the store and its URL stops resolving to your store content.
Store Insights, inside the store builder, reports on the store itself. The figures include visitors, page views, attributed sales, units sold, Time on Store, New-to-Brand sales, average order value, and repeat purchase rate. Traffic is broken out by source: Sponsored Brands, tag-attributed traffic from Amazon Attribution tags on external links, Posts, and organic or direct visits.
Attributed sales use a 14-day attribution window by default. A shopper who visits today can still be credited to the store for a purchase up to two weeks out, so sales figures for the most recent two weeks will keep moving. Judge sales on periods that have closed out.
The most useful comparison is your store against its own earlier numbers, so record the first four weeks after launch as a baseline and check against it on a fixed routine:
| Cadence | Store Insights figure | What to look for |
|---|---|---|
| Weekly | Visitors by traffic source | A drop in one source. If Sponsored Brands traffic falls, check whether a campaign paused or ran through its budget before you touch the store. |
| Weekly | Visitors and page views by page | Pages that draw visits but no sales, where the ASINs on the page are the first thing to check. |
| Monthly, on data more than 14 days old | Attributed sales, sales per visitor, average order value | The trend against your baseline, page by page. |
| Monthly | New-to-Brand sales | Whether the store reaches shoppers who haven't bought the brand before, or mostly serves existing customers. |
| Monthly | Time on Store | Which page layouts hold attention, so you can reuse them on weaker pages. |
| Quarterly | Repeat purchase rate, plus a full page review | Refresh store creative at least every 90 days. |
For testing layouts, Amazon has a native A/B feature called Manage Experiments, but its minimum traffic threshold is high. If your store doesn't reach it, run version A for four weeks and version B for the next four and compare the two periods.
Store Insights tells you what happened on the store and Retail Analytics tells you what happened to the ASINs, and these three comparisons connect the two.
Featured ASINs against the rest of the catalog. From Reports > Retail Analytics, pull Glance Views from Traffic and Shipped Units from Sales for the ASINs you placed in the store. Compare their conversion rate before and after launch, and against ASINs you didn't feature over the same weeks. If the featured group moves and the rest don't, the store is the likely reason.
Store sales against margin. Attributed sales count revenue and say nothing about what Amazon earns on those units. Check Net PPM in Retail Analytics for the featured ASINs. A store built around low-margin ASINs can lift sales while dragging the margin picture your vendor manager sees. Weekly Net PPM for the week ending Saturday is available by end of day Monday, so a Tuesday store review has both datasets in hand.
Store pages against search demand. If your team has Brand Analytics, compare your category page themes with the Search Terms dashboard and name pages the way shoppers search. Brand Analytics only opens for users internal to the brand, so an agency building the store will need someone on your team to pull it.
Store Insights lives in the Ads console and Retail Analytics lives in Vendor Central, and neither one joins to the other by ASIN. Every comparison above is a manual export from two systems, repeated each week, and the Vendor Central side only reaches back as far as Amazon's interface will show you. InsightLeap brings in product-level Vendor Central sales, traffic, inventory, and Net PPM on a schedule and keeps history past that window, so the before-and-after view for your featured ASINs is already there when you open the store report.
Connect the accounts before you build, record a baseline in the first month, and review the store on the same day you pull Retail Analytics.