Conflicting returns values

What Google requires

Fields that do not contradict

The parts of a return policy, whether returns are accepted, the window, the fees, the country, have to describe one coherent policy. Fees attached to a policy that says it takes no returns, or a country code that is not valid for the policy, put two facts in conflict. Google reports it as Conflicting returns values.

What Google does

The policy is refused as incoherent

Google cannot apply a policy that contradicts itself, so your default can take its place, and the returns terms shown to shoppers are not the ones you configured. The conflict is easy to introduce when per-item overrides are layered on top of an account policy.

How to fix it by hand

Reconcile the fields

• Remove fees from any policy that declares no returns.
• Use a valid country for the policy the fields describe.
• Make the window and the fees consistent with the accept/deny stance.

What FeedMender checks today

3 checks apply, read from the scanner's registry

The scan catches fees on a no-returns policy, self-contradicting windows, and invalid policy countries.

• returns_no_returns_with_feesblocks
• returns_window_contradictionblocks
• returns_country_invalidblocks

What the scan does not check today: the return policy configured in your account; it reconciles the fields present in the feed, not the Merchant Center setting.

The quicker way

Let the scan reconcile them

Run the free scan and it flags every return policy whose fields contradict each other. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.

Scan your feed