That's precisely what this is about: building tiered pricing, quantity discounts, and customer groups in a way that is logical, maintainable, and doesn't inadvertently put your margins on a diet. The goal isn't to make everything maximally complicated, but to translate your customers' reality into clear pricing rules so that buyers don't have to do calculations, sales has fewer special cases, and you don't have to frantically search for price lists during peak periods.
If, by the end of this article, you have a pricing logic that you can explain in two minutes, then your setup is strong because it will still be understood in six months. For the technical basis, it's worth taking a look at the Shopware documentation, because that's where the mechanics surrounding... customer-specific pricing This is explained, which often makes the difference in B2B setups as soon as you start working with login prices or ERP conditions.
Why B2B pricing works differently than B2C pricing
In B2C you often buy by feeling, in B2B you buy according to need, by list, by process, and things like carton quantity, pallet, delivery frequency and order value limits usually count more than a pretty percentage.
Many buyers don't think in terms of a single product, but rather in bundled packages of requirements; therefore, a price only works well if it is predictable, if it fits the purchasing logic, and if it remains reliable without further inquiry.
Typical B2B questions your shop needs to answer without someone submitting a ticket: From what quantity does it become cheaper, does this apply to all variants, does this apply to my customer group, does the quantity count across multiple items, and what happens if I narrowly miss the next level?
If you answer these questions with clear rules, you'll gain speed, less friction in the checkout process, and significantly fewer "Can you just...?" messages from sales.
The three building blocks you can use to control B2B prices in Shopware
You can think of it like a modular system, where each component has a specific task: tiered pricing rewards quantity per product, quantity discounts control behavior via the shopping cart or groups of items, and customer groups define who sees which price range and which rules apply.
If you clearly separate these tasks, the whole thing becomes surprisingly manageable, even with many products and multiple customer types.
1) Tiered pricing when the quantity depends on the individual product
Tiered pricing is suitable when the quantity purchased of a specific item is crucial, for example with consumables, spare parts, packaging, or anywhere you have clear quantity jumps.
The pattern is simple but effective: You set levels that match purchasing behavior, and you make the benefit visible so that the next level seems like a small, realistic incentive, rather than a mathematical puzzle.
Three to five levels are often sufficient, because each additional level requires maintenance, and maintenance is often pushed aside in daily business until it catches up with you at the worst possible moment.
2) Quantity discounts when the quantity is spread across multiple items
Quantity discounts are your tool when quantity depends not only on a single product, but on a group, a category, variants or a purchasing requirement, for example, when a project price should apply from a total quantity of 30 pieces, regardless of whether it's red, blue or black.
This allows you to control not only individual items, but also to guide the shopping cart, because the customer realizes that it is worthwhile to complete the order in one go.
The logic is important here, otherwise you'll be giving a discount in the wrong place: You define what counts, for example quantity in category X, quantity in manufacturer Y, quantity in day Z, or you link it to the shopping cart value if the order value is more important to you than the quantity.
A clear quantity discount is like a railing; it guides the customer through the purchase process without them getting lost.
3) Customer groups when conditions are linked to the buyer
Customer groups are the foundation because they answer the question of who is allowed to see which rules, and in B2B this is often more important than the actual discount level.
Retailers, major customers, key accounts and regular business customers have different terms and conditions, payment methods, minimum order values and sometimes even different product ranges, and you don't want to cover that up with ten special rules, but rather map it clearly using groups and priorities.
When considering customer groups, don't just think about prices, but also about access and display: Who is allowed to see the net price, who sees the gross price, who has to register, who needs activation, and who only gets certain payment methods after verification.
If you clarify this upfront, you'll save yourself the typical headaches later on when someone suddenly says, "But we already gave customer X a net price," while your shop is openly online.

B2b shopware Tiered pricing – Shopware – for retailers, developers and customers – 🛒How to cleverly manage tiered pricing, quantity discounts, and customer groups in Shopware B2B shops🧮
Plan your customer groups before you update prices, so you don't create a discount graveyard.
The most common mistake is to enter prices first and only then consider which groups actually make sense, because then the groups end up being named after individual cases and nobody recognizes what they stand for anymore.
Do it the other way around: You define a small, clear set of groups that reflects the real customer types, and for each group you determine which differences are truly relevant.
A pragmatic starter setup that works in many B2B shops without immediately becoming excessive: Standard B2B for normal business customers, dealer for resellers, large customer for high volumes, key account for negotiated terms, and optionally employees for internal purchases, if that is even necessary for you.
After that, the rule is: only expand if you have a recurring case that cannot be neatly squeezed into the existing groups.
If you are unsure whether a customer needs their own group, use the following test question: Does only the price change, or does access, payment, delivery and product range also change?
If price is the only concern, a customer-specific price or a targeted rule is often better than a new group, because every new group later generates maintenance costs that no one anticipates.
A pricing strategy that you can implement in Shopware without losing track of things later.
For tiered pricing and discounts to really work, you need a clear intention; otherwise, you'll be handing out discounts like confetti and wondering why your profit margin has suddenly disappeared.
Start with a simple logic: reward volume increases that reduce your costs, reward shopping carts that simplify processes, and reward customer types that bring you predictable volume or low service costs.
Three typical goals that you can formulate as clear rules: More quantity per item through sensible tiered pricing, more items per order through quantity- or value-based shopping cart discounts, and less sales effort through login pricing where the customer can directly see their terms and order without asking.
When you translate these goals into rules, pricing suddenly becomes a system, no longer just a gut decision.
Technical setup, so your pricing remains maintainable
In small shops, prices can be maintained directly on the product page, but in B2B this quickly becomes too slow because the product range and terms and conditions grow, and you would otherwise end up with duplicate data maintenance as soon as an ERP or... CRM is involved.
Therefore, the best order is usually: First, create customer groups cleanly, then define rules, then maintain tiered prices where they are truly product-logical, and solve special conditions via customer-specific prices or imports if you have many individual deals.
When working with rules, document them briefly, ideally with a one-liner per rule, so that you will know later why they exist, because “it’s always been this way” is not a tech argument, but a ticket to price hell.
In many teams, a small internal table containing the name, target, group, validity, and trigger is sufficient, because this information is invaluable later in support cases.
In the middle of your setup, it's worth taking a look at official information on the Price Indication Ordinance , because especially with open shops, questions about net, gross and price display quickly arise, and a quick comparison saves discussions.
Setting tiered pricing correctly ensures it generates revenue and doesn't create support cases.
A good tiered pricing strategy does two things at once: It is easy to understand and it is financially sound because it reflects the reality of your costs, so pick, PackingShipping, payment fees and return risk.
You don't want a series that looks great, but where you start making a loss from the second stage onwards because logistics costs for small items are more of a burden than you thought.
Here's how to set proven price tiers: Use round quantities that fit the carton, bundle or pallet, clearly show the tiers on the product, and give a clear indication of the quantity at which the next price applies, so the buyer doesn't have to guess.
If you have product variants, carefully check whether the tiered pricing should apply per variant or across all variants, because this is exactly where many B2B shops inadvertently create the wrong incentives.
Here's an example you can replicate directly: You sell adhesive tape, cardboard in packs of 36 rolls, and your customers typically order 36 or 72. Then, if you set increments at 1, 36, 72, and 144, you'll see that the 36-roll increment often acts like a magnet because it triggers the "cardboard" thought in the mind.
If you also clearly communicate whether the price displayed is net or gross, you will have fewer questions and fewer misunderstandings during checkout.
Quantity discounts via category or shopping cart, so you promote demand instead of individual items.
Quantity discounts work particularly well when customers buy in supply chains, i.e. not “one product”, but “everything for maintenance”, “everything for the project”, “everything for the month”.
You can then use rules that only apply to certain categories, so that discounts don't accidentally devalue premium products that you actually want to protect.
Practical example: In the cable tie category, every variant counts; from 50 pieces there is a 6 percent discount, from 200 pieces there is a 10 percent discount, and this only applies to the retailer group, because otherwise end customers would suddenly see a wholesale logic that doesn't suit them at all.
This is exactly how you manage B2B “cleverly”, because you reward quantity, but define the framework within which quantity counts.
Another tip that is often underestimated: Use minimum order values or minimum quantities per group if handling small orders is expensive, because this protects you without having to work with aggressive discounts.
Many shops save themselves a discount level because instead of “more discount” they prefer to use “higher minimum quantity”, and that is often the cleaner solution.
Customized pricing when sales and ERP require genuinely special conditions
Once you have framework agreements, project prices, or customer-specific item prices, manual maintenance in the shop quickly becomes dangerous because you end up with duplicate data maintenance and every import error ends up directly in the shopping cart.
Here's the better strategy: Prices come from the leading system, the shop displays them correctly after login, and you define clear priorities so that special prices override group prices, but not vice versa.
Pay attention to four things that will save you a lot of stress later: validity periods so that prices don't run indefinitely, clear assignment of customer to price, clear assignment of item to price, and a fallback that kicks in if a price is missing so that the shop doesn't work with zero prices or incorrect standard prices.
If you like, you can also work with test customers per group who cover exactly the most important cases, because then you Updates and be able to review new rules in minutes.
Net, gross and visibility: how to avoid typical B2B pitfalls
Many B2B shops want to display net prices because it is more practical for purchasing; however, the crucial question is whether your shop is really only accessible to businesses, or whether it is open on the internet, because visibility changes the requirements for price display.
This isn't a big deal, but it's something you should consciously decide on, because simply saying "we're B2B" doesn't automatically solve all the problems.
For a clear and understandable classification, information from chambers of commerce is often helpful because they collect typical cases from practice, for example on price indications and labeling in online commerce.
UX tips to ensure B2B buyers actually use your discounts, even on mobile devices
B2B users often buy on the side, in the warehouse, in the car before the appointment, on the tablet in goods receiving, and that's exactly why the pricing logic must not only be correct, but also quickly grasped, otherwise the user takes a screenshot, sends it around internally, and then the order takes another two days.
They want price levels and discounts to be visible, for it to be clear which rule currently applies, and for the next benefit not to be hidden, but to act like a small, clear invitation.
What works really well in practice: A compact overview of the discount tiers on the product, a note in the shopping cart such as “8 more pieces until the next tier”, a clear indication of net or gross price directly on the price, and a short explanation of why a discount applies, so that buyers don't have to discuss it internally.
If you use a slightly cheeky tone, please make sure it's helpful, for example "8 more pieces and it gets cheaper", because that's motivating without seeming silly.
Typical mistakes you can avoid by setting priorities
Most pricing problems arise not because Shopware is incapable of doing something, but because rules overlap and no one has clearly defined which price wins when two things apply simultaneously.
Therefore, establish a clear hierarchy, for example: customer-specific price beats group price, group price beats discount rule, discount rule beats standard price, and promotions are either at the very top or very clearly limited so that they do not accidentally overwrite everything.
Two other classics: tiered pricing that doesn't match packaging units, and discounts that apply to excessively broad product quantities because categories or tags are poorly maintained.
If you don't structure your product data properly, you can build the best discount logic, it will still go wrong because rules are only as good as the data they evaluate.
As an additional guide to typical topics surrounding price information in online retail, a legal analysis is also helpful because it provides examples that are often found in shops.
Three mini-scenarios to quickly test your pricing logic
Scenario 1: Standard B2B with tiered pricing per product
You sell seals, individual orders are expensive to handle, the carton quantity is 50, so set up increments at 1, 50, 100, 250 and communicate this clearly so that the buyer doesn't ask, but plans directly for cartons.
Result: More orders in sensible quantities, fewer small quantities picked, and a shopping cart that looks “processed”.
Scenario 2: Dealer group plus quantity discount in category
Dealers have a basic discount, for example minus 8 percent, and an additional discount applies from 200 pieces in the workshop supplies category, because this motivates the dealer to cover the demand in one go.
Result: More items per order, fewer split orders, better shipping planning.
Scenario 3: Key account with special prices from the ERP system
Your key account has negotiated item prices until the end of the year; after logging in, they see exactly these prices, which come from the ERP system, and your shop calculates correctly automatically, without sales having to intervene manually each time.
Result: Fewer inquiries, less effort required for quotations, and fewer errors, because only one system manages the prices.
A 14-day plan that takes you from a wild mix of discounts to clear rules.
If you approach it in a structured way, you don't have to rebuild everything at once; instead, you work your way up from the foundation, and each week the pricing becomes cleaner, rather than touching everything once and then never again.
Start with customer groups and visibility, then move on to the top products with real volume, then to one or two volume discount rules, and finally test on mobile devices with test customers, because that's where most "oops" moments occur.
Specifically: Days 1 to 2 define groups and access logic, days 3 to 5 stagger the 20 most important products, days 6 to 8 build two clear quantity discount rules, days 9 to 11 check the listing presentation, product and shopping cart, days 12 to 14 conduct tests with three typical orders per group, including shipping, tax, rounding and payment methods.
Taking before and after screenshots makes it much easier to show internally what has improved, and you'll get faster feedback before going live.
Now you, give me real numbers, then I'll answer you with appropriate logic.
In the comments, please describe what you sell, what typical quantities look like, whether you think in terms of pieces, cartons or pallets, and what types of customers you have: dealers, wholesalers, project customers or a mix. I want real-world examples because that's exactly where the best pricing strategies come from.
If you like, include a mini-example, item price, typical quantity, desired target, then I can formulate a tiered pricing and discount idea that fits the logistics and margin without turning your shop into a discount labyrinth.
If you are unsure whether you should use tiered pricing or shopping cart rules, please briefly tell me whether your customers tend to buy one item in bulk or whether they prefer to put together bundles of items as needed, because the best structure depends on this.
And yes, I promise I'll answer without marketing fluff, but with a clear rule idea that you can implement directly in Shopware.
Who wrote this post
Storetown Media is a Shopware agency based in the Pinneberg district near Hamburg. We have been implementing B2B features such as tiered pricing, quantity discounts, and customer groups since 2012 – initially in ordering systems for companies, and now in Shopware 6, Magento 2 , and WooCommerce.






















{% endif %} {% if title and title != "" %}
{{ title }}
{% endif %} {% if excerpt and excerpt != "" %}