How I Fixed a Client's Shipping from Tokyo Airport

1 May 2026

I was sitting at Tokyo airport on Wednesday afternoon, waiting for my flight home, when a WooCommerce client called.

Two of their last orders had come through as pickup-only. One was from Queensland, which was the giveaway. Nobody in QLD is driving to Newcastle to pick up an order. Something was wrong with shipping.

Less than 30 minutes until boarding. The family was already keen to line up. I had my laptop and my phone as a hotspot.

First thing I did was log into the site and test it myself. The only shipping option at checkout was pickup. No delivery rates were coming through. I checked the WooCommerce Australia Post plugin, the paid one at $120 USD per year. There was an update available, and buried in the release notes was a brief mention that Australia Post had changed their shipping rates API. That tipped me off straight away. The version we were running was talking to the old address and the requests were silently failing.

The quick fix would have been to renew the subscription at $120 USD and download the vendor's update. But I had less than 30 minutes and the family were keen to get in line so we could get settled on the plane. So I asked Claude to fix the existing plugin instead.

Claude read the plugin code, confirmed the endpoint change, and checked the Australia Post developer docs to verify the new URL before patching anything.

Then it built the patched file, saved a backup, uploaded the fix, and ran a final end-to-end check by hitting the homepage to make sure nothing else broke.

The whole thing took about as long as it took me to get a coffee.

I posted to the team chat before I walked to the gate: "Quick fix with Claude instead of $120usd subscription to plugin." We're planning to move this client onto our own Jezweb Australia Post plugin when the timing is right, but mid-airport wasn't the moment for a plugin swap.

We were still running the paid plugin we'd bought from woocommerce.com years ago. The vendor had already shipped an update with the fix, but it was behind a $120 USD renewal wall. Pay to keep the licence current, or the shipping stays broken.

Without Claude, I could have probably figured it out myself. Eventually. I'm not a PHP developer, and some of our team would have done it a lot faster than me. But even someone who knows PHP well would have spent longer reading the API docs and tracing the endpoints than Claude took to just do it.

That's the part worth paying attention to. I didn't need to be a developer. I needed to understand the problem well enough to point Claude at it. "The Australia Post API endpoint has changed, here's the plugin, fix the URLs." That was the whole brief. The fix came back in minutes.

We're planning to move clients like this onto our own Jezweb Australia Post plugin over time, so we control the code and the updates. But even with the paid plugin still installed, having Claude meant the difference between "fixed before boarding" and "wait until someone in the team gets to it."

The point isn't to avoid paying for software. The point is what happens when something breaks and it needs fixing now. For something as core to an ecommerce business as shipping calculations, "renew your licence first" isn't a great answer when a customer is trying to check out.

Claude isn't magic. It didn't understand the business context, it didn't know the client, and it didn't decide to fix the problem. What it did was read the code, understand the API change, and produce a working diff in a few minutes, rather than me spending an hour reading API documentation and writing it myself.

That's useful in the same way a good reference book is useful: it doesn't think for you, but it saves you a lot of searching.

The decision to fix it ourselves instead of renewing the subscription was mine. The diagnosis was mine. The push to production was mine. Claude wrote the actual code change, and that saved enough time that I could do the whole thing before my flight.

Not the AI that replaces your judgment. The AI that removes the gap between "I know what needs to happen" and "it's done."

The client's customers can choose shipping again. And I made my flight.

This is part of something bigger we've been doing at Jezweb. We've now built over 30 custom WordPress plugins, and we include them in our clients' hosting service. Australia Post shipping, WooCommerce delivery dates, image optimisation, spam filtering, SEO tools, payment gateways. Things that used to cost $50-150 a year each in third-party plugin subscriptions.

We're building them because they make for good practice for our team, they're genuinely useful for our clients, and in a lot of cases they save everyone money. Right now we're happy to take plugin requests. If there's a paid plugin you're relying on and you think there might be a better way, let us know. We've been replacing them at no extra cost because the exercise pays for itself in what we learn and the value it adds.