SystemFlare
ES Talk to an engineer

E-commerce rescue & modernisation

E-commerce rescue and modernisation for shops that grew up fast

Slow pages, an old PHP version, a fragile 1C exchange and a server nobody dares to touch. We make the shop safe first, then fast, then easier to change.

E-commerce rescue and modernisation is hands-on engineering for existing online shops on OpenCart, ocStore, Magento, Laravel or WooCommerce: backups, hardening, performance, ERP/1C integration security and a planned upgrade path. It is for shop owners and e-commerce managers whose platform has become risky or slow. Projects start at €3,000 and usually take 2–4 weeks.

Who it is for

  • Owners and managers of online shops on OpenCart, ocStore, Magento, Laravel or WooCommerce
  • Shops whose products, prices and stock come from 1C or another ERP
  • Businesses whose original developer or agency is no longer around
  • Teams planning a platform upgrade and afraid of losing data or sales

Why now

  • The shop runs on an old PHP or platform version that no longer gets security updates
  • Pages are slow, the server runs out of memory, or the disk keeps filling up
  • The ERP/1C exchange endpoint is open to the whole internet and nobody knows who else can call it
  • The server already failed once, and you are not sure the backups would bring the shop back
  • Payment pages now fall under PCI DSS 4.0.1 requirements 6.4.3 and 11.6.1 (since 31 Mar 2025), and you do not know which scripts load on checkout

What you get

  • Health check and report: platform and PHP versions, extensions, server load, disk, database, security exposure, in plain language
  • Backups first: encrypted, off-site (borg), database every 6 hours, files nightly, with a tested restore
  • Server hardening: origin only behind the CDN/WAF, PHP only for allowed entry points, SSH keys only, FTP removed
  • ERP/1C exchange lock-down: the endpoint allowed from one IP only, credentials rotated, exchange logs checked
  • Performance work: PHP-FPM and worker tuning, caching, slow-query fixes, cleanup of duplicate background jobs
  • Code in Git with a staging copy on sanitised data, so changes can be tested before they reach customers
  • Upgrade path: a written plan for moving to a supported version or platform, with a rehearsal on staging

How it works

  1. Look

    Read-only inspection of the server, code and database, and a plain-language report of what is risky.

  2. Make it safe

    Backups, hardening and code in Git before anything else changes.

  3. Make it fast

    Server tuning, caching and database fixes, measured before and after.

  4. Plan the future

    An upgrade or migration plan, rehearsed on staging, with a clear price.

What we typically find in a shop that “just works”

Shops that have run for years without a technical owner tend to look alike inside:

  • Old dumps and stray scripts in the public folder. In one shop, a forgotten script ran ALTER TABLE on the live database when anyone opened its URL.
  • phpMyAdmin or an admin panel open to the internet.
  • PHP executable anywhere, so a single uploaded file can become a backdoor.
  • The 1C exchange endpoint open to anyone, even though it can rewrite your prices.
  • Background workers duplicated over the years, some running as root, eating memory the shop needs.
  • No staging: every change is tested on paying customers.

None of this needs a rebuild. It needs a careful week or two of engineering, in the right order.

Safe first, then fast

We never start with optimisation. First we take backups and prove they restore. Then we close the doors that are open. Only then do we tune the server and database, because tuning a server that can be taken over is wasted work.

On a B2B wholesale marketplace, cleaning up and tuning the server took background workers from 49 to 9, raised free RAM from 2.5 to 10.3 GB, allowed PHP-FPM workers to go from 10 to 50, and brought root disk use from 80% to 48%.

What we do not do

We do not redesign your shop or run your marketing. We fix the engineering underneath, so your designers, developers and managers can work on something stable.

Related work

Questions clients ask

Which shop platforms do you work with?

OpenCart and ocStore, Magento, WooCommerce, Laravel-based shops and custom PHP. We often work with shops that exchange products, prices and stock with 1C or another ERP.

How much does it cost to fix an old online shop?

From €3,000 excluding VAT for stabilising and securing a typical shop. A full upgrade or migration to a new platform version is quoted separately once we have seen the code.

How long will it take, and will the shop go offline?

Usually 2–4 weeks. The shop stays online. Changes go through staging first, and anything that needs a short maintenance window is planned with you for a quiet hour.

Is our 1C exchange a security risk?

It often is. The exchange endpoint can create and change products and prices, and it is frequently reachable by anyone. We restrict it to your 1C server's IP, rotate the credentials and check the logs for unknown callers.

Should we upgrade or rebuild the shop?

Usually upgrade. Rebuilding loses years of small fixes and SEO. We look at your extensions, customisations and data, and recommend the cheapest path that ends on a supported version.

Can we change the shop ourselves afterwards?

Yes. Once the code is in Git with staging and checks, you can continue with your own developer, with us, or add our AI-managed setup so you can request everyday changes in plain language.

Get a plain-language check of your shop

Send us your shop address and platform. We will tell you what is risky today and what we would fix first, for free.

Get a free assessment