New store frontend

The new store goes live overnight, and in the morning customers just shop

We test on a copy of the store, switch over in the quietest hours and keep the old theme on standby. If anything goes wrong, we're back on it in minutes.

Tell us about your store

How it works

Four steps to switch over

The same for a new theme or a headless front end.

1Store copyThe new front end runs on a copy with real products, prices and test payments. Your team checks it before launch.
2ChecklistA full order with payment, customer emails, redirects, sitemap, Google Analytics tracking. We tick off every item.
3Overnight switchWe swap the front end in the quietest hours and place a test order on the live store straight away.
4Old theme on standbyThe previous theme stays installed. If something breaks, we restore it before customers notice.

When it makes sense

When a front end launch needs a plan

The store can't stop

Every hour offline is lost orders, and in peak season even a short outage costs.

The last launch went wrong

A new theme went live on a Friday afternoon and the cart was broken all weekend.

Lots of integrations

Orders go to the ERP, BaseLinker and couriers, so a new front end must not interrupt them.

Campaigns are running

Ads point at specific URLs that must keep working the same way after the switch.

On your platform

How we switch over on six platforms

How we switch depends on the platform. We always keep a way back.

Shopify

The new theme waits unpublished. Publishing it, or going back, is one click.

WooCommerce

A store copy on a separate staging server, a theme switch and a full backup before launch.

PrestaShop

Template tested on a copy, switched in the admin, with a database backup in case we need to go back.

Shopware

The theme is assigned to a test channel first, then to the main one. Going back means reassigning it.

IdoSell

The new template is prepared in the admin and activated overnight. The old one stays available.

Shoper

The template is prepared and checked before activation, with the previous one ready to restore.

Results

What we check after launch

In the first days we watch whether the store sells as well as before, or better.

1Orders in the first 24 hours
2Cart and payment errors
3Pages returning 404
4Orders reaching the ERP and couriers

If any number looks off, we act the same day.

FAQ

Common questions

What time do you switch the store over?

In your store's quietest hours, usually at night. We pick the time from your Google Analytics data.

Will customers see a maintenance page?

Usually not. The front end changes without taking the store offline, and orders keep coming in.

What if something breaks after launch?

We restore the previous theme, fix the issue on the copy and switch over again.

Will orders still reach the ERP and couriers?

Yes. Integrations run in the store back end, and we check them with a full test order before launch.

Let's talk

Tell us about your store

Share your store's address, platform and the integrations that must keep working. We reply within one business day.

New store frontend

Other parts of this service

Checkout audit

We measure mobile speed in PageSpeed Insights (LCP, INP, CLS), walk through the product page, cart and payment, and use Google Analytics to find the step where shoppers drop off.

I want to know more

Mobile-first design

Home page, product list, product page and cart, designed for the phone screen first. You approve the design before we write code.

I want to know more

A faster checkout

Guest checkout, address autocomplete, a parcel-locker map in the cart, delivery cost shown on the product page, and BLIK, Apple Pay and Google Pay on the first payment screen.

I want to know more

New theme or headless frontend

A new theme on your current platform is usually enough. For large catalogues and high traffic we build a separate frontend that reads store data through the API.

I want to know more

See the whole service