Shopware 6 B2B Guide: Roles, Approval Workflows, Pricing Rules & Company Accounts

What is Shopware 6 B2B?

Shopware 6 B2B is the ability to run account-based purchasing: one company, multiple users, controlled permissions, approvals, and pricing logic that matches real commercial agreements. The modern direction is B2B Components (rather than relying on the legacy B2B Suite).

In practical terms, a Shopware 6 B2B setup usually includes:

• Company accounts (one business entity, many users)
• Role-based access (who can buy, approve, see prices)
• Order approval workflows (review before checkout)
• Pricing rules (group pricing, contract pricing, tiered pricing)

External reference: Shopware B2B Components overview

Company accounts in Shopware 6

The foundation is the company account. Instead of one user acting alone, a company has multiple employees (buyers, managers, finance) purchasing under shared rules, addresses, and history.

A good company account model typically includes:

• Company profile (billing identity, tax/VAT context, default addresses)
• Multiple users linked to that company
• Shared order history for reorders and account-level reporting
• Clear “who does what” inside purchasing

Example: A distributor customer may have 6 buyers placing replenishment orders weekly, but only 1 procurement manager allowed to approve orders above a threshold.

Roles and permissions (role management) in Shopware 6 B2B

In B2B, permissions protect both sides. Customers avoid policy violations, and you avoid chargebacks, credit issues, and “oops” orders. Shopware supports role management so each employee account has the right level of access.

Common roles you’ll model:

• Buyer: can create carts and submit orders
• Approver: can approve/reject based on rules
• Company admin: can manage users and addresses
• Finance: can access invoices and documents

Example: Buyers can check out up to €1,000; above that, orders must be approved by the “Purchasing Manager” role.

Want Shopware-native role patterns and concepts? We often pair this with a lightweight permissions blueprint during delivery. You can also explore our Shopware plugins if you need extensions around purchasing UX.

Approval workflows in Shopware 6 (how approvals work)

Approval workflows are essential when customers have budgets, cost centers, or compliance requirements. A clean approval process reduces purchasing friction because it matches internal reality instead of forcing workarounds.

1. Buyer creates an order and submits it for approval.
2. Approver reviews and approves or rejects.
3. Approved orders proceed to checkout and fulfillment.

Example triggers: approval required if order total exceeds €1,000, if a restricted category is included, or if the buyer role is “Junior Buyer”.

External reference: Shopware order approval entities & workflow

B2B pricing rules in Shopware 6 (customer-specific pricing)

B2B pricing is rarely one fixed catalog. You’ll usually need a mix of: contract pricing per customer, tiered pricing per quantity, and rules based on customer groups or regions.

The best approach is to keep pricing logic rule-driven and integration-friendly, so you can sync negotiated prices from ERP/PIM without hardcoding discounts in templates.

• Customer group pricing: wholesale vs reseller vs key account
• Contract pricing: company-specific price lists
• Tiered pricing: quantity breaks for repeat orders

Example: “Resellers get net pricing + tier discounts on consumables, but spare parts keep standard margin unless the order quantity exceeds 20 units.”

External references: Shopware Rule Builder documentation and Shopware customer-specific pricing feature

Why Shopware 6 is a strong fit for EU & DACH B2B brands

Shopware is widely adopted in Europe, and many EU B2B brands choose it when they need flexible workflows, multi-language selling, VAT-aware operations, and integration-ready architecture for ERP and PIM.

Example: A DACH manufacturer selling in DE/AT/CH can run one platform with localized language, tax handling, and account-specific pricing while keeping one shared product and integration backbone.

Extended Shopware 6 B2B features you should plan for

Once roles, approvals, company accounts, and pricing rules are in place, most B2B brands expand into “day-2” capabilities: quotes, quick ordering, self-service portals, returns, and deep ERP/CRM/PIM integrations. This is where Shopware 6 becomes a true B2B platform instead of a catalog with login.

Quote management and RFQ handling

Many B2B orders start as a request, not a checkout. With Shopware’s Quote Management, buyers can request a quote from the cart and merchants can review, adjust, and send quotes back for acceptance, turning negotiations into a trackable workflow instead of email chains. See the official documentation: B2B Components overview and Quote Management (developer docs) .

Custom pricing engine and contract-style pricing

“Custom pricing engine” in B2B usually means a blend of rule-based pricing (discount logic), customer-specific price lists, and contract terms (validity windows, tier breaks, negotiated SKUs). In Shopware 6, the scalable approach is to keep the rules clean and feed contract pricing from ERP/PIM where possible, rather than hardcoding exceptions.

If you want a blueprint for customer-specific and contract pricing in Shopware, MageSpark can help you design the rule model and integrations: Shopware development.

Customer portals with self-service tools

B2B customers expect self-service: managing users, addresses, saved carts/order lists, reorders, invoices, quotes, and approval status without calling sales. The account area often becomes a lightweight “portal”. The best implementations keep it fast, mobile-friendly, and aligned to the customer’s actual workflow (buyers vs approvers vs finance).

Multi-level approval workflows

Approvals are rarely one-step in enterprise accounts. Multi-level approvals typically require thresholds, category rules, and escalation paths (e.g., team lead → procurement → finance). Shopware’s order approval component supports rule-driven approval logic and role-based permissions. Reference: Order approval component .

Bulk ordering and quick order tools

Bulk ordering is a conversion lever in B2B. Instead of browsing categories, repeat buyers want a fast SKU/quantity input, CSV import, and “reorder” flows. Shopware’s B2B Components include Quick Orders to reduce friction for replenishment purchasing.

Inventory synchronization and advanced order tracking

Real-time stock, ETA, split shipments, and order status updates usually depend on your ERP/WMS and shipping stack. Shopware provides the commerce layer, but the “truth” often lives in operations systems. Plan this early: define which system owns inventory, what “available” means, and how status events flow back to the customer portal.

Return and RMA handling

Returns are not just B2C. B2B returns often include authorization, reason codes, partial returns, and credit notes. Shopware offers returns management as part of its commercial features (plan dependent). See: Returns management documentation .

Multi-currency, multi-language, and mobile-optimized B2B UX

Multi-language and multi-currency are table stakes for EU and cross-border B2B. The ranking and conversion advantage comes from execution: localized pricing display (net/gross), clear tax logic, and mobile-first quick ordering and approvals. If your buyers approve orders on phones, the approval and quote flows must be fast and simple.

ERP, CRM, and PIM integration capabilities

For most serious B2B stores, integrations decide success. Typical patterns include: ERP for pricing + inventory + order export, PIM for product data quality, and CRM for account context. If you’re planning integrations, we recommend mapping data ownership, sync frequency, and failure handling up front (especially for pricing and stock).

If you want a practical implementation plan (roles, approvals, quotes, quick order, and integrations) tailored to your business, MageSpark can provide an architecture sprint and implementation roadmap: Talk to MageSpark.

Best-fit industries for Shopware 6 B2B

Shopware 6 is not a generic B2B platform. It performs best in industries where purchasing involves structured accounts, repeat orders, negotiated pricing, and system integrations.

• Manufacturing: spare parts, consumables, dealer portals
• Wholesale & Distribution: tiered pricing, bulk ordering, reorders
• Industrial Equipment: approval-based purchasing, contract pricing
• Automotive & Mobility: part catalogs, VIN/SKU-based ordering
• Healthcare & B2B Supplies: compliance, role-based buying

If your customers purchase on behalf of a company rather than as individuals, Shopware’s account-based model becomes a strategic advantage.

Shopware B2B vs other ecommerce platforms

Choosing a B2B platform is less about features and more about flexibility and long-term ownership. Shopware 6 occupies a middle ground between rigid SaaS tools and over-engineered enterprise stacks.

• vs Shopify Plus: more control over pricing, workflows, and approvals
• vs Magento (Adobe Commerce): lighter architecture, faster execution for mid-market B2B
• vs SAP Commerce: significantly lower complexity and total cost of ownership

Shopware is often chosen when B2B brands need customization without locking themselves into a heavy enterprise ecosystem.

When Shopware 6 excels for B2B commerce

Shopware 6 performs exceptionally well when business requirements go beyond standard catalog selling but do not justify enterprise-grade overhead.

• Multiple buyers per account with approval rules
• Customer-specific and contract-based pricing
• ERP-driven inventory and pricing logic
• EU-centric compliance, VAT, and localization needs
• Custom B2B portals and self-service workflows

In these scenarios, Shopware offers the best balance between flexibility, performance, and maintainability.

Industry use cases and proof points

Successful Shopware B2B implementations usually follow clear, repeatable patterns.

Wholesale distributor: Quick order tools, tiered pricing, and reordering flows reduce sales friction and move volume online.

Manufacturer: Spare part portals with approvals and ERP-driven stock visibility replace manual order processing.

Regional B2B brand: Multi-language storefronts with localized pricing and VAT logic support cross-border EU sales.

How to set up a high-performance Shopware 6 B2B store

Performance in B2B is not just page speed. It’s operational performance: fewer errors, faster approvals, and less manual work.

1. Define company roles, permissions, and approval thresholds
2. Design pricing rules and contract logic before development
3. Plan ERP, PIM, and CRM integrations early
4. Optimize quick order and reorder UX for repeat buyers
5. Test mobile approval and ordering flows

A structured setup phase saves months of rework later.

Shopware B2B best practices from MageSpark

From real-world B2B projects, a few principles consistently separate successful implementations from painful ones.

• Model business rules first, features second
• Keep pricing logic centralized and auditable
• Design portals for real buyer behavior, not demos
• Integrate ERP systems as data owners, not afterthoughts
• Optimize for repeat orders, not first-time buyers

MageSpark focuses on building Shopware B2B systems that scale operationally, not just technically.

Common mistakes when implementing Shopware 6 B2B

• Implementing features before defining rules: approvals and roles must match the real buying process.
• Over-customizing too early: start with clean rule design, then extend only where needed.
• Hardcoding pricing: use Rule Builder + customer-specific pricing models for scale.
• Ignoring integrations: ERP/PIM decisions should shape product, customer, and pricing data flows.

If you want a quick sanity check, we can review your requirements and provide a short implementation blueprint. Start here: Contact MageSpark.