Vohkus

Vohkus operated a large-scale B2B commerce environment with around 400,000 SKUs and more than 170 active companies. The platform had grown around third-party B2B adaptations, supplier feeds, company-specific pricing, and operational workarounds.

The commercial model was valuable, but the platform structure made pricing behaviour, deployment confidence, and ownership harder to control within an architecture-led implementation.

The existing architecture had several pressure points that were becoming expensive to manage:

• Company pricing depended on pre-calculated imports and heavy indexing.
• Rule logic was distributed across global, company, and import layers.
• Middleware carried responsibilities that needed clearer ownership and integration discipline.
• Release confidence was reduced by fragile dependencies and unclear validation paths.

The platform was re-engineered around Adobe Commerce B2B capability, with the commercial model translated into clearer system boundaries.

• Native B2B architecture replaced inherited adaptation layers.
• Pricing logic was redesigned around real-time markup and supplier rules.
• Frontend and checkout behaviour were rebuilt around the way Vohkus needed to sell.
• Integration responsibilities were clarified so change could be governed more confidently.

Delivery was moved into a more controlled operating rhythm. Version control, CI, staging validation, and a weekly release cadence gave the platform a clearer route from change request to production.

That ongoing governance mattered because the work was not a one-off rebuild. The platform needed to keep evolving without losing the structural control the rebuild had restored.

Vohkus moved onto a more stable Adobe Commerce B2B foundation with clearer pricing ownership, reduced middleware dependency, and a release model that supported ongoing change.

The outcome was not just technical improvement. It was a platform model that made commercial logic easier to see, govern, and improve.