Shipping policy schema disagrees with checkout
Trace a shipping markup mismatch across country, order value, handling time, transit time, and product exceptions before updating the published policy.
By Crawlito · 5 min read
In short
- Google documents standard shipping services under Organization and product-specific shipping details under Offer.
- Handling time and carrier transit time describe different parts of delivery.
- A shipping rule needs a defined destination, order conditions, currency, and supported service.
On this page
- Define one reproducible order scenario
- Map the store policy to the right structured level
- Separate handling from transit time
- Reproduce threshold and destination boundaries
- Verify the published policy and the customer path
- Test a service renamed by the carrier integration
- Frequently asked questions
- Check the product's public description
If structured shipping information disagrees with checkout, reproduce one order scenario and compare the destination, items, value, service, and delivery timing across both surfaces. Fix the policy data or mapping that disagrees with the store's actual offer. Google supports standard shipping policies under Organization and product-specific exceptions through OfferShippingDetails on an offer. Google’s shipping policy documentation
Define one reproducible order scenario
Start with a public product, a quantity, a destination region, and an order value. Record the currency and whether a discount affects the threshold calculation. “Free delivery over 50” is incomplete if the checkout applies the threshold after discounts while the policy page describes the subtotal before discounts.
Use a test cart and stop before payment. Compare the available shipping service and charge at the point where the customer can see them. A cart showing an estimated fee before the address is known may legitimately differ from the final quoted service. Label the stage of the journey in your evidence so the policy owner can interpret it.
Include the actual product configuration. A lightweight accessory and an oversized item can use different delivery methods even when their prices are equal. A mixed cart can also change the available service. The diagnosis needs a concrete scenario that another person can reproduce, not a screenshot of a total without the items and destination.
Map the store policy to the right structured level
Google's standard policy model uses ShippingService under the organization's hasShippingService property, with conditions describing where and when a service applies. Product-level overrides use a more limited model under the offer. Read the current property definitions for the level you are editing rather than copying a field from one model into the other.
Create a mapping table before writing JSON. For each public service, identify the destination, threshold or weight condition, currency, rate, handling period, transit period, and any excluded product class. Keep the names aligned with checkout so a reader can recognize the service being described.
| Store fact | Evidence to retain |
|---|---|
| Standard domestic service | Published policy and matching checkout option |
| Free-shipping threshold | Subtotal basis, currency, and boundary examples |
| Dispatch preparation | Handling period and operating days |
| Carrier movement | Transit range for the supported destination |
| Oversized item exception | Product classification and available shipping option |
The organization schema guide helps locate the existing store entity. A second organization block containing a contradictory delivery policy can make the page harder to interpret even when each block passes a syntax test.
Separate handling from transit time
A product can take two working days to prepare and another two days with the carrier. Treat those periods according to the documented properties and the store's real operating calendar. “Two-day shipping” can mean dispatch within two days, arrival two days after dispatch, or an overall promise. Ask the policy owner what the customer is actually being offered.
Check order cutoff times and business days. An order placed late on Friday can follow a different schedule from one placed early on Tuesday. A template that adds calendar days to every order may disagree with the carrier and warehouse calendar. Use the public wording to make the applicable conditions understandable.
Test a normal weekday, a cutoff boundary, and a closure period relevant to the service. Keep the expected result grounded in the merchant's current operational policy. If a temporary disruption changes the offer, update the visible policy and the structured representation through the same source where possible. A delivery estimate copied into a static template can remain stale long after checkout changes.
Reproduce threshold and destination boundaries
Choose cart values immediately below, at, and above the free-shipping threshold using the merchant's actual currency precision. Apply a qualifying discount and repeat if discounts affect the calculation. A comparison at exactly the threshold often reveals whether the code implements “over” or “at least” the stated amount.
For destination rules, test one ordinary address in the served area and one address in an explicitly excluded region using your approved test data. A country-level rule can be too broad when the service excludes islands or special zones. Use the supported geographic fields only when they accurately express the policy; otherwise revise the public description and mapping with the merchant.
Check product exceptions on an individual product and in a mixed cart. If the markup claims free standard delivery for a large item that checkout treats as freight, follow the catalog attribute that controls the exception. The product schema guide explains how to inspect the selected product and offer. Keep ordinary products as controls so a fix to the exception does not change the storewide offer unexpectedly.
Verify the published policy and the customer path
Fetch the public policy and product pages after the release. Inspect the structured entities, confirm the service names and conditions, and compare them with a clean test cart. A page cache can retain the previous threshold even while checkout reads a new backend value. Record the response time and source revision when chasing that difference.
Use the supported structured data testing tool for the model you publish, then inspect the values it recognized. Validation can establish whether fields are accepted but cannot prove that a carrier serves the promised region or that the store dispatches on Saturday. Those are operational facts to confirm with the policy owner.
Follow the policy link from the product page and checkout. A generic footer link can open a policy for the wrong market after a locale switch. Make sure a new customer can identify the terms applying to the offer without a saved session. The multilingual site guide provides a method for testing those direct visits.
Keep a small regression set with the threshold boundaries, an exception product, and an ordinary destination. Repeat it when the merchant changes delivery rates, currencies, carrier integrations, or warehouse calendars. Record which part of the policy changed so the next report can be compared with a known release.
Test a service renamed by the carrier integration
A merchant may rename a delivery option in checkout while the policy page still uses the carrier's former label. Compare the service identifier behind each name before treating them as different offers. A display-name change can be harmless, while an identifier change may select a genuinely different transit schedule or fee.
Choose one destination and cart where the service is available, and inspect the mapped handling and transit values alongside the quote. If the old identifier no longer resolves, correct the integration mapping and verify the default service selected for new orders. Keep an unavailable-service case in the test so the site does not publish a delivery promise after the carrier option disappears.
Frequently asked questions
Should I publish only the fastest possible arrival time?
Describe the service and conditions the merchant actually offers. A best-case observation is insufficient evidence for a general customer promise.
Can product shipping details override a store policy?
Google documents product-level shipping details for exceptions. Check the supported fields and ensure the exception describes the relevant offer accurately.
Why does checkout differ only after a coupon?
The threshold may be calculated from a discounted subtotal or a different order basis. Reproduce the rule at the boundary and align the published wording with the intended policy.
Check the product's public description
Run the free page check on an affected product page, then compare its shipping data with the same test cart. The page and checkout should describe one coherent offer.
Filed under Structure and schema. Topics: ecommerce, structured-data, google