Customer & tiered pricing
Individual prices per customer, group and quantity, shown correctly everywhere.
// Growth · B2B
B2B portals built for how you sell
Role-based catalogues, tiered and customer-specific pricing, quotes and company accounts — the B2B features wholesale and industry actually need.
// What you get
B2B features we implement
Company accounts
Multiple buyers, roles and budgets under one company account.
Quote & offer flows
Request-for-quote and offer approval workflows that fit B2B.
Fast reordering
Order lists, quick order and reorder for repeat B2B buyers.
Punchout & procurement
Connect to customer procurement systems via punchout where needed.
Restricted catalogues
Show each customer only the products and prices they're allowed to see.
// Why it matters
E-commerce that respects B2B rules
B2B buying is not B2C with a higher price — it has contracts, tiered pricing, approval flows and company structures. Codewerk Solutions builds Shopware B2B portals with role-based catalogues, customer-specific and tiered pricing, quote flows and company accounts. We use the Shopware B2B Suite where it fits and build custom logic where it doesn't.
The result is a portal that matches how your customers actually order — reducing manual quoting and phone orders, and making it easy for business buyers to purchase from you again and again.
// In detail
Technology, performance and SEO
What we actually do under the hood — so you can judge the work, not just the promise.
Technology & architecture
Customer groups for tiers, contract prices synced from the ERP for individually negotiated customers, scale prices, and the Rule Builder used sparingly and named clearly. We decide explicitly which system is the master of prices — the shop or the ERP — because shops that never answer that end up with two prices for one product.
B2B workflows
Order approvals across a buying team, budgets and cost centres, quote requests, quick order by article number, CSV upload, reorder from history, and credit limits. These unglamorous features are what decide whether a buyer comes back next month.
Security & access
Roles that mirror your customer's org chart, 2FA on accounts that can place orders, and a hard rule that customer-specific prices never touch a shared cache — because that is exactly how pricing leaks between customers.
// FAQ
Frequently asked questions
Yes, and for individually negotiated customers that is usually the right architecture: the ERP owns the price, the shop displays it, and a middleware keeps them in sync with retries and an audit log.
Yes — the display mode is tied to the customer group and tested with a real customer login before launch. Getting this wrong does not just look unprofessional, it creates invoice disputes.
Sometimes. For approval workflows and buyer hierarchies they save real effort. For simple customer-specific pricing, customer groups and contract prices are often enough — and cheaper. We tell you which case you are in.
Let's talk about your project
Send a short brief — we reply within one business day.