When one shared login is no longer enough
Picture this: a buyer at one of your key accounts accidentally orders three times the approved budget because every employee shares the same shop login. No approval, no cost centre, no limit. The invoice lands on the accounting team's desk and triggers a chain reaction that you as the supplier did not cause, yet still feel.
This situation is anything but rare. Recent studies show that B2B buyers switch suppliers when ordering processes become too cumbersome or too error-prone. Employee accounts in a B2B shop are therefore not a technical detail, they are a tangible sales argument.
With Shopware 6.7.13, complex purchasing organisations can now be modelled through B2B Components without custom development: multi-level approvals, order budgets, roles and permissions, and so-called multi-context employee accounts, where one user can buy on behalf of several companies or departments. This guide shows how to use these functions sensibly, structured around five concrete rules.
Rule 1: Model the real purchasing organisation, not a shared login
The most common problem in B2B shops is a single company login shared by several employees. Order histories blur together, responsibilities become unclear, and approvals are simply impossible because nobody knows who placed which order.
The right approach is to mirror the actual organisational structure. Shopware B2B Components allow customers to be set up as company units, with individual employee accounts assigned to those units. Each person receives their own login, linked to their role and permissions.
In practice this means:
Buyers, team leads and approvers receive separate access
Orders are clearly attributable to one user
Reporting and invoicing become traceable
Employees who leave the company can be deactivated individually
Benefit: Transparency on both sides. Your customer keeps control over internal processes, and you as the supplier reduce follow-up questions and sources of error.
Rule 2: Cut roles and permissions by task, not by hierarchy
A classic mistake: roles are assigned by seniority. The department head gets every permission, the clerk almost none. In practice this forces department heads to handle operational tasks because their staff simply cannot place orders.
Roles should instead be defined around tasks. Three basic roles have proven themselves in practice:
Orderer: May add products to the cart and place orders, but only up to a defined value threshold
Approver: Receives approval requests and can confirm or reject orders without having to order themselves
Administrator: Manages accounts, budgets and roles within the company account
Shopware B2B Components allow granular permissions per role, for example whether a user may request quotes, view invoices or change addresses. These settings should be discussed with the customer during onboarding rather than being defined alone in the back end.
Benefit: Less coordination effort, clearer processes and a shop that supports your customer's internal workflows instead of blocking them.
Rule 3: Define order budgets and value thresholds bindingly
Budgets in a B2B shop are more than a technical barrier. They translate your customer's internal purchasing policy into the digital channel. Without this function, a B2B shop is simply unusable for many companies because the finance department has no control.
Shopware B2B Components make it possible to store budgets at user or role level. The following structure works well:
Single order value threshold: Above which amount does an order require approval?
Period budget: How much may a buyer spend per month or quarter?
Team budget: Does a shared budget apply to a department, or does each user have their own?
It is important that budgets are not communicated as a signal of mistrust. They are a service. Your customer can give staff more autonomy precisely because clear guard rails exist. At the same time, you as the supplier reduce cancellations and reversals caused by unapproved orders.
Benefit: Predictability for the customer, less operational friction for you.
Rule 4: Design approval workflows so they do not become a bottleneck
A multi-level approval workflow may sound like bureaucracy. In practice it is the opposite: it replaces email chains, phone calls and handwritten signatures with a structured, traceable process.
The most common mistake with B2B approval workflows is a chain that is too long. If an order has to be approved across three levels of hierarchy, it takes days and the buyer reaches for the phone instead. The following is therefore recommended:
A maximum of two approval levels for standard orders
Automatic approval below defined value thresholds
Clear escalation rules when an approver does not respond, for example after 48 hours
Email notifications for approvers with a direct link to the approval
Shopware B2B Components map this logic natively. The B2B approval workflow can be configured individually per company account, so a large customer with a complex structure receives different rules than a smaller dealer.
Benefit: Faster order lead times, fewer media breaks and a process buyers actually want to use.
Rule 5: Carry the customer's cost centres and order numbers through
This point is underestimated in many B2B shop projects, even though it determines customer acceptance. Accounting and purchasing departments work with internal cost centres, project numbers and their own order numbers. If this information cannot be captured in the shop, the buyer has to supply it later by email, or the invoice cannot be allocated internally.
The solution is simple: mandatory or optional fields in the checkout process where the customer can enter their own reference. This data is then passed to the ERP system and appears on the invoice.
The following fields are recommended in practice:
The customer's internal order number, often referred to as a PO number
Cost centre or project number
Delivery address with a contact person at department level
Free text field for internal notes
This information has to flow cleanly into the ERP handover. A shop that transfers order data to the ERP completely and in a structured way significantly reduces manual rework on both sides.
Benefit: Smooth invoicing, fewer queries, higher customer satisfaction and a clear efficiency gain in order processing.
What often goes wrong: three typical pitfalls
Even with the right functions, avoidable mistakes occur in practice. The three most common:
Onboarding is skipped. Employee accounts and roles are created in the back end but never explained to the customer. The result: staff keep using the old shared login or simply call instead.
Budgets are set too restrictively. If every second order needs an approval, acceptance collapses. Start with generous thresholds and adjust afterwards.
The ERP handover is planned too late. Anyone capturing cost centres and order numbers in the shop must ensure those fields actually arrive in the ERP. This should be verified before go-live, not discovered afterwards.
Conclusion: structure builds trust
Employee accounts in a B2B shop are not a feature reserved for large corporations. They are the difference between a shop buyers use daily and one that is quietly abandoned after three months. Roles and permissions in the B2B shop, clearly defined order budgets and a lean approval workflow turn a digital catalogue into a genuine sales channel.
With version 6.7.13, Shopware B2B Components provide a solid foundation that works without custom development. What matters, however, is not the technology alone but the care taken during setup and the understanding of the customer's purchasing processes. Those who invest here gain customer loyalty while reducing their own effort in order processing.
Do you have specific questions about your setup, or would you like to know which configuration makes sense for your customer structure? Get in touch.
