A business customer logs into your B2B shop and expects exactly what was negotiated on the phone or in the framework agreement: their price. Not the list price, not the consumer price, but the individually agreed condition including volume tiers. If they see a wrong price or none at all, they reach for the phone - or for a competitor's offer. 44 percent of B2B buyers are willing to switch supplier purely because of a poor digital buying experience (Forrester). This article shows how customer-specific prices, customer groups and volume tiers are mirrored from your ERP system into the shop in real time - without prices drifting apart between the ERP and the shop.
Why Customer-Specific Prices Become the Standard in 2026
B2B purchasing has gone digital in recent years. 83 percent of B2B buyers now prefer to order and pay through digital channels rather than through field sales or phone (Gartner), and around 73 percent prefer online purchasing in general (Sana Commerce). A key driver is the generational shift in procurement: millennials and Generation Z already make up roughly 71 percent of B2B buyers (Forrester) - people who take their private ordering experience as the benchmark and expect the same ease at work. Anyone buying on the job wants to see their own price immediately after login, without waiting for a manual quote.
And a lot is decided by the price itself. 74 percent of B2B buyers expect clear pricing directly on the website (BigCommerce). If the price is missing or wrong, trust erodes fast: 29 percent of buyers cite pricing inaccuracies as a concrete data problem with their suppliers (Sana Commerce), and a lack of transparency around availability and delivery is the biggest frustration in the buying process for 40 percent (Sana Commerce). In B2B, a wrong price is not just annoying - it is a reason to switch supplier. The individual price after login is therefore not a nice extra but the entry ticket to digital B2B sales, as also embodied by a B2B self-service portal.
In the B2B Buyer Report based on 750 surveyed buyers, a large majority say they encounter outdated systems and inaccurate data in digital purchasing - 81 percent report noticeable barriers, and 75 percent are therefore considering switching supplier (Sana Commerce). The common denominator is real-time data quality: current stock, reliable delivery dates and, precisely, the correct customer-specific price. Solving these three points cleanly addresses the most common reasons for abandonment in B2B buying all at once.
Customer Groups, Price Lists and Tiers: the Building Blocks
Customer-specific prices sound complicated but consist of a few well-combinable building blocks. Almost any B2B pricing logic can be assembled from three elements: the customer group, the assigned price list and the volume tiers. Understanding these blocks is the basis for transferring your own pricing logic cleanly from the ERP into the shop.
Customer groups
Customers are bundled into groups by conditions, industry or sales channel - for example Standard, Gold or contract customer. The group decides which price list applies and whether net prices are visible at all.
Price lists
Each group is assigned a price list. It can express percentage discounts on the base prices or contain fixed article prices - including individually negotiated conditions for single customers.
Volume tiers
Within a price list, the unit price drops with the order quantity. From 1, from 50, from 250 units, different prices apply - the classic volume discount that decides the buyer's margin in B2B.
In practice, further details are added: time-limited promotional prices, minimum order quantities, price units such as packaging or pallet sizes, and the question of whether prices are shown gross or net. In many companies, this logic has been maintained in the ERP or the inventory system for years. The mistake would be to rebuild it in the shop by hand. Because then two truths exist - and sooner or later they drift apart. How pure price rules and promotions differ from this is shown in the article on the Shopware Rule Builder.
The Core Problem: Price Drift Between ERP and Shop
Price drift arises when prices are maintained in two places and those places are not in sync. The most common pattern is the nightly batch job: once per night, an export pushes prices from the ERP into the shop. During the day, the shop can therefore be wrong for hours - every price change, every new condition, every corrected tier price only becomes visible the next morning. For a consumer shop that may be enough. In B2B, where prices are negotiated and adjusted at short notice, it is a risk. The fact that pricing inaccuracies in particular are perceived as a data problem by 29 percent of buyers (Sana Commerce) is therefore no coincidence but the direct consequence of outdated synchronization.
| Aspect | Nightly export | Live request |
|---|---|---|
| Freshness | up to 24 hours old | price at the moment of request |
| New condition | visible next day | effective immediately |
| Error source | two price sources | one source (ERP) |
| Maintenance effort | duplicate upkeep | upkeep only in the ERP |
Anyone maintaining contract prices directly in the shop and in parallel in the ERP creates two truths that drift apart. Manual price maintenance is also error-prone and produces inconsistent prices across channels. In the worst case, the shop shows a price that is too low and you have to deliver at it, or one that is too high and drives the customer away. Both can be avoided if the ERP remains the single leading price source and the shop only requests the price instead of managing it itself.
Single Source of Truth: the ERP Owns the Price
The way out of price drift is the principle of a single leading source. The price is maintained in exactly one place - in the ERP or the inventory system - and the shop requests it there instead of keeping its own copy. To keep responsibilities cleanly separated, a clear split of which system owns which information helps:
- The ERP owns: base prices, customer-specific price lists, tiers, promotional prices, credit limits and the assignment of customer to customer group. This is also where sales, accounting and inventory management come together.
- The shop owns: presentation, the buying process and the assignment of the logged-in user to their customer account. It renders the price but does not calculate it itself.
- The interface connects both: it translates the shop's price request into a query to the ERP and returns the finished, customer-specific price including the tier - ideally in real time.
- The fallback safeguards: if the ERP is briefly unreachable, a last-known price or a clear status message takes over so that the buying process does not run into a void.
This principle lowers not only the error rate but also the maintenance effort. Sales continues to maintain conditions where they are used to - in the ERP - and does not have to learn a second system. The shop thus becomes the extended arm of the existing pricing logic, not its competitor. When cleanly connecting systems such as SAP Business One or Microsoft Dynamics, exactly this division of roles is the decisive planning step.
How Live Price Determination Works Technically
From the outside it looks like magic: the customer logs in and sees their price. Technically, behind it lies a clearly defined sequence that can be broken down into a few steps and runs in fractions of a second per page view:
- Login and identity: the user signs in. The shop now knows their customer account and the assigned customer group.
- Price request: for the displayed articles, the shop sends a request to the interface - with article number, customer group and desired quantity.
- Resolution in the ERP: the ERP determines the matching price list, applies customer-specific conditions and evaluates the volume tier.
- Return of the tier: the interface returns not just a single price but the complete tier, so the shop can show the next-better quantity.
- Display: the shop shows the net price, states VAT correctly and renders the tier directly on the product page and in the cart.
Such a price response is deliberately kept lean. It contains the article number, the customer group, the currency, the net flag and the steps of the volume tier. A simplified example of a price interface response:
{
"sku": "SCR-M6-200",
"customer_group": "gold",
"currency": "EUR",
"net": true,
"price_tiers": [
{ "min_qty": 1, "unit_price": 9.80 },
{ "min_qty": 50, "unit_price": 8.90 },
{ "min_qty": 250, "unit_price": 7.50 }
],
"valid_until": "2026-12-31",
"source": "erp"
}A live request per article and page view can generate many queries for large catalogs. A short, customer-group-based cache of a few minutes noticeably relieves both ERP and shop without prices becoming meaningfully stale. What matters is to purge the cache specifically on price changes and to separate it per customer group, so that one group's price never ends up with another. Plain server performance also feeds directly into fast price display here.
Displaying Volume and Net Prices Correctly
The best live price is of little use if it is displayed unclearly. In B2B, different rules apply than in the consumer business. Business customers calculate in net prices, which is why the net amount should be in the foreground - VAT is stated additionally and transparently, as pricing rules permit for commercial customers. The volume tier belongs visibly on the product page: a small table showing from which quantity which unit price applies makes the next price advantage immediately recognizable and encourages larger order quantities.
The clearly visible, correct price is not a detail but a revenue lever: 74 percent of B2B buyers expect clear pricing directly on the website (BigCommerce), and 44 percent switch supplier when the digital experience does not convince (Forrester). Showing tier and net prices clearly reduces queries to sales, speeds up ordering and strengthens loyalty to existing conditions. This combines well with a quick order for regular customers.
In addition, it is worth looking at price presentation as such: anchor prices, list prices struck through against the individual price and the labeling of savings work in B2B too - but must be kept legally clean. How prices can be presented psychologically and in a legally sound way is deepened in the article on price display in the online shop.
Integration Paths: Interface, Middleware, Monitoring
How live price determination is connected concretely depends on the existing system and the complexity of the pricing logic. In practice, three building blocks have proven themselves; they can be combined, and we tailor them during the interface connection according to the starting point:
Direct interface
The shop talks to the ERP's API directly - for example with JTL-Wawi or a modern ERP interface. Short paths, ideal for manageable pricing logic and a single leading system.
Middleware
A middleware decouples shop and ERP, translates formats and buffers load peaks. Sensible when several systems, channels or complex conditions come together.
Price monitoring
Monitoring watches the synchronization: how long does a price request take, do queries fail, do shop and ERP price diverge? Automatic alerts surface errors before customers notice them.
Regardless of the path, the goal stays the same: the price comes from one source, is requested in real time and is displayed correctly in the shop. The effort depends on the number of customer groups, the depth of the tiers and the connected channels. Since B2B buyers today use ten or more channels on average in a single purchase journey (McKinsey) and around 34 percent of B2B revenue already runs through self-service and online sales (McKinsey), clean integration pays off twice - the shop becomes a reliable sales channel alongside field sales and phone, as also described in digitalizing B2B sales.
Checklist: Bringing Customer Prices Cleanly Into the Shop
Before customer-specific prices go live, a structured look at the prerequisites is worthwhile. The following checklist summarizes what a resilient live price connection looks like:
- Prices, price lists and tiers are maintained exclusively in the ERP
- Each customer is clearly assigned to a customer group with a matching price list
- The shop requests prices in real time instead of importing them nightly
- Net prices are in the foreground and VAT is stated correctly
- The volume tier is visible on the product page and in the cart
- A fallback takes over if the ERP is briefly unreachable
- Monitoring watches response times, errors and price deviations
Bring Customer Prices Live Into the Shop Now
Individual prices after login are no longer a luxury in B2B but the foundation of functioning digital sales. Given 44 percent of buyers ready to switch on a poor digital experience (Forrester) and 83 percent who prefer to order digitally (Gartner), the correct, visible price decides revenue and loyalty. To achieve this, XICTRON connects your inventory management and ERP with the shop, so that customer groups, price lists and tiers are served in real time and without price drift.
One leading price source
We anchor your ERP as the single source for prices and connect the shop via interface or middleware - eliminating duplicate maintenance and price drift.
Live prices with tiers
Customer groups and volume tiers are requested in real time and displayed cleanly in net - including a fallback and customer-group-separated caching for stable load times.
Monitored synchronization
Price monitoring reports deviations, slow requests and outages before they show up in the buying process - safeguarded in managed hosting.
Tailored to your model
Whether framework agreements, project-based prices or customer-specific catalogs - we map your grown pricing logic in the B2B shop.
Whether a nightly export still suffices today or a live request is needed depends on your pricing logic and your customers. We analyze the current state of your connection, clarify the division of roles between ERP and shop and set up a live price determination that fits your business model. Recurring check and reconciliation steps can be automated so that they run reliably without manual intervention. Talk to our team to bring your customer-specific prices into the shop.
This article draws on figures from Forrester on the switching readiness of B2B buyers and the generational shift in procurement, on Gartner on digital ordering and payment preference, on the B2B Buyer Report by Sana Commerce (survey of 750 buyers on data quality, price accuracy and switching readiness), on BigCommerce on the expectation of transparent pricing, and on analyses by McKinsey on omnichannel purchase journeys and self-service revenue in B2B. The figures cited can change over time and serve as guidance; this article does not replace individual professional or legal advice. As of August 2026.
Customer-specific prices are individually agreed conditions that a business customer sees after login - depending on their customer group, the assigned price list and the volume tiers. Instead of a general list price, each customer receives the price that applies to them, including negotiated discounts. This matches the expectation of 74 percent of buyers to see clear prices directly on the website (BigCommerce).
The shop requests the price in real time from the ERP through an interface. After login, it transmits article number, customer group and quantity; the ERP determines the matching price list and tier and returns the finished net price including its steps. This keeps the ERP as the single leading price source, and the shop only displays the price instead of managing it itself.
With a nightly export, the shop can be up to 24 hours old during the day. New or corrected conditions only become visible the next day, so shop and ERP prices drift apart. Since 29 percent of buyers cite pricing inaccuracies as a data problem (Sana Commerce), an outdated import noticeably increases the risk of wrong prices and thus the switching readiness of customers.
It means that prices are maintained in exactly one place - in the ERP or the inventory system - and all other systems only request this value. The shop keeps no price copy of its own but renders the price delivered by the ERP. This way no price drift arises, the maintenance effort drops, and sales continues to work in its familiar system.
In B2B, net prices are typically in the foreground because business customers calculate in net. VAT is stated additionally and transparently. Pricing rules permit the net display towards commercial customers. Whether and how gross prices appear in addition depends on the customer group and the legal framework and is defined during setup.
We anchor your ERP as the leading price source, connect the shop via interface or middleware and set up a live price determination with customer groups and tiers - including net display, fallback and customer-group-separated caching. Price monitoring watches response times and deviations. This way customer-specific prices can, in our experience, be reliably integrated into ongoing operations instead of being maintained twice in the shop (project experience).