WooCommerceWhat we build on WooCommerce
Seven things we do most for WooCommerce stores.
Is WooCommerce the right home for you?
WooCommerce gives you full control, and the upkeep that comes with it.
Teams choose WooCommerce for
When it is not the right fit
How WooCommerce works, and why it slows down
WooCommerce is a plugin that turns a WordPress site into a store. That one fact explains most of its strengths and most of its problems. You own everything, and everything runs on your server.
Every page is built by PHP, on your hosting
When a shopper opens a product, WordPress loads its core, your theme and every active plugin, then queries the database. Page caching hides that cost for most visitors, but carts, checkouts and account pages can’t be cached. That’s why a store can feel fine on the home page and crawl at checkout.
Orders now have their own tables
For years, orders were stored as WordPress posts, mixed in with blog content. High-Performance Order Storage (HPOS) moved them into dedicated tables and is the default for new stores. Older stores often still run in compatibility mode because one plugin was never updated. We find that plugin before anything else.
Two APIs, two jobs
The WooCommerce REST API (v3) is for back-office work: your ERP reading orders, pushing stock and updating prices, authenticated with API keys. The Store API is what the block-based cart and checkout use in the browser. Mixing them up is a common reason custom checkouts break after an update.
Background jobs run through Action Scheduler
Subscription renewals, webhooks and many plugin tasks are queued in Action Scheduler. If WP-Cron isn’t firing reliably, that queue backs up, and renewals or ERP syncs run late without warning. On busy stores we trigger it from a real server cron instead.
When a WooCommerce store is slow, the cause is almost always hosting, a few heavy plugins or a queue nobody is watching.
Where should a WooCommerce store live?
Hosting is the biggest single factor in WooCommerce speed. Here is how we think about the three common options. We partner with WP Engine, Nexcess and Hostinger, and we’ll still tell you if another set-up suits you better.
Budget shared or entry WordPress hosting
Small catalogues, modest traffic- Good for
- New or small stores with a few hundred orders a month and a tight budget.
- Watch for
- Limited PHP workers, so checkout slows when several people buy at once.
- You manage
- Plugin updates, backups you can restore, and a staging copy.
Fine to start on. Plan the move before a big launch, not during it.
Managed WordPress or WooCommerce hosting
Where most growing stores belong- Good for
- Stores where uptime and checkout speed directly affect revenue.
- What you get
- Server-level caching, staging, daily backups, an object cache and support who know WordPress.
- You manage
- Plugin choices and testing updates on staging before they go live.
Our usual recommendation, with less to babysit and more predictable speed.
VPS or cloud server
High volume or unusual needs- Good for
- Large catalogues, heavy custom code or integrations that need their own workers.
- Watch for
- Security patching, monitoring and scaling are now your job, or ours on a care plan.
- You manage
- The server itself, plus everything above.
Worth it with a team or partner who will look after the server every week.
A WooCommerce build, start to launch
- Week 0
Audit call
Plugins, hosting and pain points in 30 minutes.
Plugin audit - Weeks 1–2
Plan
Theme, plugin stack and data plan agreed.
Stack plan - Weeks 3–8
Build
Block theme, extensions and integrations, demoed weekly.
Staging site - Weeks 9–10
Test
Checkout, renewals, emails and sync tested.
Test report - Week 11+
Launch and care
Go-live, then a care plan or hand-over.
Live store
What can go wrong on a WooCommerce project
These are the risks we plan around from the first week.
One payment or shipping plugin update on a Friday afternoon can stop orders over the weekend.
Updates go to a staging copy first, we run a test order through each payment method, then release in a quiet window with a backup taken minutes before.
A plugin that writes order data to the old posts table can leave orders half-synced after the switch.
We check every plugin for HPOS compatibility, run sync mode first, compare order counts and totals, then switch with compatibility mode on until the numbers match.
If Action Scheduler stalls, subscription renewals and webhooks pile up without anyone noticing.
We move scheduling to a real server cron and alert if the queue of past-due actions grows beyond a set limit.
Stock edited in both places, or a failed sync no one noticed, leads to overselling.
One system owns each field, every sync has an error path, and a daily reconciliation report flags differences before customers do.
What you get each month, and what we need from you
A care plan only works if both sides know their part. Here is the rhythm for a typical WooCommerce care plan.
What we do
- Every weekUpdates, tested first
Core, theme and plugin updates applied on staging, a test order placed, then released.
- Every dayBackups and monitoring
Off-site backups, uptime checks and alerts for failed orders or a stuck queue.
- Every monthA written report
What we updated, what broke and how we fixed it, speed trends and what we’d tackle next.
- When neededSmall changes included
A new shipping rule, a tweak to a template, a plugin swapped for something leaner.
What we need from you
- OnceAdmin and hosting access
A named admin account for us, hosting access and the payment gateway’s test mode details.
- Before campaignsA heads-up
Tell us about sales and launches, so we freeze updates that week instead of releasing them.
- MonthlyFifteen minutes
Read the report and approve or park the suggestions.
- OngoingOne owner for each system
Who decides about prices, stock and content, so a change request never stalls.
About WooCommerce development
Anything else, ask on the audit call.
Ask an engineer
Not answered here? Ask on the free 30-minute audit call. An engineer replies within one business day.
Quick facts
- Based in Delhi, India Working across time zones, with written weekly updates.
- Fixed quote first Nothing is billed before you agree it.
- You own it The code, workflows and accounts are yours.
- Stores and ERPs Shopify, BigCommerce, WooCommerce and Adobe Commerce, with NetSuite, SAP Business One, Odoo and Dynamics 365.
What is HPOS and do we need it?
High-Performance Order Storage keeps orders in dedicated database tables instead of the posts table, which is faster and more reliable at volume. Intelligize Digital checks your plugins are compatible, then migrates.
Should we use the block-based checkout?
Usually yes for new builds. It is the direction WooCommerce is going, but some older payment or checkout plugins still need the classic checkout, so we check first.
How many plugins is too many?
There is no number, but every plugin is another update to test. Intelligize Digital looks for overlap and replaces several plugins with one small custom feature where it pays.
Should we move to Shopify instead?
Sometimes. If nobody wants to maintain hosting and updates, a hosted platform may suit you. If you rely on WordPress content or custom features, staying can be right. The audit compares both.
Can you connect WooCommerce to our ERP?
Yes. We use the WooCommerce REST API and webhooks with workflow automation to sync orders, stock, prices and customers with Odoo, NetSuite or Business Central.
Which hosting do you recommend for WooCommerce?
For most growing stores, managed WordPress or WooCommerce hosting with staging, daily backups and an object cache. Intelligize Digital partners with WP Engine, Nexcess and Hostinger and recommends the plan that fits your traffic, catalogue and budget.
What is the difference between the WooCommerce REST API and the Store API?
The REST API is for back-office systems such as an ERP reading orders and updating stock, authenticated with API keys. The Store API powers the block-based cart and checkout for shoppers in the browser. Integrations should use the REST API.
Why are our subscription renewals running late?
Usually because Action Scheduler depends on WP-Cron, which only runs when someone visits the site. Intelligize Digital moves scheduling to a real server cron and monitors the queue so renewals and webhooks run on time.
Is WooCommerce secure?
WooCommerce core is well maintained. Most security problems come from outdated or abandoned plugins and weak hosting. A care plan with tested updates, a short plugin list and monitoring removes most of the risk.
Related WooCommerce reading
How many plugins does
your store really need?
Send us your plugin list and hosting setup. An engineer replies within one business day.
What happens next
- An engineer replies Within one business day, by email.
- A free 30-minute audit On a call with an engineer.
- A fixed quote It follows the audit. Nothing is billed before you agree it.