Potential inaccurate value: multipack [multipack]

What Google requires

A retailer pack count, as a whole number

multipack is the integer count of identical items you have grouped into one unit, so it is a whole number or nothing, and it is a retailer-defined pack: Google says not to submit it for a manufacturer-defined multipack. Google reports a doubtful value as Potential inaccurate value: multipack [multipack], and a required-but-absent count as Missing value: multipack [multipack].

What Google does

The unit misreads and unit pricing skews

A value that misstates the sellable unit — a pack count on a single item, or a manufacturer bundle sent as a retailer pack — can throw off the per-unit price computed from unit pricing. The product still serves, but the comparison shoppers make on price per unit is built on a wrong quantity.

How to fix it by hand

Set an honest retailer count

• Give multipack a whole number, and only on packs you grouped yourself.
• Leave it empty for single items and for manufacturer-packaged multipacks.
• Keep multipack and unit pricing consistent so the sellable unit reads the same everywhere.

What FeedMender checks today

One check applies, read from the scanner's registry

multipack_value checks one thing: that the value is a whole number, digits only. A non-numeric value such as 3-pack or two is flagged.

• multipack_valueblocks

What the scan does not check today: whether the number is positive or plausible — a bare 0 passes — whether the pack is retailer-defined, manufacturer-defined or a single item, and how the count compares to unit pricing or the landing page. None of that is decided from this check.

The quicker way

Let the scan check the count

Run the free scan and it flags every multipack value that is not a whole number. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.

Scan your feed