Consulting on 1C-Bitrix Edition Selection for Your Project

Consulting on 1C-Bitrix Edition Selection for Your Project

"We need a Bitrix site — which edition should we get?" The answer depends not on the budget or on "what people usually buy," but on the specific set of features the project requires. Overpaying for "Enterprise" when "Small Business" is sufficient is wasteful. Buying "Standard" when an online store is needed is a loss of time and money on an upgrade a month later.

Edition Map: What Actually Differentiates One from Another

The marketing descriptions of editions on the 1C-Bitrix website list dozens of items. In practice, the difference comes down to a few fundamental technical capabilities:

This is not a complete list, but these items determine the choice in 90% of projects.

How the Consultation Works

A consultation is not a lecture on edition features. It is a structured requirements gathering session with a clear answer: "You need edition X, because…"

Block 1. Project type. Corporate website, online store, B2B portal, intranet portal, aggregator, marketplace. The type immediately eliminates some options.

Block 2. Key functional requirements. Is commerce needed? Is 1C integration needed? Are multiple sites needed? Is multi-warehouse needed? Each question gets a concrete answer linked to an edition.

Block 3. Load. Projected traffic, peak load. A project with 10,000 unique visitors per day and peaks 5x higher during sales events — this is a cluster requirement, meaning at minimum "Business."

Block 4. Growth horizon. What is planned for the next year? An upgrade + rework costs more than choosing the right edition from the start. We calculate.

Block 5. Not 1C-Bitrix? Sometimes the task is not solvable with 1C-Bitrix at all. An internal corporate portal with tasks — that is Bitrix24. A non-standard marketplace — possibly another platform or custom development. An honest consultation includes this conclusion as well.

Atypical Cases

"We need a B2B portal with individual pricing." Basic implementation — "Small Business" with multiple price types. If individual pricing per legal entity is needed — "Business" with extended pricing logic, or custom development on "Small Business" storing prices in a separate table.

"We need a marketplace." No edition is a marketplace out of the box. This is always custom development. The edition choice depends on functional requirements: if separate supplier accounts, multi-warehouse, and separate analytics are needed — at minimum "Business."

"We need multiple languages." Multi-language via separate language sites — works from "Standard." Multi-language via one page with a language switcher and no separate sites — this is custom development and does not depend on the edition.

Case Study: Consultation for a Factory with B2B Sales

Client — a manufacturer of pump equipment. Stated need: "We need a catalog site with the ability to submit an inquiry."

After a structured interview it turned out:

• They want to connect 1C:Trade Management for price and stock synchronization → minimum "Small Business"
• 3 regional sites with regional pricing are planned within 6 months → "Business" is needed
• A dealer portal with dealer pricing is in the roadmap for the year → "Business" can handle it, custom pricing fields
• The installation must handle 2,000 unique visitors per day without peak issues — quite achievable on one good server without a cluster

Conclusion: "Business." Taking "Small Business" now means an upgrade in six months plus a rework of the multisite structure. The price difference between licenses is less than the cost of the upgrade.

The client made the decision based on calculations, not gut feeling.

Format and Deliverable

Initial consultation — 2–3 hours: requirements interview, answer with rationale.

Extended consultation — 1–3 business days: preparation of a document justifying the edition choice, listing required modules, and estimating licensing costs. This document serves as the entry point for architecture design and budget planning.