Google Merchant Center issue
Missing unit pricing measure
An offer may need a measure such as volume, weight, length, or area so its unit price can be understood.
Google’s source: Official Merchant Center guidance ↗
What Google is reporting
Google's unit-pricing measure attribute represents the quantity sold. Requirements vary by category and local rules, so check the affected market and Google's issue detail.
Why this happens
- A relevant measure is missing from the product source.
- The source does not distinguish package size between variants.
- Unit and base-measure values are formatted inconsistently.
These are possibilities, not a confirmed cause for your account.
Does it affect eligibility?
This attribute is optional for many products but required for certain products and markets. Do not infer a universal disapproval rule from a missing-attribute notice.
How to diagnose it
- Identify the affected offers, destinations, and countries.
- Confirm the actual package quantity and applicable local requirements.
- Inspect the product source for unit_pricing_measure and, where relevant, unit_pricing_base_measure.
How to fix it
- Add the accurate measure and supported unit for the exact product in your source data.
- Set the base measure where relevant and ensure the displayed unit price is consistent.
- Resubmit and review Google's processed product status.
What CommerceVigil checks
CommerceVigil reports Google's issue and, for deterministically matched offers, recent traffic context. It does not decide which local regulation applies.
Google’s reported issue remains authoritative. AI explanations are separate from deterministic evidence checks.
Frequently asked questions
Is it mandatory everywhere?
No. Google describes it as optional generally and required for some regulated products in certain markets.
Does CommerceVigil calculate my package size?
No. Use your verified source catalog data.