Integrations · Bitrix24 · MoySklad
Bitrix24 ↔ MoySklad integration
Client:
NDA
Category: Integrations
Stack: Bitrix24, MoySklad API, PHP, queues, logs
Timeline: 1–3 weeks
Problem
Products, stock and orders diverged between the CRM and the warehouse, sync was unstable and duplicates appeared.
Constraints
Different data models, MoySklad API limits, the requirement not to lose or duplicate records.
What I did
- Two-way sync of companies, contacts and deals
- Owner mapping between the systems
- Duplicate search by UUID and key fields
- Correct handling of cents/rounding
- verify / sync / count modes for safe runs
- Logging of incoming and outgoing requests
Architecture
Bitrix24
→ Exchange service layer
→ Queue / retries
→ MoySklad API
→ Exchange logs
Result
An exchange history appeared: it is clear where and why sync fails; data no longer diverges manually.
What can be reused
Mapping layer
Deduplication rules
verify mode before a live run
Exchange log format
Related services and solutions
Services
Bitrix24 D7: boxed development and stabilization
I work not only with interface settings, but at the level of the box, the code and internal APIs.
Services
API integrations with logs, retry and duplicate protection
An integration is not just a REST request. You need mapping, logs, error handling, retry, duplicate protection and a clear exchange status.
Ready-made solutions
Integration Hub
An intermediate backend for exchange between Bitrix24, 1C, MoySklad, Telegram, APIs and other services.
Ready-made solutions
Webhook Inbox / Logger
A module for receiving, storing and diagnosing incoming webhook events.