Short answer
“No shipping rates available” means Shopify could not find an eligible delivery option for the exact cart and destination. The fastest diagnosis is to keep the address fixed and simplify the cart: test one product at a time, identify the product or profile that removes the rate, then inspect the matching zone, origin, weight or price conditions, and app-calculated provider. Do not treat the message as only a theme problem when checkout also fails.
What the error actually means
Shopify evaluates the destination, market, shipping profile, fulfilment origin, cart contents, and rate conditions together. If no complete path produces a rate, checkout cannot offer shipping. The wording may vary, but the underlying issue is eligibility.
- Destination is unsupported.
- No rate matches the order value or weight.
- A product or location is missing from the expected profile.
- An app or carrier did not return a rate.
- The cart combines profiles or origins in an unsupported way.
Use a one-variable test
Start with a known address and one ordinary product. If a rate appears, add the other products back one at a time. If the first product fails, test a different destination in the same zone, then another zone. This isolates whether the trigger is the product, cart composition, or location.
Inspect gaps and boundaries
Rate conditions often fail at boundaries: a weight just above the highest band, a subtotal between price ranges, or a product with zero or incorrect weight. Record the actual cart value and weight and compare them with every condition in the applicable profile.
Escalate with a reproducible example
If the configuration looks correct, capture the product, variant, quantity, destination, cart value, time, and expected rate. This gives Shopify Support or the app developer enough information to reproduce the failure instead of starting with a generic screenshot.
Checklist
- Known test address
- Single-product cart
- Correct market and zone
- Correct profile and origin
- No gap in price conditions
- No gap in weight conditions
- Accurate product weight
- App/carrier service enabled
- Backup rate considered
- Reproducible example recorded
Questions
Is this always caused by a shipping app?
No. Native zones, profiles, locations, and rate conditions can all cause the same result.
Why does one product work and another fail?
The failing product may use a different shipping profile, origin, weight, collection, or app-calculated condition.
Should I add a fallback rate?
A backup rate can protect checkout when a carrier calculation fails, but it should be priced deliberately and tested against margin risk.