FeedMender/Errors/Multiple restocking fees
Common rejections
Multiple restocking fees
A return policy can carry one restocking fee. Two of them, or a fee written in a format Google cannot read, make the policy ambiguous, and Google refuses the ambiguity.
What Google requires
One restocking fee, correctly formatted
The restocking fee is a single value per policy, either a fixed amount with a currency or a percentage, in the format Google expects. Two restocking fees on one policy, or a percentage that does not read as a percentage, is invalid. Google reports it as Multiple restocking fees.
What Google does
The policy is refused, and the default can apply
Two fees leave Google unable to tell the shopper what a return costs, so the policy is not applied as written and your default return policy can take its place. A malformed fee has the same effect. Because returns costs feed into the trust signals on the listing, a rejected fee quietly weakens the offer.
How to fix it by hand
Leave exactly one fee, well-formed
- Keep one restocking fee per policy; remove the duplicate.
- Write a fixed fee as an amount with a currency, and a percentage in the percentage format.
- Where there is no restocking fee, omit it rather than sending an empty or zero placeholder.
What FeedMender checks today
3 checks apply, read from the scanner's registry
The scan catches the second restocking fee and validates the amount and percentage formats.
returns_two_restocking_feesblocksreturns_restocking_fee_formatblocksreturns_restocking_percentage_formatat risk
What the scan does not check today: the return policy configured in your account; it reads the fees present in the feed, not the Merchant Center setting or your live policy page.
The quicker way
Let the scan check the fee
Run the free scan and it flags every policy with two restocking fees or a malformed one. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.