> 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/1/user-guide/setup/install.md).

# Installation

Installing the B2B Platform

{% embed url="<https://www.youtube.com/watch?v=R_d9gIZ0_q4>" %}

## Install

1. Upload files to custom/plugins/b2bsellerscore
2. install and activate the Plugin at the Shopware Backend
3. Or run in console `bin/console plugin:refresh && bin/console plugin:install b2bsellerscore && bin/console plugin:activate b2bsellerscore`&#x20;
4. go to console and run command `bin/console b2b:platform:build` at root directory
5. run `bin/console cache:clear`

\=> if you want: run `bin/console b2b:create:test-data` for insert default test data (customer/contacts) li

{% content-ref url="/pages/-MVKl3ImnQkiXJeAs2Um" %}
[Use Test-Customers](/b2b-platform/1/user-guide/setup/test-daten.md)
{% endcontent-ref %}

Info: we recommend the install over the cli, not over the shopware backend - sometimes there are errors

first, you have to install the "B2Bsellers Core" Plugin.

### Install-Script for all B2Bsellers Suite Plugins&#x20;

We recommend to use our script to install all B2Bsellers Plugins within one command. You can change all used plugins...

```
#!/bin/bash

echo "Installing all B2bSellers Suite Plugins"

bin/console plugin:refresh
bin/console plugin:install -ac B2bSellersCore

bin/console theme:change b2bplatformtheme
bin/console b2b:platform:build

bash ./bin/build-storefront.sh
bash ./bin/build-administration.sh

exit 0
```

## Important: With every activation/deactivation of the addons the Javascript and the CSS must be built afterwards.

Because all addons are "Symfony bundles", it is necessary to execute the following commands after each addon activation/deactivation:

* bin/console b2b:platform:build
* bash bin/build-administration.sh
* bash bin/build-storefront.sh

## Setup

1. Change the plugin configuration (admin api and store api credentials are needed)
2. Add emails to the following "business events": account\_activation.send and account\_request.send

## Api

Flag for sending welcome mail via api (customer create + update) -> \_sendWelcomeMail

## Console commands

#### 5.1 Entity Mapping Command (CustomerPrices):

**Usage:**

`bin/console b2b:entity:map`

#### 5.2 Platform watch command

**Usage:**

`bin/console b2b:platform:watch <user> <password>`

**Arguments:**

| Argument     | Description                |
| ------------ | -------------------------- |
| **user**     | Customer/Employee E-Mail   |
| **password** | Customer/Employee password |

**Example:**

Sales Agent: `bin/console b2b:platform:watch m.sommer@luxon.de mediagraphik` Customer-Employee `bin/console b2b:platform:watch Henk.Becker@bosch-pt.com mediagraphik`


---

# 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/1/user-guide/setup/install.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.