Store identity
- Merchant workspace
- Store ID / canonical domain
- Channel connection
- Store-specific configuration
YEEDOOR treats each store as an explicit operating scope. The store is mapped to the marketplace, advertising, product-feed and analytics assets that belong to it, so AI analysis and actions use the correct business context.
A merchant may authorize one Google identity that can access many Ads accounts, GA4 properties and Merchant Center accounts. A company may also own several Shopify stores or seller accounts. The operating system still needs to know which assets belong together.
This makes it possible for one company to add multiple stores while keeping each store's Google and marketplace assets separate. AI can still compare stores at the merchant level when the user asks for a portfolio view, but store-level actions remain scoped.
Resolve which store the user or agent is operating.
Load the Google, marketplace and analytics assets mapped to that store.
Read, recommend and execute only inside the resolved store scope.
For an AI agent, a good tool is not only “update product” or “analyze ads.” It should know which merchant and store it is operating for, which provider account is attached to that store, and whether the merchant granted the required permission.
Bring every store and its connected assets into a structured merchant workspace.