Missing delivery options need a basket-specific explanation
When Magento displays no shipping methods, the customer cannot finish the order even if products and payment appear healthy. The useful question is not simply whether shipping is enabled. It is whether the current basket and destination qualify for a method, whether the rate request succeeds and whether checkout displays the returned result correctly.
Midoriweb starts with one failing basket and one expected delivery outcome. We record product types, weights, quantities, destination country and postcode context, website and any discount applied. A working comparison basket helps isolate the difference. This turns a broad checkout complaint into a testable delivery-rule or integration problem.
If the failure affects live customers, explain the affected destinations and approximate start time in a support request. For general checkout failures, our checkout error guide helps identify whether shipping is actually the first broken stage.
Establish the intended delivery rules
Write down what should be offered before inspecting configuration. Which countries or regions are served? Are there weight, value or product restrictions? Does the store offer a fixed rate, table rates, free shipping or a carrier quotation? Is the expected service available to all customer groups and websites?
This business definition is essential because a missing option can be correct behaviour. A bulky product, excluded destination or unsupported service combination may legitimately remove a method. The customer experience still needs to explain the restriction clearly, but the technical fix differs from a failed carrier API.
Avoid enabling an unrestricted delivery option just to allow checkout to continue. That can accept orders the business cannot fulfil at the displayed price. A temporary alternative requires explicit operational agreement about service coverage, cost and handling.
Confirm the address and basket data used for quotation
A rate calculation can depend on country, region, postcode, basket value and weight. Check the actual data submitted at the shipping step rather than relying solely on what appears in the input fields. Address autocomplete, custom validation or saved-address handling can produce a difference between visible text and the value used by Magento.
Compare an address entered manually with an equivalent saved address where relevant. Check that required region information is represented in the format expected by the installed integration. Do not assume that every postcode format is interchangeable or that a country-wide test covers remote-area restrictions.
Product data matters too. An unexpectedly high weight or a virtual product mixed into a physical basket may change the path being tested. Use a minimal basket to isolate the rule, then return to the customer’s original combination to verify the explanation.
Review scope and method configuration
Magento configuration can vary by website or store scope. Confirm the effective values for the storefront being tested, including inherited settings. A method enabled in one context may remain unavailable in another. Record the scope of any proposed correction so that it does not unintentionally change delivery policy elsewhere.
Check allowed destinations, applicable service selections, thresholds and the handling of unavailable methods. With table rates, compare the imported data and the condition used to select a row. A rate file that looks valid in a spreadsheet can still omit the specific basket or destination combination.
Adobe’s free shipping documentation distinguishes method configuration from promotional rules. Treat those as related but separate settings. A free-shipping promotion does not automatically establish that every necessary delivery method is available in the current checkout.
Trace carrier requests and responses
For live carrier rates, determine whether a request is sent, whether the carrier accepts it and what services are returned. A remote authentication error, validation failure, timeout or empty eligible-service list can all become a similar message in checkout. The actual response is the evidence that separates them.
Review recent account, credential, endpoint or service changes through the authorised administrator. Do not place keys or complete customer addresses in public logs or a general support email. A redacted response and safe request reference are usually enough to establish the failure category before secure access is arranged.
A carrier response can be technically successful while returning no service for the supplied shipment. Compare package dimensions, weight units and destination information with the account’s supported services. The integration should not silently reinterpret units or discard a relevant rejection reason.
Check promotions and custom checkout interactions
A discount may change the amount used by a shipping threshold, while custom rules can restrict methods by product or customer context. Compare the basket before and after the promotion and record which totals the rule evaluates. Our coupon diagnosis guide covers the associated promotion checks.
If the backend returns suitable methods but the frontend shows none, inspect the checkout update sequence. A stale selection, JavaScript error or custom component may prevent the customer interface from reflecting the response. This is different from a carrier or rate-table problem and should be tested at the rendering boundary.
Change one condition at a time. Simultaneously adjusting rates, promotion rules and checkout JavaScript may make the problem disappear without showing which change was necessary. That creates uncertainty when the same symptom returns after the next deployment.
Design a safe recovery and customer message
The recovery should preserve the agreed delivery policy. If a carrier service is unavailable, a business-approved fallback may be appropriate, but it should state the actual price and expectation. Do not promise next-day delivery merely because a fallback method can be displayed.
Where an address or basket is genuinely ineligible, the message should explain what the customer can do next. A clear postcode correction, product restriction or contact route is more useful than “something went wrong”. The frontend should identify the relevant field or condition without exposing internal exception details.
Midoriweb can investigate the application and integration through Magento checkout support. Work should connect the observed failure to a specific correction, with configuration changes documented so operations knows what has changed.
Verify the destinations that matter
Use a small matrix of representative destinations, basket values, weights and product combinations. Include boundary cases just below and above a threshold, as well as a destination that should remain excluded. Verify the displayed price, selected method and order record, not just the presence of a radio button.
Check guest and account checkout when they use different address flows. Confirm what happens when a customer changes the address after selecting delivery. The old method should not remain accepted if it is no longer valid for the new destination.
For the initial brief, provide a redacted example basket, the destination category, the expected method and the observed message. Include whether the issue is universal or selective. That evidence allows the investigation to begin with the delivery decision that actually failed.
Shipping-method questions
Why does shipping work for some postcodes only?
The cause may be intentional coverage, incomplete rate data or a carrier-specific restriction. Compare the failing and working destinations against the intended business rules.
Can a discount affect delivery availability?
Yes, where rules depend on basket totals or promotional conditions. Verify the effective calculation rather than assuming the displayed subtotal is the value every rule uses.
Should we switch off address validation?
Not as a general fix. First identify the invalid or incorrectly mapped value and correct the relevant input or integration behaviour while preserving necessary validation.