nearle admin agent
This commit is contained in:
26
services/tools/help/platform-vs-merchant.md
Normal file
26
services/tools/help/platform-vs-merchant.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
question: Why can I not see a shop's orders or stock from the platform workspace?
|
||||
also:
|
||||
- buddy will not answer about a merchant
|
||||
- nearle admin cannot see sales
|
||||
- how do I check what is stuck for a tenant
|
||||
- platform account no tenant
|
||||
area: platform
|
||||
source: services/tools/registry.go, services/agents/platform.yaml
|
||||
---
|
||||
A Nearle staff account reads across every merchant and belongs to none. It
|
||||
carries no shop, and every tool that reads orders, stock, tills or deliveries
|
||||
needs one — so from the platform workspace those questions have no answer rather
|
||||
than a slow one.
|
||||
|
||||
That is the design, not a missing feature. "Every merchant at once" is not an
|
||||
answer to "what is stuck?", and a total across unrelated businesses would be a
|
||||
number nobody could act on.
|
||||
|
||||
To look at one merchant's operations, work inside that merchant's own console,
|
||||
where the shop is fixed and the figures mean something.
|
||||
|
||||
What can be answered from here is how Nearle itself works: what onboarding a
|
||||
branch creates, what assigning a delivery partner does, how the global catalogue
|
||||
reaches a shop's shelf, and why a till account is not a console login. If an
|
||||
answer would need a specific shop's data, it will say so rather than estimate.
|
||||
Reference in New Issue
Block a user