Launching an online store on Bitrix from scratch in 2026: how to start selling in 3 weeks

Launching a Bitrix E-Commerce Store in 3 Weeks: A Survival Guide

The most expensive mistake at the start is ordering a "unique" online store for millions of rubles and waiting six months for it. During that time, the hypothesis either dies or competitors take the market. But the opposite extreme — putting the store on a template and hitting its limits six months later — isn't a way out either. In 2026, launching sales doesn't require turnkey custom development, but it also isn't reduced to "install a template and forget it". The difference is in understanding exactly what you're buying and for how long.

Below is a practical plan that saves you from a cash gap and endless development, without closing your eyes to the real limits of each path. It's not about the "perfect site" but about a working tool that will start bringing orders this month and won't need to be rewritten in a year.

1. Ready-Made Solution vs Custom Development: An Honest Breakdown

The "template vs custom" debate is usually held from two extreme positions. Some say a template is "cheap and fast", others say "a real store only runs on custom". The truth is that each approach has its own strengths and weaknesses, and you choose based on the specific task, not a slogan.

Ready-Made Solution: What You Pay For and What You Trade

A ready-made professional template — for example, solutions from Aspro on the 1C-Bitrix Marketplace — isn't just markup. It's an assembled store with catalog, filters, cart, personal account, payment and delivery pages, mobile adaptivity. All of this has been tested on hundreds of other projects and works out of the box.

Pros of a ready-made solution:

• Fast start. A store with working purchase scenarios is up in days, not months. You test the hypothesis on real orders right away.
• Ready-made standard mechanisms. Cart, checkout, personal account, promo codes, discounts — all of this is already built and tested. You don't pay for what has been solved a thousand times.
• Predictable cost. The budget is known upfront — it equals the template price plus a small customization. No "surprises" along the way.

Cons of a ready-made solution:

• Scaling difficulties. When the business grows and non-standard scenarios are needed — custom pricing logic, non-standard loyalty programs, specific integrations — the template starts to get in the way. Customization on top of the template often goes "around" its architecture, accumulating technical debt.
• Difficulties integrating your own code. The template is someone else's codebase with its own rules. You can plug your own modules and services into it, but you have to work with its structure. The more custom code, the harder it is to maintain.
• Update problems. Updating the template with customizations in place is a separate headache. The developer who made the changes must track new versions, carefully transfer their edits, and test. The "one-click update" only works for a clean template with no customizations.

A ready-made solution is the right start but not always the right finish. It pays off when your task is to quickly test demand on a standard sales scenario. And it starts getting in the way when your business logic becomes non-standard.

Custom Development: Why It Exists at All

Custom development isn't "flashiness" or "an upsell". It's a tool that solves tasks that don't fit into a template's bounds. And it, too, has its strengths and weaknesses.

Pros of custom development:

• Exactly what the business needs. No "we'll bolt it onto the template" — the architecture is assembled for specific processes: custom discount logic, non-standard price types, specific checkout scenarios, unique integrations.
• Clean codebase. The developer understands how the project is built, where everything lives, and why. New modules plug in without looking back at someone else's decisions.
• Freedom to evolve. The business changes — the store changes. No "the template can't do this", "the update will break the customization", "we'll have to rewrite half the store".
• No dependency on the template vendor. Your project belongs to you, not to a vendor whose rules you're obliged to follow.

Cons of custom development:

• More expensive and slower. A custom store from scratch is 200,000–500,000 rubles and 2–4 months of work minimum. For testing a hypothesis, that's too much.
• Requires a competent contractor. A unique project is easy to ruin if the team lacks experience. Poorly designed custom is worse than a template, because nobody but the author understands it.
• Takes full responsibility for quality. In a template, edge cases have already been thought through for you. In custom, all of this must be provided for yourself.

When custom development is justified:

• The business logic is non-standard and doesn't fit template scenarios.
• A long-term project with constant development and customization is planned.
• There are requirements for performance, security, or integrations the template doesn't cover.
• The team has an experienced developer who leads the project and is responsible for its architecture.

Summary for part one: a ready-made solution is about speed and hypothesis testing, custom development is about long-term evolution and non-standard logic. Starting with a ready-made solution is usually more profitable, but if you know for sure that standard scenarios are too tight for you, it's more honest to lay the groundwork for custom right away.

2. License Economics: "Small Business" vs "Business" — and Why Sometimes "Start" and "Standard" Are Better

The 1C-Bitrix license is the second mandatory payment after the template. Four editions are on open sale: "Start", "Standard", "Small Business", and "Business". The internet usually recommends "Small Business" as the golden mean, but that's not a universal truth. Especially when it comes to custom development.

When "Small Business" Is the Right Choice

The "Small Business" edition is a reasonable compromise for those launching on a ready-made template and planning a standard e-commerce store with one warehouse.

• One warehouse.
• One price per product for all customers.
• You're just opening and don't know how fast growth will be.

When it's time to upgrade to "Business":

• A second warehouse or multiple shipping points has appeared.
• Different prices are needed for different customer groups: retail, small wholesale, large wholesale, dealers.
• Product sets and kits are required to increase the average check.

"Business" costs 96,500 ₽, "Small Business" — 47,000 ₽. Upgrading is done in one click, without data loss or catalog migration. Buying "Business" in advance "just in case" isn't necessary — that's frozen money you need in circulation at the start.

Why with Custom Development You Should Look at "Start" and "Standard"

Here's where it gets interesting. If you go the custom development route, "Start" and "Standard" editions aren't "outdated stubs" — they're full-fledged tools on which a working e-commerce store can be built. I have enough real cases with stores on exactly these editions, and I can say honestly: I really like this option.

Why:

• The core is lighter and works faster. "Start" and "Standard" don't drag along modules that aren't used in a specific project. Less code to load, fewer database queries, more responsive admin panel and public part. At a start where every millisecond of TTFB affects conversion, this is noticeable.
• Bitrix itself already includes all the basic protection tools and filling conveniences. No "pay extra for security" — XSS and CSRF protections, access separation, and data validation come out of the box.
• All the basics for an e-commerce store deploy fast enough. Catalog, cart, checkout, personal account, payment and delivery modules — all of this works on "Start" and "Standard" without restrictions. The difference from "Small Business" is in specific tools like multi-warehouse and price types, not the base store.
• 1C integration doesn't become a serious problem. Especially when the data source is the site itself, and stock updates are done via JSON. In that scenario, full CommerceML exchange isn't needed — a simple, predictable REST endpoint on the site side that receives updated stock in batches is enough. This is several times easier than the "full" 1C exchange and works faster.

In other words: if you're building a custom project and know for sure you don't need the specific tools of "Small Business" and "Business", buying them in advance is overpaying. "Start" or "Standard" will give you a light core, all the base store functionality, and a convenient development process.

An Important Warning

If you're planning a standard e-commerce store on a ready-made template and know for sure the business will grow toward multi-warehouse and multiple price types — "Small Business" will be more profitable. And remember: trying to bypass the edition's limits through discounts and user groups instead of price types will show itself at the first 1C integration — the exchange by price types won't see your discounts.

3. The Sacred Trio of Automation: Payment, Delivery, Warehouse

A site without integrations is a beautiful showcase that takes up your personal time. Every order has to be processed manually: copying data, calculating delivery, creating invoices. At the start this is tolerable, but within a week the order flow turns into a mess. So three things need to be connected immediately.

Payment: Acquiring with 54-FZ Receipts

Without online payment, you lose some customers who aren't ready to pay by invoice or cash to the courier. On the 1C-Bitrix Marketplace there are ready-made acquiring modules from banks and payment services: Tochka Bank, Forabank, PayKeeper, Robokassa, Unitpay. They accept Visa, MasterCard, MIR, and SBP cards.

It's critical that the module transmits the cart items for generating a receipt under 54-FZ. This isn't an option but a legal requirement. Without fiscalization, selling online is prohibited. Most popular modules already implement cart transmission for the receipt — you just need to connect a cloud cash register in the service's personal account.

What this gives: the customer pays for the order on the site, the receipt goes to the tax authority automatically, and you don't waste time manually closing shifts and preparing reports. Connection takes one or two days including cash register setup.

Delivery: CDEK and Boxberry Out of the Box

Manual delivery calculation is a pain. The client waits for a response, the manager calculates the cost according to the carrier's price list, then manually creates the invoice. With ten orders a day, this takes an hour; with a hundred — a working day. Delivery modules remove this load entirely.

The official CDEK module for 1C-Bitrix is installed from the Marketplace. It calculates the cost and delivery time directly in the cart, lets the customer choose a pickup point on the map, and lets the manager create a courier request from the admin panel. The Boxberry module works similarly: cost calculation, pickup point selection, shipment creation, tracking.

What this gives: the customer sees the exact delivery cost before placing the order — this reduces the abandoned cart rate. The manager doesn't copy data manually but creates the shipment in one click. The tracking number is pulled into the order automatically.

Accounting: MoySklad or SBIS

Tracking stock in Excel or "by eye" ends the same way: you sell a product that isn't in stock or order something that's already there. At the start, a cloud solution that syncs with the site is enough.

MoySklad is the simplest option for small business. Integration with 1C-Bitrix works through a module: products, stock, prices, and orders sync automatically. There's a free tier and inexpensive subscriptions. For a startup or sole proprietor, this is more than enough.

SBIS (Saby) is a heavier system, but if you already have accounting in this service or plan to work with EDI, the integration pays off. The Integration with SBIS (Retail) module exports the product catalog and category hierarchy to 1C-Bitrix and syncs orders and statuses.

What this gives: you see current stock on the site and in the accounting system simultaneously. Managers process orders instead of transferring data between tables. Errors from "double entry" disappear.

4. Pre-Launch Checklist: What the Developer Must Hand Over

When the developer delivers the project, it's important to get not just a "working site" but infrastructure you can use. Here's the minimum set without which the launch turns into dependence on the contractor.

• A clean domain registered to you. The domain must be registered in your name or company, not the developer's. This is your main digital asset. Check that you have access to the domain control panel and that registration is extended for at least a year.
• Configured corporate email on the domain. Addresses like info@domain.ru, sales@domain.ru build trust. Set up email through Yandex 360, Mail.ru for Business, or another service. All emails from the site (order confirmation, notifications) must come from your domain, not a free mailbox.
• Cloud backup. 1C-Bitrix has a built-in backup mechanism. Set up automatic backups of the database and files on a schedule — daily or weekly. Store copies not on the same server as the site but in cloud storage: in the 1C-Bitrix cloud or with a third-party provider. The "1C-Bitrix" cloud always stores three latest copies. This is your insurance against hacking, server failure, or accidental deletion.
• Access to the admin panel and server settings. You should have the site administrator login and password, as well as access to the hosting panel. Don't leave this data only with the developer.
• Instructions for basic operations. How to add a product, change a price, view an order, cancel an order. This isn't "training on everything" but a minimum set so you can manage the store without calling the developer for every little thing.
• Configured notifications. Email and, if needed, SMS notifications about new orders. You should learn about a sale immediately, not by logging into the admin panel "to check if there's anything."

This checklist isn't bureaucracy. It's the difference between "a store that runs itself" and "a store that relies on the contractor's word."

The Bottom Line

Launching a Bitrix e-commerce store in three weeks isn't fantasy. It's the result of choosing the right tools for the specific task. A ready-made solution saves you when you need to quickly test a hypothesis on a standard sales scenario. Custom development is justified when the business logic is non-standard and long-term evolution is planned. The license edition is chosen for processes, not "for growth": "Small Business" for a typical store, "Start" or "Standard" for a custom project with a light core.

A cash gap at the start happens not because of "low sales" but because money went into long development that isn't generating revenue yet, or into a license that isn't used to its full potential. Understanding exactly what you're buying and for how long — that's the main insurance against endless development and a blown budget.

Теги: 1C Bitrix