ST · Stores
Dropshipping · print-on-demand · merch drops · digital stores/courses This page lists everything the Leumas graph records about how it relates to the rest of the system.
What ST · Stores is
Dropshipping · print-on-demand · merch drops · digital stores/courses It is recorded in the Leumas graph as a revenue in the architecture grain.
What ST · Stores relates to
The graph records 7 relationships for it, across 3 kinds. It contains ST · Digital products, ST · Digital stores and courses and ST · Dropshipping, and 2 more.
What it depends on, and what depends on it
Nothing is recorded as a dependency of ST · Stores. It is used by Revenue.
Why it is shaped this way
Studio creates and operates stores, catalogs, content funnels, and fulfillment workflows. Admin owns commercial policy, payment configuration, supplier risk, refunds, disputes, and portfolio oversight.
How to read this
Every relationship here is one of nine shared kinds, mapped from the source graph rather than invented. A kind that a source uses and this model does not express is dropped and counted rather than turned into "related to", so what you see understates the source rather than embellishing it.
- Contains: ST · Digital products, ST · Digital stores and courses, ST · Dropshipping, ST · Merch and sub-brand drops and ST · Print on demand.
- Part of: Monetization.
- Used by: Revenue.
Questions
What does ST · Stores depend on?
This graph records no dependencies for ST · Stores.
What uses ST · Stores?
Revenue.