> 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/available-add-ons/product-request.md).
# Product Request
The B2Bsellers Product Request add-on allows shop operators to convert standard "Buy" buttons into inquiry forms for specific items. This is ideal for complex products, custom-manufactured goods, or high-value machinery where a direct sale is less appropriate than a professional consultation.
## Core Functionality
When a product is marked as a request item, the "Add to Shopping Cart" button is replaced by a contact form.
* Global vs. Local Logic: You can set rules globally in the plugin configuration or override them for specific products.
* Smart Forms: If a buyer is logged in, the form automatically pre-fills their personal data.
* Contact Integration: Optionally, the system can display the customer's assigned personal contact person directly alongside the inquiry form.
## Configuration Options
### Product-Level Settings
Found under Product > B2B Specifications > Additional Fields > Product Request Fields:
* Request Form Activated: Toggle to turn the product into a request-only item.
* Rule-Based Exceptions: Use the Shopware Rule Builder to define who *can* still buy the product directly (e.g., VIP customers or specific sales channels). This local rule will overwrite global plugin settings.
* Price Visibility: Choose whether to show or hide the price for this specific item.
### Global Plugin Settings
Found under Extensions > My Extensions > B2Bsellers Suite - Request product > Configuration:
* Recipient Email: Define a central address where all incoming inquiries are sent.
* Global Exclusion Rule: Set a default rule for which groups (e.g., "Logged-in B2B Users") see a standard checkout instead of a form.
* Default Price Display: Set the baseline for whether prices appear shop-wide for request products.
* Contact Person Toggle: Enable this to show the assigned account manager to the buyer during the inquiry process.
## Technical Logic & Flow
The module leverages the Shopware Rule Builder, providing high flexibility for complex B2B scenarios.
| **Feature** | **Description** |
| ------------- | ------------------------------------------------------------------------ |
| Direct Buying | Can be restricted to specific customer groups or rules. |
| Data Capture | Collects names, emails, and custom messages. |
| Pre-filling | Reduces friction for logged-in users by auto-populating contact info. |
| Flexibility | Local product settings always take precedence over global configuration. |
### Extending the Form
The request form is designed for high flexibility. Developers can easily adjust the layout or add custom fields by extending the corresponding Twig template in the storefront.
* Dynamic Variables: Any new input field you add to the Twig template is automatically processed.
* Email Integration: You do not need to register new variables manually. The `name` attribute of your HTML input becomes the variable name inside the email template.
* *Example:* Adding `` makes `{{ project_deadline }}` instantly available in your request emails.
---
# 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/available-add-ons/product-request.md?ask=&goal=
```
`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.