A customer can find a product, add it to the cart and then discover that no shipping option is available. For a store selling physical goods, that is a break in the buying journey even when every page loads correctly. The right investigation starts with the actual basket and destination that produced the result.

RevenueGuard can check that shipping is available for a configured physical-product journey. That helps expose a problem in the selected scenario, but it cannot establish that every postcode, carrier service or mixed basket is covered.

Reproduce the destination and basket

Write down the country, state or region, postcode, product and quantity used in the failing check. Confirm that the address fields are complete enough for the store’s shipping rules. Repeat the same path in a fresh guest session.

Be especially careful when comparing two tests. A lightweight item shipped domestically may have different options from a bulky product sent overseas. A virtual product may not require shipping at all. Testing it would not explain why a physical-product basket fails.

Check the matching shipping zone

WooCommerce uses shipping zones to determine the methods available for a destination. A customer matches the first applicable zone, so a more specific zone placed after a broad one may not be the zone you expect. Inspect the matching zone and make sure it has an enabled method appropriate to the scenario. Refer to WooCommerce’s shipping-zone documentation for the exact configuration workflow.

Record the intended business rule before changing it. “This postcode should receive standard delivery” is more useful than “make any method appear.” A temporary workaround that displays an unsuitable rate may create a different problem for fulfillment.

Review conditions that change eligibility

Consider what is different about this basket: quantity, product type, shipping class, destination, discount or order total. If an extension controls conditional shipping or carrier rates, review its own rule evaluation and diagnostic information.

Use one change at a time in an appropriate test environment. First establish whether the intended method exists in a simpler eligible basket. Then add the original scenario’s conditions back until the difference is clear. Preserve the original evidence instead of relying on memory.

Distinguish no method from an incorrect method

An availability check can tell you that a shipping option appeared. It does not necessarily establish that the price, delivery promise or carrier selection is commercially correct. A £1 delivery charge where your business expects £10 is a separate issue from an empty shipping section.

Build a manual review table for your important regions: example postcode, representative product, intended service and expected pricing rule. Check this table after a shipping configuration change. RevenueGuard’s selected journey adds recurring observation of one defined path alongside that broader review.

Configure monitoring around a stable scenario

Choose a product that is normally published and in stock. Enable the shipping requirement in the monitoring configuration and supply the relevant destination details. Confirm that the initial check passes for the right reason.

If you deliberately stop shipping to a region or retire the monitored product, update the scenario. Otherwise an expected business change can produce repeated alerts that distract the team. The setup guide explains where the journey configuration lives.

Verify recovery and the neighboring cases

After correcting the rule or service, repeat the original failing basket and postcode. Then check at least one nearby scenario that should remain unchanged, such as another shipping region or a basket below a free-shipping threshold. Record what you tested.

A RevenueGuard recovery notice means the monitored path passed again. It is a useful signal for the team, not a substitute for verifying your whole delivery policy. For a wider incident involving cart or payment behavior, continue with the checkout investigation guide.

FROM GUIDANCE TO OBSERVATION

See the path your store depends on.

RevenueGuard brings configured checkout checks, store signals and incident evidence into one place. Early-access availability is limited; paid purchasing is not open yet.

Request early access Read the setup guide