MARKET Market + Marketplace

Modules for Bitrix24 Market and 1C-Bitrix Marketplace

Two different storefronts — Market for the Bitrix24 CRM and Marketplace for the 1C-Bitrix CMS. Payment systems, EDM, chat integrators, industry solutions. From spec to publication and certification.

What we'll build for you

What's included

Market — for Bitrix24 (CRM)

Apps for the cloud over REST API, and modules for the self-hosted edition — with migrations, an admin area, OAuth. We often ship one product in both flavours to cover both audiences.

Marketplace — for 1C-Bitrix (CMS)

Full PHP modules for 1C-Bitrix sites: installer, updates, language files, admin-area integrations. Publishing and certification are handled on the Marketplace side.

Payment systems

Integration of your acquiring: cards, instalments, SBP-style instant payments, B2B payments. Published as a module — into Market or Marketplace, or both in parallel.

EDI & document exchange systems

Connecting EDI operators, exchanging invoices and waybills, syncing documents between Bitrix24 and your accounting system. Local requirements considered.

Chat integrators & messengers

Your own channel in Bitrix24 Open Channels: your messenger, chat-bot, omnichannel. With the right actions, templates and media.

Industry-specific modules

Ready-made solutions for a niche: auto service, healthcare, logistics, real estate, B2B distribution. Configurations + custom logic in one package.

Pre-publication preparation

Description, icons, screenshots, video, EULA, technical documentation. Built so moderation passes on the first attempt.

Post-publication support

Updates for new platform versions, response to tickets, feature evolution. Partner-style monetisation model if needed.

How we work

Working format — 4 steps

STEP 01

Brief and review

1–2 days

We understand the task. If a packaged solution fits — we say so up front.

STEP 02

Hourly estimate

Transparent breakdown. Fixed price per sprint.

STEP 03

Development with AI

1–2 week sprints

1–2 week sprints. Demo at the end of each, corrections happen right there.

STEP 04

Handover and support

Documentation, knowledge transfer, ongoing support via b3x.by.

Budget and timeline

How long it takes

Typical module
3–6 sprints
6–12 weeks to publication
Minimum entry
1 sprint
Prototype and architecture sign-off
Payment
Fixed per sprint
Contract, legal entity

Concrete figures — after the brief. The brief is free.

Similar projects

Stories from this service line

A selection of cases for this service — in the Cases section. During the brief we'll pick stories that match your task, including those under NDA.

FAQ

Frequently asked questions

What is the difference between Market and Marketplace?
These are two different storefronts of two different products. <strong>Bitrix24 Market</strong> — apps and modules for the Bitrix24 CRM (cloud and self-hosted). <strong>1C-Bitrix Marketplace</strong> — modules for sites running on the 1C-Bitrix CMS. They have different technical requirements, different moderation and different audiences. We handle both.
Will the module be ours or yours?
By default — yours: you are the client, you own the code and publish it under your developer account. If you don't have an account, we can publish it under ours and transfer it; we work that out at the brief.
How long until publication?
A typical module — 6–12 weeks. Most of that is development and testing, plus 1–3 weeks for packaging and moderation. For complex modules (a payment integration with regulator checks, a state-service integration) we budget more.
What if moderation rejects the module?
We pre-check the platform requirements and resolve grey areas before publication. If moderation does ask for changes — we make them within the project, without a separate invoice.
Can one product be built for both platforms at once?
Yes, we often do that. The business logic is shared; only the platform adapters differ: REST/self-hosted for Bitrix24, a PHP module for the 1C-Bitrix CMS. It's less work than two separate projects.
Can a module be monetized?
Yes, both platforms support paid modules and subscriptions. We help pick a monetization model, set up billing and handle trial periods.
Who handles module support after publication?
We can: respond to user requests, ship updates for new platform versions, evolve the functionality. Or your team — we hand over documentation. We agree on this at the start.

Ready to discuss?

Drop us a note — we reply within a business day

Telegram is the fastest channel. The brief is free, no commitment.

✈ Telegram