Too many values entered for subscription cost

What Google requires

One subscription_cost, with the right fields

subscription_cost bundles the billing period, the contract length and the recurring amount into a single value, sent once per product. It carries only the sub-attributes it defines, and the period has to be one the surface allows, so a weekly cycle is not accepted for mobile device subscriptions. Google reports a stuffed or repeated attribute as Too many values entered for subscription cost.

What Google does

The plan cannot be read

A repeated attribute or a surplus of fields means Google cannot resolve a single coherent plan, so the device-plus-contract offer the attribute exists for does not serve as intended.

How to fix it by hand

Send one clean plan

• Send subscription_cost once per product, with only the fields it defines.
• Use month or year as the period, avoiding a weekly cycle where the surface forbids it.
• Keep period, length and amount together and consistent.

What FeedMender checks today

Two checks apply, read from the scanner's registry

The scan catches the repeated attribute and the extra fields from the feed.

• subscription_too_many_fieldsblocks
• subscription_repeatedblocks

What the scan does not check today: the two live-page subscription issues, Subscription mismatch and Inaccurate subscription costs, which compare the feed against your landing page; those cannot be found by reading the file.

The quicker way

Let the scan read the plan

Run the free scan and it flags every subscription that is repeated or carries too many fields. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.

Scan your feed