EDM module for Bitrix24 Market
An industry vendor wanted their own module for sending electronic documents straight from CRM cards. We built a universal module supporting 4 EDM platforms and passed certification in 2 weeks.
The task
The vendor wanted to launch in Bitrix24 Market with an EDM (electronic document management) module — so that sales managers could send an invoice, act or waybill straight from a deal card, without switching into the EDM operator's account.
Key requirement — support several EDM platforms at once. The vendor's clients used different operators, and rewriting the module for each was inefficient.
The starting point
No ready-made solution in the Market covered all of the platforms the vendor needed. There were modules for individual EDM operators — but without a unified interface, without templates, and with average ratings of 3–4 stars (UX complaints).
The client had backend integration expertise with EDM, but no experience building for the Bitrix24 Market standard — manifest structure, security rules, OAuth requirements.
What we did
A two-week sprint, in phases.
- Days 1–2: spec, architecture sign-off — a single abstract EDM adapter plus 4 concrete implementations; app manifest, OAuth flow
- Days 3–7: module core — UI button on the deal/invoice card, recipient selection wizard, document templates, send queue with retries
- Days 8–10: 4 EDM adapters — implementation and tests against operator sandboxes
- Days 11–12: passing the Bitrix24 security checklist, fixing flagged items (typical: CSP, validation of incoming EDM payloads)
- Days 13–14: submission for certification, Russian-language documentation, demo video for the Market listing
The outcome
The module passed certification on the first try — no requests to rework. Published in Bitrix24 Market under the client's brand; more than 12 active installations in the first quarter (normal for a niche EDM module).
The abstract-adapter architecture let the vendor add a 5th and 6th platform later on their own — on top of our scaffolding, without our involvement. That was one of the goals: leave the client self-sufficient.
2 weeks from spec to publication — because AI takes most of the routine off the table: standard OAuth code, validators, documentation generation, test scenarios. What's left for us is the business logic and the integration edge cases.
The client's name is withheld under NDA. Real names and details are shared at the brief.
A similar task?
Describe it briefly — within 1–2 days we'll come back with an analysis and an hourly estimate. If a packaged solution fits, we'll say so honestly.