When a Google feed needs shipping_weight

Shipping weight is conditional. It becomes useful or required for the shipping configuration you actually use, rather than for every product in every account.

Reviewed October 4, 2026 · Independent guidance · Static feed check with contextual limitations

What does this issue mean?

The shipping_weight attribute represents the weight used for delivery calculations. It is not automatically the same as a product’s bare material weight, dimensional weight or a storefront display unit. Account-level services may calculate rates by weight, while flat-rate services may not depend on this field.

Why this happens

Missing values can originate in variant weights, inconsistent source units or a feed plugin mapping an unrelated numeric field. A zero default can appear populated while remaining inaccurate. Before adding values, determine how your shipping service uses weight and which packaging assumptions apply to the offered item.

How to diagnose and fix it

1. Check whether the Merchant Center delivery service for the target market depends on shipping weight.
2. Confirm the source product or package weight and its unit from reliable logistics data.
3. Export a positive numeric value with a supported unit such as kg, g, lb or oz.
4. Review products with unusual packaging, bundles or minimum quantities and verify the resulting delivery rate.

Before and after example

The examples are illustrative. Replace them with verified information for your own offer; copying an example identifier, amount or URL would introduce incorrect data.

Before

<g:shipping_weight>1500</g:shipping_weight>

After review

<g:shipping_weight>1.5 kg</g:shipping_weight>

The example assumes a verified 1.5 kg weight. Feed Doctor checks submitted format; it does not invent missing weight or flag every omission as a universal requirement.

Shopify fix

Find the affected product and exact variant in your Shopify catalog, then identify which product field or Google & YouTube channel setting supplies shipping_weight. If a separate feed app generates your export, inspect its mapping instead of assuming the channel settings control that file. Change verified source data, save it, and obtain a fresh export.

Compare one affected variant and one previously correct offer before making a bulk change. Do not change stable IDs just to improve a report score. If the issue involves identifiers, verify whether the connector reads barcode, brand or manufacturer reference data. If it concerns a live page or shipping account setting, a feed-column edit alone may not resolve it.

WooCommerce fix

Open the relevant product or variation and inspect the attribute consumed by your Google feed integration. Google for WooCommerce can map product attributes into feed attributes; third-party feed generators may use different mappings. Check both the stored value and the exported result, especially when parent attributes are inherited by variations.

Update the source value or mapping deliberately and regenerate the feed. Keep product identity, currency and variant relationships consistent. Avoid editing only a downloaded snapshot if a scheduled exporter will replace that change. For an account or website issue, repair the effective configuration and public offer as well as reviewing the file.

Verify the repair before submitting

Keep the original feed as a backup and compare the same affected product IDs in the regenerated file. Confirm that the expected product count remains unchanged and that no unrelated fields disappeared. If you applied a bulk rule, inspect offers outside the original affected set as a control; an overly broad mapping can fix one problem while creating another.

Run a new static scan, then separately check live product information and your Merchant Center diagnostics. File format validation cannot determine every policy, account, image or website condition. Processing and recrawling take place in Google’s systems, so a corrected file is not an immediate promise of approval. Use the actual updated diagnostics to decide whether additional investigation is required.

Frequently asked questions

Related feed issues

• How to review missing shipping in Merchant Center
• How to fix invalid Google Merchant Center price format
• How to fix missing product descriptions in Merchant Center

Official references: Google product data specification, Shopify Google & YouTube requirements, WooCommerce attribute mapping. Requirements can vary by product, country and account setup.