Headless or Bitrix: when a new storefront is needed and when it is overkill
A monolithic template means 1C‑Bitrix renders every page itself. Frontbox is a Next.js storefront and an app that sit on top of your Bitrix and are run by an engineer on a subscription. Here is the breakdown: speed, money, timelines, risk. No pressure to switch.
Three key differences
Everything at once: a monolith redesign touches templates, the backend and the ERP sync.
Only the storefront: Bitrix, 1C and CRM stay, the front reads data via API.
LCP 6–14 s without a CDN, TTFB 800–3,000 ms, built‑in search from 2 s.
LCP 1.7–2.2 s, TTFB 90–150 ms on edge cache, search under 100 ms — based on client data.
A new site on the template — 1.5–5 million ₽ up front and 4–12 months.
From 19,000 ₽/mo with an engineer in the subscription, live in 2–6 weeks, instant rollback.
Point by point
Left — the monolithic 1C‑Bitrix template as it usually runs for stores with 500+ SKUs and 1,000+ unique visitors a day. Right — Frontbox per subscription terms.
- Bitrix
- A template inside 1C‑Bitrix: Bitrix renders the pages itself, catalog and orders live there too
- Frontbox
- A Next.js storefront and an app on top of your Bitrix; catalog and orders stay in Bitrix, data flows via API
- Bitrix
- 6–14 s without a CDN
- Frontbox
- 1.7–2.2 s on 4G — server rendering and edge cache
- Bitrix
- 800–3,000 ms on typical hosting
- Frontbox
- 90–150 ms on edge cache
- Bitrix
- Built‑in search, from 2 s
- Frontbox
- Elasticsearch under 100 ms with facets at 100k+ SKUs
- Bitrix
- Often yellow or red
- Frontbox
- Green thanks to server rendering and edge caching
- Bitrix
- Any redesign touches the backend; the 1C integration is rewritten or reconfigured
- Frontbox
- Not required: we work via API, the 1C integration stays intact
- Bitrix
- A separate project with its own budget and timeline
- Frontbox
- iOS + Android from the same code as the site. Add‑on to the subscription, included in White Label
- Bitrix
- 4–12 months
- Frontbox
- 2–6 weeks to traffic switchover
- Bitrix
- 1.5–5 million ₽ up front for a new site
- Frontbox
- From 19,000 ₽/mo on a subscription; White Label 95,000 ₽/mo × 18 with a source‑code buyout
- Bitrix
- Complex, touches the backend
- Frontbox
- Instant: traffic goes back to the original site
LCP, TTFB and search speed are based on client data: production sites on Frontbox and their previous stores on the monolithic template without a CDN. Frontbox prices are indicative and depend on the catalog.
When to stay on the Bitrix template
- A catalog under 500 products and a standard purchase flow: monolith speed is enough, the investment will not pay off
- Traffic under 1,000 unique visitors a day — the speed difference exists, but maintaining a second stack outweighs it
- A budget under 19,000 ₽/mo: start with Bitrix cache tuning (a 20–30% gain) and a CDN
- You plan a full platform replacement: Frontbox as an intermediate step is redundant, design the new stack directly
When Frontbox
- The store is on Bitrix, the catalog is 500+ SKUs and pages take 6–14 seconds to load
- Built‑in search answers in seconds and you need instant search with facets
- Core Web Vitals are in the red and rankings are slipping
- You need a new design and a branded app, but rewriting the backend and the ERP sync is off the table
- You want one invoice: storefront, app, SEO, content and an engineer in one subscription
How to switch without a big bang
Bitrix stays the source of data. We do not rewrite the backend or migrate the catalog: the storefront connects via API, traffic moves gradually, rollback is a single setting.
- 01
Audit and a straight answer
In 1–2 days we measure LCP, TTFB and Core Web Vitals and review the catalog, search and ERP sync. We say it plainly: worth switching or not. If not — we explain why.
- 02
Demo on your catalog
We connect the catalog from Bitrix and show search, product pages and the app on your products. Bitrix, 1C and CRM stay untouched.
- 03
Storefront next to the live site
The new front runs on a staging domain. URL structure, meta tags, redirects, sitemap and robots.txt are prepared in advance — rankings are preserved.
- 04
Gradual switch
Traffic moves in parts over 2–7 days. The old template stays as a fallback, rollback is instant. Full index transition takes 2–4 weeks.
Questions about choosing an architecture
What store owners on Bitrix ask. Everything else — on a demo.
What is the difference between headless and the Bitrix monolith?
In a monolith the frontend and backend are one system: Bitrix renders the templates itself. In headless the storefront is separate (Next.js) and reads data from Bitrix via API. The backend does not know what the site looks like, which is where speed (server rendering + edge cache), design freedom and independence from CMS updates come from.
Do we need to migrate data?
No. Bitrix stays the source of data: products, orders and customers live exactly where they were. The storefront reads them via API in real time.
What happens to the 1C integration?
Nothing changes. Frontbox runs on top of Bitrix: orders, stock levels and prices synchronise through the same Bitrix as before.
Is headless only for large stores?
It makes practical sense from a catalog of 500+ SKUs or traffic of 1,000+ unique visitors a day. At lower volumes the speed difference exists, but the cost of maintaining a headless stack outweighs the gain. If your case does not fit — we will say so.
What happens to SEO during the switch?
We preserve URL structure, meta tags, redirects, sitemap and robots.txt. Core Web Vitals usually improve right after launch thanks to server rendering and edge caching. Full index transition takes 2–4 weeks.
Frontbox or a full migration to Next.js?
Frontbox is faster (2–6 weeks), cheaper to start (from 19,000 ₽/mo) and rollback is instant. A full migration makes sense when Bitrix architecture blocks business logic or the project is built from scratch: typically 3–6 months, estimated after a short discovery.
Can Bitrix be sped up without headless?
Three paths: Bitrix cache tuning (free, a 20–30% gain), a CDN on top of Bitrix (cheaper, but does not fix TTFB) and a headless storefront (fixes it completely). After the audit we tell you which path will deliver results in your case.
Not sure which to choose? Start with a review
Send a link to your store. We measure speed, look at the catalog and ERP sync and tell you plainly: whether you need a new storefront or tuning Bitrix is enough. No commitment.