Case study / System

Reworking a partner B2B platform

An existing solution combining Bitrix24 and 1C-Bitrix: Site Management needed to match actual partner workflows. I clarified business requirements and contributed to the architectural redesign with the team.

My role
Business requirements and architecture with the team
Status
Core B2B workflows implemented; development continues

Context and challenge

The partner B2B business operated on an existing combination of Bitrix24 and the Business edition of 1C-Bitrix: Site Management. The task was to rework the solution around the actual company workflows and support its continued development.

Business needs had to be connected to the system design. A list of technical changes was not enough: we needed to understand what partners had to do, which data came from 1C and which responsibilities remained with the web platform.

My contribution

I identified the actual business requirements and contributed to the architectural redesign alongside the team. I organised the work of specialists and joined technical tasks as needed.

The implementation depended on colleagues' work. The outcome described here belongs to the team. My primary role was requirements, architecture and development organisation.

What was implemented

Area Team outcome
Platform combination The existing Bitrix24 and Site Management solution was reworked
Product data 1C integration for the catalogue was implemented
Partner terms Data exchange for partner discounts was implemented
Registration Russian and international counterparties can register
Further development One senior developer handles ongoing development

Customisations reuse platform capabilities. Changes are reviewed and released as patches under an established procedure; deployment is partly automated through GitLab CI/CD. Explanations and guides are prepared for users and project participants.

Practical outcome

The team implemented the required B2B workflows and brought the solution to a state where a designated senior developer handles further development. This gives the project clear responsibility for continued engineering work.

Design, infrastructure, management and technical leadership remain separate functions. One developer handling further development does not mean one person maintains the entire product.

What this case demonstrates

I helped turn the problem description into requirements and architectural decisions the team could implement. This work combined knowledge of Bitrix24, Site Management and integrations with organising development across the team.

This public account is limited to the challenge and the distribution of roles. It contains no internal addresses, customer data or non-public diagrams. I make no claims about measured financial impact or load figures in this case.

If your B2B system has accumulated customisations, each change may require a lengthy investigation. We can start by discussing an assessment and a sequence of improvements.

Shall we discuss
your project?

Describe the problem and the result you need. I will explain where I can help.

One-off tasks: a contract with a self-employed provider under Russia’s professional income tax regime (NPD). Commercial projects: a contract with a Russian limited liability company (OOO). Terms and provider details are agreed before work starts.