> 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/plugin-konfiguration.md). # Core configuration Every setting in the core configuration of the B2Bsellers Suite {% embed url="" %} The core configuration holds the settings that apply to the whole B2Bsellers Suite. This page describes every setting, grouped exactly as the cards appear in the administration. ## Accessing the core configuration In the Shopware administration, open **B2B settings** and choose **Core settings**. The same options are also reachable through **Extensions > My Extensions > B2bSellersCore > Configuration**. {% hint style="info" %} All settings can be configured individually per sales channel. {% endhint %} ## General shop settings The general shop settings control how much of the shop is visible without a login. ### Shop access is only possible when logged in When this is enabled, customers have to log in before they can see any page. Typical use cases are spare parts shops or closed shops where only customers with credentials may enter. ### Show navigation only when logged in When enabled, the category navigation is hidden from customers who are not logged in. ### Redirect destination for closed shops when not logged in Choose where visitors of a closed shop are sent: * **Shopware standard login/registration** * **B2b-Sellers login page** ### Pages visible before login Even in a closed shop you may want certain pages to remain readable. This setting lists all Shopping Experiences layouts of your shop; choose one or several. ### Controller/Routes reachable before login Determines which routes can be reached without logging in. Enter one route name per line. This is particularly useful for whitelisting routes provided by third-party plugins. Routes in Shopware are declared like this: ```php #[Route(path: '%path%', name: '%name%')] ``` **Important:** enter only the value of `name` (the route name), one per line. ### Login page image An image shown as the background on the left of the B2Bsellers login page. If none is selected, random images are used. A square image is recommended. ### Enable customer specific caching When enabled, the customer ID and the tax state are added to the cache keys. This affects the following routes: `CategoryRoute`, `ProductDetailRoute`, `ProductSuggestRoute`, `ProductListingRoute`, `ProductSearchRoute` and `CrossSellingRoute`. ### Store geolocation information in the customer context When enabled, data such as city and region is stored alongside the customer data and used in the user session handling, which helps customers spot unusual activity on their account. See [User Sessions](/b2b-platform/user-guide/using-the-b2b-platform/user-sessions.md). ### Activate passwordless login via email When enabled, customers and employees can request a login link by e-mail instead of entering a password. How long that link stays usable is configured under [Passwordless login](#passwordless-login). ### Allow to delete employee account When enabled, employees can delete their own account from the B2B Platform. This removes the employee record permanently. ### Display detailed permission error message When enabled, the error page names the missing permission and the responsible contact person instead of showing a generic message. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/K84VyMgCnmeqeGZqHjfL/01%20General%20Shop%20Settings.png) ## Document archive The document archive is shown in the customer portal through the **Documents** entry. It is used to make invoices and other relevant documents available. The data shown there matches the contents of the folder you specify on your web server, and the file name schema determines who may see which document. ### Relative path of the server root Enter the path to the shop's document archive on your server. The root refers to `/`, not to the `www` folder. {% hint style="danger" %} Make sure the folder lies outside `www`. If the path is reachable over `https://`, protected data can be downloaded directly. This must be avoided under all circumstances. {% endhint %} ### File name schema The file name schema determines how files are stored in the folder you selected. You can use plain text as well as the following variables: * `{customerNumber}` — number of the associated customer * `{type}` — for example invoice, offer, credit * `{year}` — year the document refers to * `{documentNumber}` — overall document number * `*` — wildcard, for parts of your file name that are not one of the variables above The default is `{customerNumber}_{type}_{year}_{documentNumber}`, which resolves to for example `10002_invoice_2021_18749.pdf`. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/dr8VaXgtcSGpB0DGVv7O/02%20Document%20archive.png) ## Products ### Hide product prices without login When enabled, prices are hidden until the customer logs in. Guests are also prevented from buying. ### Disable functionality to add line items to shopping card when not logged in When enabled, customers are asked to log in before they can add products to the cart, which prevents guest purchases. ### Show button to switch to list view on product listing page (only when logged in) When enabled, a button is added next to the pagination on listing pages for logged-in customers. It switches between the grid view (the default) and the condensed list view. {% hint style="info" %} The functional cookie `useB2bList` has to be allowed for this setting to work consistently. {% endhint %} ### Only show follow-up articles if sales are activated? When enabled and a clearance sale is running, the follow-up items defined on the product are additionally shown on the product detail page. ### Show product comments globally When enabled, the comment field is shown on all products, regardless of their individual setting. ### Who can see and use product comments? Restricts the comment feature to selected groups: * **Guests** * **Shop customers** * **B2B customers** When no group is selected, the comment feature is globally active. ### Enable time restriction for customer specific prices When enabled, customer-specific prices honour their validity period, so you can define seasonal prices for specific products. For performance reasons the validity period is only evaluated while this setting is switched on. ### Priority for multiple customer prices with the same quantity scale Decides which price applies when several customer prices share the same quantity scale and differ only in their validity period: * **No prioritisation (show all prices)** * **Currently valid price first, undated price as fallback** * **Undated price first, currently valid price as fallback** While a prioritisation is active, prices outside their validity period are never applied. ### Enable hide products query When enabled, products that must not be visible to the current customer are already excluded at query level rather than filtered out afterwards. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/Y96wuCwHgdzvzS3FsLUd/03%20Products.png) ## Checkout ### Show complete payment buttons on order list When enabled, the Euro quick action and the **Complete payment** button inside the order dialog become available, so an open payment can be completed straight from the order list. ### Show note field When enabled, a comment field is shown in the checkout and transferred to the order. The field appears in the last order step and applies to the entire order. It is stored on the order under **Details > B2B Order > Note**, and is available as the custom field `b2b_order_customer_note`. {% hint style="info" %} The setting for comment fields per order position is found under **Catalogues > Products > the desired product > B2B Specifications > B2B Product > Show comment**. {% endhint %} ### Show commission field When enabled, a commission field is shown in the checkout and transferred to the order. It appears in the last order step, applies to the entire order, and is stored under **Details > B2B Order > Commission** as the custom field `b2b_order_customer_commission`. ### Show checkout clear button When enabled, the checkout gains a button that empties the entire shopping cart. ### Enable order confirmation mail recipient selection When enabled, a box lets the buyer select by checkbox which e-mail addresses receive the order confirmation. The Shopware default is the customer's e-mail address. The entries come from the employees of the current customer. ### E-mail recipients of the order confirmation Determines who appears in that list: * **Customer E-Mail** — the e-mail address of the customer. * **Employee E-Mail** — all employees of the current customer. * **Administrator E-Mails** — all employees of the current customer who are administrators. ### Enable Express Checkout When enabled, a button is added to the cart flyout and the cart page that places an order through a single dialog, skipping several confirmation screens. {% hint style="warning" %} After activation you have to whitelist every payment method that should be available for express checkout, under **Settings > Payment methods > Edit details**, where an extra option is added. {% endhint %} Depending on the other options you enabled, the dialog also shows fields such as **Note** or **Commission text**. Buyers can adjust the billing and shipping address, choose payment and shipping method, select a cost center, review the costs, request approval, and submit the order. ### Fallback payment method for Express-Checkout The payment method used if the customer has not selected one in their express checkout settings. ### Enable permanent shopping cart Stores shopping carts beyond a single session, so customers keep their items across sessions, devices and visits. ### Behavior of the permanent shopping cart * **Employee and customer bound** — for each customer, every employee has their own cart, unaffected by colleagues. * **Employee bound with price recalculation** — one employee keeps the same cart across all customers, but prices are recalculated for the respective company. * **Customer bound** — for each customer, all employees share the same cart. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/BU3CS7IwCq0Sn5taHwfH/04%20Checkout.png) ## Registration process ### Register new customer directly as B2B customer When enabled, customers registering in the storefront are declared business customers automatically, which gives them access to the B2B area of the shop. This setting has no effect while the registration request form is active. ### Employee invitation link validity in days How many days an employee invitation link stays valid. Enter a plain number; the standard validity is 30 days. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/jYFmXgXPl8wrh4YlN0pp/05%20Registration%20process.png) ## Registration request by e-mail ### Registration request form instead of registration When enabled, an enquiry form is shown in the storefront instead of a registration form. Customers can no longer register themselves; the shop operator registers them in the system. This is recommended for shop operators who create all customers in their ERP first and transfer them to the shop afterwards. The request is sent by e-mail to the shop operator. ### Trade confirmation in the registration When enabled, a business confirmation can be uploaded during registration. This is only possible in combination with the request form, because the business confirmation is not stored in the customer account. ## Create initial admin employee ### Automatic creation of the first admin employee at customer creation When enabled, the address data entered during registration (e-mail, full name) is used to create the first administrator employee automatically, without any further input. When it is switched off, the person registering is instead asked to create that administrator employee themselves in an additional form. ### Send welcome e-mail on customer creation via API When enabled, a welcome e-mail is sent for the initial employee whenever a customer is created through the API. ### Send welcome e-mail when creating via API only if corresponding flag exists When enabled, the API call is checked for a parameter that decides whether an employee created via API receives a welcome mail. The request has to contain `_sendWelcomeMail`. This only takes effect together with the setting above. ## Platform ### Customer navigation The entry point of the B2B Platform navigation for logged-in employees. The default is **Customer Menu**, maintained under **Extensions > B2B-Platform menu** (`/admin#/b2b/platform_menu`). Selecting a different folder uses that folder as the starting point and shows only the items inside it. {% hint style="danger" %} Customers can only reach items listed in the selected folder. Other elements are not accessible even by URL and return a "403 Permission denied" error. {% endhint %} ### Sales agent navigation Works exactly like the customer navigation, but applies to sales representatives. ### Output orders from all assigned customers When enabled, employees see the orders of all customers assigned to them, regardless of which customer they are currently logged into. ### Cockpit widgets on the dashboard Whether the cockpit widgets also appear on the dashboard page: * **Don't show cockpit widgets** * **Show cockpit widgets above the shopping experience** * **Show cockpit widgets under the shopping experience** ### Target page after login The default page B2B customers are redirected to after logging in and when clicking the shop logo. Any entry of your B2B Platform configuration can be chosen. Employees can override this for their own account. ### Target page after login into employee as sales representative The same default for the case that a sales representative has logged into an employee account. Sales representatives can override this for their own account. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/8h3rAqjjrq0copr0USz9/06%20Platform.png) ## Shopping Experiences ### Customer-Dashboard Shopping Experiences The Shopping Experiences layout shown to B2B customers on the dashboard at `/b2b_platform`. ### Sales-Representative-Dashboard Shopping Experiences The Shopping Experiences layout shown to sales representatives on their dashboard. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/7wmNns6OfPkhNgPf7a8h/07%20Shopping%20Experiences.png) ## Fallback contact person If a customer has not been assigned a contact person, a fallback contact person is displayed. These fields customize the left side of the customer menu that opens when clicking the avatar icon: **Name**, **Department or company**, **E-mail address**, **Phone number** and **Fallback profile picture**. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/8ANv7bc7UOhn9ONmuwLd/08%20Fallback%20Contact%20Person.png) ## Passwordless login ### Validity (minutes) How many minutes a passwordless login link remains usable before it expires. Enter a plain number. ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/ISLqGSQKkYvl9lbmUlhC/09%20Passwordless%20Login.png) ## Customer activity ### Track customer activity When enabled, additional data is collected and made available to sales representatives at `/b2b_platform/customer-activities`. Customers can always deactivate this for themselves in their account settings. The data includes: * product viewed * product added to cart * order placed * offer created, viewed and so on * logged in and out ![](https://content.gitbook.com/content/N7trivXBQb3doKIrPW2i/blobs/rPPPjw7ltq9C9iO1bv5A/10%20Customer%20Activity.png) ## Usage statistics & product improvements The B2Bsellers Suite can share configuration and usage data to help improve the product. ### Allow sending B2Bsellers Suite configuration settings When enabled, the configuration of the suite is transmitted. ### Allow transmission of usage statistics When enabled, anonymous usage statistics are transmitted. See [Statistics for Product Improvements](/b2b-platform/user-guide/configuration/statistics-for-product-improvements.md) for details on what is collected. ## Barcode search ### Enable barcode scanner in search When enabled, the storefront search offers a barcode scanner, so products can be found by scanning a barcode with the device camera. --- # 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/plugin-konfiguration.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.