Account Types

This is a deep dive into the different types of accounts and their respective roles. These can be setup when configuring your organization/site/employees.

Retailer

• Retailers own stores and they sell stuff. Most of the accounts are going to be retailers.
• Retailers are running kiosk apps in their stores where orders are created. In many cases this is guided experience involving store clerk.
• All data that comes from the store is owned by retailer. Retailers have relationship with the customer and they communicate with the customer.
• Product returns are coming to retailers. Retailers have contracts with brands to sell their products. Brands are invoicing retailers for products they sell.

Retailers in the Platform

• Everything they do is within their own organization, they cannot access anything outside of it.
• They can create accounts for their employees.
• They can onboard new sites to their organization.
• They cannot select tenant, if they have tenant assigned to their organization it's automatically assigned to their sites and orders. Retailer-tenant relationship is created by Awesome Ind. or support - however support has some limitations.
• They can select available products in their stores and assign prices (only retailer and support can define price of a product in the store).
• They can accept orders (in the future this will be automated with point of sales integration).
• They can view sales statistics and kiosk app analytics.

---

Tenant

• Tenant is an organization on top of the retailer. Tenant is enforcing its branding onto retailers and can view and manage everything retailers are doing.
• Usually tenant is a retailer at the same time.
• Usually when integrating with other cloud systems data is organized in a context of the tenant. Therefore integration configurations lives on the tenant level.

Tenant in the Platform

• Relation with tenant is optional. However it's useful for the data relation simplicity, for instance, if retailer from our system is represented as tenant in other system - it's easier to assign to that retailer the same organization as tenant.
• Tenants can create retailers organizations. Those organizations have that tenant assigned to them.
• Tenant can onboard sites and employee accounts to its retailers. Tenant can see all orders from linked retailers.
• Credentials to access other cloud systems are configured for tenants (at least for all the use-cases we currently have)

---

Brand

• Brands are creating products that are then sold buy retailers.
• Brand manages relationship with retailers in many cases. They have agreements with retailers to sell their products.
• Brand manages relationship with manufacturer. When designing a product brand needs to make sure they will be able to manufacturer it somewhere. Sometimes brand is manufacturer as well or they are producing some part of the final product and other manufacturer makes the rest.
• Brand can decide which of their products are available by what retailers.

Brand in the Platform

• Cannot see orders as retailers do. They can't have access to the customer data.
• Brands see statistics of amount of sales from retailers for their products. For example, Store A sold x amount of product A yesterday.
• They can't see prices of their products set up in the site and if the site has products from other brands, given brand can see only their products in that site.
• Brand can choose organizations that can see their products.
• Brand can choose manufacturer that is producing their products.

---

Manufacturer

• Manufacturers can be assigned to products by brands
• Manufacturers are using Platform mostly through API integration with their ERP systems. Depending on the integration it's either pull system (manufacturers pulls a list of orders) or push (we are sending order data to manufacturer, i.e. webhooks)
• Each product and manufacturer have different workflow resulting in different statuses reported back to out Platform.
• Manufacturers are responsible for providing shipping tracking info.

Manufacturer in the Platform

• Manufacturer can only see orders and order items that include products for them to produce. If an order has items dedicated for other manufacturers they are not visible.
• Manufacturer doesn't have direct access to customer data, only to shipping address and associated biometric data that's required for manufacturing - nothing else.
• Credentials are assigned per manufacturer, in the future per manufacturer site.
• When manufacturer returns status of the production we have to map it to our internal status. on an order

---

Support

• Support helps retailers and tenants setup their accounts
• Support usually is on the phone with end customer or retailer hence they need to have access to pretty much all the data from organizations they are supporting

Support in the Platform

• Support can view/edit all sites, employees, orders and organization details from all supported organizations
• Support can create retailer organizations