Use this checker before changing Merchant Center shipping settings, adding product-level exceptions, launching a final-sale promotion, or updating return policy copy.
Free ecommerce tool
Shipping and Returns Consistency Checker
Find the places where shipping and return promises can drift apart across the storefront, checkout, Merchant Center, and structured data.
Quick answer
Shipping and return promises should say the same thing in the policy page, product page, checkout flow, Merchant Center settings, and structured data. If one system has an exception and the others do not, buyers and shopping systems can receive conflicting expectations.
Public policy URL, Where policy is managed, Standard return window in days, Visible shipping promise, Product-level exceptions, Relevant page or checkout copy
A consistency score, likely mismatch risks, and the next fields to reconcile before applying changes across the catalog.
Enter your details to generate a decision-ready output.
Why this matters in a real store
Shipping and Returns Consistency Checker matters because ecommerce growth work usually breaks down in the handoff between a number, a platform warning, a campaign idea, and the person who has to make the next decision. A store team may know something is wrong, but still lose time because the issue is not written in a way that connects the symptom to a next action.
Use this page as a practical translation layer. The goal is to slow down the first reaction, name the business risk, and give the team enough context to decide whether the next move is a calculation, a feed change, a campaign QA step, or a page update. The tables and checklists are there to make the work repeatable, but the judgment comes from understanding why the issue appears in the first place.
What consistency means
Shipping and returns copy is easy to treat as legal boilerplate, but shoppers experience it as part of the product offer. A return window on the policy page, a delivery promise on the product page, and a fee shown at checkout all shape the same buying decision.
The consistency problem usually appears when one team changes a rule in one place. A merchandiser marks a clearance item final sale, a feed manager adds a product shipping override, or operations changes the delivery window for a warehouse region. If the other surfaces do not change, the store now has multiple versions of the same promise.
Surfaces to compare
| Surface | What to capture | Mismatch to watch |
|---|---|---|
| Policy page | Return window, return fees, exclusions, contact path | Policy says 30 days while product pages say 14 days or final sale. |
| Product page | Delivery estimate, final-sale note, product-specific restrictions | A product has an exception that only appears after checkout starts. |
| Cart and checkout | Shipping service, cost, cutoff, destination limits | Checkout gives a different speed or cost than the visible page promise. |
| Merchant Center | Account shipping services, return policy, product overrides | Shopping surfaces receive a rule that does not match the storefront. |
| Structured data | Return policy markup and offer details | Markup describes a different return window than the public policy text. |
Run the check
- Capture the standard policy exactly as a shopper sees it.
- Capture one affected product page and one checkout path.
- Record whether a product-level exception changes the standard rule.
- Compare the same promise against Merchant Center and structured data settings.
- Update the system that disagrees and save the owner plus review date.
Decision note
The goal is not to make every policy page longer. The goal is to keep every buyer-facing and channel-facing surface from making a different promise.
Reference rules
Methodology and limits
The checker reviews the public policy URL, return window, shipping promise, exception notes, and visible page copy for common drift signals such as missing return windows, unclear final-sale language, and product-level shipping exceptions.
This tool does not inspect a live Merchant Center account, checkout, or structured data crawl. Treat the result as a comparison worksheet and verify the exact settings in each system.
Reusable download
Use the related CSV as a working file for the calculation, checklist, or planning step covered on this page.
Common questions
Should return exceptions live on the product page or the policy page?
Both may need to mention them. The policy page should define the rule, while affected product pages should surface the exception close to the buying decision.
Can Merchant Center settings replace visible policy copy?
No. Merchant Center settings help Google understand the offer, but shoppers still need clear public policy language on the site.
What is the highest-risk mismatch?
A product sold as final sale, oversized, preorder, or custom without the exception appearing consistently in page copy, checkout, and merchant settings.