39 results found
-
external order id / externe Auftragsnummer
EN:
In B2B, it is common practice for the purchaser to provide an external order number to ensure matching within customer accounting. Therefore, an optional field with “external order number” should be possible in the shop when placing the order (can be switched on/off in admin and per channel). This should be displayed in the order overview for the customer when logged in.DE:
Im B2B ist es üblich eine externe Auftragsnummer seitens des Bestellers zu übergeben, um das matchen innerhalb der Kundenbuchhaltung zu gewährleisten. Daher sollte ein optionales Feld mit "externe Auftragsnummer" im Shop bei der Bestellabgabe möglich sein…17 votes -
B2B Components: allow modification of Employee invite timeout
Currently there is a hard coded timeout of 2 hours when employees are invited into an organization in B2B Components. Shop owners and potentially customers should be able to modify this time to fit their needs.
13 votes -
Option for B2B Components order related mails send to customer Orga employee mail
In B2B environments, orders are often placed by employees acting on behalf of their organization. Currently, Shopware sends order confirmation emails only to the primary email address of the customer account (Main Account).
However, in many cases, it is desirable for the employee who submitted the order to also receive — or solely receive — the order confirmation email or documents.
To address this, a new configuration option should be added to the customer or organization settings, allowing administrators to define the default behavior for order confirmation emails.
Functional Proposal:
Add a setting in the B2B customer configuration:
Option A:…
12 votes -
OCI punchout support
More and more our B2B customers want to connect their ERP or ecommerce platform via merchants onlineshop per OCI punchout.
So we need OCI (version 4.0 and 5.0) support directly in Shopware.
12 votes -
B2B: Template for employees and their roles
As a shop owner, I want to be able to define a set of employees and their roles. Set A: "Quick Order" and "Quote Management"; set B: all B2B components, for example. Maybe it could be combined with the Rule Builder: if rule A is true, set A.
12 votes -
Allow approvers to edit orders in B2B-Approval-Workflows
Problem Description:
In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.
Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.
This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.
Current Behavior:
When an order requires approval:
- The approver can only approve or reject the order
- The approver cannot:
- Change product quantities…7 votes -
B2B: allow defining and using of multiple VAT IDs per customer account
Currently, only one VAT ID can be defined for a customer. This may be undesirable for some companies that are tightly related to other legal entities or have sub-companies they want to create orders for. In that case, multiple customer accounts would need to be created for proper invoicing.
The database structure already has a field to store a VAT ID with an address, so it would be useful to allow saving different VAT IDs depending on the address, so that customer can choose them during checkout.
7 votes -
Hide Price and Add to Cart Button – Show “Request Quote” Only
In B2B scenarios, it is often necessary to offer products without displaying prices or allowing direct purchases. I propose adding a feature to the B2B Components that allows specific products to be configured so that the price and “Add to Cart” button are hidden. Instead, only a “Request Quote” button should be displayed.
This would enable merchants to:
Offer products where prices are negotiated individually.
Streamline the quoting process for high-value or custom items.
Improve compliance with B2B pricing strategies and contractual agreements.The configuration should be product-specific and easy to manage via the admin panel, ideally with bulk selection…
7 votes -
B2B Components: Assign existing account to company account
Shop owners occasionally report that the unusual process of registering as a B2B employee leads to them signing up normally through the frontend which creates a bit of a mess.
It would be helpful if we provided the functionality to assign normal customers as employees to a B2B enabled company account as this would save effort for everyone involved.
Taking this idea further and to avoid unnecessary manual action for shop owners, we could implement this feature for the B2B account itself so THEY can invite existing (already registered) accounts to their company and integrate them into the B2B structure.…
6 votes -
Multi-user support for customer service representatives – login as any company employee in a B2B environment
In B2B transactions, customer service representatives regularly handle and process orders on behalf of customers, especially for telephone orders or orders requiring extensive consultation.
Currently, they log in to the backend with administrator rights and then use the "Log in as customer" function in the frontend to place orders directly in the shop or to assist customers with their use.
However, this approach currently only works for the primary user of a company account.
In cases where a customer uses multiple employee accounts within a company structure, it is not possible to log in as another employee of that company…
5 votes -
Add exceptions for Tax-free (B2B) option
Currently, a shop owner can decide based on the country of delivery if a B2B order with a valid VAT No. may be taxed or not. However, in some constellations the decision must be made based on the VAT No. as well.
Example:
German customer with German VAT No. orders something to the Netherlands. When the country settings for NL have the “Tax-free (B2B)” option checked, VAT will not be charged. However, since the customer is a Germany based company with a German VAT No., an order like this does not count as an intra-EU supply but as a supply…5 votes -
Support for Spanish NIE Numbers in VAT/Tax ID Validation
In the merchant registration form (e.g., via the B2B Suite or customer registration), Spanish NIE numbers are currently rejected as invalid VAT/Tax IDs. However, the NIE (Número de Identidad de Extranjero) is the official fiscal identification number for foreigners in Spain and is accepted by the Spanish tax authorities.
A valid NIE follows this format:
Starts with X, Y, or Z → 7 digits → ends with a letter
Example: Y5432178PCurrently, the validation logic does not accept such values, blocking legitimate registrations from Spain-based users.
5 votes -
Support promotions / discounts in when requesting a quote
Currently, you cannot request a quote as long as there is an active promotion in your cart.
5 votes -
B2B checkout: Order reference and deliverydate
SW6 B2B Component should have same functionality as the previous B2B-suite. In Order process (checkout) merchants should have form-fields for own Order-Reference and wishes for the delivery-date.
(order.customFields.b2bOrderReferenceHolder, order.customFields.b2bDeliveryDateHolder)
5 votes -
Inheritable category and menu visibility in organizational units (B2B)
Currently, category and product visibility settings can only be explicitly configured per category within organizational units.
When a parent category is selected, the subcategories beneath it are not automatically included.
This leads to the following problems with extensive category structures (several hundred subcategories):
- very high manual maintenance effort
- increased susceptibility to errors
- poor maintainability when structural changes are made
- limited scalability in a B2B contextIn addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.
Target Image:
- Selecting a parent category…4 votes -
B2B Components: Include divergent mail addresses in search results
Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.
For example:
Our B2B root account is company@example.com.
Our employee's mail address is employee@shopware.com.Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.
So the request is to have an option to index employee mail addresses and associate them with…
4 votes -
Add Custom Text Field per Cart Line Item (B2B Commission Feature)
Would be great to have a feature within the Shopware 6 - B2B Components that allows B2B customers to add a custom text field for each cart line item (like a Commission). This enhancement aims to improve flexibility and support B2B customer-specific internal processes during order creation.
In many B2B scenarios, customers need to add additional information for each product in their shopping cart — for example, internal article numbers, project references, delivery notes, or other customer-specific comments. Currently, there is no native option to capture such information directly at the line-item level.
4 votes -
Create shopping lists out of the cart overview
As a merchant/customer, I now have the ability to add items to my wishlist in the cart overview but not to a shopping list.
Adding the ability to add items to a shopping list right out of the cart would be beneficial.4 votes -
Commercial: improve organization units for shopping lists
Currently, the organization unit field on shopping lists is purely an informational indicator from which unit the list was originally created.
The following improvements should be added to give this more utility:
- The OU field should be definable during creation (i.e. by admins or the customer account) and changeable / re-assignable afterwards when needed.
- Role permissions should be added that define which lists from which OU an employee can see - this allows better separation between units which should not see lists from other departments.
3 votes -
Let B2B Employees changed their own password
It should be a standard functionality that a user can change their password.
This is currently not possible.
Please implement this.
3 votes
- Don't see your idea?