Which shipping rate does Google use when several conditions match?

Definition: When more than one ShippingConditions object applies to a product, Google uses the lowest shipping cost for the situation. If the costs are equal, Google uses the shipping information with the fastest shipping speed.

Key facts

• Google's ShippingService documentation says a service can contain multiple shippingConditions objects.
• Google applies the lowest-cost rule to the conditions that apply to the product and situation, then displays that rate and its associated shipping speed.
• Schema.org defines ShippingConditions as constraints and shipping information that can depend on weight, size, price, and destination; every specified condition must be met for the object to apply.
• A Schema.org ServicePeriod represents a duration with constraints such as cutoff time and business days, and is used for shipping handling time or transit time.
• Schema.org describes ShippingService as criteria used to determine if and how an offer could be shipped to a customer.

What makes several shipping conditions match?

Google's shippingConditions property describes shipping cost or delivery times for a particular set of conditions. The documentation gives a product weight range, product dimensions, order value, and delivery location as examples. A single ShippingService can therefore contain rules that overlap for one order.

Schema.org describes a ShippingConditions object as a set of constraints and shipping information. All specified conditions must be met for that object to apply. For example, an order-value range and a destination can both constrain one rule, while another rule can cover a different order-value range for the same destination.

The shape of a condition can be represented like this, following Google's ShippingService example:

{
  "@type": "ShippingService",
  "shippingConditions": [
    {
      "@type": "ShippingConditions",
      "orderValue": { "@type": "MonetaryAmount" },
      "shippingRate": { "@type": "MonetaryAmount" },
      "transitTime": { "@type": "ServicePeriod" }
    }
  ]
}

How does Google choose between matching rates?

Google's documented rule is a cost comparison followed by a speed comparison. First, it considers the ShippingConditions objects that apply to the product. It uses the lowest shipping cost for the given situation and displays that rate with the associated shipping speed. When two or more applicable conditions have the same shipping cost, Google uses the shipping information with the fastest shipping speed.

Schema.org defines shippingRate as the cost of shipping to the specified destination. Its definition says that the maxValue and currency values of a MonetaryAmount are typically the appropriate values. The rate comparison therefore concerns the shipping charge expressed by the matching condition.

Which fields carry the rate and delivery speed?

For a standard business shipping policy, Google documents ShippingService nested under Organization through hasShippingService. For a non-standard policy for one product, it documents OfferShippingDetails nested under Offer; the offer-level policy supports a smaller property set than the organization-level policy.

The cost belongs in shippingRate. The delivery estimate belongs in transitTime, which Google's documentation describes as the expected time between leaving the shipping origin, typically a warehouse, and arriving at the shipping destination, typically the customer. handlingTime covers the delay after an order is received and before goods leave the warehouse. Schema.org's ServicePeriod provides the duration structure and can also carry business days and a cutoff time.

How can a site check the result?

Google recommends validating the markup with the Rich Results Test, then deploying pages with the structured data and using the URL Inspection tool to test how Google sees the page. The page must be accessible to Google and cannot be blocked by robots.txt, a noindex tag, or login requirements.

For an overlap review, compare every specified condition in each object, keep the objects whose constraints all match the same product and order, and compare their shipping rates. The documented selection result is the lowest cost, with shipping speed deciding an equal-cost comparison. Google's page does not document a further tie breaker when both cost and shipping speed are equal.

Related terms

• OfferShippingDetails structured data
• Structured data
• Offer structured data
• Google Merchant Center

FAQ

Does Google choose the fastest shipping option when prices differ?

No. Google's ShippingService documentation says Google first uses the lowest shipping cost. Shipping speed decides the comparison when the shipping cost is the same.

What must be true for a shipping condition to apply?

All specified conditions in the ShippingConditions object must be met. A rule can combine constraints such as order value and destination.

What happens when matching conditions have the same cost and speed?

Google's documented rule specifies the fastest shipping speed as the tie breaker for equal costs. It does not state a further selection rule for a remaining tie.

Sources

1. Google Search Central, "Merchant shipping policy (ShippingService) structured data", 2026-09-08
2. Schema.org, "ShippingConditions", 2026-09-16
3. Schema.org, "ShippingService", 2026-09-16
4. Schema.org, "ServicePeriod", 2026-09-16

---

Check how a page reads to answer engines. Open the GEO score analyzer