Unit pricing measure is the Google Merchant Center attribute, submitted as <g:unit_pricing_measure>, that states how much product a single unit contains -- its weight, volume, length, or count -- so Google can calculate and display a price-per-standard-unit figure next to the listing. The value combines a number and a unit abbreviation, formatted like 750ml, 1.5kg, or 2ct.

Why It Matters

Several countries, most notably Germany and France, legally require unit pricing on any product sold by weight, volume, length, or area, and Google enforces this by disapproving eligible items in those Merchant Center targets when unit_pricing_measure is missing. Beyond compliance, unit price is also a genuine comparison tool for shoppers choosing between differently sized packs of the same product category, so omitting it on food, beverage, cosmetics, and cleaning-supply listings can quietly cost conversions even in markets where it isn't legally mandatory. Feed teams managing catalogs sourced from multiple suppliers often find pack sizes recorded in inconsistent units, some in grams and others in ounces, making this a prime candidate for cleanup before submission.

How It Works

Google pairs unit_pricing_measure with a second attribute, unit_pricing_base_measure, which defines the reference unit Google should price against, such as 100g or 1l; Google then divides price by unit_pricing_measure and multiplies by unit_pricing_base_measure to render the comparison. Accepted units include ml, cl, l, g, kg, oz, lb, fl_oz, in, ft, sqm, and ct, and the number must be a positive decimal -- ranges, approximate values, or blank placeholders are rejected outright. The attribute is optional worldwide except in countries with unit-pricing regulations, where Google treats it as effectively required for applicable product categories and will disapprove non-compliant items rather than merely suppressing the display. Meta Catalog has no equivalent attribute, since Meta's ad formats don't render a per-unit price comparison, so this field only needs to be maintained in the Google-bound version of a feed. Because pack-size data frequently arrives from suppliers in mismatched units, it's a common target for normalization rules before either sale-price or unit_pricing_measure gets submitted downstream.

Example

<item>
  <g:id>SKU-62744</g:id>
  <title>Cold-Pressed Olive Oil - 750ml</title>
  <link>https://example-shop.com/products/olive-oil-750ml</link>
  <g:price>14.99 USD</g:price>
  <g:unit_pricing_measure>750ml</g:unit_pricing_measure>
  <g:unit_pricing_base_measure>100ml</g:unit_pricing_base_measure>
</item>

Related Concepts

Unit pricing measure only produces a meaningful figure alongside price, since it's the divisor applied to that value, and it sometimes needs to be recalculated whenever sale price is active if a market's regulations require the unit price to reflect the discounted rate too. Because supplier data rarely arrives in one consistent unit system, reliable unit_pricing_measure output is usually a byproduct of solid normalization rules applied earlier in the feed pipeline rather than something fixed item-by-item. Teams expanding into EU markets for the first time should treat this field as a launch-blocking requirement to check early, not a detail to patch after the first round of disapprovals arrives.