> 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/configuration/b2b-rules.md).

# B2B Rules

B2B-specific conditions for the Shopware Rule Builder

B2B specific rules (for the Shopware Rule Builder)

## What are B2B specific rules?

The Shopware Rule Builder is a very powerful tool with which you can define many rules. The rules are linked to each customer, and therefore the B2bSellersCore plugin also offers B2B specific rules, which can then be used for various use cases.

#### Example:

A rule recognizes a sales representative if they are logged in as a customer in the shop. This rule could be used, for example, in the B2B platform navigation to display the menu item "Customer-specific prices" only to a logged-in sales representative.

## The following B2B-specific rules exist:

* Is a sales employee
* Is a sales employee with feature: Supervisor
* Is a business customer
* Is a logged-in user
* Sales employee is logged in as a user
* Is a logged-in user with admin rights
* Is a logged-in user without admin rights
* Is a logged-in user with \[select roles]
* Is a logged-in user with \[select permission]
* Is a customer with a given custom field value

#### Examples:

![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/sxmyvuCOinhBQg2LgFwP/FireShot%20Capture%20150%20-%20Sales%20representative%20is%20logged%20in%20as%20an%20employee%20-%20Example%20-%20Rule%20bui_%20-%20luxon.demo.b2b-commerce-suite.com.png)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.b2b-sellers.com/b2b-platform/user-guide/configuration/b2b-rules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.