WooCommerce stores
on today’s foundations
We build WooCommerce stores and bring older ones up to date, with orders in tables of their own, a checkout built from blocks and your other systems connected, so the store can grow with the business.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When the store still runs the way it began
Many businesses run a WooCommerce store that has grown for years, one extension at a time: extensions are the add-ons that bring in features beyond WooCommerce’s own. Its orders may still be kept the way WooCommerce first kept them, as posts in tables shared with the site’s pages and products, while new stores keep them in tables of their own.
Its checkout may still be the classic one, the checkout page WooCommerce has long had, while new stores get the block checkout, built from blocks. Every extension added along the way still runs, and some may have been written for the old ways, so moving to the new ones means checking each extension first, and the move tends to be put off.
What we build
Stores built on WooCommerce and WordPress and kept on WooCommerce’s current ways of working, with every change tried on a copy of the store before it reaches your customers.
New WooCommerce stores
A store on WordPress with a custom theme, the part that sets its design and layout, built around your products and the way you sell them.
Moves to WooCommerce
Products, customers and past orders brought over from another platform or a custom build, with every old address redirected to its new page.
Orders moved to their own tables
Orders moved to the new order tables, with compatibility mode on while each extension that reads them is checked, so the store can switch back.
Checkouts rebuilt in blocks
The classic checkout moved to the block checkout, each of your changes to it rebuilt where the block checkout supports them, and tried with test orders.
Custom extensions
Features your store needs, built as extensions of your own on the hooks WooCommerce supports, the set points in its code where an extension can run, and kept apart from the theme.
Payments and delivery
Payment and delivery options added through each provider’s own extension, set up for your store and tried with test orders before customers use them.
Connections to stock and finance
The store kept in step with your stock and finance systems, with one system in charge of each detail, so stock levels, orders and invoices agree.
A store that stays quick
The store measured for shoppers and for your team in the admin, the causes of slow pages and slow screens found first, then fixed where they matter most.
Updates kept current and secure
WooCommerce, WordPress, PHP and every extension kept on supported versions, each update tried on a copy of the store first, with security fixes on a regular rhythm.
- Stores on any platform, or help choosing one:E-commerce
- The site around the store:WordPress Development
- Care once it’s live:Support & Maintenance
- Developers in your own team:Hire WooCommerce Developers
Orders in tables of their own
WooCommerce first kept each order the way WordPress keeps a post, in tables shared with the site’s pages and products, with most of its details stored as separate rows. High-Performance Order Storage, WooCommerce’s name for the newer way, keeps orders in tables made for them, and new stores have used it by default since WooCommerce 8.2.
A store moving its orders can turn on compatibility mode, which keeps a second copy in the old tables as orders are created or changed, so it can switch back while it checks that every extension that reads orders works with the new tables. WooCommerce lists any extension that doesn’t support them yet, and won’t switch over while one is active.
Order 1024
Processing
- Linen apron
- Tea towel
- Table runner
Total
Gift note
The order itself
Its number, status and totals.
Its addresses
Where to bill, and where to deliver.
How it was placed and handled
Where it was placed, when it was paid, and whether its stock was taken off.
Anything extensions add
Details of their own, such as a gift note.
Before, most of these were rows in tables shared with your pages and products.
{{ orStatus }}
A checkout made of blocks
A WooCommerce store’s checkout is one of two kinds. The classic checkout is a page that extensions change through hooks. The block checkout, the default for new stores since WooCommerce 8.3, is built from blocks a team can arrange in the editor, and extensions change it in ways of its own, among them places set aside for them and a way to add fields.
Some of the classic checkout’s hooks work in the block checkout, but not all, so a store moving to it first checks that each extension touching the checkout has a version for blocks, rebuilds its own changes the block checkout’s way, and tries both with test orders. The classic checkout still works, so a store can move when its extensions are ready.
Start with a review of your store
The review covers its WooCommerce, WordPress and PHP versions, and where each stands on support; where its orders are kept, and which extensions support the new order tables; which checkout it uses, and which extensions change it; its extensions and theme, which are maintained, and which do the same job twice; its payment, delivery and other connections; its speed, for shoppers and in the admin; and how it’s updated, backed up and tested.
Starting a new store? We build the catalog, the checkout and one connection and release them early, so customers can buy while the rest is built.
Either way, you get a written review and a proposal for the first step.
Questions worth asking
Is WooCommerce the right platform for us?
It suits a business that wants its store and its content on one WordPress site, on hosting it chooses, with features it can add as its own. Most stores are best served by an established platform, and if another would serve you better, we’ll tell you and recommend the simplest option that fits.
E-commerceStores on Shopify:Shopify Development
Should we move our orders to the new tables?
WooCommerce recommends it, and for most stores it makes sense once every extension that reads orders supports the new tables; WooCommerce won’t switch over until they do. Compatibility mode keeps a copy in the old tables while you check, so the store can switch back. That copy is for reading only, so an extension that still writes orders there is updated first. WooCommerce’s documentation sets no date for the move.
Do we have to move to the block checkout?
No, not as WooCommerce’s documentation stands in October 2026: the classic checkout still works. The block checkout is the default for new stores, so we move a store to it once each extension that touches its checkout has a version for blocks.
Can you move our store to WooCommerce?
Yes, from another platform or from a custom build. Products, customers and past orders are brought over and checked against the old store, and every old address is redirected to its new page, so links and bookmarks keep working. How long it takes depends on the store, and the review sets it out.
Can you take over our existing store?
Yes. We work on a copy of the store first, read its theme and extensions and note the versions it runs, and the review says what to change, in what order. Nothing changes on the live store until you agree.
Our store is slow. Can you make it faster?
Usually, once the cause is found. We look at how the store performs for shoppers and for your team in the admin, find what slows each down, from images and extensions to the server, and fix what matters most, measuring each fix.
Performance & OptimizationCan it connect to our stock and finance systems?
Yes. We settle which system has the final word on each detail, from stock levels to invoices, then keep the store in step with your stock and finance systems.
Systems & API IntegrationCan you build a feature just for our store?
Yes, as an extension of your own, built on the hooks and APIs WooCommerce supports and kept apart from the theme, so a new theme doesn’t take it away, and each WooCommerce update is tried against it on a copy of the store first.
Who hosts it?
WooCommerce is software that runs on your own WordPress site, so the store runs on hosting you choose. Hosting and the platform beneath your software are a service of their own.
Cloud, DevOps & SecurityHow do you keep it secure?
By keeping WooCommerce, WordPress, PHP and every extension on supported versions, and trying each update on a copy of the store before it goes live. Each WooCommerce version sets the WordPress and PHP versions it needs, so the three are planned together. Our security work adds threat modeling, code review and checks in every build.
Application SecurityWhat does it cost?
It depends on the store: what it sells, the extensions it runs, and whether it’s new or moving onto current versions. You get a written proposal before any work starts: the scope, the price or rate, and how you pay.
PricingCan WooCommerce developers work inside our own team?
Yes. We introduce WooCommerce developers matched to your store within 48 hours of your request, all working in your time zone, and you decide who joins.
Hire WooCommerce Developers
WooCommerce and its associated designs are trademarks of Automattic Inc. Webair isn’t affiliated with or endorsed by Automattic.
Let’s build it better
Tell us about your store, or the one you have in mind. A short call is enough to agree what to look at first.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}