The “Missing field ‘hasMerchantReturnPolicy'” warning appears when your Shopify product structured data lacks return policy information. Fix it by adding a MerchantReturnPolicy object to the offers in your theme’s product JSON-LD, or by configuring your return policy in Google Merchant Center, which Google accepts instead of markup.

You open Google Search Console to check on your store, and there it is — a wall of yellow warnings under the Merchant listings report:

⚠️ Missing field ‘hasMerchantReturnPolicy’ (in ‘offers’)

Often with its twin right beside it:

⚠️ Missing field ‘shippingDetails’ (in ‘offers’)

Hundreds of affected pages. Every product on your store, flagged. Your first reaction is probably somewhere between “did my SEO just break?” and “what even is a hasMerchantReturnPolicy?”

First, breathe. Here’s the honest picture: this is a warning, not an error. Your products are still indexed, still eligible for search results, and Google is not penalizing you. What Google is telling you is that your product structured data — the machine-readable JSON-LD your theme outputs — describes your products and prices, but says nothing about your return policy (and usually your shipping details). Google increasingly wants that information to power richer merchant listings in Search: those result cards that show “Free 30-day returns” and “Free delivery” right under your product. No markup, no enhancements.

So while you can ignore it, you shouldn’t. Return and shipping info in search results is free conversion power — shoppers click results that answer “can I return it?” before they’ve even visited. And the fix is very achievable.

In this guide I’ll show you both legitimate ways to fix it, as a Shopify developer who has cleared this exact warning on client stores many times:

1. The code fix (free, permanent): add the hasMerchantReturnPolicy and shippingDetails fields to your theme’s product JSON-LD
2. The Merchant Center fix (no code): configure your return and shipping policies in Google Merchant Center, which Google explicitly accepts in place of markup

Plus how to verify your fix with the Rich Results Test and get Search Console to re-validate. Let’s clear those warnings.

Table of Contents

• What This Warning Actually Means (And Why It’s Everywhere)
• Does It Hurt Your Rankings? The Honest Answer
• The Two Legitimate Fixes — Which Should You Use?
• Before You Start
• Fix 1: Add the Fields to Your Theme’s Structured Data (Code)
  • Step 1: Find Your Product JSON-LD
  • Step 2: Add hasMerchantReturnPolicy to Offers
  • Step 3: Add shippingDetails While You’re There
  • If Your Theme Uses Shopify’s structured_data Filter
• Fix 2: Configure Policies in Google Merchant Center (No Code)
• Step 3: Verify with the Rich Results Test
• Step 4: Validate the Fix in Search Console
• Best Practices for Shopify Product Structured Data
• Common Mistakes to Avoid
• Troubleshooting
• FAQ
• Conclusion

What This Warning Actually Means (And Why It’s Everywhere)

Every Shopify theme outputs structured data — a block of JSON-LD in your product page’s code that describes the product to search engines: name, image, brand, price, availability. Google reads it to build product rich results and merchant listings.

A few years ago, Google expanded what it wants inside the offers part of that data. Beyond price and availability, it now looks for:

• hasMerchantReturnPolicy — can the item be returned, within how many days, by what method, and who pays?
• shippingDetails — what does shipping cost, to where, and how long does it take?

Most Shopify themes — including Dawn and most paid themes — were built before (or without) these fields, so they simply don’t output them. Result: Google crawls your perfectly healthy product pages, notices the fields are absent, and files a “missing field” warning for every product. That’s why the warning appears suddenly, sitewide, without you changing anything — Google changed what it checks, not your store.

Does It Hurt Your Rankings? The Honest Answer

No — and be skeptical of anyone selling you panic. Google classifies these as non-critical issues: your products remain valid and eligible for search. There is no ranking penalty for a missing optional field.

What you’re missing is upside:

• Eligibility for the fuller merchant listing experience — return-policy and shipping annotations shown directly in search results and Google Shopping surfaces
• The click-through advantage those annotations create (“Free 30-day returns” under your result vs. nothing under your competitor’s)
• A cleaner Search Console, which matters when you’re monitoring for issues that do hurt

So the priority is real but calm: fix it this week, not this minute.

The Two Legitimate Fixes — Which Should You Use?

My recommendation for most stores: do both. Configure Merchant Center (it’s the authoritative source for Shopping surfaces and survives everything), and add the markup (it’s what the Search Console report actually checks, and it makes your structured data complete for all consumers, not just Google).

Before You Start

You’ll need:

• Your actual return policy details: return window in days, who pays return shipping, return method. The markup must describe your real policy — publishing “30-day free returns” in structured data while your policy page says “no returns” is asking for trouble
• Access to Online Store → Themes → Edit code (for Fix 1)
• A Google Search Console property for your store (you have one if you’re seeing the warning)

And the standing rule: duplicate your theme (Online Store → Themes → ⋯ → Duplicate) and make code edits on the copy.

Fix 1: Add the Fields to Your Theme’s Structured Data (Code)

Step 1: Find Your Product JSON-LD

1. Go to Online Store → Themes → ⋯ → Edit code on your duplicate
2. Open Sections → main-product.liquid
3. Search (Ctrl/Cmd + F) for: application/ld+json

You’re looking for a <script type="application/ld+json"> block containing "@type": "Product" — in Dawn and most Dawn-based themes it sits near the bottom of main-product.liquid (in some themes it lives in a snippet like structured-data.liquid; search there if needed).

Inside it, find the "offers" part. Depending on the theme it’s either an array built by a variant loop or a single offer object. Each offer looks roughly like:

json

"offers": [{
  "@type": "Offer",
  "availability": "https://schema.org/InStock",
  "price": 49.00,
  "priceCurrency": "USD",
  "url": "https://yourstore.com/products/example"
}]

If you found it — continue to Step 2. If instead you find {{ product | structured_data }} (Shopify’s auto-generating filter, used by some newer theme versions), jump to the dedicated section below.

Step 2: Add hasMerchantReturnPolicy to Offers

Inside each offer object (in a variant loop, that means inside the loop so every offer gets it), add the return policy field. Place it after an existing field, keeping JSON commas valid:

liquid

"hasMerchantReturnPolicy": {
  "@type": "MerchantReturnPolicy",
  "applicableCountry": {{ localization.country.iso_code | json }},
  "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
  "merchantReturnDays": 30,
  "returnMethod": "https://schema.org/ReturnByMail",
  "returnFees": "https://schema.org/FreeReturn"
},

Now customize the values to match your real policy:

• merchantReturnDays — your actual return window (14, 30, 60…)
• returnFees — https://schema.org/FreeReturn if you pay return shipping, or https://schema.org/ReturnFeesCustomerResponsibility if the customer does
• returnMethod — ReturnByMail for most online stores; ReturnInStore if applicable
• returnPolicyCategory — the three honest options:
  • MerchantReturnFiniteReturnWindow — returns accepted within N days (most stores)
  • MerchantReturnUnlimitedWindow — returns accepted anytime
  • MerchantReturnNotPermitted — no returns (yes, declaring “no returns” also clears the warning — Google wants the policy stated, not a generous one). With this category, drop the merchantReturnDays, returnMethod, and returnFees lines
• applicableCountry — the Liquid above outputs the shopper’s localized country automatically; hardcode "BD", "US", etc. if you prefer one primary market

Step 3: Add shippingDetails While You’re There

Since its twin warning almost always travels with this one, fix both in one edit. Add alongside the return policy, inside each offer:

liquid

"shippingDetails": {
  "@type": "OfferShippingDetails",
  "shippingRate": {
    "@type": "MonetaryAmount",
    "value": 0,
    "currency": {{ cart.currency.iso_code | json }}
  },
  "shippingDestination": {
    "@type": "DefinedRegion",
    "addressCountry": {{ localization.country.iso_code | json }}
  },
  "deliveryTime": {
    "@type": "ShippingDeliveryTime",
    "handlingTime": {
      "@type": "QuantitativeValue",
      "minValue": 0,
      "maxValue": 1,
      "unitCode": "DAY"
    },
    "transitTime": {
      "@type": "QuantitativeValue",
      "minValue": 2,
      "maxValue": 5,
      "unitCode": "DAY"
    }
  }
},

Customize: "value" is your standard shipping rate (0 for free shipping; use your flat rate otherwise), handling time is how long before you ship, transit time is the carrier window. If your rates vary heavily by region or weight, publish your most common/default rate here and let Merchant Center (Fix 2) carry the detailed matrix — GMC is the better home for complex shipping tables.

Save the file, and mind the JSON: every field except the last inside an object needs a trailing comma, and none after the last. A single comma mistake makes the whole block invalid — which is exactly what the verification step will catch.

If Your Theme Uses Shopify’s structured_data Filter

Some newer theme versions generate product JSON-LD with a one-liner: {{ product | structured_data }}. Shopify controls that output — you can’t inject fields into it directly. Your options, in order of sanity:

1. Use Fix 2 (Merchant Center) and let Google take policies from there — the zero-maintenance path
2. Replace the filter with a custom snippet: build the full Product JSON-LD yourself (name, image, description, brand, offers with the new fields) in a snippet, render it where the filter was, and remove the filter so you don’t emit duplicate Product schema — two competing Product objects on one page confuses validators. This is a developer-level change; if that’s not you, option 1 exists precisely for this case
3. Never just paste a second <script type="application/ld+json"> Product block alongside the filter’s output — duplicate Product markup creates new warnings while “fixing” this one

Fix 2: Configure Policies in Google Merchant Center (No Code)

Google explicitly supports providing return and shipping policies through Merchant Center account settings instead of on-page markup — and for Shopping surfaces, Merchant Center is authoritative anyway.

1. If you haven’t already, install the Google & YouTube channel app from the Shopify App Store and connect your store to your Google Merchant Center account (the app syncs your product feed automatically)
2. In Google Merchant Center, open the settings area for your business info / shipping and returns
3. Add your return policy: return window, restocking fees, who pays return shipping, applicable countries
4. Add your shipping service: destination countries, delivery time estimates, rates (this is where complex rate tables belong)
5. Save — policies apply account-wide to all synced products

Reality check on the Search Console report: GSC’s Merchant listings report evaluates your on-page markup, so it may keep listing the missing-field warnings even while Google happily uses your Merchant Center policies. Functionally you’re covered; cosmetically the report only goes fully green with the markup fix. That’s the practical case for doing both.

Step 3: Verify with the Rich Results Test

Before asking Google to re-validate anything, prove your markup is right:

1. Open the Rich Results Test: search.google.com/test/rich-results
2. Paste a product page URL from the theme where you made the edits (publish the duplicate first, or test with the theme preview URL)
3. Run the test and expand the Merchant listings / Product snippets results
4. Confirm:
   • hasMerchantReturnPolicy and shippingDetails now appear under offers
   • No new errors — if the test reports invalid JSON, you have a comma or quote problem in your edit; re-check Step 2/3 carefully
5. Fix anything flagged, re-test until clean

Only move on when the test is clean — validating in Search Console with broken markup just earns you a failed validation email a week later.

Step 4: Validate the Fix in Search Console

1. In Search Console, open Shopping (or Experience) → Merchant listings
2. Click the “Missing field ‘hasMerchantReturnPolicy'” warning row
3. Click Validate Fix
4. Repeat for the shippingDetails warning if listed

Google then re-crawls a sample of affected pages and, over the following days to a few weeks, marks the issue as passed. Don’t be alarmed by the timeline — validation is slow by design, and the warning count declines gradually as pages get re-crawled. Your markup was fixed the moment you published; the report just takes time to say so.

Best Practices for Shopify Product Structured Data

Markup must match reality. Your structured data, your policy pages, and your Merchant Center settings should all tell the same story. Mismatches between claimed and actual policies are the kind of thing that gets Merchant Center accounts suspended.

Have a real returns page. Shopify’s policy pages (Settings → Policies) generate your refund policy page — fill it in properly and link it in your footer. The markup describes the policy; the page is the policy.

Fix both twins together. hasMerchantReturnPolicy and shippingDetails almost always appear as a pair; one edit session clears both.

Document your edit. Theme updates replace main-product.liquid. Keep your two JSON blocks saved in a note so re-applying after an update takes two minutes.

Re-test after any theme or app change. SEO apps and page builders sometimes inject their own Product markup. Run the Rich Results Test occasionally to make sure you have exactly one clean Product object per page.

Don’t chase every optional field. Google’s product schema has dozens of optional properties. Return policy and shipping are the ones behind these warnings and the merchant listing experience — fix those, keep the rest simple.

Common Mistakes to Avoid

1. Panicking over a warning. It’s not a penalty, your rankings didn’t drop, and “fix within a reasonable week” is the right energy.
2. Publishing a fake generous policy. Declaring 30-day free returns in markup while your actual policy differs misleads shoppers and risks Merchant Center action. If you don’t accept returns, say so — MerchantReturnNotPermitted is valid and clears the warning too.
3. Breaking the JSON. One missing comma invalidates the entire structured data block — turning a cosmetic warning into a real error. Always verify with the Rich Results Test before validating in GSC.
4. Adding a duplicate Product schema block. Two Product objects on one page is worse than one incomplete object. Edit the existing markup, or replace it — never stack.
5. Editing the live theme. Same rule as always: duplicate, edit, verify, publish.
6. Forgetting the fix after a theme update. The #1 reason this warning “comes back.” It didn’t come back — the update erased your edit. Re-apply from your saved copy.

Troubleshooting

The Rich Results Test says my JSON is invalid after the edit. Comma or quote error. Compare your edit character-by-character against the snippets above — the classic mistakes are a missing comma before your new field, an extra comma after the last field in an object, or smart quotes pasted from a word processor instead of straight quotes.

I can’t find any application/ld+json block in my theme. Search other likely files: a structured-data snippet, theme.liquid, or check whether an SEO app is injecting the markup (view your live product page source and search for hasMerchantReturnPolicy / "@type":"Product" to see what’s actually rendering and from where). If an app owns the markup, configure it there or in Merchant Center.

My theme uses {{ product | structured_data }}. You can’t edit the filter’s output. Use Merchant Center for policies, or replace the filter with a complete custom JSON-LD snippet — see the dedicated section above. Don’t add a second Product block next to it.

I fixed it, but Search Console still shows the warning. Expected. GSC re-crawls slowly — click Validate Fix and give it days to weeks. Confirm the markup is actually live by viewing your published product page source and searching for hasMerchantReturnPolicy.

Validation failed. Some sampled pages still lack the field. Usual causes: the fix went live on a non-published theme, some products use a different product template that wasn’t edited, or an app overrides your markup on certain pages. Check each, then re-validate.

The warning came back months later. A theme update replaced your edited file. Re-apply your saved snippets — and if you’re on the update treadmill, the Merchant Center route (immune to theme updates) is your friend.

I have both the theme markup AND Merchant Center configured — which wins? For Google Shopping surfaces, Merchant Center settings take precedence. That’s fine — consistency between the two is what you want, not competition.

FAQ

1. What does “Missing field ‘hasMerchantReturnPolicy'” mean in Shopify? Google Search Console is flagging that your product pages’ structured data doesn’t include return policy information in the offers. It appeared sitewide because your theme never output that field — Google recently began checking for it.

2. Is it an error or a warning? Will my rankings drop? It’s a non-critical warning. Your products stay indexed and eligible for search results, and there’s no ranking penalty. Fixing it unlocks richer merchant listings (return/shipping info shown in results), which helps click-through.

3. How do I fix it without an app? Add a MerchantReturnPolicy object to the offers in your theme’s product JSON-LD (free copy-paste code in this guide), or set your return policy in Google Merchant Center — Google accepts either.

4. What about the “Missing field ‘shippingDetails'” warning? Same cause, same fix session: add an OfferShippingDetails object alongside the return policy. This guide includes the code for both.

5. Which fix is better — code or Merchant Center? Both are legitimate; do both if you can. Merchant Center survives theme updates and is authoritative for Shopping; the markup fix is what makes the Search Console report itself go green and completes your on-page schema.

6. My store doesn’t accept returns — can I still fix the warning? Yes. Use returnPolicyCategory: MerchantReturnNotPermitted. Google wants the policy declared, not necessarily generous — honestly stating “no returns” clears the warning.

7. Where is the structured data in the Dawn theme? In main-product.liquid — search for application/ld+json. Some themes keep it in a snippet instead, and some newer versions generate it with the {{ product | structured_data }} filter, which requires the alternate approaches covered in this guide.

8. Will an SEO app fix this for me? Some structured-data apps add these fields, but this is a genuinely small edit — paying a monthly fee solely for two JSON blocks rarely makes sense. If you already run an SEO app that outputs Product markup, configure it there to avoid duplicates.

9. How long until the warning disappears from Search Console? After you click Validate Fix, days to a few weeks — Google re-crawls sampled pages gradually. The markup is working from the moment it’s live; only the report lags.

10. What values should I use if my shipping rates vary a lot? Put your default/most common rate in the markup and maintain the detailed rate tables in Google Merchant Center, which is built for complex shipping matrices.

11. Can wrong return policy markup get me in trouble? Yes — declaring policies you don’t honor (e.g., free returns you actually charge for) misleads shoppers and can trigger Merchant Center enforcement. Keep markup, policy pages, and reality identical.

12. Does this warning affect stores that don’t use Google Shopping? The merchant listing experience mostly benefits Shopping-surface visibility, but Product rich results in regular search also read this data. Either way, the fix is cheap and the markup completeness is worth it.

13. Will the fix survive Shopify theme updates? The code fix won’t — updates replace main-product.liquid, so save your snippets and re-apply. The Merchant Center fix survives everything, which is a good reason to set it up as your backstop.

14. How do I confirm the fix actually worked? Run a product URL through Google’s Rich Results Test and confirm hasMerchantReturnPolicy (and shippingDetails) appear under offers with no errors — then Validate Fix in Search Console and let it re-crawl.

Conclusion

That intimidating wall of yellow in Search Console comes down to one sentence: your theme describes your products to Google, but never mentioned your return policy or shipping. Google now asks; your theme predates the question.

The fix is refreshingly contained. Add the MerchantReturnPolicy and OfferShippingDetails blocks to the offers in your product JSON-LD — with values that match your real policies — verify with the Rich Results Test, and hit Validate Fix. Configure the same policies in Google Merchant Center as your update-proof backstop, keep your policy pages consistent, and save your snippets for the day a theme update erases them.

No penalty was ever looming — but now, instead of a wall of warnings, your products are eligible to show “30-day returns” and delivery estimates right in the search results, where they quietly out-click every listing that doesn’t.

That’s Shopify SEO at its best: small, technical, and compounding. For more of it, the resources below are your next step.

Keep Learning and Get Help

Prefer to follow along on video? Watch the full step-by-step walkthrough of this exact fix here: How to Fix Missing field ‘hasMerchantReturnPolicy’ in Shopify — and subscribe for more Shopify SEO and customization tutorials: youtube.com/@foysalshopifyexpert

Want your Shopify SEO handled for you? If you’d rather have an expert clear your Search Console issues, complete your structured data, and optimize your store’s technical SEO, hire me directly on Upwork: My Upwork Profile

Ready-made Shopify sections and code. I sell polished, plug-and-play Shopify code products — one-time payment, no subscriptions: ecommercethesis.gumroad.com

Learn Shopify professionally. Turn skills like this into freelancing income with my structured course: Freelancing with Shopify — or browse all courses.

Stuck on a step? Reach me directly on WhatsApp for personal help: wa.me/8801991505652

Happy optimizing — and enjoy a green Search Console.