Skip to content
codecollab.pl
E-commerce stores · technology for the job

A WooCommerce store that actually sells.

I build WooCommerce stores from scratch, rebuild the ones that stopped selling, and move stores off Shoper, PrestaShop or Shopify - without losing Google rankings and without a break in sales. 30+ WooCommerce deployments since 2018, code on your repository from day one, integrations with the Polish e-commerce stack. A fixed bid in writing: one price, the scope and the date.

30+ deployments since 2018 · 8 years in production · fixed bid in writing
§ 01​ Sound familiar?

Three things that cost you sales.

I.

Slow as a snail

Every second of load time is an abandoned cart and more expensive advertising. I bring the store down to a fraction of a second - by going into the code and the foundation, not by bolting on another plugin.

carts walk away
II.

It looks like 2015

People judge a store in seconds. An old, inconsistent look does not earn trust - nobody hands over a card. A redesign on the existing product base changes that.

no trust
III.

The platform is holding you back

The subscription grows with your turnover, the one feature you need "cannot be done", and plugin stacked on plugin breaks after every update. I clean up the foundation, or move the store to WooCommerce without losing Google rankings.

migration + clean-up
§ 02​ Path one

How do you build a WooCommerce store from scratch?

A new WooCommerce store - designed around your range and your sales, not around a plugin catalogue.

Architecture before code

Before the first line of code, we settle the product model, variants, shipping and taxes. The database goes straight onto HPOS - the newer WooCommerce order storage that keeps the store fast at thousands of orders instead of slowing down month after month.

foundation for scale

A checkout that closes

I design the cart and checkout around one goal: the customer pays, rather than filling in a survey. BLIK and fast bank transfers - the payment methods Polish buyers expect - minimum fields, delivery costs visible from the first step.

fewer steps, more orders

The Polish stack from day one

Baselinker, InPost and wFirma - the tools Polish stores actually run on, so orders, parcels and invoices connect themselves instead of being clicked through by hand. The code and the repository are yours from day one - no dependence on the developer.

integrations for PL
§ 03​ Path two

Rescuing what you have.

Not every store has to be rebuilt from zero. Most of the time, fixing the foundation is enough - and that is cheaper than you think.

A redesign without building from zero

A new, consistent look on the existing product and order base. History, customers and Google rankings stay in place - what changes is what the buyer sees. The store sells normally throughout, because the work happens on staging.

a new look, no risk

Speed and order in the checkout

Every second of load time is an abandoned cart and more expensive advertising. I go into the code and fix the foundation rather than bolting on another plugin: performance on mobile, cart and checkout without leaks.

speed + CRO

Crashes and updates that break things

The store goes down after updates, payments stopped working, or you are looking at a white screen? I clean up the plugins and fix the cause, not the symptom. There is a separate page on speeding up, repairs and further development.

fixing the cause

The store runs, but slowly, or it crashes, or it needs B2B features? That is a separate page: development and optimisation of a WooCommerce store.

§ 04​ Path three · leaving Shoper or PrestaShop?

Migration to WooCommerce - without losing Google rankings.

I move stores from Shoper and PrestaShop, or from Shopify, onto WooCommerce - with the products, the orders and the Google rankings. Typically 4-6 weeks: URL map and 301 redirects, testing on staging, switch-over without a break in sales. The three risks companies fear most - lost rankings, downtime and missing data - I take on with process, not with promises.

The whole process step by step, each source platform separately and the most common questions: migrating a store to WooCommerce.

§ 05​ Want to read first?

Before you decide.

Three pages that show how I work with stores - the detail, without the marketing:

I. Migrating a store to WooCommerce The whole process step by step: URL map and 301 redirects, staging, testing and a switch-over without a break in sales. Read → II. Development and optimisation of an existing store For stores that already run but are slow, crash after updates, or need B2B features and new integrations. Read → III. Ongoing support after launch What happens once the store is live: updates, monitoring, fixes and a fixed number of hours every month. Read →
§ 06​ Proof, not promises

Real deployments, real numbers.

30+ WooCommerce deployments since 2018 - all of them in production, and some clients on maintenance for years. Most of the work sits under NDA, including the migration of a national brand from PrestaShop to WooCommerce with no break in sales. The public proof is Złota Faza - a company site rather than a store, but the bottlenecks were the same: redesign and performance.

Woo deployments
30+
since 2018, all in production
Performance
38 → 100
Lighthouse, Złota Faza rebuild
Migration
4-6 weeks
typically, staging and 301s as standard
Pricing
in writing
a fixed bid, no "from X PLN"
"Krystian talked less and did more. He quoted it, gave a date, and delivered. The site is up, Google sees it, customers come in." Michał Wacławik · Złota Faza · Electrical Installations
Read the full case study →
§ 07​ Questions

Before you write.

Always an individual bid, in writing - no "from X PLN" price list. The price depends on the number of products, the integrations and whether I am building from scratch, rebuilding or migrating - I match the scope to the problem, not the other way round.

It depends on the scope: the number of products, the integrations and how much content has to be moved. You get the exact date in writing together with the price. I work in weekly sprints with a demo every week, so you see progress from the first week.

Yes. All the work happens on a separate staging copy while your store sells as usual. Only the tested version goes to production - the switch-over happens without a break in sales.

Typically 4-6 weeks, depending on the number of products and integrations. All the work happens on a separate staging environment - we only switch production over to the tested version, with no break in sales.

No, not if it is done properly. I map every old URL to a new one and set up 301 redirects, carry over the category structure and meta tags, generate a sitemap and watch indexing in Search Console. That is the most common reason traffic drops during a migration - and exactly what I prevent.

Products with variants and images, categories, customers, order history, content (pages, blog) and the SEO configuration (meta tags, redirects). From Shoper and PrestaShop, or from Shopify - with sales running the whole time.

WooCommerce gives you full ownership of the store and the code - no subscription growing with your turnover and no platform limits. SaaS platforms are faster to start with, and at low turnover a migration usually makes no sense - I will say that straight. The maths changes when the subscription, transaction fees and app costs add up to more than running your own store, or when the platform blocks your growth.

§ 08 Next step

Your store should sell, not get in the way.

Describe the project in a few sentences - I come back personally with the scope, one price and a date.

30+ deployments since 2018 · 8 years in production · code on your repository