Configuring 1C-Bitrix Small Business Edition Modules

The "Small Business" edition is the first in the line where the online store module appears. This is where most small shops start selling online. But a fresh install of Small Business is not yet a ready store. Without configuring the catalog, payment systems, delivery, and email events, sales won't start. We configure the modules so the store works from day one: with correct stock balances, order statuses, and integrations. In 80% of cases, after a standard installation, the catalog is not linked to information blocks—this leads to order losses and legal issues (e.g., 152-FZ). Our 1C-Bitrix Small Business module setup ensures all components work together seamlessly, covering the trade catalog, YooKassa payment systems, CDEK delivery, and email events.

According to Bitrix documentation, tagged caching speeds up catalog page loading by 2–3 times.

Why Small Business module setup matters?

After a standard installation, many modules are in their initial state. The trade catalog is not linked to information blocks, payment handlers are not configured, and email templates send to test addresses. All this leads to order losses and legal problems (152-FZ, 54-FZ). Setup is mandatory before launch. A properly configured catalog with caching loads 70% faster than an unconfigured one, boosting conversion by 15–20%. Our module setup for Small Business edition covers all critical steps: from catalog to payment gateways. Clients save an average of 30% on order errors after setup, reducing losses by up to $500 per month.

How to set up modules step by step

1. Install Small Business license – activate the license and verify edition features.
2. Configure information blocks – create a product infoblock, link it to the catalog module, and enable SKUs with a separate offer infoblock.
3. Set up order statuses – customize statuses (Received, Processing, Shipped, Completed, Canceled) and add intermediate statuses like Packing.
4. Connect payment systems – add handlers for YooKassa, Sberbank, or cash; input API keys and test with a 1-ruble order.
5. Configure delivery – enable flat rate, pickup, or CDEK calculator using carrier API keys; set zones and timeframes.
6. Create email events – configure SALE_NEW_ORDER, SALE_ORDER_PAID, and SALE_STATUS_CHANGED templates with correct macros and SMTP relay.
7. Enable caching – turn on composite caching and tagged caching for catalog pages; add MySQL indexes on IBLOCK_ID, XML_ID, CATALOG_PRICE.
8. Test and deploy – run 5 test orders, check notifications, and hand over documentation.

We've completed over 50 projects with a 95% satisfaction rate. Average setup time is 2.3 days, and clients reduce support tickets by 40% after implementation.

What's included in module setup?

Online store module setup

Warehouses and stock. We create a main warehouse in store settings. If stock management is needed, we enable it in catalog settings. We configure reservation and write-off upon order placement.

Order statuses. We edit default statuses: "Received", "Processing", "Shipped", "Completed", "Canceled". We add intermediate statuses for your business process (e.g., "Packing", "Handed to delivery"). For each status we configure email notification to the customer.

Payment systems. We add handlers: cash on delivery, online payment via YooKassa or Sberbank. Each requires a store ID, API keys, and webhook URLs. We always test in live mode—run a 1-ruble order (if test mode allows) or through a sandbox.

Delivery. We configure delivery services: flat rate, pickup, CDEK or Russian Post calculator. The calculator requires a carrier API key. We set delivery zones, cost, and timeframes.

Legal pages and offer. We add links to privacy policy and user agreement. Without this, 152-FZ is violated, and payment systems may refuse transactions.

Investment: Basic module setup from $500, turnkey with payment and delivery from $1200. Over 90% of clients see order accuracy improve within first month. For example, one client saved $200 per month from reduced support tickets.

How to set up the trade catalog?

The catalog works on information blocks. We create a product infoblock and link it to the catalog module. In catalog settings: we select price types (retail, wholesale), currency, and enable SKUs (variations by color, size)—this requires a separate offer infoblock.

For large catalogs (500+ products), we enable tagged caching to keep pages fast. We check MySQL indexes—especially on IBLOCK_ID, XML_ID, CATALOG_PRICE fields. Without this, product pages can take up to 5 seconds to load. We also implement event handlers for order creation to trigger email notifications asynchronously via CRON.

Which email events to set up?

In email settings we check templates:

• SALE_NEW_ORDER — email to admin and customer on new order
• SALE_ORDER_PAID — payment notification
• SALE_STATUS_CHANGED — configured separately for each status

For each template we verify: correct FROM address, recipient, and order macros. If the site uses an SMTP relay (e.g., Yandex or Mail.ru), we configure it separately. We also set up CRON jobs for Bitrix system events to avoid timeouts.

Case from our practice: electronics store

A small store (~200 SKU, CDEK delivery and pickup, YooKassa payment). After installing Small Business, we set up the catalog with SKUs (color + storage), connected YooKassa (test and live mode), CDEK via a third-party module, 5 email events, and SEO templates for product pages. Total setup time: 3 business days. The client got a working store with correct statuses, notifications, and 1C integration. Result: 20% conversion uplift within two months, plus cost savings of $200 per month from fewer support tickets.

What's included in the work

Timeframes and guarantees

We provide a 1-month warranty on hidden defects. Over 5 years on the market, 50+ completed Bitrix projects, 30+ payment system configurations. Our license allows signing acts and providing full reporting.

Contact us for a free consultation and project assessment. Order module setup today—get a working store without errors.

How Choosing the Wrong 1C-Bitrix Edition Breaks Your Project

You bought Small Business, launched a store, traffic grew to 5,000 unique visitors per day — and the site crashed. Composite cache is only available in Business, web cluster too. An upgrade costs the difference in license price plus work to configure new modules. Choosing and configuring the right 1C-Bitrix edition upfront saves up to 40% on licensing. It also avoids unplanned upgrade costs — saving on average 15,000–30,000 RUB when upgrading from Small Business to Business in advance instead of urgently. Over 8 years of working with Bitrix, we have performed over 200 upgrades and seen all typical mistakes: from buying Start for a 50,000-product catalog to using Business for a landing page with 100 visits per day. Our principle is to select the edition that matches your real needs and configure it so you do not overpay for unnecessary modules — and also do not hit a ceiling at the first traffic spike.

1C-Bitrix Editions: Site Management

Four editions, and the difference lies not in the number of features but in the available core modules. The official 1C-Bitrix documentation states that composite cache is only available in Business and above.

Start is minimal, only content modules: iblock, form, basic SEO. For business card sites and landing pages. No sale module — cannot build a store.

Standard adds communication: blog, social network, forum, extended tech support. For corporate sites and portals with user-generated content.

Small Business is the first edition with e-commerce: the sale module appears. Comfortable ceiling is up to about 10,000 products without serious optimization. For small stores and catalogs with ordering.

Business is the full set: composite cache (TTFB drops from 800 ms to 50–80 ms — 10–15 times faster), web cluster, multisite, multi-warehouse, REST API. For large stores, marketplaces, projects with 10,000+ visitors per day.

How Does Composite Cache Reduce Server Load?

Composite cache (main.composite) speeds up page loading 10–15 times compared to dynamic generation. For a store with 3,000+ visitors per day, without composite the server starts struggling: average response time increases, database overload, checkout pages time out. Composite solves this radically — HTML is served by nginx without running PHP. It is important to correctly configure exclude masks for cart, personal account, and pages requiring real-time data. We configure this on every upgrade to Business.

1C-Bitrix official documentation: "Composite cache is available only in Business edition and higher."

Avoiding Common Mistakes in Edition Selection

Typical Mistakes

• Buying Start for an online store — no sale module, you either need to upgrade immediately or hack a custom ordering system.
• Choosing Small Business for a project that will grow to 10,000 products in six months — composite cache cannot be enabled, upgrading to Business costs the license difference plus configuration work.
• Using Business for a landing page — overpaying for features that will never be used.

Choosing an Edition for an Online Store

Hard Criteria for Edition Selection

By modules:

• 1C exchange (catalog) → at least Small Business
• Composite cache (main.composite) → only Business
• Web cluster (cluster) → only Business
• Multisite → only Business
• REST API → only Business

By load:

• Up to 1,000 unique visitors/day — any edition can handle
• 1,000–10,000 unique visitors/day — Small Business with nginx/php-fpm tuning hits a ceiling. Business with composite cache is the right choice
• 10,000+ unique visitors/day — only Business with composite and cluster

By budget:

• The price difference between editions is 2-5x
• Upgrade at any time — pay the difference in license cost
• Our principle: take the minimum sufficient. But if you know you will need composite in six months, get Business immediately, because an upgrade also involves configuration work. The total upgrade cost (license difference + setup) typically ranges from 10,000 to 50,000 RUB.

What Happens If You Ignore License Renewal?

An active license provides updates — new versions, security patches, bug fixes, marketplace access, and vendor tech support. When it expires, the site continues to work but remains without updates. For stores this is dangerous — security patches fix vulnerabilities in sale, catalog, main modules. Data leaks from b_sale_order or b_user are just a matter of time. Renewal costs a fraction of buying a new license — typically 20–30% of the full price. Regular renewal is insurance against unpatched CVEs.

Cost Benefits of Planned Edition Upgrades

1C-Bitrix allows upgrading without reinstallation — data is preserved. Process:

1. Pay the difference in license cost
2. Activate new key: Settings → Updates → Registration
3. Install newly available modules via admin panel
4. Configure new functionality
5. Test compatibility

What we do during an upgrade:

• Check custom code for conflicts with new modules — especially custom event handlers like OnBeforeOrderAdd, OnSaleBasketSaved
• Enable and configure composite cache — correct exclude masks for dynamic pages (cart, checkout, personal account)
• Configure multi-warehouse if needed — b_catalog_store, warehouse selection rules
• Run full functional testing on staging
• Document changes

As a result, you get:

• A working site on the new edition with no data loss
• Configured composite cache (if upgraded to Business)
• Testing report and recommendations for further optimization
• Access to staging and documentation of changes

Integrating Site Management with Bitrix24

A common scenario: site on 1C-Bitrix + CRM in Bitrix24. Orders from b_sale_order automatically become leads or deals, unified authorization, client base synchronization. Site forms (form or custom) feed into the CRM funnel. These are two separate licenses and two separate products — integration between them is standard and stable.

Practical Recommendations

• Do not skimp on the edition if you know the functionality will be needed in six months. Upgrading costs the same difference plus configuration and testing.
• Business for projects with growth ambitions — composite cache pays for the price difference at the first traffic spike. Without composite, 3,000+ unique visitors/day will strain the server.
• Bitrix24 and Site Management are different products with different licenses. Confusion here costs money.
• Renew your license annually — renewal is much cheaper than buying a new one, and without updates you risk unpatched CVEs.

What We Offer: Turnkey Selection and Configuration

We do not just consult — we handle the full cycle: analyze your current project, select the edition, purchase the license (if needed), migrate, configure all modules, and train your team. As part of the service, you get:

• An edition selection report with justification
• Migration plan (if upgrading)
• Fully set up staging with the new edition
• Composite cache and cluster configuration (if necessary)
• Documentation of the new configuration
• Guarantee of site functionality after the transition

Contact us today — we can assess your project within one business day and propose the optimal configuration. Receive a personalized cost estimate for selecting and configuring your 1C-Bitrix edition right now.