Case Studies

Integration cases

Integration with Fizcult

We ensured the integration of the CartaMe mobile app with the accounting system of the Fizcult retail chain based on 1C: Trade Management 8.3, so that CartaMe users could become participants in the chain's loyalty program and use their single Loyalty ID as a discount card number.
On the CartaMe side, API exchange specifications, a test environment and all necessary conditions for rapid integration were prepared. The integration was carried out in close cooperation with the partner's team, which enabled a fast and coordinated launch.
The data exchange logic was implemented as follows: the 1C system, according to its own schedule set on the client side, connected to the CartaMe system and retrieved a list of new users who had given consent to participate in the Fizcult retail chain's loyalty program. During the initial exchange, only the Loyalty ID as the discount card number and the phone number for deduplication in the client's database were transmitted.
After the user's first visit to the store and purchase, the profile in 1C was activated. Subsequently, in accordance with the user's previously provided consents for personal data processing, the system could request and use additional information necessary for fully managing the loyalty program participant's profile.

Development stages

1
Studied the client's accounting system architecture.
3 hrs
Conducted a deep audit of the accounting system (1C, ERP, CRM) to identify integration points. Analyzed directory structures, document flow and business processes to propose seamless integration without modifying the "core."
2
Prepared API exchange specifications for integration.
5 hrs
Developed a detailed API mapping: request formats, transfer protocols (REST/SOAP), data schema and error handling scenarios. A clear API specification allowed integration logic to be aligned between the developers and our team even before integration began, reducing alignment time by 40%.
3
Deployed a test environment.
1 hr
Quickly set up an isolated test environment fully simulating the production environment. This enabled safe debugging of exchanges without risking the client's production data.
4
Configured the mechanism for transferring new loyalty program participants.
3 hrs
Implemented automatic and secure transfer of new loyalty participant data from the front-end system to 1C. Configured trigger events so that the user profile is instantly created in the accounting system when a target action is performed.
5
Implemented exchange of the minimum required data for registration and deduplication.
8 hrs
Implemented the Data Minimization principle: transmitting only mandatory fields (full name, phone, email) for quick registration and duplicate checking. Configured deduplication algorithms (search for matches by phone/email) to prevent the creation of duplicate cards in 1C.
6
Configured the logic for subsequent profile activation in 1C.
6 hrs
Developed delayed profile activation: after the initial exchange, the participant is marked as "pending." Full activation in 1C occurs after verification or fulfillment of conditions (e.g., consent for personal data processing).
7
Verified the correct operation of consents and personal data exchanges.
2 hrs
Legally secure integration: we tested end-to-end transfer of consent statuses (marketing, SMS, partners) from the collection interface to the counterparty card in 1C.
8
Conducted joint testing and launch of the integration.
1 hr
Organized cross-functional testing with the participation of your business users and IT department. Verified all positive and negative scenarios, load and disaster recovery.
Used module
Connected product
What the client got:
Team
5
Total hours
29
Days
10
Technologies:
Rest API Rest API
Python Python
Project team:
Victor
СТО
Dmitry
Head of Development Departmen
Andrei
Developer
Anna
Lawyer
Marina
Project manager
Chief Technology Officer
1
Head of Development Departmen
1
Developer
1
Lawyer
1
Project manager
1
Back to cases list