First, Check the Exact Product — Not Just Your Storewide Shipping Policy
Suppose your normal shipping rule is:
$12.99 flat rate
You open Merchant Center's shipping settings and see exactly that.
So everything looks correct.
But the affected product still shows:
$5 shipping
Why?
That individual product may contain its own:
shipping
attribute.
And when product-level shipping information is supplied, it can override your account-level shipping settings for that product.
So I'd compare:
Account-level shipping
vs.
Product-level shipping
before changing anything.
This is especially worth checking if only a small number of SKUs are affected.
If 10 products show the wrong rate while 5,000 others are fine, I would look for a product-level override before assuming the whole shipping setup is broken.
A Simple Example
Imagine your account says:
Standard shipping: $9.99
But one old feed row still contains:
shipping = US:9.99 USD
No problem.
Then six months later you increase shipping to:
$12.99
You update the account-level policy.
But the product-level override remains:
$9.99
Google may continue using the product-level value for that item.
Meanwhile your checkout charges:
$12.99
Now the storewide setup looks right, but the product still has stale shipping data.
This is why I wouldn't diagnose a shipping mismatch only from the Shipping and returns page.
I would check the affected SKU itself.
Then Reproduce the Same Checkout Google Is Comparing
Shipping is highly dependent on context.
A customer in one location may pay:
$5
while someone in another state pays:
$14
A $60 order may have paid shipping.
A $120 order may qualify for:
Free shipping
So when you test the issue, don't simply add the product to your cart and look at whatever rate appears for you.
Try to reproduce the same conditions Google is evaluating.
Check:
destination
order value
product quantity
product weight
shipping service
free-shipping threshold
Otherwise, you may compare two completely different shipping scenarios.
Use Merchant Center's Shipping Calculator
For affected products, Merchant Center currently provides a Shipping calculator on the product details page in supported locations.
It can show:
attached shipping policies
shipping cost
destination-specific information
availability
which policy provides the displayed rate
If several shipping policies apply, Merchant Center can show the lowest applicable cost that Google would present.
That makes it a useful debugging tool.
Instead of asking:
“Why does Google say $7?”
you can start asking:
“Which shipping policy produced Google's $7?”
That's a much easier problem to solve.
Check Free-Shipping Thresholds Carefully
This is another place where configurations drift apart.
Your website may say:
Free shipping over $100
But Merchant Center is configured as:
Free shipping over $75
Now consider an $80 order.
Merchant Center
Free shipping
Checkout
$9.99 shipping
That's a mismatch.
Or the opposite could happen.
Google allows Merchant Center shipping rules based on order value, including free shipping above a defined threshold.
So if the error only appears on certain basket values, I would inspect:
minimum order value / free shipping threshold
before anything else.
Weight-Based Shipping? Verify the Weight
If your shipping cost depends on product weight, the next thing I would check is:
shipping_weight
For weight-based or carrier-calculated shipping, Merchant Center uses the submitted shipping weight to calculate the rate.
Google specifically requires shipping_weight when using certain weight-based shipping setups.
For example:
Real packaged weight
8 kg
Feed
shipping_weight = 2 kg
The customer may be charged based on 8 kg at checkout.
Google may estimate the shipping cost from 2 kg.
The shipping policies themselves can both be correctly configured.
The bad input is the product weight.
This is why a shipping mismatch isn't always a “shipping settings” problem.
Sometimes it's a product-data problem.
Don't Forget Package Dimensions
Carrier-calculated shipping can also depend on package dimensions.
Merchant Center supports product attributes such as:
shipping_lengthshipping_widthshipping_heightshipping_weight
for shipping calculations where relevant.
This matters especially for:
furniture
large home goods
bulky equipment
lightweight but oversized packages
A large lightweight parcel may cost much more to ship than its physical weight suggests.
If your checkout uses dimensional weight but Merchant Center does not have the same package information, the two systems may calculate different rates.
Look for Fees Added Only at Checkout
Here's a less obvious version.
Your website shows:
Shipping: $8
Then checkout adds:
Handling fee: $4
The shopper ultimately pays:
$12
Merchant Center only knows about the $8.
Google's current guidance says additional mandatory charges such as handling or carrier-related fees need to be represented appropriately rather than appearing unexpectedly only at checkout.
So ask:
Is checkout adding a required logistics-related fee that Merchant Center never sees?
If yes, hiding it until checkout doesn't solve the problem.
The shopper still pays it.
Check Whether the Problem Is Regional
Suppose your shipping rules are:
Mainland US
$8
Alaska
$25
Hawaii
$25
But Merchant Center applies:
$8 nationwide
The rate is accurate for most customers.
It is still wrong for some destinations.
Merchant Center supports destination-based shipping rules in supported markets, and you can also use shipping overrides where necessary.
So if Google gives you example products or locations in the warning, pay attention to them.
The important clue may not be the product.
It may be:
where the shopper lives.
What if You Can't Calculate the Exact Shipping Cost?
This is one of those cases where Google's guidance is surprisingly practical.
If you genuinely cannot reproduce the exact shipping charge in Merchant Center, Google recommends getting as close as possible—and slightly overestimating rather than underestimating the shipping cost.
Why?
Because this is much worse:
$5 shipping
Checkout
$15 shipping
than:
$15 shipping
Checkout
$13 shipping
The first creates an unpleasant surprise at checkout.
That doesn't mean you should massively inflate shipping rates.
Excessive overestimation can hurt performance.
The point is:
don't advertise a shipping cost lower than what customers may actually be forced to pay.
If Hundreds of Products Are Wrong, Stop Checking Them One by One
If one product has the wrong shipping rate, I would inspect:
that product's override.
If 15,000 products suddenly have the wrong rate, I would inspect:
account-level policy
ecommerce platform synchronization
shipping app
feed generator
recent configuration changes
The number of affected products tells you something.
Large-scale mismatches usually point toward a shared system.
Small isolated mismatches often point toward product-specific data.
One Thing I Would Not Do
I would not increase the product's base price just to make the shipping warning disappear unless the business actually intends to include that cost in the product price.
A shipping mismatch is normally solved by making shipping data and checkout behavior agree.
Changing:
Product price: $49 → $59
just because shipping is off by $10 can create a second problem:
price mismatch.
Fix the field or shipping rule that is actually wrong.
My Quick Debugging Order
If Merchant Center reports inaccurate shipping costs, I'd check:
Affected product
→ Does it have a product-level shipping override?
↓
Merchant Center shipping calculator
→ Which policy is producing Google's displayed rate?
↓
Checkout
→ What does the shopper actually pay for the same destination and basket?
↓
Thresholds
→ Are free-shipping/minimum-order rules aligned?
↓
Weight and dimensions
→ Are calculation inputs accurate?
↓
Extra fees
→ Does checkout add handling or logistics charges?
↓
Region
→ Does shipping change by destination?
Only then would I start redesigning the entire shipping configuration.
After You Fix It
Google's current process for inaccurate shipping-cost issues is:
Correct the Merchant Center shipping settings or product-level shipping data.
Resubmit or refresh the relevant product data.
If the account or product has been disapproved, request a review where applicable.
Google says a fresh crawl after a review request will often complete in roughly 24–48 hours, though additional verification may apply depending on the issue.
So don't request repeated reviews before the underlying configuration is actually fixed.
If Shipping Isn't Your Only Data Problem
Shipping-cost configuration mostly lives in Merchant Center, your feed and your checkout rules.
Mingche's free Product Page Check is not a dedicated shipping audit.
But if you're also seeing inconsistent:
prices
availability
variants
structured data
you can check three public product pages from the same store first.
Check 3 Product Pages for Free →
That helps answer a different question:
“Is my public product-page data consistent?”
For a pure shipping-cost mismatch, focus first on:
Merchant Center shipping settings → product overrides → checkout → destination → weight / dimensions.
Bottom Line
When Google says your shipping cost is inaccurate, don't start by asking:
“What shipping price should I type into Merchant Center?”
Start by asking:
“Why is Google calculating one rate while my checkout calculates another?”
Then find the source:
account shipping policy
→ product-level override
→ weight / dimensions
→ destination
→ order threshold
→ checkout fees
The correct fix is the one that makes the amount shown on Google line up with what the shopper will actually have to pay.
Disclaimer
Mingche is an independent product-data readiness service and is not affiliated with or endorsed by Google.
Product-data auditing or correction does not guarantee approval, visibility, ranking, traffic or sales. Google independently determines Merchant Center eligibility and how products appear across its services.
Comments
Post a Comment