Who: Mariusz Szatkowski, a senior WooCommerce and WordPress developer since 2006. I work alone: no team, no subcontractors.
What: Custom WooCommerce development, payment and shipping integrations, multi-currency stores, subscriptions, B2B rules, ERP links and headless builds where they make sense.
Where: Remote from Gdynia, Poland, for shops across the EU, the UK and beyond. Communication runs by email, written documents and the repository. For VAT OSS, local payment methods and multi-market checkout, see the WooCommerce EU readiness assessment.
How much: priced per project after a written brief: fixed price for a defined scope, time and materials for ongoing work, a monthly plan for maintenance.
How does custom WooCommerce development on WordPress work?
WooCommerce developer: I am Mariusz Szatkowski (WPPoland). I build the catalogue, checkout, payments and the ERP link myself, remotely from Gdynia, with WordPress since 2006. No package prices here. Send a short brief via /en/contact/ and you get a written quote.
If checkout is already broken, start with the WooCommerce rescue sprint. Once the shop is stable, the store reliability plan covers ongoing care. If you are weighing Shopify instead, read the Shopify developer page.
WooCommerce makes sense when you want content and commerce on one WordPress install that you own: catalogue, checkout, stock and payment integrations next to your articles and landing pages. You bring the graphic design or wireframes; I turn them into a working theme and wire up the parts behind it, from REST and GraphQL integrations to payment gateways, and I measure performance against a baseline I agree. More on the general side in WordPress developer.
Who you are hiring
- Shipping commercial WordPress since 2006, before Gutenberg and the REST API
- Senior-led: the engineer at discovery is the engineer at the keyboard at week six
- No offshore handoff, no PM layer billed back to you
- WordCamp Europe organiser, WordPress Foundation Credits mentor
- Shopify Academy: CRO learning path plus Partner Marketing (Credly, 2025)
What does a WooCommerce developer do?
A WooCommerce developer builds and adapts the catalogue, checkout, payment and shipping layers of a store and connects them to inventory and accounting. Every decision there touches revenue, which is the difference from general WordPress work.
- Shopping flow: cart steps, checkout fields and product layouts that match how your customers buy.
- Stability: updates, plugin conflicts and performance problems, handled on staging before production.
- Integrations: ERP, CRM, carriers and payment gateways, so orders do not get retyped by hand. More in WooCommerce integrations with ERP and wholesale APIs.
One developer or an agency?
When you hire me, the person who reads your brief writes the code and answers your email. That suits a store that needs a senior developer on a defined scope. It does not suit a project that needs several workstreams at once or someone on call at night; I do not offer 24/7 cover or a guaranteed response time.
| Model | When it fits | What to get in writing |
|---|---|---|
| One senior developer (WPPoland) | Defined scope, one store, written process | Scope, staging, rollback, who has access |
| Agency | Parallel workstreams, hard deadline, on-call needs | Capacity, handoffs, who touches checkout in an incident |
How do checkout recovery, OMS and marketplaces work in WooCommerce?
A store that already sells rarely needs a new theme. It needs someone who reads checkout logs, payment webhooks and the order mapping into an OMS or marketplace feed.
Typical jobs on a live store:
- Payments: Stripe, PayPal or a local gateway leaves orders stuck in
pending. - Shipping: the carrier widget works in the cart, label generation fails.
- OMS or marketplace: duplicated stock, broken variants or a stalled order queue.
- ERP: invoices and stock drift apart after a plugin update.
I reproduce the fault on staging, fix the code or the API configuration, then check the mobile purchase path again.
How can a WooCommerce developer help you?
Custom features
I implement the design you supply and add what a template cannot do: product filters, a booking flow, your own discount rules or a product configurator.
Performance
Product and category pages are where speed matters. I measure Core Web Vitals on those templates, slim down scripts and queries, and repeat the measurement after the change. Faster pages remove friction; they do not guarantee more sales on their own.
Integrations
Carriers and label printing, a warehouse system that updates stock automatically, and payment methods that report a final status back to the order.
Security and updates
Updates tested on staging first, backups kept for 30+ days in EU countries, uptime monitoring every 1 to 5 minutes. Before I get access to a store with customer data, I sign a data processing agreement under Art. 28 GDPR.
Where technical depth pays back
Audits of slow stores keep turning up the same things: overlapping plugins, slow category queries and a checkout that wobbles under load. Another cache plugin rarely fixes it. The work is reading the query plan around wp_postmeta, trimming autoloaded options, profiling hooks and running a load test. What I promise afterwards is measured: a baseline, test conditions and the result after deployment. I do not promise a conversion lift, because product, traffic and price drive that too.
Which technical stack do I use in WooCommerce projects?
I pick tools around the store’s integrations, load and maintenance needs:
On top of that: Redis object cache, Varnish or LiteSpeed page cache, NGINX, and GitHub Actions so releases are repeatable and reversible.
What is headless WooCommerce?
Classic WooCommerce renders HTML on the server. In a headless build WordPress and WooCommerce keep products, orders, payments and storage, and a separate frontend in Astro or Next.js reads them over GraphQL or REST. That gives more control over Core Web Vitals and design and keeps the admin away from the public frontend, at the cost of two systems to maintain. I suggest it only when the trade-off fits.
Which integrations belong in a WooCommerce stack?
| Category | Tools |
|---|---|
| Payments | Stripe, PayPal, Square, Mollie, Klarna |
| Shipping | DHL, UPS, FedEx, Royal Mail, ShipStation |
| ERP/CRM | SAP, Microsoft Dynamics, Salesforce, HubSpot, Zoho |
| OMS and marketplaces | BaseLinker-type OMS, Amazon, regional marketplaces |
| Marketing | Mailchimp, Klaviyo, ActiveCampaign |
| Automation | Zapier, Make, n8n |
| Multilingual | WPML, Polylang, TranslatePress, Aelia |
Fewer plugins to maintain and a cleaner upgrade path on major WooCommerce releases are what lower the running cost over the years.
How do you do SEO for a WooCommerce store?
WooCommerce generates product and category pages in bulk. Left alone they ship thin text, duplicate filter URLs and heavy templates.
- Product schema: Product and Offer structured data, and AggregateRating only where the reviews are real.
- Category pages: treated as landing pages with real intro copy, internal links and a canonical rule, so they stop competing with each other.
- Filters: decide per parameter whether to canonicalise, noindex or block. The classic Layered Nav widget writes
filter_color=red,bluewith a raw comma, while the Product Filters block writesfilter_color=red%2CbluethroughURLSearchParams. Under RFC 3986 those are different URLs, so the store has to pick one form for links, canonicals and sitemaps. - Core Web Vitals: product and category LCP is usually one hero image and a page builder; fixing those two moves the whole catalogue.
Yoast or Rank Math give you the controls; how to use them depends on WooCommerce’s URL and template model. Background: best CMS for SEO in 2026 and what happens when an AI agent checks out.
What is AI-ready commerce and the Universal Commerce Protocol?
AI assistants that buy on a shopper’s behalf need clean product data. I check readiness for the Universal Commerce Protocol: catalogue and variant consistency, stock and availability signals, permission boundaries and checkout validation, then a pilot with monitoring and a rollback plan. Which channels support the protocol is confirmed during discovery; I do not promise visibility in any particular assistant. The broader work is described under AI implementation and MCP server development.
Selected WooCommerce work
- Performance recovery: WooCommerce scaling and TTFB recovery, a B2B catalogue under load.
- Wholesale integration: WooCommerce wholesale API integration, stock and price sync with an automotive parts wholesaler.
- Computer parts store: capslock.pl, WooCommerce with wholesaler integration and marketplace exports.
- Retail: floresy.online, a store for artificial plants and flowers.
- My own plugins: more than 25 free WordPress and WooCommerce plugins I publish in the WordPress.org directory, including Shoplex for EU shop rules (Omnibus, withdrawal button, GPSR) and Customs for the EU duty of 3 euros per item.
How to brief a WooCommerce project
Write down the scope, the systems the store has to talk to, constraints and what should work at the end. I reply in writing with questions and then a quote with its assumptions.
