Guides

Fixing Google's "Missing field shippingDetails" warning

Published October 4, 2026 · Updated November 11, 2026

Google's “Missing field shippingDetails” warning means it could not find shipping details in a product’s markup. The warning alone does not make the page ineligible for merchant listings. Compare your public shipping terms with Google’s settings and markup before choosing a fix.

Jump to a section

What the warning means

Google's merchant listing markup has two required Offer fields, price and priceCurrency. Everything else, shippingDetails included, is recommended. A missing recommended field is reported as a warning, and a page with warnings still qualifies for merchant listing results; it just shows them without the shipping cost and delivery estimate Google can add when it has them.

So the question is not "how do I make the warning go away" but "where should Google read my shipping terms from". Google's merchant-listing guidance lists this order when shipping configurations conflict: product-level Merchant Center feeds, Content API settings, Merchant Center or Search Console settings, product Offer markup, then Organization markup. The shipping-policy page lists the latter four. Merchant Center's product shipping attribute can override account settings for the matching product and location under its documented conditions. Check the same product and destination before changing page markup.

If your shipping terms are the same for every product, Google recommends site-wide settings or site-wide markup over per-product markup. Per-product shippingDetails is for products whose terms differ from the rest.

Five-minute self-check

  1. Open one representative product page and its linked shipping policy. Record the destinations, shipping cost or threshold, delivery estimate, and any exceptions a shopper can actually read.
  2. Paste that product URL into Google's Rich Results Test. Inspect the Product's Offer for shippingDetails; write down what it says or that it is absent. The warning describes this markup, not every shipping setting Google may use.
  3. If you use Merchant Center, compare the account shipping settings and any product-specific shipping attribute for that same item and destination. Google documents when the product attribute overrides the account setting.
  4. Choose the next step: clarify public copy if a shopper cannot tell what applies; correct a wrong account or product setting if one exists; correct conflicting markup if it is present. An absent markup field alone does not tell you which of those jobs is needed.

This check covers one product and one destination. Repeat it for a product with different shipping terms before treating a store-wide policy as complete.

Fix 1: set shipping in Search Console or Merchant Center

If Google recognises your site as an online merchant, Search Console offers shipping and returns settings under its merchant settings, and Merchant Center has its own shipping settings. These can cover products that share terms. Google's documented order puts account settings ahead of page markup, while product-level feed data can take precedence for an item. Check product exceptions before treating an account setting as the answer for every item.

This route needs no theme edit. The Merchant listings report checks the page's markup, so its missing-field warning may remain after you add correct settings. Compare any product-level feed data too; it may supply a different rate or speed for that product.

Fix 2: site-wide markup on your Organization

A standard shipping policy for the whole store goes on your Organization markup as hasShippingService, not as shippingDetails. Google documents it as the recommended markup form. It lives once, on the page that carries your Organization markup (usually the home page), and describes the conditions under which you ship and what it costs.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Store",
  "url": "https://www.example.com/",
  "hasShippingService": {
    "@type": "ShippingService",
    "name": "Standard shipping",
    "fulfillmentType": "FulfillmentTypeDelivery",
    "shippingConditions": {
      "@type": "ShippingConditions",
      "shippingDestination": { "@type": "DefinedRegion", "addressCountry": "US" },
      "shippingRate": { "@type": "MonetaryAmount", "value": 5.95, "currency": "USD" }
    }
  }
}

Rates can be a fixed amount, as above, or a ShippingRateSettings node with a percentage of the order value; conditions can add order-value and weight ranges. Google's organization shipping page lists every property.

Fix 3: shippingDetails on each product's Offer

When a product ships on different terms from the rest, or you would rather every product page carry its terms, add shippingDetails to that product's Offer. Google requires shippingRate and shippingDestination; deliveryTime is recommended, and it is the part a shopper actually asks about.

"offers": {
  "@type": "Offer",
  "price": 49.00,
  "priceCurrency": "USD",
  "availability": "https://schema.org/InStock",
  "shippingDetails": {
    "@type": "OfferShippingDetails",
    "shippingRate": { "@type": "MonetaryAmount", "value": 5.95, "currency": "USD" },
    "shippingDestination": { "@type": "DefinedRegion", "addressCountry": "US" },
    "deliveryTime": {
      "@type": "ShippingDeliveryTime",
      "handlingTime": { "@type": "QuantitativeValue", "minValue": 0, "maxValue": 1, "unitCode": "DAY" },
      "transitTime": { "@type": "QuantitativeValue", "minValue": 2, "maxValue": 5, "unitCode": "DAY" }
    }
  }
}
  • Ship to more than one country at different rates: make shippingDetails an array with one OfferShippingDetails per destination.
  • Free shipping: a shippingRate with value 0.
  • Keep the numbers the same as your shipping policy page says. Markup that disagrees with the page is worse than no markup.

Where this goes on a Shopify store

Shopify themes write the Product markup themselves. Find the file that does it by searching the theme code for "@type": "Product" (in the code editor, Online Store, Themes, Edit code); the file name varies by theme. The shippingDetails node goes inside the offers object that file writes. The rate, destination and delivery days are typed into the theme by hand, so if you change your shipping rates, change them here too.

If you would rather not edit the theme, a structured-data app can add the node, and Fix 1 needs no code at all. Whatever you choose, use one method: two sources of shipping terms that disagree is the one way to make this worse.

Checking the fix

  • Paste one product URL into Google's Rich Results Test and confirm the Offer now shows the shipping node with no missing-field notice.
  • In Search Console, open the Merchant listings report, select the warning, and choose Validate fix. Google re-reads a sample of the affected pages over the following days or weeks and reports back.
  • If you chose Fix 1, the report's markup warning can remain. Verify the effective terms for a product and destination in Merchant Center rather than treating the warning alone as proof of a missing policy.

If Search Console also flags your returns terms, use the return-policy warning guide to compare the public policy, settings and markup before changing either.

Why this matters beyond the warning

Delivery cost and delivery time are two of the questions that stop a purchase, and a system answering a shopper reads them from the product's Offer, where the price is, not from a policy page three clicks away. Terms that exist only as a paragraph on a shipping page have to be found and paraphrased; terms in the Offer can be repeated exactly.

A Findwise scan reads a sample of a store's public pages and checks the same ground from the shopper's side: whether the store states shipping and return terms only in prose with nothing in the product markup, whether a shipping node names a rate and a destination, and whether the policy nodes a store does publish are attached to each product's Offer. Each finding cites the page it was seen on. Findwise estimates from public pages; it does not test AI assistants and cannot say what any assistant shows for your store.

Sources

Check your own store

Create a free account to see what your public pages tell AI shopping systems about your products. Track weekly changes and work through your next priority fix.

Create your free account