Product · 1C-Bitrix

Online store or corporate portal on 1C-Bitrix — in 4–10 weeks

Every week without a working store is lost revenue. We launch on a ready-made template with 1C integration from 199 000 ₽; a custom build for your processes — from 499 000 ₽. Pay by milestones, fixed team, source code is yours.

  • from 199 000 ₽
  • 4–10 weeks
  • 1C 8.3 out of the box
  • You own the source
Web storefront
iOS + Android
PWA

Frontbox · core

Next.js + Elasticsearch

SSR · ISR · edge cache · facets · synonyms · auth

~120msTTFB
1.9sLCP
88mssearch
1C‑Bitrix
1C
CRM / ERP

Their stores and portals run on 1C-Bitrix — built by us

  • leikkaushelmi
  • УралМеталл

What we build on 1C-Bitrix

Two scenarios: online store or corporate portal

One stack, two project types. Each has a base scope in the fixed package and extensions on demand.

Online store on 1C-Bitrix

For stores with a 500–50 000+ SKU catalog where 1C is already in place or about to be.

  • Catalog: categories, faceted filters, fast search
  • Product page: SKUs and variants, prices and promos, multi-warehouse stock, media gallery
  • Cart and checkout: promo codes, shipping calculation, payments (Sber, Tinkoff, YooKassa)
  • Two-way 1C sync: catalog, stock, prices, orders, statuses
  • Customer account: orders, statuses, loyalty points
  • SEO basics: clean URLs, sitemap, Product/BreadcrumbList markup, performance
  • In higher tiers: marketplaces (Ozon, WB, Y.Market), B2B pricing, custom modules

Corporate portal

For companies of 50+ that need a single workspace, document workflow and SSO.

  • Users, roles and permissions, SSO (AD/LDAP)
  • Form builder for requests and approvals
  • Documents and orders with approval routing
  • News, knowledge base, comments
  • Email, messenger and 1C:HR integrations
  • In higher tiers: BI reports and dashboards, data buses, HR/CRM, high availability

Mix is possible: an online store + a closed dealer/B2B portal on the same codebase.

Integrations

Integrations with clear "from X ₽" pricing

If there’s no off-the-shelf module for your system, we write one for your environment. Custom integrations are scoped after the spec, billed at 4 990 ₽/hour.

  • Payments

    Sber, Tinkoff, YooKassa, CloudPayments, Yandex.Kassa

    from 25 000 ₽

  • CRM

    Bitrix24, AmoCRM, RetailCRM

    from 35 000 ₽

  • 1C

    UT 11, Retail 2.3, ERP 2.5 (8.3)

    from 60 000 ₽

  • Marketplaces

    Ozon, Wildberries, Y.Market

    from 45 000 ₽ per channel

  • Shipping

    CDEK, Boxberry, DPD, Russian Post, Delovye Linii

    from 20 000 ₽ per carrier

  • Messengers & notifications

    Telegram, WhatsApp, SMS

    from 15 000 ₽

Cases

Stores and portals we shipped on 1C-Bitrix

Each case has before/after numbers: conversion, AOV, page speed, peak-period order volume.

    How we work

    Six stages with a demo after each one

    Milestone payments. After each stage — a demo on staging and a clear "continue or re-prioritize" decision point.

    1. 011 week

      Discovery & spec

      We capture requirements, lock in integrations, and draft the catalog structure. Output: a spec the contract is signed against.

    2. 022 weeks

      Design & prototype

      The designer builds a prototype of the key screens. We iterate until approval. Final mockup — in Figma.

    3. 033–5 weeks

      Core build

      Bitrix devs assemble the template, configure the catalog, cart, checkout. In parallel the frontend finalizes layouts.

    4. 041–2 weeks

      Integrations

      We connect 1C, payments, shipping, CRM. Every integration is verified on staging.

    5. 051 week

      Testing & UAT

      QA runs an 80+ checklist. You run UAT on staging. Bugs get fixed.

    6. 061 week

      Launch & handover

      Deploy to production, hand over access and source code. We train your team on the admin panel and 1C sync.

    Pre-launch

    What we check before going live

    Before going to production we run an 80+ checklist. Key items:

    • Backups

      Daily automated, manual before every release, restore drill on staging.

    • Performance

      PageSpeed >85 on PDP, DB indexes, CDN cache, asset optimization.

    • Security

      Up-to-date Bitrix core, WAF on CDN, password policy, audit logs.

    • 1C sync

      Two-way, with error handling, monitoring and alerts.

    • SEO

      Canonical, hreflang, sitemap, robots, Product/Offer/BreadcrumbList markup.

    • Legal

      Offer, personal-data policy, 152-FZ, cookie consent.

    • Analytics

      Yandex.Metrica with e-commerce events, goals, funnels.

    Team

    Who works on your project

    We assign a fixed team to each project. The roster is in the contract — we don’t shuffle people between clients. After launch the same people handle support if you take a retainer.

    • PM

      Single point of contact, owns timeline and approvals.

    • 1–2 Bitrix devs (back-end)

      Core, catalog, integrations, 1C sync.

    • Front-end developer

      Markup, template, JS logic.

    • Designer

      Mockups and UI kit (when included in the package).

    • QA engineer

      Checklists, manual and basic automated testing.

    • DevOps (Enterprise only)

      Servers, monitoring, high availability.

    What sets us apart

    Six reasons clients pick us for 1C-Bitrix

    • 1C 8.3 — two-way sync

      Catalog, stock, prices, orders — both ways. We work with UT, Retail, ERP. Standard exchange modules — no workarounds that break on the next 1C update.

      UT 11 · Retail 2.3 · ERP 2.5

    • Cases with numbers, not a logo wall

      Each case has a "before" and "after": conversion, average order value, LCP, peak load. No friendly rounding.

      before/after in every case

    • Pricing and timelines on the first screen

      Three fixed packages with a clear scope and "from X ₽" pricing. Time in weeks, milestone payments, demo after each one. No "let’s discuss the cost on a call".

      from 199 / 499 / 990 K ₽

    • The team stays on your project

      A fixed crew works on your project the whole time: PM, 1–2 Bitrix devs, frontend dev, QA, designer. The roster is in the contract. After launch the same people handle support.

      team locked in the contract

    • Migration from another CMS without losing SEO

      We have migrated stores from WordPress, OpenCart, Modx, Joomla. Catalog, order history, customer base and SEO carry over: 301 redirects, meta, content. Search rankings stay intact.

      WordPress · OpenCart · Modx · Joomla

    • Source code and access — yours by default

      After launch you get the full code, server access and architecture docs. If you decide to switch vendors — you do it without losses or negotiations.

      handed over by default

    Stack comparison

    Bitrix / Frontbox / custom — what to pick

    One project, three ways to build it. We compare on the parameters that actually move ROI.

    Parameter1C-BitrixFrontbox (headless)Custom Next.js
    Time to launch4–10 weeks2–6 weeks (with existing backend)3–6 months
    Cost to startfrom 199 000 ₽from 35 000 ₽/mo or 95 000 ₽/mo × 18from 1 500 000 ₽
    1C integrationOut of the box, standard modulesThrough Bitrix backendBuilt from scratch
    Storefront speedAverage (needs tuning)Very high (5× faster)Depends on the vendor
    Vendor lock-inLow (standard CMS)Low (standard stack)High
    Catalog sizeUp to ~200 000 SKUAnyAny
    When to pickNeed 1C integration and a fast startAlready on Bitrix, hit a speed ceilingUnique business logic, big budget

    Anti-case

    When Bitrix is not your fit

    We won’t take on a Bitrix project — and we’ll point you to the right place — if:

    • B2C startup with no 1C

      If you don’t plan to roll out 1C — Tilda or Shopify will launch in a week and cost 2–3× less.

    • Main pain is speed and Core Web Vitals

      If Bitrix functionality is enough and the store is just heavy — put our Frontbox on top of it, or build straight on Frontbox.

    • Simple catalog with no integrations

      Tilda, Insales or Bitrix "Site" will do — no need to overpay for full custom development.

    • The team already runs on another CMS

      WordPress, Drupal, Modx — stay on it. Bitrix shines where it’s already part of the IT landscape.

    In those cases we say "not our project" and point you to someone who fits.

    Add-on

    Hit a speed ceiling? Replace just the frontend

    Store already on Bitrix and the problem is speed and Core Web Vitals? You don’t have to rewrite everything. We layer our Frontbox on top of your backend — a Next.js frontend with Elasticsearch search. Bitrix stays, the 1C sync keeps running. The store gets 5× faster, LCP drops from 4–6 s to 1.5–2 s.

    Pricing

    Three packages with a clear scope

    All prices are "from X ₽", final number locked after the spec. Payment over 4–6 milestones, demo after each.

    Launch · from 199 000 ₽
    • Timeline4–6 weeks
    • DesignReady template, brand colors and logo
    • CatalogCategories, filters, search
    • 1CCatalog, stock
    • Payments1 gateway
    • Shipping1 standard carrier
    • Marketplaces
    • Support30 days included
    Standard · from 499 000 ₽
    • Timeline6–10 weeks
    • DesignCustom design for key screens
    • Catalog+ advanced filters, variants, loyalty
    • 1C+ prices, orders, statuses, documents
    • Payments2 gateways
    • Shipping2–3 carriers
    • Marketplaceson demand +45 000 ₽ per channel
    • Support30 days + retainer option

    Third tier — Enterprise (from 990 000 ₽ or a retainer from 150 000 ₽/mo): full custom design and UI kit, B2B pricing, custom 1C exchange (incl. labelling), all required gateways and SBP, up to 3 marketplaces, 90 days of support + 24/7 SLA option. Timeline 8–12+ weeks.

    FAQ

    Frequently asked questions

    • How long does launch take?

      Launch — 4–6 weeks, Standard — 6–10, Enterprise — 8–12. The only things that move the date are approvals on your side and integration complexity.

    • Can the template be customized to our processes?

      Yes. The template is a starting base, not a sealed box. Customizations are built as modules — we don’t touch the core, which keeps Bitrix updates clean and the 1C sync stable.

    • Which 1C configurations do you support?

      1C 8.3: Trade Management 11, Retail 2.3, ERP 2.5. Two-way exchange of catalog, prices, stock, orders, statuses and documents. If your 1C has been customized — we write a custom exchange handler, ballpark 60–150 K ₽.

    • What about post-launch support?

      Every package includes 30 days of basic support (Enterprise — 90). Beyond that — a retainer from 50 000 ₽/mo or T&M at 4 990 ₽/hour. Support is handled by the same team that built the project.

    • Do you hand over source code and access?

      Yes, by default. After launch you get the full code, server access and architecture/exchange documentation. You can switch vendors at any time — no negotiations, no losses.

    • Can we migrate from another CMS?

      Yes. We’ve migrated from WordPress, OpenCart, Modx, Joomla. We move the catalog, order history, customer base and SEO (301 redirects, meta, content). Add 1–2 weeks on top of the base package.

    • Which Bitrix edition do we need?

      Business — for most stores with up to ~50 000 SKUs and standard functionality. Enterprise — for high-load, B2B, custom modules and clustering. License goes into the estimate or we use yours.

    • What guarantees that you won’t disappear after the prepayment?

      Payment over 4–6 milestones with a demo after each. Contract with fixed deadlines and late-delivery penalties. The team is fixed and named in the contract.

    Let’s scope your project

    Message us on Telegram about the catalog, integrations, timeline. We’ll come back with a preliminary estimate within 1–2 business days. No three-page briefs.

    What’s next - Related sections