WordPress and WooCommerce development

We build and fix WordPress sites and WooCommerce stores: custom plugins, child themes, Elementor Pro layouts, multilingual setups and stock and price sync with 1C or an ERP. We also rescue sites that other developers left behind, and several stores have been in our care since 2021.

When to call us

Most WordPress projects come to us with a history: a theme edited by three people, forty plugins and one integration nobody fully understands.

Stock and prices live in 1C or an ERP, and someone retypes them into the store every week
The site went down after a plugin update, and the agency that built it no longer answers
Category pages take several seconds to open, and the admin panel is even slower
The theme files were edited directly, so every update wipes someone's changes
You need the store in several languages without running separate sites
The Elementor layout falls apart on phones, and fixing one page breaks another

What we do

WooCommerce stores

Catalogs with attributes and filters that work, product search, checkout and payment gateways, order statuses and emails. New stores or changes to the one you already sell from.

Custom plugins and mu-plugins

Business logic lives in its own plugin or in a must-use plugin, not in theme files. It survives theme updates, can be switched off for testing and is kept in version control.

Child themes and Elementor Pro

Child themes on top of a commercial or custom theme, layouts from Figma built in Elementor Pro, and mobile layouts that hold up on small screens.

1C and ERP integration

Products, stock, prices and attributes arrive in WooCommerce from the system that owns them. Orders can travel back, so nobody copies data between two windows.

Multilingual sites

Polylang setups with translated pages, products, categories and slugs, correct hreflang and a language switcher that leads to the same page in another language.

Rescue and speed

Diagnosis of sites that crash, show a white screen or slow down after updates. We find the cause, fix it and set things up so it does not happen again.

Stock and prices from the system that owns them

In many stores the real catalog lives in 1C or another accounting system, and the website is a copy that goes out of date by lunchtime. We connect the two so products, stock levels, prices and attributes move into WooCommerce on a schedule, without anyone retyping them. The hard part is the details: WooCommerce keeps lookup tables that must be refreshed after an import, or filters and search show the wrong products, and the accounting system sometimes sends data that WooCommerce refuses. We handle those cases in code and log them, so a failed import is noticed the same day.

Rescuing a site someone else built

A typical call starts with the site being down after an update. Usually it is a broken plugin release, rolled back within the hour, plus a database record that needs repair. The longer work comes after: we put the code into a repository, set up a staging copy, move custom code out of the theme into a child theme or a plugin and remove what nobody uses. Page builder data needs particular care, because Elementor stores layouts as serialized data that a careless search and replace will break. We have also moved a multilingual site from one translation plugin to Polylang without losing its translations.

Kept alive for years, not for a launch

Several of the stores we work on have been in our care since 2021. None of them has a developer on staff, so when something breaks on a Saturday, they write to us. The routine is ordinary and it works: updates on a staging copy first, then the live store after checking catalog, cart and checkout, backups to separate storage, and monitoring that watches the checkout page rather than only the home page. Speed work happens along the way, when a category page starts to crawl or a new plugin adds a second of load time.

How we start

Access and snapshot

You give us admin, hosting and repository access. We take a full backup and record plugin versions, speed and key pages before changing anything.

Diagnosis or spec

For an existing site you get a list of problems and risks. For new work you get a scope with the pages, integrations and plugins involved.

Build on staging

Changes are made on a copy of the site. You review them there, not on the live store.

Release

The changes go live at an agreed time, and we check catalog, cart, checkout and forms right after.

Support

If you want, we keep looking after the site every month: updates, backups, fixes and small changes.

What we work with

WordPress

Code

Integrations

Operations

Ways to work with us

Fixed-scope project

A new store, an integration with 1C or an ERP, a redesign in Elementor or a move to Polylang, with an agreed scope.

Monthly support

Updates, backups, monitoring, fixes and a volume of small changes every month, for stores that cannot afford to be down.

Hourly or single task

A crash after an update, a slow category page or a plugin conflict, billed by the hour or as a fixed task.

Related projects

ConvetePHP, WordPress EYE-t – FarmaplantUX / UI design, MySQL, PHP, JavaScript, CSS3, HTML5, WordPress Freedom LessonsUX / UI design, MySQL, PHP, JavaScript, CSS3, HTML5, WordPress

Reviews

We treat each client and his project with love.

Revol team continues to streamline the client’s development capabilities through their high-quality work and reliable support. They communicate effectively and exhibit a strong understanding of the client’s needs and business.

Tomas

CEO (Yukon, Canada)

The work from Revol, have fully met expectations and satisfied the client. Their fresh approach and ability to remain available for support have been valuable assets. Customers can bring them on for a communicative, client-oriented team to achieve their goals with.

Andrey

CEO, Stellium (USA)

Frequently asked questions

Can you take over a store built by another agency?

Yes, that is how most of our WordPress work starts. We take a full backup, look through the theme, plugins and custom code, and tell you what is broken, what is risky and what can wait before agreeing any scope.

Which accounting systems can you connect to WooCommerce?

We have built and supported 1C exchanges with WooCommerce for years. Other ERP and accounting systems can be connected through their API or file exports. The rule is the same in every case: the system that owns the data is the source, and the store follows it.

Our site broke after an update. What do you do first?

Bring it back. Usually that means rolling back the plugin or theme release that caused it and repairing the database if needed. Then we find out why it broke and set up a staging copy, so the next update is tested before it reaches the live site.

Will you edit plugin or theme files directly?

No. Changes go into a child theme or a custom plugin, so updates do not overwrite them. If a previous developer edited plugin files, we move those changes out first.

Elementor or a custom theme?

Elementor Pro suits sites where the owner wants to change pages without a developer. A custom theme suits stores where speed and a strict design matter more. Many sites use both, and we will tell you which fits after looking at what you have.

Can you make our store multilingual?

Yes, with Polylang: translated pages, products and categories, translated URLs and correct hreflang so search engines show the right language. We also move sites from other translation plugins to Polylang with their existing translations.

Can you speed up a slow store?

Usually. We measure first, then look at slow database queries, heavy plugins, images, caching and the server itself. You get before and after numbers, so it is clear what each change did.

Do you build new WordPress sites from scratch?

Yes, from a design in Figma or from a brief. For larger web applications we often suggest a different stack, and our web development page explains when that makes sense.