WooCommerce work
that survives updates.

Custom extensions, HPOS compatibility, checkout and payment integrations, and the ERP sync your store has been faking with a spreadsheet. Prepaid in Hour Blocks of 6, 12 or 24 hours, written as a proper plugin against documented hooks so the next WooCommerce release does not undo it.

Custom extensions HPOS compatibility Payment gateways Shipping methods Erp & stock sync

Within two business days

Your message goes straight to the studio. No sales queue, no account manager in between.

Prepaid Hour Blocks

Buy 6, 12, or 24 hours up front at $30/hr. Unused hours never expire.

10 live products

PHP in production, with WordPress and WooCommerce plugin work built against the official APIs.

You own the code

Full source, in your repository, with the reasoning written down. No lock-in to us or anyone else.

Six jobs that make up
most WooCommerce work.

Written with enough technical detail that you can tell whether we have actually opened WooCommerce, rather than whether we can spell it.

Custom extensions and product logic

The thing your store needs that no plugin on the marketplace quite does: a custom product type, per-customer pricing, a configurator that calculates a price from options, a bundle that reserves stock from its components, a role-based wholesale tier. Built as its own plugin against WooCommerce hooks and CRUD classes, with settings in the WooCommerce settings screens where your team already looks.

  • Custom product types & data panels
  • Dynamic and role-based pricing rules
  • Bundles, add-ons & configurators
  • Custom order statuses & workflows
  • Settings inside WooCommerce, not a new menu
  • Uninstall that leaves the database clean

HPOS migration and compatibility

High-Performance Order Storage keeps orders in dedicated tables instead of the posts table. It is the default for new stores and it is a large speed win at volume - but any custom code that touches orders through post meta breaks quietly when you turn it on, which is the worst way for order code to break. We audit the custom code, move it onto the order CRUD API, declare compatibility properly, and verify against a synchronised copy before the switch.

  • Audit of custom order meta access
  • Migration to the order CRUD API
  • Compatibility declared for your plugins
  • Verification against synchronised data
  • Third-party plugin compatibility check
  • A rollback path if a plugin is not ready

Checkout, blocks and payment gateways

Block cart and checkout changed how customisation works: a filter that used to add a field to the classic checkout does nothing in the block version, and a payment gateway needs a separate block integration to appear at all. We build gateways against the WooCommerce gateway class plus the block payment-method integration, add checkout fields through the supported extensibility points, and keep the classic checkout working where you still need it.

  • Custom payment gateways, both checkouts
  • Block checkout fields via supported APIs
  • Store API usage for headless front ends
  • Validation that reads well to customers
  • Webhook handling for asynchronous payments
  • Refunds and partial refunds wired through

Shipping rules and carrier integrations

Shipping is where store owners lose margin quietly. A method that calculates from real weight and dimensions, honours destination zones, and falls back sensibly when the carrier API times out is worth more than any theme change. We also wire the other direction: label creation, tracking numbers written back onto the order, and the customer email that carries them.

  • Custom shipping methods & zones
  • Live carrier rate lookups with fallbacks
  • Weight, dimension & postcode rules
  • Label and tracking write-back
  • Pickup points and delivery windows
  • Tax and duty edge cases surfaced early

ERP, stock and accounting sync

Orders that have to reach your accounting system, stock levels that have to come back the other way, product data that lives in a supplier feed. The trap is doing any of it inside the checkout request, where a slow partner system turns into an abandoned cart. Everything goes through Action Scheduler as a queued, retry-safe job with an idempotency key, so a partner outage delays the sync instead of losing the order.

  • Queued syncs via Action Scheduler
  • Idempotent jobs safe to retry
  • WooCommerce REST API in both directions
  • Supplier feed import and normalisation
  • Conflict rules when both sides changed
  • A failure log a human will actually read

Store performance

A slow store is usually not WooCommerce being slow. It is thirty plugins each adding queries to every page, product meta lookups with no index behind them, an options table autoloading megabytes on every request, and hero images shipped at full resolution. We profile with query monitoring on a staging copy, fix the causes in order of size, and give you the before and after numbers.

  • Query profiling on category & product pages
  • Autoloaded options cleanup
  • Index design for custom meta lookups
  • Object caching and transient hygiene
  • Image sizing and lazy loading
  • Plugin audit with an honest removal list

What you can install and keep.

Everything ships as something your next developer can read, install and maintain without us in the room.

A self-contained plugin

Your custom work in its own plugin with a proper header, version number and activation hooks - never scattered into a theme functions.php that the next redesign deletes.

Documented hooks only

Built against WooCommerce actions, filters and CRUD classes. No core edits, and a deliberately short list of template overrides.

HPOS compatibility declared

Anything touching orders uses the order CRUD API and declares compatibility, so switching storage later is not a second project.

Tested on a staging copy

Store changes get built and verified against a copy of your real data, with your real plugin set, before they go anywhere near live orders.

Install and settings notes

How to install it, what each setting does, and what happens on uninstall - written for whoever manages the store, not just for a developer.

A support window

A short window after handover. If our change caused it, fixing it is not billed as new hours.

What we can honestly show you.

Client work stays under NDA, so what we show is what we run ourselves: our own commerce-shaped work and the plugin practice behind it.

Plugin practice

WordPress plugin development

The sibling service page, covering how we build WordPress and WooCommerce plugins: official APIs, no core edits, full source that you own. Same working method, same Hour Blocks.

Plugin development
Payments

UslugeHR

A booking marketplace with role-based accounts and Stripe wired into the booking flow. Built on Laravel rather than WooCommerce - named honestly - but the payment, refund and entitlement logic is the same problem.

Read the case study
Catalogue data

CijeneHR

Thousands of products from multiple retailers, normalised into one comparable catalogue with price history. Directly relevant to supplier feeds, stock sync and product data cleanup on a store.

Read the case study
Sounds like your project? Prepaid Hour Blocks · reply within two business days
Start a project

Four steps, no discovery call
you have to sit through.

Tell us what the store needs. Store work is built and verified on a copy of your data before it meets a real order.

1

Tell us the problem

A few sentences on what you have and what you need. Rough is fine - we ask the questions that matter and tell you honestly if it is not a fit.

2

Pick an Hour Block

Prepay a block of hours - 6, 12, or 24. The block is the budget: we work until it is used, or you top up.

3

Work in the open

Work happens as a plugin on a staging copy of your store, with your real plugin set installed, so conflicts surface before customers find them.

4

Handover and support

You get the source, the runbook, and a short support window for anything that surfaces after launch.

Bought in
prepaid Hour Blocks.

No volume games and no agency margin on top. You buy the block of hours that fits the size of the job, so you know the number before we start rather than after.

Starter 6 hrs
$180

Typically enough for a focused fix, a small feature, or an integration you are stuck on.

Start with Starter
Pro 24 hrs
$720

Typically enough for a larger build with integrations, auth, or billing wired in.

Start with Pro

Every Hour Block is hours at $30/hr with no discount. It is a bucket of time, not a fixed-scope deliverable. Unused hours do not expire - roll them into the same project or a later top-up. If the work runs long, you buy another block; nothing is billed without you agreeing to it first.

Frequently asked.

What is HPOS and do we need to care about it?

High-Performance Order Storage moves orders out of the WordPress posts table into dedicated order tables. It is the default for new stores and it is much faster once you have serious order volume. You care about it because any custom code that reads or writes orders through post meta will silently stop working or write to the wrong place. Making a store and its custom code HPOS-compatible is a specific, boundable job.

What is an Hour Block, and what if the job takes more or fewer hours?

An Hour Block is a prepaid block of hours: Starter is 6 hours for $180, Standard is 12 hours for $360, Pro is 24 hours for $720. It is a bucket of time, not a fixed-scope deliverable. Unused hours do not expire and roll into the same project or a top-up. If the work runs over, you buy another block, and nothing gets billed without you agreeing to it first.

Will your changes survive a WooCommerce update?

That is the whole point of doing it as a plugin. Custom work goes into its own plugin using documented hooks, filters and the CRUD classes, never as an edit to WooCommerce core or a theme that will be replaced. Template overrides are used only where WooCommerce provides them, and we keep the overridden file list short so version bumps stay boring.

Can you build a custom payment or shipping method?

Yes, both. A payment gateway extending the WooCommerce gateway class, with the separate block-checkout integration so it also appears in the block cart and checkout rather than only the classic one. Shipping methods that calculate from weight, dimensions, destination or a live carrier API, with sane fallbacks for when that API is down.

Can you connect WooCommerce to our ERP, CRM or warehouse?

Yes. Usually through the WooCommerce REST API in one direction and queued jobs through Action Scheduler in the other, so a slow or offline partner system does not block a customer checking out. Every sync is built to be safe to run twice, because eventually it will be.

Our store is slow. Is that a WooCommerce problem?

Usually not by itself. It is normally too many plugins running queries on every page, unindexed meta lookups, an oversized options table autoloading on every request, or images served at full size. We measure first and tell you which of those it actually is, rather than selling you a caching plugin and hoping.

Do you work on the store theme too?

For functional work, yes: product page layout, cart and checkout behaviour, block templates. If you need a new brand look, we scope that as its own piece of design work rather than pretend it is the same job.

How do we start?

Send a few sentences through the form on this page: what the store sells, what is missing or broken, and which plugins are involved if you know. You get a reply from us directly, usually within two business days, with questions and which Hour Block fits.

Tell us about your WooCommerce store.

What the store sells, what is missing or broken, and which plugins are involved if you know. A few sentences is plenty - we read every message and reply within two business days with an honest read and the Hour Block that fits.

Prefer email?

[email protected]
Please enter your name
Please enter a valid email
Which Hour Block?
Tell us a little about the project
Thanks - we have got it.

Expect a reply from us within two business days.

Hour Blocks from $180reply within two business days Start a project