Imagine: you have products, you have customers in CRM, but no website. You could install a CMS, buy hosting, hire a developer. Or you could launch a store right inside Bitrix24 in two weeks, without leaving the ecosystem. We've done it many times—and we know where the hidden pitfalls lie. In this article, we'll look at when the Bitrix24.Sites builder is the best solution and when it becomes a brake on growth.
Let's get straight to the facts: the builder is ideal for a small catalog (up to 1000 products) and businesses where all processes are tied to CRM. But if you need complex filtering by properties, automatic discounts, integration with delivery services—you'll have to switch to a full-fledged CMS. We help clients choose the right path at the start, so they don't overpay for migration a year later.
Our experience shows: 70% of stores on the builder hit limitations within 6 months. That's why we offer a free audit—we'll evaluate your project and tell you which option suits you.
What to Choose: Bitrix24.Sites or 1C-Bitrix CMS?
These are two different products with different architectures, although both are released by the same company.
| Parameter | Bitrix24.Sites | 1C-Bitrix CMS |
|---|---|---|
| Hosting | Bitrix24 cloud | Own server / hosting |
| Product catalog | From CRM (products and services) | Infoblocks + commercial catalog |
| Number of products | Up to 30,000 (depends on tariff) | No limits |
| Templates | Block builder, fixed blocks | Full control over layout |
| Custom code | Limited (JS snippets in blocks) | Full access to PHP, templates, components |
| SEO | Basic (title, description, SEF URLs) | Full control (canonical URLs, sitemap, microdata) |
| Integrations | Bitrix24 REST API | REST API + events + agents + CLI |
| Payment systems | Bitrix24.Cash, YooMoney, CloudPayments | Any via sale module handlers |
The main difference is the degree of control. CMS gives full access to the server, file system, and database. The builder operates in a cloud sandbox. According to official Bitrix24 documentation, the builder supports up to 30,000 products, but in practice, slowdowns are noticeable at 5,000.
How a Store on Bitrix24.Sites Works
The store in Bitrix24.Sites works based on the CRM catalog. Products are created in CRM -> Products and Services. Each product is a CRM entity with fields: name, description, price, images, variations, unit of measurement.
Purchase process:
- Customer selects a product on the site
- A deal is created in CRM with the product items attached
- Customer receives a payment link or pays on the site via widget
- After payment, the deal automatically moves to the next stage in the funnel
- Manager sees the order in CRM and processes it
The entire process is tied to the CRM funnel. This is both an advantage and a limitation. The advantage: the manager works in a familiar CRM interface, sees the customer communication history, and can use funnel automation (robots, triggers). The limitation: there is no classic "cart -> checkout -> payment -> delivery" with delivery method selection, cost calculation, or promo code application.
Payment via Bitrix24.Cash
Bitrix24.Cash is the built-in payment acceptance mechanism. It supports connecting:
- YooMoney (formerly Yandex.Cash) — bank cards, e-wallets, SBP
- CloudPayments — cards, Apple Pay, Google Pay
- PayPal — for international sales
- Payment by invoice — for B2B, generates a PDF invoice
Setup takes 15-20 minutes: connecting a payment system in CRM -> Settings -> Payment methods, entering API keys, configuring fiscalization (54-FZ).
The payment link is generated automatically and sent to the customer via SMS, email, or messenger directly from the deal card. Or the customer pays on the site via the embedded widget.
Integration with CRM Funnel
The strength of the "store + CRM" bundle lies in automation. Typical scenario:
Funnel robots for the store:
- When a deal is created -> send order confirmation to customer
- When paid -> send receipt, notify warehouse
- 3 days after delivery -> request review
- On cancellation -> start return process
Triggers:
- Customer opened payment link but didn't pay -> reminder after 2 hours
- Customer hasn't purchased in 30 days -> move to reactivation funnel
All this is configured without code via the visual robot and business process designer in Bitrix24.
When the Builder Is Enough
Bitrix24.Sites is suitable for:
- Small catalog — up to 500-1000 products without complex filtering
- Services — consulting, training, service, where a lead form is more important than a cart
- B2B with individual terms — when price is negotiated, not fixed on the site
- MVP / niche testing — quick launch to test demand
- CRM complement — the company already works in Bitrix24 and wants to add a storefront
Characteristic sign: the business process revolves around the manager, and the site is the entry point for enquiries.
Why the Builder Stops Working: Signs for Migration to CMS
The builder's limitations appear gradually as the store grows. Let's break them down by category.
Catalog and filtering. The builder has no smart filter (bitrix:catalog.smart.filter). Products are displayed as a list or grid with minimal sorting. No faceted indexes, no filtering by product properties, no multi-regionality. For a clothing store where customers choose by size, color, material, and brand—this is critical.
SEO. The builder provides basic settings: title, description, SEF URLs for pages. But there is no control of canonical URLs for pagination, no automatic sitemap.xml generation with products, no Product/Offer microdata for Google Merchant Center, no hreflang setup for multilingual sites. For a store where organic traffic is the main channel, this is a serious obstacle. CMS provides 5 times more SEO capabilities, including a full set of meta tags, XML maps, and microdata.
Discounts and promo codes. The CRM store has no cart rules from the sale module. No conditions like "buy 3 units — get 10% discount", no cumulative discounts, no promo codes with usage limits. You can change the price manually in a deal—but that doesn't scale.
Delivery. No integration with delivery services (CDEK, Boxberry, Russian Post) with automatic cost calculation. No pickup point selection on a map. Delivery cost is either fixed or calculated by the manager manually.
Performance and scale. The builder runs in the Bitrix24 cloud, and page load speed depends on the current platform load. There is no way to set up a CDN for images, optimize server cache, or enable Composite caching. With a catalog over 5,000 products, catalog speed starts to degrade.
Signs that it's time to migrate to CMS:
- Catalog exceeds 1,000-2,000 products with filtering needs
- SEO becomes a priority acquisition channel
- Complex discount rules and promo codes are needed
- Integration with warehouse, 1C, delivery services is required
- Conversion is limited by UX that cannot be changed in the builder
- Business needs multi-regional or multi-language support
Migration strategy. Moving from Bitrix24.Sites to 1C-Bitrix CMS is not a disaster, but it's not file copying either. Products are exported from CRM in CSV format and imported into the CMS commercial catalog. Customer base is transferred via REST API. CRM integration is preserved—the crm module in 1C-Bitrix supports synchronization with Bitrix24 via a connector.
Page content will have to be re-laid out—builder blocks do not convert to CMS templates. This is manual work, and you should be prepared for it.
What's Included in Creating a Store on Bitrix24.Sites
Our certified specialists with over 10 years of experience perform the full cycle, from CRM setup to site launch turnkey.
| Stage | Content | Time |
|---|---|---|
| CRM setup | Sales funnel, deal fields, robots | 1-2 days |
| Catalog | Product creation, categories, photos | 2-4 days |
| Site builder | Template selection, page layout, catalog binding | 2-3 days |
| Payments | Connecting YooMoney/CloudPayments, fiscalization | 1 day |
| Testing | Full purchase cycle, mobile version | 1-2 days |
| Launch | Domain connection, SSL, analytics | 1 day |
The result includes:
- Ready online store on Bitrix24.Sites with configured catalog and payment
- Integration with CRM funnel and deal automation
- Documentation on store setup and management
- Training for managers on order handling in CRM
- Transfer of access and logins
We guarantee on-time launch—the average project takes 7 to 14 business days.
Want to evaluate your project? Get a consultation—we will analyze your business for free and suggest the best option.