How to set up return policies in Google Merchant Center for WooCommerce

How to set up return policies in Google Merchant Center for WooCommerce

A return policy should tell customers exactly what happens when a WooCommerce order needs to be returned, exchanged or refunded.

Google Merchant Center also needs this information so that it can understand the conditions attached to the products promoted through Shopping ads, free listings and other supported Google surfaces.

Problems begin when the return policy displayed on a WooCommerce store does not match the policy configured in Merchant Center.

A website may advertise free 30-day returns while Merchant Center states that customers must pay a return fee. The website may accept opened products while the Merchant Center policy permits only unopened items. A store may sell products in several countries while its return policy covers only one of them.

Other stores publish a generic template that does not explain:

• How long customers have to request a return
• Whether the return window begins after purchase, dispatch or delivery
• Which product conditions are accepted
• Who pays the return shipping cost
• Whether a restocking fee applies
• How customers initiate a return
• Whether exchanges are available
• How long refund processing takes
• Which products are excluded
• Which countries the policy covers

These omissions can create customer confusion, prevent Google from verifying the policy, contribute to website-transparency problems or result in a rejected return policy.

The objective is not to create the most generous policy possible merely for Google.

The objective is to create a lawful, commercially realistic and customer-accessible policy, publish it clearly on the WooCommerce store and configure the same conditions accurately in Google Merchant Center.

The short answer

To set up a Google Merchant Center return policy for WooCommerce:

• Decide the store’s real return, exchange and refund rules.
• Check the consumer laws that apply to the business and target countries.
• Do not copy another store’s policy without reviewing it.
• Edit or create a dedicated Refund and Returns Policy page in WordPress.
• Make the page publicly accessible without requiring an account or personal information.
• Link to the policy from the website footer.
• Explain the return window and when it begins.
• List accepted and excluded product conditions.
• State whether defective and non-defective products can be returned.
• Explain how customers initiate a return.
• State the available return methods.
• Explain who pays return shipping.
• Disclose every restocking or handling fee.
• Explain whether exchanges are accepted.
• State the expected refund-processing time.
• Add country-specific or product-specific exceptions where required.
• Confirm that checkout, order emails and customer-support instructions do not contradict the policy.
• Open Google Merchant Center.
• Go to Products & store, then Shipping and returns.
• Open the Return policies tab.
• Select Add return policy.
• Enter the public WooCommerce return-policy URL.
• Select the applicable countries.
• Configure returns, exchanges, product condition, return window, methods and fees.
• Review every value against the website.
• Save the policy and monitor its verification status.
• Use return_policy_label only for products that follow a non-default policy.
• Add structured data only when it accurately represents the visible policy.
• Update the website, Merchant Center and product data together whenever the policy changes.

Do not invent more favourable return terms solely to make the product listings look better.

A “free returns” annotation is useful only when the business genuinely provides free returns under the stated conditions.

Why return policies matter in Google Merchant Center

A return policy is part of the customer’s complete purchasing experience.

The customer journey does not end when a product is added to a WooCommerce cart. Customers need to understand what happens if:

• The item arrives damaged.
• The wrong product is delivered.
• The product does not fit.
• The customer changes their mind.
• The product differs from its description.
• A variation was ordered incorrectly.
• The item is no longer wanted.
• An exchange is required.
• A refund is approved.
• The returned parcel is lost.
• The request is submitted outside the allowed period.

Google may use return information from Merchant Center and the website in ads, product listings, Gmail and other supported experiences. Google therefore expects the policy to be clear, accessible and consistent.

Google’s current return-policy requirements say that the policy should be available without login, registration or the submission of personal information. Google also expects the policy in Merchant Center to remain consistent with information displayed elsewhere on the website, including the footer, return page and promotional banners.

A hidden or incomplete policy is not corrected merely by adding information to Merchant Center.

Google treats the website’s customer-facing return and refund policy separately from the Merchant Center configuration. Both areas need attention.

A return, refund and exchange are not the same action

These terms are often combined, but they describe different parts of the process.

A return is the physical or documented process of sending or bringing an item back.

A refund is the repayment issued after the store accepts or otherwise resolves the request.

An exchange replaces the original item with another product, size, colour or unit.

A WooCommerce store may:

• Accept returns and issue refunds.
• Accept returns and offer exchanges.
• Offer both refunds and exchanges.
• Refund a damaged item without requiring its physical return.
• Accept returns for defective products but apply different rules to buyer’s-remorse returns.
• Reject returns for certain lawful product categories.
• Offer store credit in selected situations.
• Permit cancellations before dispatch under separate rules.

The website should distinguish these outcomes.

Do not write “returns accepted” if customers can receive only store credit and no monetary refund. Do not advertise “free returns” if the customer must pay the carrier. Do not state “full refund” if a percentage or fixed restocking fee will be deducted.

Start with the real WooCommerce policy

Merchant Center should describe an existing store policy. It should not become the place where the business invents its rules.

Before opening Merchant Center, determine:

• Where the business operates
• Where products are sold
• Which consumer laws apply
• Which product categories are offered
• Which items can and cannot be returned
• How many days customers receive
• When the return period begins
• How returns are requested
• How returned products are transported
• Who pays the return cost
• Which item conditions are accepted
• Whether exchanges are available
• Whether restocking fees apply
• How and when refunds are issued
• Whether seasonal extensions are offered
• Whether different countries require different policies

Legal requirements vary by jurisdiction, product category and sales method. Google’s form does not replace applicable consumer law. Obtain qualified legal advice when the business is uncertain about its obligations.

Do not shorten a legally required return period because a Merchant Center field appears to allow a shorter value. Do not prohibit a return that customers are legally entitled to make.

Create the return policy page in WooCommerce

WooCommerce normally creates a draft page titled “Refund and Returns Policy” during installation.

According to the official WooCommerce refund-policy guidance, the page is a starting template rather than a universal policy. It must be edited to match the actual store.

To find it:

• Open WordPress administration.
• Go to Pages.
• Select All Pages.
• Search for Refund and Returns Policy.
• Open the page.
• Replace sample statements with the store’s real conditions.
• Review the page for legal and operational accuracy.
• Publish or update it.

If the draft was deleted, create a new page with a clear title such as:

• Refund and Returns Policy
• Returns and Refunds
• Returns, Exchanges and Refunds

Avoid vague titles such as “Information” or “Customer help.” Google and customers should be able to recognise the page immediately.

Make the policy publicly accessible

The policy URL entered in Merchant Center should:

• Use HTTPS.
• Load without a customer account.
• Work in a logged-out browser.
• Work on desktop and mobile.
• Return a successful page response.
• Avoid an endless redirect.
• Avoid a maintenance or coming-soon page.
• Avoid a blocked country redirect.
• Display the policy in the appropriate language.
• Remain indexable and accessible to Google.
• Avoid requiring cookie acceptance before the policy can be read.
• Avoid placing the essential terms only inside a downloadable file.
• Avoid hiding the policy behind a contact form.

Add a visible link to the website footer so that the page can be reached from every important shopping page.

It can also be linked from:

• Product pages
• The cart
• Checkout
• Order-confirmation emails
• The customer account area
• Frequently asked questions
• Shipping information
• Customer-service pages

Do not provide different return conditions in each location.

If the footer says “30-day returns” but the full policy says “14 days,” the inconsistency must be corrected.

What the WooCommerce return policy should explain

Applicable countries

State which countries or regions the policy covers.

If domestic and international orders use different rules, explain the difference clearly.

For example:

• Domestic orders can be returned by mail within 30 days after delivery.
• International orders can be returned within 14 days after delivery.
• Customers are responsible for international return shipping unless the item is defective.
• Certain products cannot be returned across borders because of shipping restrictions.

Merchant Center policies are associated with countries of sale. A policy created for one country should not be assumed to cover every other target country automatically.

The return window

State the exact number of days available and the event that begins the period.

Clear:

Eligible products may be returned within 30 calendar days after delivery.

Unclear:

Products may be returned within a reasonable period.

Potentially inconsistent:

Products may be returned within 30 days of purchase.

If delivery takes ten days, “30 days after purchase” and “30 days after delivery” are materially different.

Google’s Merchant API policy model describes a numbered return window as days after delivery. Merchant Center’s configuration should match the public explanation used by the store.

If the policy provides lifetime returns, say what lifetime means and which products qualify.

Accepted item conditions

Explain the required condition of returned products.

Possible requirements include:

• Unused
• Unworn
• Unwashed
• Unopened
• In original packaging
• With tags attached
• With all accessories
• With serial numbers intact
• Without customer damage
• In resalable condition

Avoid using “new condition” without explaining what the store considers new.

If slightly used products can be returned, describe the acceptable level of use. If opened packaging is allowed, do not configure Merchant Center as accepting only unopened items.

Defective and non-defective returns

Google’s setup flow currently includes options for:

• Returns for defective and non-defective products
• Returns for defective products only
• No returns

Choose the option that describes the real business policy.

A defective return can involve:

• Manufacturing defects
• Damage present on delivery
• Incorrect products
• Missing components
• Products that do not function as described

A non-defective return can include:

• Buyer’s remorse
• Incorrect size selected by the customer
• Colour preference
• Duplicate order
• Product no longer wanted

Google advises merchants to provide policies that apply beyond defective-product scenarios. Regardless of the selected option, the website must explain the actual rules without implying broader rights than the store provides.

How customers request a return

Describe the first action the customer must take.

For example:

• Submit a form.
• Contact the support email address.
• Open a request from My Account.
• Call customer service.
• Obtain a return merchandise authorisation number.
• Download a return label.
• Visit a physical store.

Include the information required from the customer, such as:

• Order number
• Customer name
• Product
• Quantity
• Return reason
• Photographs for damaged products
• Requested resolution
• Contact details

Do not require customers to discover the process only after contacting the store.

Return methods

Merchant Center currently documents the following return methods:

• In store
• At a drop-off location
• By mail

Select only methods genuinely available to customers.

If by-mail returns are accepted, Merchant Center may ask how customers receive the label:

• Download and print
• Label included in the box
• Customer responsibility

Match this selection to the website.

Do not choose “label included in the box” if no label is actually sent with the order. Do not choose “download and print” if customers must purchase postage themselves without receiving a label.

Return shipping fees

Explain who pays for the return and under which circumstances.

A policy may distinguish between:

• Merchant error
• Defective product
• Product damaged in transit
• Wrong item sent
• Customer changed their mind
• Customer ordered the wrong size
• International return
• Oversized product
• In-store return

For example:

We pay the return shipping cost when the product is defective, damaged on arrival or incorrectly supplied. For buyer’s-remorse returns, the customer is responsible for return shipping.

This is more accurate than “return shipping may apply.”

If a fixed return fee will be deducted from the refund, state the amount and currency. If the amount depends on the carrier or product, explain how it is calculated before the customer completes the return.

Restocking fees

Merchant Center currently permits policies to describe:

• No restocking cost
• A fixed cost
• A percentage of the product price

A restocking fee is separate from return shipping.

If both apply, disclose both.

For example:

• Return shipping: 8 EUR
• Restocking fee: 10% of the product price

Do not configure “No cost” if a handling, inspection, repackaging or administrative fee is deducted under another name.

A fee should also comply with applicable law.

Exchanges

State whether exchanges are available.

If they are, explain:

• Which products qualify
• Whether size and colour exchanges are permitted
• Whether an exchange depends on stock
• Who pays the additional shipping
• Whether price differences are charged or refunded
• Whether international exchanges are supported
• What happens when the replacement is unavailable

If the store handles exchanges by refunding the first order and creating a new order, explain that process clearly.

Refund method

Explain how approved refunds are issued.

Possible outcomes include:

• Original payment method
• Bank transfer
• Store credit
• Gift card
• Exchange
• Partial refund
• Full refund

Do not promise a refund to the original payment method if the operational process provides only store credit.

WooCommerce can record refunds and, depending on the payment gateway, may send the refund through the gateway. The technical ability to press a refund button does not define the customer’s legal or contractual rights.

Refund-processing time

Merchant Center asks how long it takes for the customer to receive a refund.

The website should distinguish between:

• Time required for the store to inspect and approve the return
• Time required for the store to initiate the refund
• Additional processing time controlled by the payment provider or bank

For example:

Approved refunds are initiated within five business days after the returned product is received and inspected. The customer’s bank or payment provider may require additional time to display the funds.

Do not claim that every refund is received immediately if the payment method requires additional processing.

Excluded products

If certain products follow different rules, identify them clearly.

Examples may include:

• Personalised products
• Engraved products
• Made-to-order products
• Hygiene-sensitive items
• Perishable products
• Opened software
• Downloadable products
• Gift cards
• Clearance products
• Final-sale products
• Safety equipment
• Products subject to legal or health restrictions

An exclusion should be lawful and visible before purchase.

Do not place a small “final sale” statement only in a post-purchase email. If a product cannot be returned, the restriction should be clear on the product page and in the main return policy.

Review the complete WooCommerce buying experience

Before configuring Merchant Center, test the policy as a customer.

Check:

• Homepage
• Product page
• Variation selections
• Cart
• Checkout
• Terms acceptance
• Footer
• Order email
• My Account
• Return-request form
• Support page
• Promotional banners
• Mobile navigation

Search the website for phrases such as:

• Free returns
• Money-back guarantee
• No returns
• Final sale
• 14-day returns
• 30-day returns
• Easy exchanges
• Lifetime guarantee
• Full refund
• Store credit
• Customer pays shipping

Every statement should be compatible with the main policy.

A banner promising “Free 30-day returns on everything” can create a serious contradiction if customised products are excluded or customers pay return shipping.

How to add the policy in Google Merchant Center

Google’s current interface uses the following path:

• Sign in to Merchant Center.
• Expand Products & store in the left navigation.
• Select Shipping and returns.
• Open the Return policies tab.
• Select Add return policy.
• Complete the setup flow.
• Review the information.
• Save the policy.

Interface wording can vary slightly by language, account configuration and future Merchant Center updates.

Step 1: Enter the return policy URL

Use the canonical public URL of the WooCommerce policy page.

For example:

https://www.example.com/refund-and-returns-policy/

Test the URL in a private browser window.

Do not use:

• A WordPress preview URL
• A wp-admin editing URL
• A staging URL
• A local-development address
• A URL requiring authentication
• An expired redirect
• A policy hosted on an unrelated store
• A generic homepage when a dedicated policy exists
• A URL blocked from Google

Google’s Merchant API reference also requires a valid returnPolicyUri and notes that Google can use it to perform a sanity check against the submitted policy.

Step 2: Select the countries

Choose the countries where the policy applies.

A standard policy may cover one or multiple countries when its conditions are genuinely identical.

Do not add multiple countries merely to reduce setup work if they have different:

• Return windows
• Fees
• Addresses
• Methods
• Consumer rights
• Cross-border restrictions
• Refund-processing arrangements

Google allows additional countries to be added later when they are not already included in another applicable policy.

Step 3: Choose whether returns are accepted

Select the accurate option:

• Defective and non-defective products
• Defective products only
• No returns

A no-returns policy does not remove the need for a public return and refund page. Google’s missing return-policy guidance says that stores which do not accept returns or refunds should state that clearly.

The page should still explain:

• Whether legally required remedies remain available
• How defective or incorrectly supplied goods are handled
• Whether cancellations are possible
• Whether exchanges or store credit exist
• How customers contact the business

Step 4: Configure exchanges

Choose whether the store accepts exchanges.

This selection should agree with:

• The return page
• Product pages
• Customer-support responses
• Return forms
• Order emails

Do not select exchanges merely because a customer can place a new order after receiving a refund. An exchange should represent an actual supported business process.

Step 5: Select accepted product conditions

Select whether returns are accepted for:

• New products only
• New and slightly used products

Use the choice that most closely represents the visible policy.

If some categories accept opened products while others do not, consider an exception policy instead of applying one inaccurate condition to the complete catalogue.

Step 6: Enter the return window

Enter the actual period customers receive after delivery.

Review:

• Calendar days or business days
• Delivery date
• Request date
• Postmark date
• Date received by the warehouse
• Lifetime returns
• Category exceptions

Merchant Center describes the return window using a number of days or lifetime. The website should remove ambiguity about how that period is calculated.

Step 7: Add seasonal extensions

A seasonal extension can provide a longer window for orders placed during a defined period.

For example, purchases made between 1 November and 24 December may be returnable until 31 January.

Before adding an extension:

• Confirm the qualifying order dates.
• Confirm the final return date.
• Confirm the countries covered.
• Confirm whether all products qualify.
• Publish the extension on the website.
• Train customer-support staff.
• Update banners and campaign pages.
• Remove or revise expired promotional statements.

Do not add a Merchant Center holiday extension that the WooCommerce store does not honour.

Step 8: Select return methods

Choose all supported methods:

• In store
• Drop-off location
• By mail

When selecting by mail, configure the return-label process accurately.

The website should provide compatible instructions, including any required return address, authorisation process or carrier restrictions.

Step 9: Select the currency

Choose the currency used for applicable fixed return or restocking fees.

The amount and currency should match the website’s customer-facing information.

If the store operates in EUR but the Merchant Center policy states a fixed fee in USD, customers and Google may receive inconsistent information.

Currency conversion does not correct an incorrectly selected source currency.

Step 10: Configure the restocking fee

Select:

• No cost
• Fixed cost
• Percentage of product price

Use “No cost” only when the business does not deduct a restocking, handling or equivalent fee.

If the fee applies only to selected products, configure an appropriate exception rather than applying it to all products.

Step 11: Enter refund-processing time

Enter the period the store actually requires to process an approved refund.

Make sure the same period appears on the website.

If the website says “within three business days” while Merchant Center says ten days, select one accurate commitment and align both locations.

Review before saving

Before saving, compare every Merchant Center field with the website in a side-by-side audit.

Check:

• URL
• Countries
• Return acceptance
• Defective products
• Non-defective products
• Exchanges
• Accepted condition
• Return window
• Seasonal extension
• Return method
• Return label
• Return shipping cost
• Currency
• Restocking fee
• Refund-processing period

Do not rely entirely on suggestions automatically extracted from the website. Google allows merchants to accept, partly accept or disregard suggested values. The business remains responsible for checking their accuracy.

Default and exception policies

A default policy applies to products that do not have a matching non-default return-policy label.

An exception policy is used when a specific product or group follows different conditions.

Examples include:

• Standard products: 30-day returns
• Premium electronics: 14-day returns
• Personalised products: no buyer’s-remorse returns
• Clearance products: shorter return window
• Oversized furniture: customer-arranged return transport
• Domestic products: free returns
• International products: customer-paid return shipping

Do not create exceptions without a real operational reason. Too many policies can become difficult to maintain.

How to create an exception policy

In Merchant Center:

• Open Shipping and returns.
• Open Return policies.
• Find the applicable standard policy.
• Select the plus icon in the Actions column.
• Enter an exception label.
• Configure the conditions that differ.
• Review the complete exception.
• Save it.

Use a clear stable label such as:

• personalised_items
• premium_electronics
• final_sale
• oversized_products

Do not use a temporary value that will be forgotten or changed during the next product operation.

How return policy labels work

Google’s official return_policy_label attribute assigns a non-default policy to a product or product group.

If the default policy applies, the attribute can generally be:

• Omitted
• Left blank
• Set to default

If an exception applies, submit the exact label created for that exception.

For example:

Default clothing product:

• Product ID: SHIRT-100
• Return policy label: blank

Personalised product:

• Product ID: MUG-CUSTOM-20
• Return policy label: personalised_items

The submitted value must match the Merchant Center exception label.

An invalid label can occur when:

• The product submits a label that does not exist.
• The label was deleted.
• The label was renamed in one source but not another.
• Capitalisation differs.
• Leading or trailing spaces are present.
• An import changes underscores or hyphens.
• A multilingual process translates the label.
• Two product sources submit different labels.
• A default product receives an exception label accidentally.

Treat the label as a technical identifier, not customer-facing marketing text.

WooCommerce product mapping for exception policies

Create a reliable rule for identifying products that use an exception.

Possible sources include:

• Product category
• Product tag
• Product attribute
• Custom product field
• Product type
• Shipping class
• A dedicated Merchant field
• A controlled catalogue rule

For example:

• Products tagged personalised → personalised_items
• Category Premium electronics → premium_electronics
• Shipping class Oversized → oversized_products

Test the rule carefully.

A category-wide mapping error could accidentally assign a no-returns policy to hundreds of standard products.

For each mapped product, confirm:

• The exception is disclosed on the product page.
• The main policy explains the exception.
• The submitted label exists.
• The country matches.
• The correct offer ID receives the value.
• Every relevant variation receives the correct label.
• Products removed from the exception lose the old label.
• Another product source does not overwrite the value.

Return policies and variable products

WooCommerce variations may follow the same return policy or different policies.

Most colour and size variations of one product usually share the same conditions. However, exceptions can occur.

For example:

• Standard jacket variations: 30-day returns
• A customised embroidered variation: different policy
• Standard furniture fabric: normal return method
• Made-to-order fabric: exception policy

Do not assume that assigning a label to the WooCommerce parent automatically assigns it to every submitted variation. Verify the actual product data sent for each offer.

If individual variations are submitted separately, check:

• Product ID
• Parent relationship
• Return-policy label
• Landing page
• Selected variation
• Visible exception notice

A customer should see the restriction before purchasing the exact variation.

Merchant API return policies

Google’s current Merchant API online return-policy resource contains fields for areas such as:

• Countries
• Default or labelled policies
• Policy type
• Return days
• Seasonal overrides
• Restocking fees
• Return methods
• Accepted item conditions
• Return shipping fees
• Policy URL
• Defective-only handling
• Refund-processing days
• Exchanges
• Return-label source

The Merchant API also provides operations for creating, retrieving, listing and deleting supported online return-policy resources.

An API integration should not invent policy values from incomplete WooCommerce data.

It should preserve:

• The business’s selected countries
• The exact public policy URL
• Stable exception labels
• The real return period
• The correct accepted conditions
• The correct fees
• The actual return methods
• The actual exchange status
• The true refund-processing time

A successful API response does not prove that Google verified the policy or that the website matches it. Google still evaluates the submitted information.

Google’s current API guidance says a newly created return policy may take up to ten business days to be reviewed and available.

How PW Merchant API fits into return-policy management

PW Merchant API is designed to support a controlled relationship between WooCommerce and Google Merchant Center.

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

• Read supported WooCommerce product information.
• Prepare supported Google product attributes.
• Submit new products.
• Update existing products.
• Organise scheduled product operations.
• Review operation results.
• Identify products requiring attention.
• Maintain a controlled Merchant API workflow.

As a WooCommerce Google Merchant Center plugin, PW Merchant API can support applicable return-policy label data when that function is available and configured.

However, it cannot determine the store’s legal policy automatically.

PW Merchant API cannot:

• Decide the lawful return period.
• Provide legal advice.
• Invent return conditions.
• Decide whether a personalised product may be excluded.
• Promise free returns on behalf of the business.
• Create a physical return process.
• Control the payment gateway’s refund time.
• Make customer-support staff honour a policy.
• Correct conflicting text across unrelated website pages automatically.
• Override another Merchant product source.
• Guarantee Google’s verification.
• Guarantee product approval.
• Guarantee Shopping visibility or sales.

WooCommerce and the store’s published policy remain the customer-facing source. PW Merchant API manages supported communication, and Google independently verifies and processes the information.

For a broader website-policy audit, see Store and Policy Pages.

Return-policy structured data

Google supports MerchantReturnPolicy structured data.

A standard business policy can be nested under Organization or OnlineStore markup through hasMerchantReturnPolicy.

A product-level policy can be placed under an Offer when a specific product requires an override. Google’s return-policy structured-data documentation explains that product-level return information can override the organisation-level standard policy for that product.

Structured data can describe information such as:

• Applicable country
• Policy category
• Return days
• Return method
• Return fees
• Return shipping fees
• Policy URL
• Accepted product condition
• Refund type

Structured data should reproduce visible information. It should not be used to hide more attractive conditions from customers while presenting them only to Google.

Review schema generated by:

• The WordPress theme
• WooCommerce
• An SEO plugin
• A schema plugin
• Custom code
• Tag Manager
• A server-side optimisation system

Avoid duplicate markup in which one system says free returns and another says that the customer pays.

Validate the markup with Google’s Rich Results Test and inspect the page through Search Console.

Structured data complements the website and Merchant Center configuration. It does not replace either one.

Return-policy verification statuses

Google verifies return policies before using them.

The Return policies table can display:

• Verified
• Pending
• Rejected

Verified

Google approved the policy for use.

Verification does not mean that every product is approved. Products can still have separate data, website or policy issues.

Pending

Google has not completed the review.

During this stage:

• Keep the policy URL accessible.
• Avoid unnecessary repeated edits.
• Confirm that Google is not blocked.
• Confirm that the website remains live.
• Confirm that the policy text still matches.
• Monitor Merchant Center.
• Allow the review period to complete.

Rejected

Google did not approve the policy.

Review the policy details and compare them with the website before submitting further changes.

Common causes include:

• Inaccessible policy URL
• Login requirement
• Missing return window
• Missing fees
• Missing return method
• Missing refund timeline
• Inconsistent conditions
• Wrong country
• Unsupported or unclear wording
• Conflicting website statements
• Policy page blocked from crawling
• Merchant Center configuration not matching the page
• An exception label without a corresponding policy

How to diagnose a rejected return policy

1. Open the policy URL while logged out

Use a private browser window and mobile device.

Check that the complete policy loads without:

• Login
• Registration
• Location selection
• Age gate
• Broken JavaScript
• Redirect loop
• Security block
• Password protection
• Consent form that hides the content

2. Confirm the URL entered in Merchant Center

Check:

• HTTPS
• Domain
• Path
• Trailing redirects
• Language
• Canonical page
• Response status

A policy moved to a new URL may leave Merchant Center pointing to an expired page.

3. Compare every configured field

Create a comparison table with:

• Website statement
• Merchant Center value
• WooCommerce operational rule
• Required correction

Do not compare only the return window.

Review countries, item condition, exchanges, methods, fees, labels and refund time.

4. Search for conflicting promises

Search the website, theme and database for old statements.

A previous “30-day free returns” banner may remain in:

• Slider content
• Footer text
• Product tabs
• Reusable blocks
• Email templates
• Pop-ups
• Translated pages
• Cached pages
• Campaign landing pages

5. Review country and language versions

A multilingual store may have an updated English policy and an outdated German, French or Turkish version.

Confirm that each target market receives a compatible policy.

Language changes should not alter the commercial meaning.

6. Review product exceptions

Check that non-default products submit the exact valid label.

Remove obsolete labels from products that now use the default policy.

7. Purge relevant caches

Clear:

• WordPress page cache
• Object cache
• Server cache
• CDN cache
• Translation cache
• Structured-data cache
• Browser cache

Then retest the public page.

8. Save the corrected source

Update all affected sources together:

• WooCommerce policy page
• Merchant Center policy
• Product labels
• Structured data
• Product-page notices
• Checkout text
• Support instructions

9. Allow Google to process the update

Do not repeatedly rewrite a correct policy every few hours. Monitor the status while Google reviews the change.

Missing return and refund policy issues

A missing-policy issue can occur even when the store owner believes a policy exists.

Possible reasons include:

• The page is still a draft.
• The footer link is missing.
• The page is blocked.
• The policy is inside general terms and difficult to find.
• The page describes refunds but not returns.
• The page describes returns but not refund timing.
• The text is a placeholder.
• The policy is available only after login.
• The mobile footer hides the link.
• The policy contains no clear rules.
• The URL returns a regional error.
• Google sees a different cached version.
• The Merchant Center URL is incorrect.

Google recommends placing a dedicated link in the website footer and clearly explaining requirements and timelines.

If the business does not accept general returns, it still needs a clear statement explaining its handling of returns and refunds.

Return policies and misrepresentation

A return-policy inconsistency can contribute to broader website-transparency concerns.

Google’s misrepresentation policy lists denying a return or refund despite a published policy promising it as an unacceptable practice.

Therefore, compliance involves more than publishing text.

The business must actually follow the policy.

Review:

• Customer-support scripts
• Return-request approvals
• Refund processing
• Carrier labels
• Warehouse procedures
• Payment-gateway actions
• Staff training
• Complaint handling
• Chargeback history

Do not publish a generous policy that the operational team cannot fulfil.

Competing product and account sources

A corrected return-policy label can be overwritten by another source.

Review:

• PW Merchant API
• Another Merchant API integration
• XML data sources
• CSV uploads
• Google Sheets
• Automated website sources
• Supplier systems
• ERP systems
• Supplemental sources
• Manual edits
• Legacy WooCommerce Google plugins

For every affected product, identify which source controls return_policy_label.

A manual Merchant Center edit may disappear during the next scheduled product update.

Common setup mistakes

Copying a generic template without editing it

A template may contain another company’s address, return period, currency or product rules.

Using one policy for countries with different conditions

Cross-border fees and legal requirements may differ.

Confusing the return window with refund-processing time

Thirty days to request a return does not mean the refund takes thirty days to process.

Promising free returns while charging for shipping

Return shipping and restocking fees must be disclosed.

Adding only defective-product instructions

Customers should understand how other permitted scenarios are handled.

Hiding exclusions on individual product pages

The main policy should explain the categories subject to exceptions.

Applying exception labels to default products

An accidental bulk rule can assign restrictive terms to the entire catalogue.

Deleting a Merchant Center policy without removing its labels

Products continue submitting a label that no longer matches a valid policy.

Using translated exception labels

Technical label values should remain stable.

Assuming structured data replaces the policy page

Customers still need a readable public page.

Assuming Merchant Center replaces WooCommerce operations

A configured policy does not create a return form, carrier label or refund workflow.

Ignoring customer-support behaviour

A policy is misleading if staff refuse the rights it promises.

Frequently asked questions

Does WooCommerce create a return policy automatically?

WooCommerce normally creates a draft Refund and Returns Policy page. It is only a sample and must be reviewed, customised and published.

Where do I add a return policy in Google Merchant Center?

Open Products & store, select Shipping and returns, open Return policies and choose Add return policy.

Do I need a return-policy page if I do not accept returns?

Yes. Clearly explain that returns are not accepted and describe how defective, incorrectly supplied or otherwise legally protected cases are handled.

Can I use one policy for all countries?

Yes, when the same conditions genuinely apply. Create separate policies when countries have different windows, fees, methods or restrictions.

What is the return-policy URL?

It is the publicly accessible HTTPS page on your website that explains the store’s return and refund conditions.

Should the policy page be in the footer?

Google recommends making it easy to find. A visible footer link provides consistent access across the store.

When should the return period begin?

State the basis clearly. Google’s numbered return-policy model uses days after delivery. The website and Merchant Center should describe compatible timing.

Can I offer different return windows for different products?

Yes. Create a standard policy and an exception policy, then assign the exception using return_policy_label.

What happens when return_policy_label is empty?

The applicable default return policy is used.

Why does Google report an invalid return policy label?

The submitted product value does not match an existing applicable exception policy. Create the matching policy or remove the invalid label.

Do all WooCommerce variations need the label?

Every separately submitted variation that follows the exception should receive the correct label.

Can I charge a restocking fee?

Merchant Center supports fixed or percentage restocking-fee settings, but the fee must be disclosed, accurate and lawful.

Is return shipping the same as a restocking fee?

No. Return shipping pays for transporting the product. A restocking fee is a separate deduction associated with handling the returned item.

Can I advertise free returns?

Only when customers genuinely pay no applicable return cost under the described conditions.

Do I need to accept exchanges?

Merchant Center allows you to state whether exchanges are accepted. Choose the option that matches the real store process.

What does Pending mean?

Google has not completed verification. Keep the policy accessible and allow the review process to finish.

What does Rejected mean?

Google did not approve the submitted policy. Review the status details and compare every Merchant Center field with the website.

How long can verification take?

Google’s Merchant API guidance says a new return policy may take up to ten business days to be reviewed and available.

Can PW Merchant API create my legal policy?

No. The business must determine and publish its real policy. PW Merchant API can support applicable product and Merchant operations but cannot provide legal rules or invent business commitments.

Does structured data guarantee that Google will display return information?

No. Structured data helps Google understand the policy but does not guarantee a specific search, Shopping or advertising presentation.

Can an incorrect policy affect the account?

A missing, unclear or contradictory policy can contribute to product, website-transparency or misrepresentation problems.

Do I need to update Merchant Center when the website policy changes?

Yes. Update the website, Merchant Center, product labels and structured data together.

Final checklist

Before considering the return-policy setup complete, confirm that:

• The business’s real return rules were documented.
• Applicable consumer laws were reviewed.
• The policy was reviewed by a qualified professional where needed.
• A dedicated WooCommerce policy page exists.
• The page is published.
• The page uses HTTPS.
• The page loads without login.
• The page works on desktop.
• The page works on mobile.
• The page is not blocked by robots.txt.
• The page is not marked noindex unintentionally.
• The page is linked from the footer.
• Product-page return claims were reviewed.
• Cart statements were reviewed.
• Checkout statements were reviewed.
• Order emails were reviewed.
• Customer-account instructions were reviewed.
• Support-page instructions were reviewed.
• Promotional banners were reviewed.
• The policy states applicable countries.
• Domestic and international rules are distinguished.
• The return window is stated.
• The event beginning the window is stated.
• Calendar and business days are distinguished.
• Accepted product conditions are explained.
• Original-packaging requirements are explained.
• Tag and accessory requirements are explained.
• Defective-product returns are explained.
• Non-defective returns are explained.
• Buyer’s-remorse handling is explained.
• The return-request process is explained.
• Required customer information is listed.
• Return methods are stated.
• In-store returns are described where available.
• Drop-off returns are described where available.
• Mail returns are described where available.
• The return-label process is explained.
• Return shipping responsibility is stated.
• Defective-product shipping costs are stated.
• Buyer’s-remorse shipping costs are stated.
• International return costs are stated.
• Restocking fees are disclosed.
• Fixed fees include the correct currency.
• Percentage fees are explained.
• Exchanges are addressed.
• Exchange shipping costs are stated.
• Refund methods are stated.
• Store-credit rules are stated.
• Refund-processing time is stated.
• Payment-provider delays are distinguished.
• Product exclusions are listed.
• Personalised-product rules are stated.
• Hygiene-sensitive product rules are stated where applicable.
• Digital-product rules are stated where applicable.
• Final-sale rules are visible before purchase.
• Seasonal extensions are documented.
• The Merchant Center policy URL is correct.
• The selected countries are correct.
• Return acceptance is configured accurately.
• Exchange acceptance is configured accurately.
• Product conditions match the website.
• The Merchant Center return window matches.
• Seasonal extensions match.
• Return methods match.
• Return-label settings match.
• Return shipping costs match.
• The policy currency is correct.
• Restocking fees match.
• Refund-processing time matches.
• Suggested values were manually reviewed.
• The default policy is correct.
• Every exception policy is necessary.
• Exception labels are stable.
• Exception labels match exactly.
• Default products have blank or default labels.
• Exception products receive the correct label.
• Variable products were reviewed.
• Every applicable variation receives the right policy.
• Product-page exceptions are visible.
• Obsolete labels were removed.
• Deleted policies are no longer referenced.
• Competing product sources were reviewed.
• Merchant API sources were reviewed.
• XML sources were reviewed.
• CSV and Sheets sources were reviewed.
• ERP and supplier sources were reviewed.
• Automated website sources were reviewed.
• The authoritative source was identified.
• Structured return-policy data was inspected.
• Organisation-level markup was reviewed.
• Product-level overrides were reviewed.
• Duplicate schema was removed.
• Structured data matches visible text.
• Rich Results Test was completed.
• Search Console inspection was completed.
• WordPress caches were cleared.
• Server caches were cleared.
• CDN caches were cleared.
• Translated policy pages were reviewed.
• Old promotional text was removed.
• The policy was opened while logged out.
• The Merchant Center status was checked.
• Pending verification was allowed to finish.
• Rejection details were reviewed if applicable.
• Customer-support staff received the current rules.
• Warehouse procedures match the policy.
• Refund operations match the policy.
• The business honours the commitments it publishes.
• Future policy changes will be updated across every source.

A Google Merchant Center return policy is not simply a field that must be completed during account setup.

It is a structured representation of a real customer-service commitment.

The WooCommerce page, product notices, checkout experience, return workflow, refund operations, Merchant Center configuration, return-policy labels and structured data should all describe the same conditions.

The most reliable setup begins on the website. It establishes lawful and operationally realistic rules, publishes them clearly, tests the complete customer journey and then enters matching information in Merchant Center.

When WooCommerce, PW Merchant API, Google Merchant Center and the customer-facing return process remain consistent, Google can understand the policy more accurately and customers can make purchasing decisions with clearer expectations.