Why shippingDetails is reported missing and whether it matters

What the error means

Your Offer does not declare shipping cost or delivery time, so your listing cannot show a delivery estimate next to the price.

Why Google rejects it

It is a recommended field rather than a hard rejection, which is why it is easy to leave alone for months. The cost is not a disapproval, it is a listing that looks thinner than a competitor whose result shows free delivery by a named date.

How to fix it

1. Set shipping rates in Merchant Center first. That covers the requirement without touching the theme and applies to every product at once.
2. For page markup, add OfferShippingDetails to the Offer with shippingRate and deliveryTime.
3. Only declare a rate you actually charge. A mismatch between markup and checkout is its own disapproval.

Common causes

Offer omits shippingDetails

Product markup may describe price and availability but contain no shipping details under its Offer. Google documents shippingDetails as a way to express shipping costs and delivery time on merchant listing product pages. Its absence can create a structured data warning even when shipping settings exist elsewhere.

Shipping details are attached outside the Offer

A JSON-LD block can be syntactically valid while placing OfferShippingDetails at an unsupported location. The property should be connected through the Offer's shippingDetails. Inspect the structured data tree to confirm the parser associates the region, rate, and delivery terms with the intended offer.

Rate or destination does not match checkout

Markup that says free shipping or a low rate for every destination can conflict with actual checkout rules. Regional zones, order thresholds, and product-specific shipping classes often make a single universal amount inaccurate. Compare the declared rate and destination with what a buyer in that region sees.

Delivery estimate is incomplete or unrealistic

If markup includes delivery time, handling and transit ranges need valid values and units. Copying a generic estimate can promise dates the warehouse does not meet. Check the public shipping policy and checkout estimates against the values emitted for each market.

Account settings are used instead of page markup

A Merchant Center shipping service may be configured even though the page schema does not include shippingDetails. These are distinct sources. Google can use settings from Merchant Center for shipping, while Search Console's structured data report evaluates what it finds in the page's markup.

Fix it on your platform

On Shopify

1. Review shipping rates and delivery zones in Shopify admin and confirm what customers see for each target market. Do not encode one rate in schema if checkout varies by destination or order value.
2. Check the published product page source for Offer and shippingDetails. Inspect the theme or schema app responsible for JSON-LD; Shopify shipping settings do not necessarily cause the theme to emit this property.
3. You can maintain shipping services in Merchant Center instead of hand-coding frequently changing rates. If you also publish page markup, keep rate and delivery statements consistent with checkout and your shipping policy.
4. For products with special shipping classes or restrictions, use accurate product or account-level configuration rather than applying the default product rate to every item.

On WooCommerce

1. Review WooCommerce shipping zones, methods, and product shipping classes, then compare the real checkout rate for representative customer locations.
2. Identify which plugin or theme emits Product and Offer schema. Configure shippingDetails in that source only if the rate and delivery terms can be maintained accurately there.
3. If Merchant Center owns shipping configuration, review its shipping services and country coverage. Do not assume those settings will appear in each page's structured data report.
4. Check variable products and products with different shipping classes separately. Make sure one Offer does not report a rate or delivery estimate that belongs to another variant.

On other platforms

1. In Wix, BigCommerce, or Squarespace, compare the platform's shipping zones and product-level shipping settings with the schema generated by its theme or commerce app.
2. If page schema cannot represent changing rates reliably, maintain shipping policies in Merchant Center and keep the storefront shipping page and checkout accurate.
3. On custom sites, put OfferShippingDetails under the relevant Offer and include a defined destination, monetary amount and currency when applicable. Add handling and transit time only when you can support those estimates.
4. Test markets, free-shipping thresholds, and product exceptions. Avoid presenting an all-country shipping amount when checkout charges differ by region.

How to confirm it is fixed

1. Select products and shipping destinations with different rate conditions. Compare the public policy, checkout amount and delivery estimate with Merchant Center configuration and page markup.
2. Use Rich Results Test on a live product URL. Confirm Google detects OfferShippingDetails beneath the correct Offer and parses its destination and rate.
3. Check the Merchant listings report for the exact warning and allow a recrawl after updates. Structured data validation does not itself update Merchant Center account shipping services.
4. Run the structured data check on representative pages to inspect shippingDetails in fetched Product markup.
5. Revisit a logged-out checkout using the same country and product to verify the rate and delivery language remain accurate.

A worked example

Hypothetical case: a home decor shop configures free shipping in Merchant Center for orders over a threshold, but its product JSON-LD says every item ships free to every US address. Search Console flags incomplete or inconsistent shipping details on the merchant listing. The owner tests checkout with a low-cost item and a high-cost furniture item, then separates the account shipping service from the page schema. They remove the blanket free rate from the Offer markup and publish only the destination and rate the product can actually receive, leaving threshold logic in the account configuration. They validate the updated page and check the report after recrawling.

Other errors like this