- Headless migration with cart UX preserved for price-on-request catalog
Split the monolithic Bitrix into a headless architecture: backend stayed on Bitrix, frontend moved to Frontbox. Cart and checkout UX preserved without any public pricing.
- Client
- LeikkauShelmi
- Year
- Service
- e-commerce
Context
LeikkauShelmi is a subsidiary of Lenkhimsintez, supplying chemicals and spare parts for road tankers and tank containers. The entire catalog is sold under individual agreements — prices are available on request only. The site ran on a monolithic 1C-Bitrix, and when the team wanted to evolve the frontend, the architecture became the bottleneck: limited flexibility and slow page load times.
What we did
We split the monolithic Bitrix into two layers: the backend stayed on Bitrix, the frontend moved to Frontbox. The key challenge was preserving the full user journey — including cart and checkout — despite the absence of public prices.
For the price-on-request model, we implemented a flow where items are added to the cart normally, the buyer completes a request form, and a manager follows up with a custom quote. This preserves the familiar e-commerce UX without displaying a price list.
The non-standard challenge: cart without prices
Most headless implementations are designed around public pricing. Here, only the account manager knows the price — and that requirement was non-negotiable: B2B contracts, individual agreements, tiered discounts per client.
The solution: Add to cart works as expected, the cart shows a line-item list without totals, and the checkout form submits as a CRM lead. The buyer sees a familiar e-commerce path — no How do I find out the price?
Result
Full production launch in 2 months. Since launch, we have seen consistent growth in organic traffic and inbound leads. The Bitrix backend was not touched — all 1C and CRM integrations continue to operate as before.