How to set up shipping and delivery times in Google Merchant Center for WooCommerce

How to set up shipping and delivery times in Google Merchant Center for WooCommerce

Accurate shipping and delivery information helps customers understand the complete cost and expected arrival time of a WooCommerce order before they visit the checkout.

Google Merchant Center also uses shipping information to determine whether a product’s delivery cost, destination coverage and estimated arrival date can be presented accurately across Shopping ads, free listings and other supported Google surfaces.

A WooCommerce store may have working shipping zones and still contain incorrect Merchant Center delivery settings.

For example, the website may calculate a three-to-five-day delivery estimate while Merchant Center advertises next-day delivery. A customer may receive free shipping at checkout, while the product listing displays a paid service. A store may dispatch products only from Monday to Friday, but Google may calculate estimates using additional working days.

Problems also occur when merchants confuse three separate concepts:

• Order cut-off time
• Handling time
• Transit time

These values work together, but they describe different stages of order fulfilment.

The objective is not to enter the shortest possible delivery time.

The objective is to describe the store’s actual fulfilment process accurately, match Google Merchant Center with WooCommerce and provide customers with a delivery estimate the business can reasonably honour.

The short answer

To configure Google Merchant Center shipping and delivery times for WooCommerce:

• Audit the shipping destinations supported by the store.
• Review every WooCommerce shipping zone.
• Confirm which shipping methods appear for each customer location.
• Record the shipping price charged by each method.
• Identify any free-shipping thresholds.
• Confirm the operational order cut-off time.
• Measure how long the store takes to prepare an order.
• Measure how long each carrier takes after collection.
• Distinguish handling time from transit time.
• List the days on which the warehouse processes orders.
• List the days on which each carrier transports or delivers parcels.
• Review holidays and seasonal disruptions.
• Check products requiring longer preparation or specialist delivery.
• Test WooCommerce cart and checkout with representative addresses.
• Publish clear shipping and delivery information on the website.
• Open Google Merchant Center.
• Select Shipping and returns from the left navigation.
• Open the Shipping policies tab.
• Select Add shipping policy.
• Choose the applicable countries.
• Choose whether the policy applies to all or selected products.
• Select carrier-calculated or manually entered delivery times.
• Enter the correct order cut-off time and time zone.
• Enter minimum and maximum handling time.
• Enter minimum and maximum transit time.
• Configure destination zones where delivery speeds differ.
• Enter the shipping cost or free-shipping conditions.
• Review the complete policy against WooCommerce checkout.
• Save the policy.
• Use shipping_label for product groups with different delivery conditions.
• Use product-level shipping data only when an account-level policy cannot describe the product accurately.
• Monitor Merchant Center for shipping-related warnings and product issues.
• Update WooCommerce, Merchant Center, product data and structured data together when conditions change.

Do not enter same-day dispatch merely because a carrier offers next-day transportation.

Same-day dispatch means the store can prepare the order and hand it to the carrier on the day it is received, subject to the published order cut-off time.

Why shipping information matters

Shipping is part of the product offer.

Customers compare more than the product price. They may also consider:

• Whether delivery is available to their location
• The shipping cost
• The earliest expected delivery date
• The latest expected delivery date
• Whether express delivery is available
• Whether free shipping requires a minimum order
• Whether the product requires special handling
• Whether delivery includes tracking
• Whether local collection is available
• Whether duties or other cross-border charges apply

Google’s current shipping attribute documentation explains that shipping covers both cost and speed. Shipping speed consists of handling time and transit time.

Google may use the submitted values to calculate an estimated arrival date. This delivery estimate may appear with eligible Shopping ads or free listings.

An inaccurate estimate can create several problems.

A delivery date that is too optimistic may result in late orders and customer complaints. A delivery date that is unnecessarily slow may make the offer less attractive than it actually is. Incorrect costs can also create a difference between the product listing and WooCommerce checkout.

Google independently decides where and how shipping information appears. Accurate shipping data does not guarantee an annotation, higher ranking, additional impressions or sales.

Shipping cost and delivery time are different

Shipping cost describes what the customer must pay for delivery.

Delivery time describes how long the complete fulfilment process is expected to take.

A shipping service can therefore have:

• Free delivery in five to seven business days
• Paid delivery in two to three business days
• Free delivery above a minimum order value
• A flat shipping charge with different regional transit times
• A carrier-calculated cost and carrier-calculated transit time
• The same cost for all products but different handling times
• Different costs for oversized or perishable products

Do not assume that correcting the shipping cost automatically corrects the delivery estimate.

A Merchant Center policy must accurately represent both areas.

For a separate cost-specific investigation, see How to fix shipping cost mismatch in Google Merchant Center for WooCommerce.

Understand the delivery-time formula

Google describes the estimated delivery date as the maximum handling time plus the maximum transit time, adjusted for the order cut-off, applicable working days and supported holidays.

The three main components are:

• Order cut-off time
• Handling time
• Transit time

A simple example is:

• Cut-off time: 2:00 p.m.
• Handling time: one to two business days
• Transit time: two to four business days

An order placed before the cut-off could therefore require up to six applicable business days after processing begins.

An order placed after the cut-off may begin processing on the next applicable business day.

The result is not always a simple calendar-day addition. Weekends, operational days, carrier schedules, holidays, the customer’s location and the selected service can change the expected arrival date.

Google’s official estimated delivery-time guidance explains this calculation and the role of each value.

What order cut-off time means

The order cut-off is the latest time at which an order can be received and begin processing on the same business day.

For example:

• Warehouse operating hours: 9:00 a.m. to 6:00 p.m.
• Carrier collection: 4:00 p.m.
• Operational order cut-off: 1:30 p.m.

The correct Merchant Center cut-off may be 1:30 p.m., not 6:00 p.m.

Orders received after the operational cut-off cannot realistically enter the same fulfilment cycle if staff need time to:

• Validate payment
• Confirm stock
• Print picking documents
• Pick and inspect the product
• Pack the item
• Print the carrier label
• Complete export documentation
• Transfer the parcel to the collection point
• Hand the parcel to the carrier

Google states that when no cut-off is configured, a default may be used. Relying on a default can produce unsuitable estimates, particularly when the warehouse operates in another time zone.

Enter the real cut-off and confirm its time zone.

A cut-off entered as 3:00 p.m. without the correct time zone may be interpreted differently from the store’s local operation.

What handling time means

Handling time is the time between receiving the order and handing the parcel to the carrier.

It may include:

• Payment confirmation
• Fraud review
• Stock allocation
• Picking
• Product inspection
• Assembly
• Personalisation
• Manufacturing
• Packaging
• Carrier-label creation
• Customs documentation
• Warehouse transfer
• Dispatch preparation

Handling time does not end when the order status changes to Processing in WooCommerce.

It ends when the parcel is actually ready for and handed to the delivery service.

If ordinary in-stock products are dispatched in one or two business days, enter:

• Minimum handling time: 1
• Maximum handling time: 2

If orders received before the cut-off are always dispatched on the same day, a handling time of zero may be appropriate.

Do not use zero merely because some orders occasionally leave on the day they are placed.

The maximum value should cover the store’s normal service commitment without hiding predictable delays.

What transit time means

Transit time begins after the carrier receives the parcel and ends when the customer receives it.

It may vary according to:

• Customer location
• Origin warehouse
• Carrier
• Carrier service level
• Urban or remote destination
• Domestic or international delivery
• Parcel weight
• Parcel dimensions
• Dangerous-goods restrictions
• Customs procedures
• Weekend operations
• Local holidays
• Seasonal capacity
• Weather and other disruptions

Transit time is not the complete time between order and delivery.

If WooCommerce states “delivery in three to five days” but the carrier itself requires three to five business days after collection, the handling period must also be included in the complete customer promise.

According to Google’s setup guidance, manually entered transit time can use a single range or destination-specific zones.

Start with WooCommerce, not Merchant Center

Merchant Center should reflect the shipping process customers actually receive.

Before creating a policy in Google, document the WooCommerce configuration and the real warehouse operation.

Review:

• Countries where checkout is permitted
• Excluded countries
• States, provinces or regions with special rules
• Postcodes with different methods
• Shipping zones
• Shipping methods
• Shipping classes
• Flat rates
• Free-shipping thresholds
• Local pickup
• Carrier extensions
• Table-rate plugins
• Real-time carrier calculations
• Product-specific shipping fees
• Handling fees
• Delivery estimates displayed on product pages
• Delivery estimates displayed at checkout
• Multiple warehouse arrangements
• Dropshipped products
• Made-to-order products
• Backorders and pre-orders
• Oversized products
• Perishable products
• International customs procedures

Do not reproduce the WooCommerce configuration mechanically without verifying it.

A shipping method can exist in WordPress but be operationally inaccurate. A carrier extension can return a price without providing a dependable delivery estimate. A shipping zone may accidentally include a country the business does not actually serve.

Review WooCommerce shipping zones

WooCommerce shipping zones determine which methods customers see based on their shipping address.

The official WooCommerce shipping-zone documentation explains that each customer matches one zone and that zones are evaluated in order. The first matching zone controls the available methods.

To review the configuration:

• Open WordPress administration.
• Go to WooCommerce.
• Select Settings.
• Open Shipping.
• Select Shipping zones.
• Review every listed zone.
• Open each zone and inspect its regions.
• Review postcode restrictions.
• Review enabled shipping methods.
• Review the order of the zones.
• Inspect the Rest of the world zone.
• Save corrections.
• Test representative addresses.

Arrange specific zones before broad zones.

For example:

1. Remote island postcodes
2. Specific state or province
3. Entire country
4. Continental region
5. Rest of the world

If a broad country zone appears before a postcode-specific zone, the customer may receive the wrong method and delivery estimate.

Review the Rest of the world zone

WooCommerce includes a Rest of the world zone for addresses that do not match another zone.

This zone can create unintended international availability.

If it contains an active flat-rate method, customers from unplanned destinations may be able to complete checkout.

Compare this setting with Merchant Center.

Do not tell Google that delivery is unavailable to a country when the WooCommerce checkout offers a method for that location. Conversely, do not enable a country in Merchant Center if the customer reaches “No shipping options were found” at checkout.

If certain countries must be excluded, configure WooCommerce and Merchant Center consistently.

Review WooCommerce shipping methods

WooCommerce core includes:

• Flat rate
• Free shipping
• Local pickup

Additional extensions may provide:

• Carrier rates
• Table rates
• Same-day courier
• Distance-based delivery
• Weight-based shipping
• Shipment by product quantity
• Multi-vendor shipping
• Dropshipping
• Freight delivery
• Collection-point delivery

Record the following for each method:

• Customer destination
• Eligible products
• Shipping cost
• Free-shipping threshold
• Minimum order value
• Order cut-off
• Handling range
• Transit range
• Operating days
• Carrier
• Service level
• Delivery exclusions

The name of the WooCommerce method is not sufficient.

A method called “Standard delivery” does not explain whether it takes two days or ten days.

Test the real checkout

Use WooCommerce checkout as a customer would.

Test:

• A nearby postcode
• A distant domestic postcode
• A remote region
• A standard international destination
• An excluded country
• A standard product
• A low-value order
• An order above the free-shipping threshold
• A heavy product
• An oversized product
• A product with a shipping class
• A variable product
• A mixed cart
• An out-of-stock or backordered product

For each test, record:

• Available shipping method
• Displayed shipping cost
• Tax treatment
• Delivery estimate
• Currency
• Free-shipping threshold
• Any handling or remote-area surcharge

A Merchant Center policy should not be considered complete until it has been compared with actual checkout results.

Publish shipping information on the website

Create a public shipping or delivery page that explains:

• Countries served
• Processing time
• Order cut-off
• Operating days
• Delivery methods
• Estimated transit time
• Shipping costs
• Free-shipping conditions
• Remote-area rules
• International delivery
• Customs or import responsibilities
• Tracking availability
• Delayed-shipment procedures
• Pre-order and backorder rules
• Oversized-product delivery
• Contact information

Make the page accessible without login.

Add a visible link from the footer and relevant customer-service areas.

Product pages should disclose significant exceptions before purchase.

Do not advertise “next-day delivery” in a banner if it applies only to selected products, locations or orders placed before a specific time.

How to add a shipping policy in Google Merchant Center

Google’s current instructions use the following general path:

• Sign in to Merchant Center.
• Select Shipping and returns from the left navigation.
• In some account layouts, this appears under Products & store.
• Open Shipping policies.
• Select Add shipping policy.
• Choose Shipping for online products.
• Select the applicable countries.
• Choose the products covered by the policy.
• Configure delivery times.
• Configure shipping costs.
• Review the information.
• Save the policy.

Google’s interface wording can change according to account type, language, country and future interface updates.

The current shipping-information requirements identify delivery time, shipping cost and applicable countries as the principal information required for a shipping policy.

Step 1: Choose the countries

Select only countries where:

• The WooCommerce store accepts orders
• A working shipping method is available
• The displayed shipping price is accurate
• Delivery can be completed
• The stated transit time applies
• The business can handle returns and customer support
• Applicable tax and customs requirements are understood

One policy can cover multiple countries when the same service, cost and delivery conditions genuinely apply.

Create separate policies when countries have different:

• Shipping costs
• Carriers
• Handling times
• Transit times
• Free-shipping thresholds
• Currencies
• Warehouse origins
• Customs procedures
• Product restrictions

Do not add a country merely because Merchant Center permits it.

Step 2: Choose the applicable products

A shipping policy can apply to:

• All products
• Products identified by a shipping label
• Another supported product group

Use all products when the policy genuinely describes the complete eligible catalogue.

Use a restricted group when products require different:

• Handling times
• Transit times
• Shipping costs
• Delivery methods
• Carrier services
• Packaging processes
• Warehouse origins

Examples include:

• Oversized products
• Perishable products
• Made-to-order products
• Personalised products
• Hazardous materials
• Refrigerated goods
• Digital products excluded from physical shipping
• Products with free shipping
• Freight products

Step 3: Choose how delivery time is calculated

Merchant Center may provide options such as:

• Google-calculated carrier delivery time
• Partner-provided delivery time
• Manually entered delivery time

Choose according to the store’s real fulfilment process and the options supported in the target country.

Carrier-calculated delivery can use factors such as:

• Warehouse or ship-from location
• Customer destination
• Carrier
• Carrier service

Google’s carrier-calculated shipping-speed guidance explains that the merchant still supplies handling time while Google calculates supported transit and overall shipping speed.

Manual delivery times may be more appropriate when:

• The carrier is unsupported.
• Several carriers are selected dynamically.
• Products use specialist freight.
• Delivery is completed by the merchant.
• A dropship supplier controls dispatch.
• Regional delivery times require custom zones.
• Carrier estimates do not represent the service sold at checkout.

Do not select a supported carrier merely because its name is familiar. Select the carrier and service actually used for the policy.

Step 4: Enter the order cut-off

Enter:

• The latest operational order time
• The correct time zone
• The applicable working days

Verify the cut-off against:

• Payment processing
• Warehouse staffing
• Carrier collection
• Order-routing systems
• Fraud review
• Supplier processing
• Same-day dispatch promises

If the carrier collects at 5:00 p.m. but the warehouse requires two hours to prepare a parcel, a 5:00 p.m. order cut-off is unlikely to be accurate.

Orders placed after the cut-off generally begin processing on the next applicable business day.

Step 5: Enter handling time

Enter the minimum and maximum number of business days.

Examples:

Same-day dispatch:

• Minimum: 0
• Maximum: 0

Same-day or next-day dispatch:

• Minimum: 0
• Maximum: 1

Standard warehouse processing:

• Minimum: 1
• Maximum: 2

Made-to-order processing:

• Minimum: 5
• Maximum: 10

Use a separate policy or product-level value when selected products take longer than the default catalogue.

Google states that item-level handling-time data overrides the account-level handling time for that product when both are present.

Step 6: Enter transit time

Enter the minimum and maximum carrier transit range in business days.

For example:

• Domestic urban delivery: one to three business days
• Remote domestic delivery: three to six business days
• International delivery: five to twelve business days

These are illustrations, not recommended values. Use measured carrier performance and contractual service levels.

Where supported, configure destination zones when different parts of a country receive different transit times.

Do not use one fast national value if remote regions normally require longer.

Step 7: Review business days

Handling business days describe when the store prepares orders.

Transit business days describe when the carrier transports or delivers parcels.

These schedules may differ.

For example:

• Warehouse handling: Monday to Friday
• Carrier transit: Monday to Saturday
• Delivery: Monday to Saturday

Google supports shipping handling and transit business-day information where applicable. Review the current handling business-days requirements and transit business-days requirements before submitting non-standard schedules.

Do not count Sunday as a handling day because the website accepts orders on Sunday. Receiving an online order is not the same as processing it.

Step 8: Account for holidays

Holidays can extend the estimated delivery date when they overlap with handling or transit.

Review:

• National public holidays
• Regional holidays
• Carrier closure dates
• Warehouse shutdowns
• Seasonal inventory counts
• Holiday campaign cut-offs
• Year-end operating hours
• Supplier closures

Do not promise delivery before a holiday based solely on normal-week performance.

Publish seasonal order deadlines clearly and update expired banners afterward.

Step 9: Configure shipping costs

Select the method that matches WooCommerce checkout.

Possible configurations include:

• Free shipping
• Free shipping above a threshold
• Flat rate
• Carrier rate
• Cost based on order value
• Cost based on weight
• Cost based on quantity
• Cost based on destination
• Rate table

The amount displayed in Merchant Center should not be lower than what an eligible customer must pay at checkout.

Review whether WooCommerce adds:

• Handling charges
• Fuel surcharges
• Remote-area fees
• Insurance
• Packaging costs
• Delivery service fees

Google may consider charges directly related to shipping part of the submitted shipping cost.

Step 10: Save and test the policy

Before saving, compare:

• Policy country
• WooCommerce zone
• Eligible products
• Carrier
• Service level
• Shipping cost
• Free-shipping threshold
• Cut-off
• Cut-off time zone
• Handling minimum
• Handling maximum
• Transit minimum
• Transit maximum
• Handling days
• Transit days
• Regional exceptions
• Product exceptions

After saving:

• Reopen the policy.
• Confirm every value.
• Test affected products in Merchant Center.
• Review customer-facing delivery information.
• Monitor diagnostics and product issues.
• Allow Google time to process the changes.

Account-level and product-level shipping

Account-level policies are usually the most manageable approach for products sharing the same shipping conditions.

Product-level shipping data can override account settings for matching products and locations.

Google recommends using account settings for ordinary models and using the product-level shipping attribute when an offer requires an exception that cannot be represented accurately at account level.

Product-level overrides require careful control because they can include:

• Country
• Region
• Postal code
• Service
• Shipping price
• Handling time
• Transit time
• Cut-off details

Google’s shipping documentation notes that supplying product-level shipping price can cause relevant account-level delivery-time and minimum-order settings to be ignored for the matching product and location. The required values must then be supplied correctly at product level.

Do not add a product-level shipping cost without checking what other policy values it overrides.

Minimum and maximum time attributes

Google product data can include:

• min_handling_time
• max_handling_time
• min_transit_time
• max_transit_time
• handling_cutoff_time
• handling_cutoff_timezone
• shipping_handling_business_days
• shipping_transit_business_days

The maximum values are especially important for calculating the customer-facing delivery commitment.

When shipping speed is submitted within product-level shipping data, review Google’s complete attribute requirements. Missing a required maximum value can invalidate the associated shipping-time information.

Use business days, not an unexplained mixture of business and calendar days.

How shipping labels work

The shipping_label attribute groups products requiring a particular shipping policy.

The label is not normally shown to customers.

Examples include:

• oversized
• perishable
• free_shipping
• made_to_order
• international_only
• freight
• long_handling

Google’s official shipping_label documentation allows merchants to group products for different shipping costs or speeds.

Use stable technical labels.

Do not translate or frequently rename them.

A WooCommerce mapping might use:

• Shipping class Oversized → oversized
• Product tag Made to order → made_to_order
• Category Chilled food → perishable
• Custom field Free delivery → free_shipping

After assigning a label, create or verify the corresponding Merchant Center policy.

A label does not contain the complete policy by itself. It connects the product with applicable shipping services.

Shipping labels and WooCommerce variations

Variable products may require variation-level review.

For example:

• Small furniture variation: standard parcel
• Large furniture variation: freight
• Standard engraving option: two-day handling
• Custom engraving option: seven-day handling

If variations are submitted as individual offers, confirm that each receives the correct shipping label and timing data.

Do not assume the WooCommerce parent value automatically reaches every variation.

Check:

• Offer ID
• Variation attributes
• Shipping class
• Shipping label
• Weight
• Dimensions
• Handling time
• Landing-page selection
• Checkout method

The customer should see the applicable delivery restriction for the selected variation.

Multiple warehouses

Multiple ship-from locations can create different delivery speeds.

Review:

• Inventory held at each warehouse
• Carrier availability
• Warehouse cut-offs
• Warehouse working days
• Handling performance
• Geographic coverage
• Order-routing logic
• Mirrored or non-mirrored inventory

Google’s carrier-calculated delivery feature can use warehouse locations in supported circumstances.

Do not list multiple warehouses as interchangeable when an order may be routed to a location without stock.

A faster calculated estimate is inaccurate if the nearest warehouse cannot fulfil the order.

Dropshipped and supplier-fulfilled products

Supplier-fulfilled products often require separate timing.

The WooCommerce store may receive the order immediately, but the supplier controls:

• Stock confirmation
• Picking
• Packaging
• Dispatch
• Carrier choice
• Tracking
• Export documentation

Measure the complete supplier handling time.

Do not enter the store’s administrative processing time as the product’s total handling time.

Use a separate label or product-level timing when suppliers have different service commitments.

Backorders and pre-orders

A standard shipping policy may not describe a backordered product accurately.

A product expected to return to stock in three weeks does not have a three-day handling time merely because delivery takes three days after dispatch.

Make availability and dispatch expectations clear on the product page and at checkout.

Do not use ordinary handling-time fields to conceal an unknown restock date.

Review whether the product should be submitted as available under Google’s current availability requirements.

Local pickup and local delivery

Local pickup is not the same as online parcel shipping.

Local delivery may also use different Merchant Center features, destination coverage and fulfilment rules.

If the store offers:

• In-store pickup
• Curbside pickup
• Same-day local delivery
• Merchant-operated courier delivery

Review the specific Google programme requirements before applying standard national shipping settings.

Do not represent pickup as free home delivery.

Merchant API shipping settings

Google Merchant API provides account shipping-setting resources that can retrieve and replace supported shipping configuration.

The current Merchant API shipping-settings reference includes supported structures for:

• Shipping services
• Delivery countries
• Rate groups
• Delivery time
• Cut-off time
• Handling days
• Transit days
• Business-day configuration
• Transit tables
• Warehouse-based delivery
• Shipping labels
• Minimum order values
• Warehouses

An important technical distinction is that the shippingSettings:insert operation replaces the shipping settings resource.

Google’s shipping-settings management guide warns that existing fields omitted from the replacement request can be deleted.

An integration should therefore:

• Retrieve the current settings.
• Preserve required existing services and fields.
• Apply controlled changes.
• Use the current resource version.
• Handle the etag where applicable.
• Avoid concurrent overwrites.
• Validate the complete replacement.
• Retrieve the result again.
• Compare it with the intended configuration.
• Log the operation without exposing credentials.

A successful API response does not prove that WooCommerce checkout matches the policy.

How PW Merchant API fits into shipping management

PW Merchant API is designed to support controlled product communication between WooCommerce and Google Merchant Center.

Depending on the installed version and supported field mappings, it can help users:

• Read supported WooCommerce product information.
• Prepare supported Merchant product attributes.
• Submit new products.
• Update existing products.
• Manage simple and variable product operations.
• Run controlled scheduled processes.
• Review successful and unsuccessful operations.
• Identify products that need attention.
• Maintain more structured WooCommerce product management.

As a WooCommerce Google Merchant Center plugin, PW Merchant API may submit supported product-level shipping information when the relevant field is implemented and configured.

However, it should not be assumed to manage every account-level shipping policy automatically.

PW Merchant API cannot:

• Determine the warehouse’s real cut-off time.
• Measure carrier performance without appropriate operational data.
• Decide which countries the business can legally serve.
• Create a carrier contract.
• Guarantee a delivery date.
• Prevent weather or customs delays.
• Correct an inaccurate WooCommerce shipping extension automatically.
• Decide the correct shipping cost without business rules.
• Guarantee Google’s acceptance of shipping information.
• Guarantee that shipping annotations will appear.
• Guarantee impressions, clicks, rankings or sales.
• Replace the store’s customer-service obligations.
• Override another product source without an applicable operation.

WooCommerce remains the commercial source, PW Merchant API supports applicable product communication, and Google independently processes and evaluates the submitted information.

Competing product sources

Shipping data can be overwritten by another source.

Review:

• PW Merchant API
• Another Merchant API integration
• XML data sources
• CSV uploads
• Google Sheets
• Automated website data
• WooCommerce Google extensions
• ERP systems
• Supplier systems
• Marketplace connectors
• Manual Merchant Center edits
• Search Console shipping policies
• Structured data

Identify which source controls:

• Shipping cost
• Shipping label
• Handling time
• Transit time
• Ships-from country
• Weight
• Dimensions

A manual correction may disappear during the next product operation.

Shipping structured data

Google supports shipping information in structured data.

Current Google Search documentation describes:

• Organisation-level ShippingService structured data for standard business shipping policies
• Product-offer-level OfferShippingDetails for applicable product shipping information

Google’s merchant shipping policy structured-data documentation explains that ShippingService can describe shipping costs and delivery times based on factors such as destination, weight and dimensions.

Structured data must match visible customer information.

Review markup generated by:

• WooCommerce
• The active theme
• SEO plugins
• Schema plugins
• Custom PHP
• JavaScript
• Tag Manager
• Cached page fragments

Avoid duplicate markup where one source says two-day delivery and another says five-to-seven-day delivery.

Structured data complements WooCommerce checkout and Merchant Center. It does not replace either one.

How to diagnose incorrect delivery estimates

1. Recalculate the timeline manually

Record:

• Order day and time
• Cut-off time
• Time zone
• Handling days
• Handling working days
• Dispatch date
• Transit days
• Carrier working days
• Holiday adjustments
• Estimated arrival

Determine which stage creates the difference.

2. Test before and after the cut-off

Place or simulate the same order:

• Shortly before the cut-off
• Shortly after the cut-off

The later order may begin processing on the next business day.

3. Review account-level policies

Check whether several shipping services apply to the product.

Google may select among applicable services according to its rules. Duplicate or overlapping policies can produce unexpected results.

4. Review product-level overrides

Inspect:

• shipping
• shipping_label
• min_handling_time
• max_handling_time
• min_transit_time
• max_transit_time
• Business-day attributes
• Cut-off attributes

An old override may replace the corrected account setting.

5. Review the customer destination

Confirm the postcode, region and country used in the estimate.

A nearby location and a remote location may receive different results.

6. Review the selected carrier

Confirm that the Merchant Center carrier service matches the service purchased operationally.

Do not configure an express service if orders are normally sent through the carrier’s economy service.

7. Review working days and holidays

A weekend or holiday can extend the displayed arrival date.

Check both warehouse and carrier calendars.

8. Review WooCommerce checkout

Confirm the exact method and price offered to the same destination and product.

9. Review other sources

Check whether another data source or integration reintroduced old shipping values.

10. Allow Google to process corrections

After updating accurate settings, allow the relevant systems time to retrieve and process the information. Do not repeatedly change correct values without identifying a remaining inconsistency.

Common setup mistakes

Using calendar days instead of business days

A three-business-day transit period may cross a weekend and take longer than three calendar days.

Confusing handling time with transit time

Warehouse preparation and carrier transportation must be measured separately.

Setting an unrealistic cut-off

The carrier collection time is not automatically the store’s order cut-off.

Ignoring the cut-off time zone

An otherwise correct time can produce wrong estimates when interpreted in another zone.

Using zero-day handling for every product

Made-to-order, personalised and supplier-fulfilled products may need longer preparation.

Using one delivery range for every destination

Remote and international destinations may require separate policies.

Ignoring WooCommerce zone order

A broad zone can override a more specific region if ordered incorrectly.

Leaving unintended Rest of the world shipping active

Customers may be able to order from countries not configured intentionally.

Applying product-level overrides unnecessarily

Product-level shipping can override account settings and increase maintenance complexity.

Using a shipping label without a matching policy

The product may not receive the intended service.

Deleting a policy while products still use its label

Affected items may lose their correct shipping conditions.

Submitting an incorrect carrier service

Transit time may be calculated for a service the store does not purchase.

Forgetting free-shipping thresholds

The Merchant Center price can differ from WooCommerce checkout for low-value orders.

Ignoring mixed carts

A cart containing products with different shipping classes may use a different method or price.

Assuming structured data controls checkout

Schema does not change WooCommerce’s actual shipping calculation.

Assuming an API response proves accuracy

Technical acceptance does not prove that customer-facing information matches.

Frequently asked questions

Where are shipping settings in Google Merchant Center?

Select Shipping and returns from the left navigation, open Shipping policies and choose Add shipping policy. Some account layouts place this area under Products & store.

What is handling time?

Handling time is the number of business days between receiving an order and handing it to the carrier.

What is transit time?

Transit time is the number of business days between carrier collection and customer delivery.

What is order cut-off time?

It is the latest time an order can be received and begin processing on the same operational day.

Is delivery time handling time plus transit time?

The general estimate uses handling and transit time, adjusted for cut-off, business days, destination and supported holidays.

What does zero handling time mean?

It means the product can be dispatched on the same business day when the order is placed before the applicable cut-off.

Should I enter calendar days or business days?

Google’s handling and transit settings generally use business days. Configure the applicable operating schedule accurately.

Can I use one shipping policy for every product?

Yes, when all eligible products genuinely share the same shipping conditions. Use labels or product-level exceptions when they do not.

What is a shipping label?

It is a technical product value used to group products for specific Merchant Center shipping services, costs or speeds.

Can shipping labels be shown to customers?

They are intended as technical grouping values and are not normally displayed as customer-facing text.

Do WooCommerce shipping classes automatically become Google shipping labels?

Not automatically. An integration or controlled mapping must submit the corresponding value.

Can product shipping data override account settings?

Yes. Product-level shipping information can override relevant account settings for the matching product and location.

Should I use account-level or product-level shipping?

Use account-level policies for shared conditions. Use product-level data only for genuine exceptions that cannot be represented accurately at account level.

Why is Google showing a later arrival date?

The order may have missed the cut-off, crossed a weekend or holiday, matched a slower zone, or received a product-level override.

Why is Google showing an earlier arrival date?

The cut-off, handling time, transit time, carrier service, working days or warehouse location may be too optimistic.

Can Google calculate carrier transit time?

Google provides carrier-calculated shipping-speed options in supported countries and circumstances. The merchant still needs accurate handling and warehouse information.

Can PW Merchant API guarantee correct delivery dates?

No. It can support applicable product-data communication, but the business must provide accurate operational and carrier information.

Does accurate shipping guarantee a fast-delivery annotation?

No. Google independently determines eligibility and presentation.

Do I need a shipping page on my WooCommerce store?

A clear public page is strongly recommended so customers can understand destinations, costs, processing and expected delivery conditions.

Should shipping information match checkout?

Yes. Merchant Center, product data, structured data and WooCommerce checkout should describe compatible costs and delivery conditions.

How should I handle made-to-order products?

Use an accurate longer handling time and, where appropriate, a dedicated shipping label or product-level exception.

How should I handle multiple warehouses?

Document each warehouse’s stock, cut-off, handling days and carrier services. Use supported warehouse-based calculation only when the routing and inventory assumptions are accurate.

Can I configure different delivery times by region?

Yes, where supported. Use destination zones, regional settings, shipping labels or appropriate product-level data.

What happens if Merchant API shipping settings omit an existing service?

Because the insert operation replaces the shipping-settings resource, omitted existing fields or services may be removed. Retrieve and preserve the complete configuration before updating it.

Final checklist

Before considering the setup complete, confirm that:

• Every WooCommerce shipping destination was reviewed.
• Every excluded destination was reviewed.
• WooCommerce shipping zones are ordered correctly.
• Specific zones appear before broad zones.
• The Rest of the world zone is intentional.
• Every zone contains the correct methods.
• Disabled methods were removed or documented.
• Flat rates match the real checkout.
• Free-shipping thresholds match.
• Carrier rates were tested.
• Handling charges were included where required.
• Remote-area fees were reviewed.
• Taxes on shipping were reviewed.
• The store’s operational cut-off was measured.
• The correct cut-off time zone was selected.
• Payment review time was considered.
• Warehouse preparation time was measured.
• Carrier collection time was considered.
• Minimum handling time is accurate.
• Maximum handling time is realistic.
• Minimum transit time is accurate.
• Maximum transit time covers the normal commitment.
• Handling time and transit time are not confused.
• Handling business days are correct.
• Carrier transit days are correct.
• Weekend processing was verified.
• Weekend delivery was verified.
• Public holidays were reviewed.
• Seasonal closures were reviewed.
• Holiday order deadlines were published.
• Countries in Merchant Center match WooCommerce.
• Product eligibility is correct.
• Standard products use the default policy.
• Exceptional products use appropriate rules.
• Oversized products were reviewed.
• Perishable products were reviewed.
• Made-to-order products were reviewed.
• Personalised products were reviewed.
• Supplier-fulfilled products were reviewed.
• Backorders and pre-orders were reviewed.
• Product shipping classes were reviewed.
• Variable products were reviewed.
• Every separately submitted variation was checked.
• Mixed-cart behaviour was tested.
• Shipping labels are stable.
• Shipping labels match the intended policies.
• Obsolete shipping labels were removed.
• Deleted policies are no longer referenced.
• Warehouse locations are accurate.
• Multiple-warehouse inventory assumptions are valid.
• Carrier services match the real services purchased.
• Manual transit ranges are supported by real performance.
• Regional destination differences were configured.
• The Merchant Center shipping cost matches checkout.
• The selected currency is correct.
• Minimum-order values match.
• Free-shipping thresholds match.
• Account-level settings were reviewed.
• Product-level overrides were reviewed.
• Product-level price overrides include required timing information.
• Handling-time attributes were reviewed.
• Transit-time attributes were reviewed.
• Cut-off attributes were reviewed.
• Business-day attributes were reviewed.
• ships_from_country was reviewed where applicable.
• Product weights are accurate.
• Product dimensions are accurate.
• Another source does not overwrite the settings.
• Merchant API sources were reviewed.
• XML sources were reviewed.
• CSV and Google Sheets sources were reviewed.
• ERP sources were reviewed.
• Supplier sources were reviewed.
• Manual Merchant Center changes were reviewed.
• Search Console policies were reviewed.
• The authoritative source was identified.
• Merchant API replacements preserve existing settings.
• Current settings are retrieved before an API update.
• Concurrency and etag handling were considered.
• API results are retrieved and compared after an update.
• Credentials and tokens are excluded from logs.
• The shipping-information page is public.
• The page uses HTTPS.
• The page works while logged out.
• The page works on mobile.
• The footer contains an appropriate link.
• Product-page delivery claims were reviewed.
• Cart delivery claims were reviewed.
• Checkout delivery claims were reviewed.
• Promotional banners were reviewed.
• Customer-service instructions match.
• Structured shipping data was inspected.
• Organisation-level shipping markup was reviewed.
• Product-level shipping markup was reviewed.
• Duplicate structured data was removed.
• Structured data matches visible information.
• Representative domestic addresses were tested.
• Remote-area addresses were tested.
• International addresses were tested.
• Excluded destinations were tested.
• Low-value orders were tested.
• Free-shipping orders were tested.
• Heavy products were tested.
• Oversized products were tested.
• Variable products were tested.
• Orders before the cut-off were tested.
• Orders after the cut-off were tested.
• The saved Merchant Center policy was reopened.
• Diagnostics and product issues were reviewed.
• Google was allowed to process the correction.
• Customer-support staff received the current delivery rules.
• Warehouse staff received the current cut-off rules.
• Carrier service levels are monitored.
• Future shipping changes will be updated across every source.

Google Merchant Center shipping configuration is not merely a cost field.

It represents the complete path from a WooCommerce order being placed to the product reaching the customer.

The most reliable configuration starts with the real store operation. It verifies destinations, WooCommerce zones, shipping methods, warehouse processing, carrier transit, working days, cut-off times and product exceptions before reproducing those conditions in Merchant Center.

Account-level policies should cover products sharing the same conditions. Shipping labels and product-level data should be reserved for genuine exceptions and maintained carefully so they do not override correct default settings unexpectedly.

WooCommerce remains the customer-facing commercial source, PW Merchant API supports applicable product communication, and Google Merchant Center independently processes the submitted information.

When the website, checkout, Merchant Center policies, product data, Merchant API operations and structured data all describe compatible shipping conditions, customers can receive clearer costs and more realistic delivery expectations.