An online store or a portal on 1C‑Bitrix
For when Bitrix is already part of your IT landscape or you need out‑of‑the‑box 1C exchange. We review the catalog, integrations and constraints of a running business — and give a range for the approach and budget.
- 1C‑Bitrix and 1C
- Catalog and integrations
- Source code is yours
- Roadmap by request
Already on Bitrix and struggling with speed and mobile? You do not need to rewrite everything: Frontbox sits on top of your Bitrix — the 1C exchange keeps working, shoppers get a fast storefront and an app.
Four reasons clients choose us
1C 8.3 — two‑way exchange
Products, stock, prices, orders — both ways. Trade 11, Retail 2.3, ERP 2.5. Standard exchange modules, not workarounds that break on the next 1C update.
The team does not leave for another project
A fixed line‑up: PM, 1–2 Bitrix developers, a front‑end developer, QA, a designer. The same people support the project after release.
Migration without losing SEO
We have moved stores from WordPress, OpenCart, Modx, Joomla: catalog, orders, customers and 301 redirects. Rankings are preserved.
Source code and access are yours
After release you get the whole codebase, server access and documentation. Leaving for another vendor needs no negotiation.
Two scenarios: a store or a corporate portal
One stack, two kinds of tasks. The scope is defined after a short conversation about your project. Scenarios can combine: a store plus a closed dealer portal on one codebase.
Online store on 1C‑Bitrix
For stores with 500–50,000+ products where 1C is already in place or coming: catalog with filters, product pages with SKUs and stock, cart and checkout, customer account, two‑way 1C exchange, basic SEO.
- filters and search
- SKUs and warehouses
- promo codes and payments
- 1C exchange
- Ozon · WB · Market
Corporate portal
For companies of 50+: users, roles and SSO, a form builder for requests and approvals, documents with approval routes, a knowledge base, integrations with email, messengers and 1C:Payroll.
- SSO (AD/LDAP)
- approvals
- document flow
- BI dashboards
B2B portal on top of the store
Personal prices, wholesale price lists, orders by invoice, history and documents — for dealers and wholesalers on the same codebase as the store.
- personal prices
- invoices for legal entities
- order history
The process depends on the task
We start with a 15‑minute brief, then build a roadmap and agree tasks in the chosen format. Before opening a store — an 80+ point checklist: backups, performance, security, 1C exchange, SEO, legal, analytics.
- 01
Analysis and specification
We capture requirements, fix integrations and the catalog structure. The output is a spec the contract is signed against.
- 02
Design and prototype
A prototype of the key screens, iterative approval, the final layout in Figma.
- 03
Development and integrations
Template, catalog, cart, checkout; then 1C, payments, delivery, CRM — each integration verified on staging.
- 04
Testing, launch, training
QA by checklist, acceptance on staging, production deploy, handover of access and source code, team training.
The engagement format is agreed per task
On the brief a product owner and a developer review the inputs and give a range for capabilities, approach and budget. There is no public price list — scopes differ too much.
Subscription
A ready template with your colours and logo, evolution by roadmap.
range on the brief
- categories, filters, search
- 1C: products and stock
- 1 payment gateway, 1 carrier
- roadmap and agreed tasks
Contract by request
Custom design of key screens and an extended set of integrations.
range on the brief
- custom design of key screens
- advanced filters, variants, loyalty
- 1C: prices, orders, statuses, documents
- 2 gateways, 2–3 carriers
Migration from another CMS
WordPress, OpenCart, Modx, Joomla → 1C‑Bitrix without losing rankings.
depends on catalog size
- catalog and order migration
- customer base
- 301 redirects, meta, content
- ranking check after the move
When Bitrix is not the right call
Honestly: sometimes something else is cheaper and faster.
A B2C start‑up without 1C
If 1C is not planned — a builder or Frontbox without a backend launches faster and cheaper.
Speed is the main pain
Bitrix features are enough but the store is heavy? Put Frontbox on top of the existing store instead of rewriting everything.
A simple catalog with no integrations
A ready solution or a light storefront is enough — no need to pay for full development.
The team is already on another CMS
WordPress, Drupal, Modx — stay there. Bitrix shines where it is already part of the IT landscape.
Frequently asked
How long does the launch take?
It depends on scope, integrations and approvals. We discuss the task first and build a roadmap — that is where the timeline estimate comes from.
Can the template be adapted to our processes?
Yes. The template is a starting base, not a locked box. Changes are made as modules without touching the core — easier Bitrix updates, unbroken 1C exchange.
Which 1C configurations do you work with?
1C 8.3: Trade Management 11, Retail 2.3, ERP 2.5. The exchange scope and integration method depend on your configuration and task.
Which Bitrix edition do we need?
“Business” for most stores up to ~50,000 SKUs. “Enterprise” for high‑load, B2B, custom modules and clustering. We include the licence in the estimate or use yours.
Do you hand over source code and access?
Yes, by default: the whole codebase, server access, architecture and exchange documentation. You can leave for another vendor at any time.
What about support after release?
Support and further tasks go into the roadmap and are delivered by agreed requests, or we move to a retainer with an SLA.
Let’s discuss your project
Describe the catalog, integrations and constraints. We usually reply within a day and suggest a 15‑minute brief with a product owner and a developer.