Headless Bitrix + Next.js
Headless 1C-Bitrix: a Next.js storefront on top of the backend that already works
Bitrix is good at the money side: orders, pricing, stock, 1C sync. It's weaker at showing products. I split those jobs. The backend stays in Bitrix, the storefront moves to Next.js with its own speed and release cycle.
Stays in Bitrix
- Catalog and info blocks as the data source.
- Orders, cart and payment via API.
- Prices, discounts and rules.
- 1C and warehouse sync.
- The admin your content team already knows.
When you don't need headless
If the catalog is small, speed is fine and there's no team to run two stacks, headless adds cost without a payoff. Tuning caching and performance on the current Bitrix is often enough. I'll tell you on the first call.
When headless is the wrong answerMoves to Next.js
- Catalog, product pages, search and filters (with Elasticsearch).
- Promo and content pages.
- A frontend you can change without touching orders.
- Frontend releases in minutes, independent of the backend.
What you get
An API layer between Bitrix and the storefront
A typed contract: the storefront does not depend on Bitrix internals, and API changes show up before release.
A Next.js storefront
Catalog, product pages, search and filters. Caching with invalidation on Bitrix events, so prices and stock stay current.
An SEO-safe move
A map of old URLs and 301 redirects, meta tags and markup carried over, section-by-section cutover.
ModernizationElasticsearch search, if you need it
Morphology, typos and fast facets instead of the default Bitrix search.
Search and catalogIndependent releases
CI/CD for the storefront: the frontend ships in minutes without touching orders.
Documentation and handover
Your team can run the storefront on its own or with my monthly engagement.
What usually breaks, and how I handle it
Cart and checkout
- What I do
- Logic stays in Bitrix, the storefront talks to it through an API, sessions and discounts tested separately
- More
- Headless Bitrix cart and checkout: five things we didn't see coming
Auth
- What I do
- Shared session or tokens, tested across domains
- More
- The authorized user sees the login form. Bitrix is up. Next.js is up. They just can't agree on who you are.
Caching
- What I do
- ISR with invalidation on Bitrix events, no stale prices
- More
- Cache Invalidation in Headless: How Next.js Learns When Bitrix Updates a Product
Redirects and 404s
- What I do
- A full map of old URLs before release
- More
- Redirects Died on Deploy Day. Bitrix Didn't Warn Us.
Images
- What I do
- A separate pipeline with resizing and CDN
- More
- Headless Bitrix Image Pipeline: What Breaks First in Next.js
Stock
- What I do
- Sync that doesn't lie to customers
- More
- Stock Sync in Headless Bitrix: Three Patterns and Why Boring Polling Wins
Bitrix API
- What I do
- Our own API layer with a typed contract
- More
- TypeScript API contract for Bitrix REST: generate types, stop guessing shapes
How the work runs
- 1
Audit
Catalog, integrations and Bitrix modules. We decide what moves first.
- 2
API layer
A typed contract between Bitrix and the storefront.
- 3
Catalog and product pages
Usually the first release, with a redirect map and SEO checks.
- 4
Cart and account
Later stages, once the first part is stable.
Timing and price
- Timing
- Depends on catalog size and integrations, estimated after the audit
- Price
- Each stage gets a fixed price after the audit.
Proof
Proof
A 28,000-SKU catalog: Next.js on top of 1C-Bitrix
The PHP backend stayed in place with orders, pricing and integrations. The storefront and search moved to Next.js and Elasticsearch, and the SEO structure carried over.
Read the case studyQuestions
- Do we need a different Bitrix edition?
- Usually not. It depends on which modules you use, which the audit covers.
- Will the content team notice?
- The admin barely changes. What changes is how fast their edits show up on the site.
- What about SEO?
- URLs, meta and markup move one to one, and the switch goes section by section.
You work with me
Ivan Ponamarev, senior full-stack engineer, 10+ years in production. You talk to the person who makes the technical decisions and writes the critical code.
Show me the catalog and I'll sketch the architecture
A few sentences about the catalog and integrations are enough for a first call.