Audit and rationalize your shipping zones and methods

WooCommerceIntermediate~20 min

Before you start

A connected store with the WooCommerce integration enabled and its read abilities on. The shipping-method write ability stays off until you switch it on for the fix pass. Back up before a large run.

Shipping settings are where a store quietly drifts. A zone gets duplicated during a redesign, a flat rate that should have moved to free shipping never did, two methods carry almost the same name, and a cost that made sense two years ago is now wrong. Nobody opens the shipping screen unless something breaks, so the mess just sits there.

This walks your zones for you and hands back a plain list of what looks wrong. Reading first, fixing second, and only the fixes you sign off on.

The prompt
Audit the shipping setup on this WooCommerce store. Work in two passes and do
not change anything in the first one.
First pass, reads only: list every shipping zone in order, then for each zone
pull its locations and the methods inside it, and for each method read its
title, its cost, and whether it is enabled. Give me back one table per zone,
and flag anything that looks off: duplicate or near-duplicate methods, a zone
with no methods at all, a disabled method that looks like it should be live,
or a cost that looks stale. Change nothing.
I will tell you which fixes to make. Only after I approve, update just those
methods, a few at a time, and show me each batch before it saves. Do not
create or delete any zone or method, only edit the ones I point at. At the
end, list every method you changed with its old and new settings.

Why this is safe to run

The entire first pass is reads. Listing zones, reading each zone, listing its methods, and reading each method all write nothing, so the audit table lands in front of you before a single setting moves.

The fix pass can only reach one ability, updating an existing shipping method, and even that stays off until you enable it. It cannot create a zone, delete a zone, or add or remove a method, because those abilities are not part of this recipe. Every change goes out in small batches you see first, each call is checked against the capability of the user you bound the agent to, and every write lands in the Activity Log with the method it touched. If a cost comes out wrong, the log tells you exactly which method to reopen.

Already connected? You do not have to paste this at all. Ask your agent for the “audit and rationalize shipping zones and methods” recipe, or just describe the job, and it runs the same two-pass flow on your own store.

How it works

  1. List every shipping zone and the order they sit in.
  2. Read each zone's locations and the methods configured inside it.
  3. Read each method's settings: title, cost, and whether it is enabled.
  4. Hand you an audit table of what looks off, and change nothing yet.
  5. After you approve, update only the methods you picked, one batch at a time, showing each batch before it saves.
  6. Return every method it changed so you can check the result.

Questions

Can it delete a zone or add a brand new shipping method?
No. This recipe only reads your zones and updates methods that already exist. It has no ability here to create or delete a zone or a method, so an audit can never quietly restructure your shipping.
Will it change what customers pay for shipping?
Only if you approve a cost change. Every proposed edit, including any change to a method's cost, is shown to you in the audit table first, and nothing saves until you say so.