B2B online shop with variant logic and account pricing…

Q: What does variant and configurator logic do in B2B?

Rules for options, exclusions, tier prices and validation. Invalid configurations are blocked before order; special items pass approval workflows.

Q: What is typical project effort for a B2B shop?

Depends on ERP depth, pricing logic, roles and migration. MVP approach: core processes first, extensions iteratively.

E-commerce & online shop

The Challenge

Different prices and approvals per customer

The business runs on frame contracts, tiers and special conditions. A standard B2C shop could not express the rules; ERP data had to stay consistent daily.

Sales and inside teams maintained prices in parallel in spreadsheets and ERP—drift caused claims and manual credits.

Our shop had to reflect contracts—not just a catalogue with list price.

Variants, configurators and search performance

Technical items with thousands of variants stressed search and filters. Configurators had to respect ERP rules without materialising every combination.

Slow listing pages and incomplete facets threatened SEO rankings and B2B self-service acceptance among key accounts.

Technical wholesale customers compare online prices with frame-contract PDFs—drift causes claims and loss of trust.

Target state: self-service with tenant-aware logic

Repeat customers should order online in a standard way; special lines pass approvals. Availability and prices come from ERP—the storefront stays fast and SEO-ready.

Inside sales should steer approvals and exceptions without checking every cart manually.

Key accounts expect the same pricing logic as in the frame contract—visible immediately after login.

Sales wanted measurable conversion and better SEO without simplifying ERP pricing rules.

Configurators should block invalid combinations early instead of sending faulty orders to ERP.

Our Solution

Shop and pricing logic

Headless architecture and pricing model

We modelled customer groups, list prices and surcharges explicitly; critical orders pass approval workflows in the portal. The storefront consumes a fast product API with caching.

Delivered under our online shop creation service; digitalisation context in the digitalisation blog category.

Phase 1: catalogue, search and account pricing

Elasticsearch indexes variants and technical attributes; Redis caches account price lists. Next.js serves SEO-structured listing and detail pages.

Pilot customers migrated in waves; fax/email parallel during transition.

Technical attributes and certificate URLs sync with Elasticsearch on index updates.

Staging mirrors ERP interfaces for realistic price and availability tests before go-live.

Phase 2: approvals, payments and ERP back-sync

Approval workflows for critical lines run in the portal; Stripe Connect maps payment flows. Orders hand off to ERP idempotently.

Inside sales sees open approvals in a queue with SLA hints; rejected lines stay commented in the cart.

Nightly jobs reconcile stock reservations when ERP events arrive delayed during the day.

When price is correct and approval is logged, the order may flow without a phone call.

Results

Self-service instead of fax and email chains

Repeat customers order online in a standardised way; exceptions remain controllable. Load times and structured data support SEO and conversion.

Inside sales handles fewer manual order re-keys; wrong-price incidents from stale lists dropped measurably.

Sales uses the approval queue instead of email chains for critical special lines.

Pilot feedback confirmed pricing logic matches frame contracts for key accounts.

KPIs after go-live

Online order share increased; average handling time for standard lines fell versus the prior year.

Conversion and repeat purchase rate among frame-contract customers improved through faster listing and checkout paths.

Core Web Vitals stayed in the green range after campaign start; SEO traffic on technical category pages rose measurably.

Engineering and operations were delivered by Groenewold IT Solutions in Germany—a headless shop with ERP connectivity Made in Germany.

Pricing and permission model

Customer groups and tiers

Frame contracts, minimum quantities and surcharges are explicit; the shop calculates only visible, allowed prices per login.

Approvals and audit

Critical lines require inside-sales approval with logging; rejected lines stay in the cart with reason.

Performance and ERP consistency

Caching and invalidation

Price and availability caches invalidate on ERP events; nightly jobs reconcile remaining stock.

SEO and structured data

Technical attributes feed structured data for discoverability; Core Web Vitals were measured before go-live.

Category pages and facet search are optimised equally for crawlers and internal search.

B2B onboarding and customer migration

Phased customer enablement

Repeat customers received access in waves; inside sales accompanied first orders and verified pricing and approval logic.

Fax and email parallel operation remained possible during transition until self-service share reached target values.

Variant configurator and ERP rules

Configurators validate combinations against ERP master data; invalid variants are blocked in the UI with explanation.

Technical datasheets and certificates attach to item variants and are downloadable in the shop.

Features

Feature overview

Tenant-aware pricing and discount rules
Approval workflows for critical line items
Search and filters via Elasticsearch
Payments integrated with ERP-aligned processes

Frequently asked questions: B2B shop with variants and account pricing

How does B2B shop logic differ from B2C?

Customer groups, account pricing, minimum quantities, approval workflows, frame contracts and ERP sync—not just cart and checkout. Tier pricing and customer-specific conditions rarely fit a standard B2C shop. The technical base is often web development with a headless architecture and explicit pricing API.

How is the shop connected to ERP or stock management?

Master data, prices, availability and orders via defined interfaces—REST, middleware or batch. The system of record and conflict rules are agreed upfront. We combine API and interface development with ERP implementation.

What does variant and configurator logic do in B2B?

Rules for options, exclusions, tier prices and technical validation—depending on product group and contract. Invalid configurations are blocked before order; special items pass approval workflows in the portal instead of undocumented email chains.

What is typical project effort for a B2B shop?

Depends on ERP depth, pricing logic, roles and migration—from lean portal to fully integrated commerce platform. MVP reduces risk: core processes first, extensions iteratively. The online shop cost calculator and e-commerce ROI calculator give initial budget ranges.

How do data migration and pricing transfer work?

Clean-up of product, customer and price data before go-live; test orders with real scenarios. Pricing is validated with sales—technically correct is not automatically commercially correct. Special cases are planned through custom software development.

Transparency about this case study

So the statements above can be judged properly, we disclose what kind of project this is, what the results are based on and who reviewed the text. More on our project approach and an overview of all reference projects.

Case type: Client project, anonymised or shown under a project name – Real project; company name, industry details or individual figures are generalised at the customer's request.
Measurement basis: Share of orders customers complete in the shop themselves versus fax and email chains, plus error rate in variant selection.
Measurement period: Go-live with phased customer migration
Data source: Sales and customer service at the technical wholesaler; company name anonymised.
Scope of the figures: Figures are rounded and stripped of identifying details; the order of magnitude is preserved.
Publication status: Evidence pending in the new approval register
Approval scope: The existing anonymised publication remains available; case-specific approval evidence still needs to be recorded in the new register.
Evidence record: Internal project file and anonymised reference record.
Technical review: Björn Groenewold, Managing Director of Groenewold IT Solutions GmbH and Hyperspace GmbH – last reviewed on 8 September 2026

Change history

8 September 2026Evidence details added to “B2B online shop with a variant configurator”: case type, measurement basis, data source and technical review.
24 February 2026Results and solution description of “B2B online shop with a variant configurator” revised; the German version was aligned.
1 January 2025Case study “B2B online shop with a variant configurator” published.

B2B online shop with variant logic and account pricing