1C-Bitrix is not the default ecommerce platform for English-speaking brands. I use it when the commercial site must sit next to a 1C (or similar CIS) ledger: stock, prices, invoices, and roles that already live in accounting. If you are a US or EU DTC brand with Stripe and Shopify in mind, this page is the wrong entry — see Shopify and other platforms or WooCommerce.

When Bitrix is the right call, the work is a real store, not a brochure: infoblocks or the commercial catalog, SKU and offers, cart, checkout, payment modules that the market actually uses, and an exchange with 1C that does not silently drift. Editions, licenses, and hosting constraints are written down before coding. A “cheap Bitrix template” that cannot export orders back to the ledger is a liability, not a launch.

Typical CIS-facing cases: a manufacturer already on 1C who needs a public catalog; a distributor with customer-specific prices; a bilingual storefront where the warehouse is still 1C. I also take migrations off aging Bitrix editions when the catalog and URL map must survive. A full replatform onto or off Bitrix is scoped on store migration, not as a theme swap on this page. Theme cosmetics without data contracts are out of scope unless we explicitly add them.

What ships: discovery of catalog depth and 1C objects, information architecture, implementation, payment and delivery modules, staging, go-live, and a short hypercare window. SEO baseline (canonical, sitemap, product structured data) is part of launch; deep answer-engine work stays on the SEO track. Catalog UX details live on catalog, cards and search. The exchange itself is detailed under ERP, inventory and order sync and the parent 1C integration service.

Timeline: a focused Bitrix storefront with a known 1C contour often takes 8–14 weeks. Multi-store, heavy B2B price types, or a dirty legacy catalog add calendar time. We slice by verticals (category → product → cart → order in 1C) so you see a clickable path early.