Shipping weight value too high

What Google requires

A number, a known unit, a believable range

shipping_weight is a number and a unit from Google's set, lb, oz, g or kg, within range: Google's ceiling is 2000 lb or 1000 kg. UK and IE accounts render the same attribute and issue as delivery weight. A weight above the ceiling raises Shipping weight value too high; an absent one where calculated shipping needs it raises Missing shipping weight.

What Google does

Calculated shipping breaks and the item falls out

An unrecognised unit or a weight outside the accepted range fails validation, and a product whose shipping cannot be computed cannot show a delivery price, which in a calculated-shipping account means it drops out. A 0 kg or a 900 kg parcel is almost always a data error, not a product, and Google treats it as one.

How to fix it by hand

Standardise the unit, sanity-check the number

• Use only Google's units, and keep them consistent across the feed rather than mixing kg and lb.
• Check the numbers: a zero or an implausibly large weight is a mapping or unit error.
• Supply shipping_weight wherever your rates are calculated from weight.

What FeedMender checks today

Two checks apply, read from the scanner's registry

The scan checks the weight's unit against Google's set and flags the values outside a believable parcel range.

• shipping_weight_rangeblocks
• shipping_weight_unitblocks

What the scan does not check today: whether the weight is the true weight of the parcel; it checks the unit and the range, not accuracy against the real item.

The quicker way

Let the scan check the weight

Run the free scan and it flags every shipping weight with a bad unit or an impossible value. The scan to identify errors is free and shows every finding before you pay anything. You only pay for the fix.

Scan your feed