> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/user-guide/using-the-b2b-platform/companies-employees-and-sales-representatives.md).

# Companies, Employees and Sales Representatives

How B2Bsellers changes the way customers are represented in the shop

This page explains the general concept behind the types of users in the shop, and how it differs from classic Shopware.

Two companies are used as examples throughout:

* **Ektek GmbH** — the customer placing orders in the shop. **Henk Becker** is their initial administrator and an employee of Ektek GmbH.
* **Luxon GmbH** — the company running the shop.

## Clarification of terms

### Company

In contrast to classic Shopware, you do not create an individual private customer for each person. Instead you create a commercial customer that serves as the central link for all employees and represents the company.

**Before:** Ektek GmbH was a single customer account that all employees logged into, sharing one password and e-mail address.

**After:** Ektek GmbH can no longer be logged into by employees. They log into their own employee accounts with their own e-mail addresses and passwords, while Ektek GmbH remains the connection point where all products and orders live.

### Employee

An employee is an account that can be assigned to one or several companies. Employees are not created through the registration form in the storefront; the company's administrators create and manage them.

**Before:** Each employee of Ektek GmbH opened their own account in the shop with their own e-mail address, leaving you to consolidate dozens of accounts' invoices later in the year.

**After:** As an administrator of Ektek GmbH you create individual accounts for your employees. All orders and invoices they create are in one place for you to access.

### Sales representative

A sales representative is a special account with extended permissions, such as creating and managing offers for customers or purchasing on behalf of customers.

**Before:** As Luxon GmbH you had to grant full Shopware administration access to anyone who needed to create orders for customers, and there was no way to trace who actually created an order.

**After:** You no longer need to give administration access to people focused on sales. You create a sales representative for them, so they can handle sales tasks inside the shop directly, and you can see who made changes for customers or created orders.

## Creating companies

A customer who wants to buy from you is the company, in this example Ektek GmbH.

The customer goes to the login screen and creates a new account for Ektek GmbH. As the shop operator you decide in the administration whether new customers are created exclusively as private customers (B2C) or as business customers (B2B).

Once registration as a commercial customer is complete, and depending on your settings, the creator is asked to create a first administrator employee. This can also happen automatically. See the core configuration setting **Automatic creation of the first admin employee at customer creation** in [Core configuration](https://docs.b2b-sellers.com/b2b-platform/user-guide/configuration/plugin-konfiguration.md).

{% hint style="danger" %}
With B2Bsellers, commercial customers are umbrellas that contain the employees who log in. Password changes on the company account (Ektek GmbH) therefore do not affect the initial administrator (Henk Becker) that was created.

Passwords must always be changed at employee level.
{% endhint %}

## Creating employees

To create an employee, the administrator of the company logs in and goes to **Company > Employees**. From there employees can be created manually, invited via a link, or imported from a CSV file.

Once created, employees can buy for the company, view invoices and more, depending on their permissions.

See [Managing Employees](https://docs.b2b-sellers.com/b2b-platform/user-guide/using-the-b2b-platform/customer-portal/managing-employees.md) for how to create and manage them, and [Navigating the Customer Portal](https://docs.b2b-sellers.com/b2b-platform/user-guide/using-the-b2b-platform/customer-portal/navigating-the-customer-portal.md) for what employees can do in the shop.

## Creating sales representatives

To create a sales representative, go to **Customers > Sales agents** in the Shopware administration and use the button at the top of the page.

See [Navigating the Sales Representative Portal](https://docs.b2b-sellers.com/b2b-platform/user-guide/using-the-b2b-platform/sales-representative-portal/navigating-the-sales-representative-portal.md) for what a sales representative can do in the shop.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.b2b-sellers.com/b2b-platform/user-guide/using-the-b2b-platform/companies-employees-and-sales-representatives.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
