FeedMender/Errors/Missing return shipping fee
Common rejections
Missing return shipping fee
When a return method implies a shipping fee, Google expects that fee spelled out. A fee with no type, or none at all where one is due, leaves the return cost undefined.
What Google requires
A fee with a type, where the method needs one
The return shipping fee states who pays to send an item back and how much, with a fee type that says whether it is fixed or free. Where the return method implies a fee, it has to be present and typed. Google reports the gap as Missing return shipping fee.
What Google does
The return cost is undefined and the policy falls back
A fee with no type, or a method that implies a fee but carries none, leaves Google unable to state the return cost, so the policy is not applied as written and your default can take over. The shopper sees a different returns promise than the one you configured.
How to fix it by hand
Type the fee and complete it
- Give the return shipping fee a type, fixed or free, wherever a method implies one.
- Write a fixed fee as an amount with a currency.
- Align the fee with the return method so the two do not contradict.
What FeedMender checks today
3 checks apply, read from the scanner's registry
The scan catches the missing fee, validates its format, and flags a fee that has no type.
returns_fee_missingblocksreturns_shipping_fee_formatblocksreturns_fee_type_missingdepends on the file
What the scan does not check today: the return policy set in your Merchant Center account; it reads the fee fields in the feed, not the account setting.
The quicker way
Let the scan complete the fee
Run the free scan and it flags every return shipping fee that is missing, untyped or malformed. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.