A broad shipping zone wins over the local rate

A valid match can still conflict with the intended coverage

The shipping-zone guide says each customer matches one zone and sees that zone's methods. List position therefore helps decide which rate rules get considered. A local zone can exist, contain enabled methods and accurately cover the destination, yet never supply the methods for that destination because an earlier zone already matches it.

That is different from checkout reporting no available shipping methods. Here the store has an option to offer; the question is why that option came from the broader coverage. It is also different from a local method calculating an unexpected amount. Establish which zone supplied the method before investigating the calculation inside it.

Walk the list using the destination from the real report

Use the affected checkout or order to identify the actual shipping region. Compare the full address only within the authorized store records. In the worksheet, retain the country, region or configured postal-area label needed to describe the match without copying a street address, recipient name or other identifying details.

Read each zone's configured geographic coverage in the order it appears. Do not rely on the zone's name: a name describes what its owner intended, while its configured coverage is what you are comparing. Mark the first zone whose coverage fits. Continue inspecting the intended local zone to document the overlap, but do not treat its later match as another source of methods for the same customer.

Record when the settings were inspected and when the reported checkout occurred. Current zone order supports an explanation of current behavior. If someone has changed it since the report, it does not establish the historical order; preserve that timing gap instead of asserting a cause.

Separate zone priority from method identity

Open the first matching zone and compare its enabled methods with the method shown at checkout. Keep the configured method and zone together in the record. A familiar method label by itself is weak evidence of which zone supplied it, particularly if your own configuration uses the same label in more than one zone.

When the first matching broad zone contains the observed method and the intended local zone sits below it, the records support a precedence explanation. When the local zone already matches first, this specific overlap explanation is not established. Investigate that zone's method settings or the component providing the rate instead of repeatedly changing zone order.

WooCommerce documents Flat Rate, Free Shipping and Local Pickup as built-in methods. Record a third-party method's extension name and version if one is involved. The core zone rule does not explain that extension's rate formula or every condition under which it supplies a method.

Choose the coverage decision before moving the zone

The rate owner should decide whether the local region is intended to have priority over the broad region. If it is, compare placing the local zone earlier with correcting an inaccurate coverage definition. Reordering changes which matching zone supplies methods; it does not repair coverage that never included the destination. Keep the change tied to the documented delivery area and the affected zone, not to an assumed cheapest rate.

After an authorized correction, compare the resulting first match and offered methods for the affected real destination, and check the overlapping areas whose priority changed. Do not submit a payment or place an order merely to inspect shipping. The useful result is evidence that the intended zone supplies the intended methods; it is not proof of carrier availability or permission to ship the products.

For a Prism checkout consultation, summarize the broad and local coverage, their recorded order and the mismatch between intended and observed methods. The checkout-review service anchors a discussion of what should be investigated before a change. Describe the help needed so scope, responsibilities, fees and terms can be confirmed; the inquiry itself does not authorize implementation.

Zone precedence map

Complete this from one real affected destination and the dated zone configuration. Work down the actual zone list to establish the first match, then compare it with the intended local zone. If the order at the time of the report is unavailable, mark the historical cause unresolved. Keep customer addresses inside the authorized store.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.