Modernization
Modernize a working e-commerce system without starting over
I upgrade working stores on 1C-Bitrix, Laravel and legacy PHP piece by piece, starting with whatever hurts sales most. Orders, pricing, ERP sync and SEO keep working at every stage.
When it's needed
- The storefront is dated, mobile is slow, and the redesign is stuck on platform templates.
- Every release is risky because frontend and backend ship together.
- The catalog grew and search and filters can't keep up.
- ERP, warehouse or CRM sync breaks now and then, and customers are the first to notice.
- A rewrite was started and has stalled.
When you don't need modernization
If the store handles its load and changes ship through normal development, a big modernization won't pay off. Sometimes a PHP upgrade, proper caching and fixing a few slow queries are enough. The audit shows this, and then I'll say so.
What usually moves first
A Next.js storefront
The backend stays where it is, the storefront gets its own speed and its own release cycle.
Headless Bitrix + Next.jsIntegrations
ERP, warehouse, CRM, payments, delivery: queues, retries, monitoring, one source of truth for stock and prices.
Backend performance
PHP-FPM, OPcache, caching, slow queries, PHP and core upgrades. Sometimes that's enough and you can stop there.
How SEO survives the move
- An inventory of every URL that brings traffic, before any work starts.
- A 301 redirect map, tested on a production copy.
- Matching titles, descriptions, H1s, canonicals and structured data before and after.
- Rendered HTML compared between old and new pages.
- Switching section by section, not the whole site at once.
- Four to six weeks of monitoring in Search Console after each switch.
Who does the work
I handle the architecture and the critical code. For larger scopes I work alongside your team.
How the work is structured
- 1
Audit or brief
An audit, or a short brief if the picture is already clear.
- 2
First stage
A fixed price and acceptance criteria.
- 3
Further stages
The same way, each with visible results in the numbers.
- 4
Handover or monthly work
Documentation and handover to your team, or a monthly engagement.
Timing and price
- Timing
- In stages, each timed after the audit
- Price
- Each stage is priced after the audit and paid per stage.
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
- Can we do everything in one project?
- We can plan everything at once, but I'll still ship it in parts. One big release on a live store is a bet there's no reason to make.
- We're on Laravel, not Bitrix.
- Same approach. Laravel is usually easier to separate from the storefront than Bitrix.
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.
What in your store gets in the way most?
That's where we start.