WooCommerce developer in Newcastle

Freelance WooCommerce developer for Newcastle upon Tyne firms: checkout, UK shipping, ERP sync and HPOS. Remote from Poland, replies in 48 hours.

WooCommerce developer

My place in the WordPress community

  • I have had a wordpress.org account since 2006.
  • I contributed to WordPress core for versions 7.0 and 7.1.
  • I maintain 30 plugins on wordpress.org.
  • I organise and speak at WordCamps.
  • I have attended every WordCamp Europe from 2017 to 2026.

My WordPress.org profile

I am Mariusz Szatkowski, a WooCommerce developer working from Gdynia, Poland. I have no office in Newcastle. I build and fix WooCommerce stores for businesses in Newcastle upon Tyne remotely, by email and shared documents, and I reply within 48 hours. I am one person, not an agency, so the person who scopes your store is the person who writes the code.

Poland is one hour ahead of the UK, so your 9:00 is my 10:00. This page is for Newcastle upon Tyne in England. I also work with stores elsewhere in the UK, Wales included.

I have had a wordpress.org account since 2006, contributed to WordPress core for versions 7.0 and 7.1, maintain 30 plugins on wordpress.org, organise and speak at WordCamps, and have been at every WordCamp Europe from 2017 to 2026.

#What does a WooCommerce developer in Newcastle do for you?

Most briefs I get for UK stores fall into four kinds: an inherited store that is slow or breaks at checkout, a new store that must connect to an ERP or a courier, a store whose order table has grown heavy, and a store that needs a custom plugin because three plugins together almost do the job.

Each starts with a read-only look at what runs today: active plugins, the checkout path, gateway webhooks, shipping zones and the slowest admin screens. You get a written scope with assumptions and exclusions. Work starts after you confirm it in writing. The full service is described on the WooCommerce developer page.

Customisation goes through WooCommerce hooks and a custom plugin, never through edits to WooCommerce core, so the store survives updates. Presentation stays in the theme and business rules stay in the plugin.

#Do I design the store? No, I build your design

I do not do graphic design, UX, mockups or wireframes. If you search for a WooCommerce designer in Newcastle, you need a designer first and a developer second. You or your designer provide the design as a Figma file or a wireframe, and I build it as a working, fast, accessible store.

A design that includes the cart, checkout, empty states, error messages and mobile layouts saves the most time. If part of it cannot be built accessibly, for example white text on a pale sale badge, I tell you before I build it, with the specific screen.

#HPOS and caching: what happens to a heavy order table

High-Performance Order Storage (HPOS) keeps orders in dedicated tables instead of the WordPress posts and postmeta tables. The WooCommerce developer documentation lists four: wc_orders, wc_order_addresses, wc_order_operational_data and wc_orders_meta. Its stated reason is dedicated indexes, which means fewer read and write operations and fewer busy tables (HPOS documentation).

HPOS has been stable since WooCommerce 8.2 and is on by default for new installations. An existing store switches over by hand. The documentation describes the route: turn on compatibility mode, which syncs orders to the posts table, let the background actions copy existing orders across 25 at a time, switch to HPOS when both tables match, and keep compatibility mode on for a while. If something goes wrong, reverting to the posts table is instant (enabling HPOS).

Two things decide how smooth that is. The first is plugins: if an incompatible plugin is active, WooCommerce disables the HPOS option, and each extension has to declare support for it. The second is custom code that reads orders with get_post_meta(). The recipe book for extension developers tells you to use WooCommerce’s CRUD methods on the order object, so that WooCommerce picks the right tables (HPOS recipe book). I audit both before the switch, take a backup, and run the migration outside your trading peak.

Caching is a separate decision. I put full-page caching on catalogue and content pages and exclude cart, checkout and account pages. I check that a logged-in customer never sees another customer’s cart. HPOS speeds up order reads and writes. It does not replace a page cache, and a page cache does not fix slow order queries. A query audit on the slowest admin and checkout requests tells you which one you need.

#Checkout, payments and UK shipping

A new build starts with one decision that is expensive to reverse: whether checkout stays on the shortcode flow, moves to the block checkout, or splits into a headless front end. I write the decision down before the first commit, with the plugins that depend on it.

For payments I document, per gateway, the flows you use (single payment, subscriptions, refunds, partial refunds, 3-D Secure), a test matrix on staging and the webhooks the gateway sends. Duplicate webhook delivery must not create a second order. Gateway choice, fees and settlement are between you and your provider. I configure the store, and your accountant confirms the tax settings.

For shipping, WooCommerce zones and classes carry the UK rules you need: Great Britain, Northern Ireland, and any surcharge areas in your carrier contract. If you ship with Royal Mail or another carrier, I connect the store to the carrier’s label service and check that only one connector is active, so orders do not arrive twice, and that the tracking number reaches the customer email.

#ERP and Microsoft Dynamics 365 Finance and Operations

A store that ships goods usually has to talk to an ERP. The general pattern is on the WooCommerce ERP integration page. For Microsoft Dynamics 365 Finance and Operations I only describe what Microsoft Learn documents.

Finance and Operations exposes an OData V4 endpoint at the environment’s /data path. It covers the data entities marked as public, supports create, read, update and delete, and returns JSON. Query options include $filter, $select, $top, $skip and $count. Paging is server-driven with a maximum page size of 10,000. By default a call returns data for the user’s default company, and cross-company=true widens that. Batch requests can group several operations into one changeset that either all succeed or all fail (Microsoft Learn: OData).

For larger volumes Microsoft points to the data management framework, where files go through source, staging and target phases, with higher throughput than the synchronous endpoint. It also lists a limit: imported strings over 32,768 characters are truncated (Microsoft Learn: data management and integration).

In a WooCommerce project that means a design choice. Orders and stock levels move through a queue with Action Scheduler, so checkout never waits on the ERP. A failed job appears in the admin with a retry button, not silently overnight. Which entities, which direction and which system owns stock are decided with your ERP partner, in writing, before I build.

#Cookies, accessibility and VAT

These apply to every UK store, so I do not repeat them here. The software development for the UK and Ireland page covers UK cookie and data protection rules, the Equality Act 2010 and public sector accessibility, and how UK VAT works when I invoice from Poland. In a WooCommerce project they turn into three checks: analytics and advertising scripts do not run before consent where consent is required, checkout fields are the ones fulfilment and tax need, and the cart and checkout can be used by keyboard.

#Newcastle upon Tyne

Newcastle upon Tyne is a city of about 300,100 people. Between the 2011 and 2021 censuses its population grew by 7.1%, against 1.9% for the North East and 6.6% for England (ONS census area changes). A store based here sells to a local market that is growing and to the rest of the UK, so I set up shipping zones, delivery messages and search visibility for the whole country, not for one postcode.

#How a project runs

  1. You send the brief, the design file and, for an existing store, the list of active plugins.
  2. I return a written scope with assumptions, exclusions and a quote. Work starts after you confirm it in writing.
  3. I build in feature branches, with a review on each, and give you a staging link.
  4. You test the full order path on staging: cart, payment with test cards, confirmation email, admin order edit and refund.
  5. I deploy with a rollback path and send documentation for shop managers and developers.

After launch, updates, backups and monitoring can move to WordPress maintenance in Newcastle. Search visibility work, such as product schema, internal linking and Core Web Vitals on shop templates, can run as an ongoing monthly engagement scoped in writing. For a company site next to the store, see WordPress developer in Newcastle.

#Questions Newcastle businesses ask

Are you a WooCommerce agency? No. I am a sole proprietorship in Gdynia, Poland, with no account manager between you and the code. If a project needs several people at once, I say so in the written scope.

Can you design the store as well as build it? No. You or your designer provide the design as a Figma file or a wireframe, and I build it.

Can you move us to HPOS? Yes, after a backup and a plugin compatibility check, with compatibility mode on and a rollback path, outside your busiest weeks.

Can you connect the store to Dynamics 365 Finance and Operations? Yes, using its documented OData and data management interfaces. Scope and field mapping are agreed in writing first.

Do you have an office in Newcastle? No, I work remotely. Everything runs by email and shared documents, and I do not propose calls or meetings.

#How do you start?

Send a short description of the store through the contact page: the business goal, active gateways, shipping setup, any ERP, and the checkout problem you see. I reply within 48 hours with the risks I see and a proposed scope.

Need this service: WooCommerce developer in Newcastle?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Latest WooCommerce developer articles

Nov 8, 2026

Harmonised legal guarantee notice in WooCommerce: what Ireland requires

From 27 September 2026 an online shop selling goods to consumers in Ireland must show the EU harmonised notice on the legal guarantee, and the GARAN label where the producer offers a durability guarantee. What S.I. No. 124/2026 changes, where each element goes and how to build it in WooCommerce.

Explore other WordPress services and knowledge base