Headless Does Not Mean Rewriting Everything — the Admin Panel Stays

When we talk to 1C-Bitrix clients about headless architecture, the first reaction is almost always the same: "Does that mean we lose our admin panel? Will our managers need retraining? What happens to the 1C sync?". It is an understandable concern — and it is based on a misunderstanding of what actually changes during a headless transition.

The short answer: only the frontend changes. Everything related to catalog management, order management, and sync with your accounting system stays in Bitrix and works exactly as it always has.

What Changes and What Stays

In a standard Bitrix installation, the same engine is responsible for data storage, business logic, and HTML page generation. In a headless architecture, these layers are separated.

What stays in Bitrix:

• The admin panel — completely unchanged
• Catalog management: adding products, editing attributes, managing stock and prices
• 1C sync: the CommerceML data exchange continues to work as before
• Order management: cart, checkout, order statuses, order history
• CRM and leads, if they were configured in Bitrix
• SEO fields, meta tags, redirects — all edited in the familiar interface

What changes:

• The frontend: instead of Bitrix templates, a Next.js application
• Page rendering: the server returns JSON via API instead of pre-built HTML
• Frontend hosting: a separate server or CDN edge (Vercel, Cloudflare Pages, etc.)

For the store managers who work in the Bitrix admin panel, nothing changes. Same interface, same buttons, same familiar workflows.

How the API Layer Works

Bitrix can serve data through a REST API — this is not a custom development, it is built-in functionality. Catalog iblocks, product attributes, categories, prices, stock levels — all of this is available through REST endpoints in JSON format.

The Next.js frontend application calls this API, receives the data, and renders pages — statically at build time or dynamically on request, depending on the page type. The customer sees a fast, modern interface. The manager sees the familiar Bitrix admin panel. Bitrix remains the single source of truth for all data.

No CMS replacement, no data migration, no staff retraining.

A Real Example: UralMetall

UralMetall is a B2B metal product supplier with a catalog of 20,000 SKUs running on 1C-Bitrix. The key requirement when scoping the project: do not touch the 1C sync, the order business logic, or the interface used by managers.

We moved the frontend to Next.js, connected Elasticsearch for catalog and search, and set up the API integration with Bitrix. The admin panel remained completely untouched. The 1C sync continued to operate normally. The new frontend went live in three weeks.

The result: catalog speed increased dramatically, Core Web Vitals moved into the green zone, and the load on the Bitrix server decreased — because it now serves only data, rather than rendering HTML for every request.

When You Actually Do Need to Replace the Backend

The honest answer: in most cases, you do not. But there are situations where Bitrix genuinely becomes a limiting factor:

• The client wants to move fully to SaaS (such as Shopify or Commercetools) for strategic reasons
• Bitrix is being used as a legacy system without an active license or updates, and maintaining it no longer makes sense
• The project's architectural requirements (for example, multi-region or multi-currency in a non-standard configuration) exceed what Bitrix can support

That is a separate, significantly larger project — and we always say so clearly during the audit phase. If headless on top of Bitrix solves the problem, there is no reason to add complexity.

The Bottom Line

Headless is a change in the tool used to generate pages, not in the tool used to run the business. If your concern is "what happens to how we work" — the answer is simple: nothing happens. Things just get faster.

Discuss the architecture of your project →