> 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/developer-guide/tips-for-deployment-continuous-integration.md).

# CI/CD

The B2Bsellers Suite is fully compatible with standard Shopware 6 deployment workflows and CI/CD pipelines. To ensure a seamless integration, there are two platform-specific requirements you must incorporate into your build process.

## License Configuration

The suite’s active features and add-ons are managed via a license file. This file must be present for the system to unlock the full B2Bsellers functionality.

* File Location: `[shopware-root]/var/b2b-license.json`
* Deployment Step: Ensure your CI/CD pipeline copies or generates this file in the `var/` directory.
* Note: If this file is missing, only the `b2bsellerscore` will be initialized, and all premium addons will remain inactive.

## Building the B2B Platform

In addition to the standard Shopware Storefront and Administration builds, you must execute a specific build command for the B2B Platform core.

{% content-ref url="/pages/AHWxRuk4pZQmlHWY3CN7" %}
[Build the B2B Platform](/b2b-platform/developer-guide/cli-commands/development-commands/build-the-b2b-platform.md)
{% endcontent-ref %}


---

# 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/developer-guide/tips-for-deployment-continuous-integration.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.