Brand registry and seller accounts
How Amazon's registered-brand model intersects with RankASIN's organization + seller_account scoping.
Amazon's model
Amazon Brand Registry is a trademark-gated program. To enroll, you need a registered or pending trademark in the relevant marketplace. Once enrolled, your brand unlocks a set of tools that are unavailable to generic sellers:
- Brand Analytics — the three CSV reports (SQP, SCP, TST) that power RankASIN's keyword research workflows
- Sponsored Brands — headline search ads and video ads featuring your brand logo
- A+ Content — enhanced detail page modules that replace the plain text product description
- Vine — Amazon's reviewer program for getting early reviews on new ASINs
- Brand Store — a dedicated multi-page storefront on Amazon.com
One seller account can own multiple registered brands. Each brand has its own analytics, its own store, and its own Brand Registry dashboard in Seller Central.
RankASIN's model
RankASIN maps to Amazon's structure with an additional layer at the top:
Organization (your company / team)
└── Seller account (one Seller Central account, one marketplace)
└── Brand (one registered brand this account controls)
└── ASIN (one product / SKU)
Organization — your RankASIN account. Your team lives here. Organization members have roles (owner, editor, or viewer) that control what they can read and write across all data under the org.
Seller account — one Seller Central account on one marketplace. "Knours US" is a different seller account from "Knours UK" even if it's the same legal entity. The seller account is the primary scoping boundary in RankASIN. Most tables — ASINs, keywords, tasks, mission progress, all report tables, listing SKUs — carry a seller_account_id foreign key and are filtered to the active account on every query.
Brand — one registered brand the seller account controls. Brand objects in RankASIN link a brand name to its seller account and hold brand-level configuration (registry status, analytics access, store URL).
ASIN — one product. ASINs belong to a seller account (not a brand directly). A seller account with two brands can have ASINs under both; the ASIN's connection to a brand is implicit via the category and keyword data, not a hard foreign key.
Why seller-account scoping
The cookie-based seller account selector — the dropdown in the RankASIN sidebar — controls the active seller account for your session. Every page that fetches data calls getActiveSellerAccountId() to read this cookie and filters all queries accordingly.
This means: if you switch seller accounts, the keyword master resets to that account's keywords, the task list shows that account's tasks, and the research uploads show that account's reports. Nothing leaks between accounts. For agencies or multi-brand operators, this is how you work on Knours in the morning and a different brand in the afternoon without data mixing.
Member roles
Organization members are assigned one of three roles at invite time:
| Field | Type | Required | Description |
|---|---|---|---|
| owner | role | no | Full access. Can invite new members, change member roles, delete members, and manage organization settings. Only owners can perform destructive operations (delete imports, archive ASINs, remove brands). |
| editor | role | no | Read-write access on ASINs, listings, keywords, tasks, and reports. Cannot manage organization membership or settings. This is the correct role for anyone actively working on the account. |
| viewer | role | no | Read-only access to all data. Cannot create, edit, or delete anything. Use for stakeholders who need visibility but should not make changes — brand managers reviewing progress, external consultants, or clients. |
Roles are enforced at the database level via Row Level Security policies, not just in the UI. An editor who calls an API route they're not supposed to write to will receive a permission error from Postgres, not just a disabled button.
Multi-brand, multi-marketplace
RankASIN is built for multi-brand, multi-marketplace operations. An organization can have multiple seller accounts — one per marketplace per brand — and you switch between them with the sidebar selector.
If you manage a brand registered in both the US and UK marketplaces, you create two seller accounts (e.g., "Knours US" and "Knours UK"), each with its own ASINs, keywords, and reports. Brand Analytics data from each marketplace lives under its respective account. The keyword masters are separate: a term ranking #1 in the US does not automatically carry significance in the UK.
Brand objects in RankASIN can span seller accounts — a brand registered in multiple marketplaces is one brand but linked to multiple seller accounts. This reflects the Amazon model where a single Brand Registry enrollment covers multiple marketplaces once the trademark is accepted in each.