01

What I build

  • Booking flows

    Booking windows, hotel or slot selection, booking snapshots and cancellation deadlines.

  • Deposits and balances

    Pay a deposit now and the remaining balance later, with clear payment states on every order.

  • Stripe checkout

    Stripe integrated and debugged, including checkout loading and AJAX failures.

  • Catalogue tooling

    Admin tools that audit large catalogues for duplicates, missing attributes and weak product images.

  • Speed and stability

    Slow stores traced to the plugin, query or cron job causing it, then fixed at that point.

02

How I work

  1. Step 1
    Map the money

    Which states an order can be in, when money moves, and what happens on a cancellation.

  2. Step 2
    Build on WooCommerce, not around it

    Native hooks and order data, so updates and extensions keep working.

  3. Step 3
    Test the unhappy paths

    Failed payments, abandoned checkouts and late cancellations, not only the demo order.

  4. Step 4
    Watch the server

    Logs and load checked after launch; a store that slows down under its own plugins gets diagnosed, not upsized.

  5. Step 5
    Hand over

    Settings screens for the rules that change, plus recorded admin guides.

03

Selected work

Client names are redacted to protect their systems. The work and the numbers are real.

  • Bookings · Deposits · Stripe

    Event hotel booking platform

    A WooCommerce layer for hotel bookings: hotel selection, booking snapshots, deposits and remaining balances, cancellation deadlines, booking windows and payment states, paid through Stripe and written back to HubSpot.

    Along the way: Stripe checkout loading issues and WooCommerce AJAX failures traced and fixed, with versioned patches because there was no staging site.

    • WooCommerce
    • Stripe
    • HubSpot
    • Custom plugin

    Read the case study →

  • Performance · Root cause

    11,000 requests from one plugin

    A store kept loading its server. The logs showed a payment plugin making more than 11,000 requests to its own site. Removing it brought the CPU back to idle, with no hosting upgrade.

    • Logs
    • WooCommerce
    • Server
  • In development · Catalogue audit

    Audit tool for a 4,000-product store

    A WooCommerce admin plugin for a catalogue of about 4,000 products: duplicate detection, missing colour metadata, simple products that should be variable, and image quality checks, with review groups that learn from the reviewer's decisions.

    • WooCommerce
    • WP-Cron
    • Admin UI
04

Quick answers

Can WooCommerce take deposits?

Yes. The booking platform above takes a deposit at checkout and tracks the remaining balance and its deadline on the order.

My store is slow. Do I need a bigger server?

Usually not first. I check logs, slow queries, cron and plugin behaviour; in one case a single plugin was flooding its own site with requests.

Do you build custom product types or rules?

Yes, as a small plugin on WooCommerce hooks, so the store keeps working with updates and other extensions.

05

Related