Service
Online store on WooCommerce
Catalog, payments, delivery on the stack your team already knows. LiqPay, Nova Poshta, sync with 1C. A custom theme — no bloated templates. Launch in 5–7 weeks for a store up to 1,000 SKUs.
An honest framing
Selling products online — the right platform choice starts here
Selling products online — you're in the right place. Need a site without a catalog? See WordPress development. Haven't picked a platform yet? Every format is covered on the e-commerce page. WooCommerce is the right choice when the catalog is up to 10,000 SKUs, the store and blog live in one admin panel, and your team already knows WordPress — or when a store needs to be added to an existing site without rewriting everything.
When another tool fits better
A 50,000+ SKU catalog with complex filtering — a headless CMS solves it more simply and is cheaper to maintain. B2B logic with multiple warehouses, negotiated pricing, and EDI — that's a custom build on Node.js. A borderline case? We'll work it out on a call: it's not in our interest to build a store on a tool you'll outgrow within a year.
What's included
Payments, delivery, and inventory for a WooCommerce store — already in the quote
Catalog and variants
- Product variants: size, color, configuration — one listing, several SKUs each with their own stock and photos. Catalog filters with no page reload.
- A multi-category structure with cross-links between categories. Product import from Excel or 1C using our template.
Payments and delivery
- LiqPay, PrivatBank, Fondy — Visa/Mastercard cards, Apple Pay, Google Pay, installment payments (Monobank, PrivatBank). Configured in the admin panel with no code changes.
- Nova Poshta API: cost calculation to a branch or by courier, tracking in the customer account, SMS notifications. Custom return flows: a form in the account, request status, photos.
Inventory, integrations, customer account
- Two-way stock sync with 1C/CRM: a sale on the site subtracts stock in 1C; a received shipment adds it to the catalog.
- Google Shopping feeds (XML, Merchant Center) and Facebook/Instagram Catalog (JSON). Customer account: order history, reorders, delivery addresses.
Custom extensions and speed
- Group pricing, complex delivery logic, promotions and discounts — we build them around your process instead of picking a "plugin that's roughly about this."
- A custom PHP theme with no page builders, a minimal set of plugins. Caching (WP Rocket or Redis), image optimization — Lighthouse Mobile ≥ 85.
- WordPress
- WooCommerce
- LiqPay
- Fondy
- ПриватБанк
- Нова Пошта
- 1С
- WP Rocket
Three scenarios
New store, migration, or upgrade — one process for each project state
- A new store from scratch
We build a new WordPress store on a custom theme: minimal plugins, maximum speed. We design the catalog structure and connect payments, delivery, and 1C. Launch in 5–7 weeks for up to 1,000 SKUs, 8–10 weeks for a large catalog with integrations.
Deliverable: a live store + a guide for your content manager + 30 days of support.
- Migration to WooCommerce
We move the catalog, orders, and SEO rankings to the new store. Redirects from old URLs, preserving meta and structure — so the move doesn't cost you positions in Google. Works for ready-made platforms and custom solutions.
Deliverable: a store on WooCommerce + a test report + redirects from the old site.
- Upgrading an existing WooCommerce store
Technical audit → an honest answer: what can be fixed, what needs rewriting. A slow store is, in 9 cases out of 10, an implementation problem, not a platform one. We don't make money on endlessly patching someone else's code — if rewriting from scratch is cheaper, we say so at the audit, not after the third invoice.
Deliverable: a work plan with priorities and a budget range.
Case studies
WooCommerce stores that take orders every day
How we work
How we get a WooCommerce store to its first payment
Brief and catalog structure
30 minutes on Zoom: how many SKUs, which variants, the delivery and return logic, whether there's a 1C or CRM. For a migration — step 1 is replaced by a technical audit of the existing store. Deliverable: the catalog structure, an integration list, a budget range, and timelines.
Design
Wireframes for the product page (with variants), catalog, cart, checkout, and customer account. Three rounds of revisions — in the budget. Deliverable: approved mockups for desktop and mobile + a fixed quote for the full scope.
Theme development and content population
We code a custom PHP theme while your content manager uploads products in parallel using our template (or we take the first batch into scope). Weekly staging deploys. Deliverable: a functional store on staging with real products.
Integrations and testing
We connect LiqPay/Fondy, Nova Poshta, 1C or CRM. We test with live transactions: a real payment, tracking, a return scenario. Deliverable: a signed test report.
Launch and handover
Migration to the production domain, Google Search Console, GA4, Google Merchant Center — done by release day. We train your content manager to work with the catalog. Deliverable: a live store + a guide for your content manager + 30 days of support.
FAQ
What people ask about WooCommerce and migration
Let's talk
Describe the task — we'll estimate the WooCommerce project
- 30 minutesOne-on-one online
- Flexible formatVideo or phone call
- Solution-focusedPractical answers
Learn more
Online store on WordPress: what we know about WooCommerce after 10 years
An online store on WordPress is one of the most common solutions for the Ukrainian market, and that's not a marketing line. Over 10 years we've launched clothing, cosmetics, furniture, and auto parts stores on WooCommerce — and the bottleneck was never the platform, only the quality of the implementation. The key isn't "which platform," it's "how well the code is written."
A slow WooCommerce is an implementation problem. An overloaded ThemeForest theme, 50 plugins, none of them optimized for the specific store — and you get a site that loads in 6 seconds. We don't install off-the-shelf themes. A custom PHP theme, a minimal, vetted set of extensions, proper caching — and Lighthouse Mobile ≥ 85.
Roughly half of the WooCommerce inquiries we get start with "the store already exists, but…" What follows is speed, an unfinished checkout, or integrations that never quite worked. We take them on. A technical audit shows what can be fixed without a rewrite and what has to be redone. If the old store is on a ready-made platform or a custom solution — we migrate the catalog, orders, and SEO rankings. Redirects from old URLs preserve positions in Google — the move passes unnoticed by the search engine.
Integrations are standard scope, not "a paid extra." LiqPay, Fondy, PrivatBank — card payments, Apple Pay, Google Pay, installments. Nova Poshta API — calculation, tracking, SMS. Two-way stock sync with 1C or a CRM. A Google Shopping feed and Meta Catalog — ads switch on the day of release, not a month later. More detail on each integration — on the main e-commerce page. All store formats →
When does a WooCommerce store outgrow the platform? When the catalog approaches 50,000 SKUs with complex filtering, or you need B2B logic: multiple warehouses, negotiated prices, EDI. Then we honestly recommend a headless CMS or a custom build — and help you plan the migration in advance, not in the middle of a crisis. Headless CMS →
Support for an already-launched store — updates, security, backups — we run as a separate service line. If your case is a new online store on WordPress or an upgrade to an existing WooCommerce store, tell us the task: in 30 minutes we'll say exactly what's needed and roughly what it will cost. Website maintenance →