Hi @jethrohazelhurst,
Thanks for sharing the details and the screenshot, I can see how confusing it is to suddenly see the “Missing unit pricing measure” warning across all your products, especially when it is not reflected in your Google Merchant Center.
This warning comes from Google’s product data requirements, particularly for countries like the UK where unit pricing is expected for certain product categories, such as items sold by weight, volume, length, or area. The Google for WooCommerce plugin surfaces these warnings early so you can address them before they potentially impact listings.
A few key points to help guide you:
• The warning may not yet appear in Merchant Center if the feed has not been fully processed or enforced there yet
• It typically applies only to products where unit pricing is relevant, for example food, liquids, or bulk goods
• If your products do not fall into those categories, this warning can often be safely ignored
If unit pricing is relevant for your products, you can add the required fields:
• Unit pricing measure, for example 500ml, 1kg
• Base unit pricing measure, for example 1L, 1kg
These can be added via the product data settings in WooCommerce or through feed rules depending on your setup. You can read more about this requirement here: https://support.google.com/merchants/answer/6324455
If you are unsure whether your products require this, feel free to share an example product or your product category and I will help you confirm whether action is needed or not.
Thread Starter
jh
(@jethrohazelhurst)
Hi @lovingbro thanks for getting back to us!
The products in question are cosmetic product like moisturisers.
We are selling to the UK market.
You say we can add the required fields – are these fields in the Google for WooCommerce product area or somewhere else?
We are using the Google for WooCommerce plugin.
Hi @jethrohazelhurst,
Please share the URL of one moisturiser product that shows the warning, and a screenshot of that product’s data details in WooCommerce, including the Google for WooCommerce section. Once I see how the data is stored on your site, I will advise the exact place to add the unit pricing measure and base measure.
Thread Starter
jh
(@jethrohazelhurst)
Sure thing! Is there a way I can share this info privately?
Hi @jethrohazelhurst,
On the ww.wp.xz.cn forums, everything is public by design, so there is no private way to share URLs, logs, or system status reports here. That said, you can safely share the details using one of these tools: https://pastebin.com, https://gist.github.com or https://quickforget.com
These services let you paste your data and share a link without exposing it directly in the thread. For screenshots, you can use https://snipboard.io and share the image link here.
Once you’ve shared those, I’ll take a closer look and guide you on exactly where to add the unit pricing fields.
Thread Starter
jh
(@jethrohazelhurst)
Hi there,
Here is an example product URL:
https://www.blushbeauty.co.uk/buy/im-from-beet-purifying-mask-70g/
Here are screenshots of the GFW fields:
https://snipboard.io/ifowpm.jpg
Here is from the merchant center:
https://snipboard.io/KjMmZe.jpg
I don’t see a field or way to add the required data.
Many thanks.
Hi there!
Thank you for bringing this to our attention.
I’ve seen multiple users request a feature to add the missing unit pricing value. You can find the related feature requests here:
https://woocommerce.com/feature-request/unit-pricing-measure/
https://woocommerce.com/feature-request/add-unit_pricing_measure-for-use-in-germany-and-austria/
I have escalated this internally to confirm whether it is still under development or if there is any available workaround. Once we have more information, we will be happy to assist you further.
Thank you for cooperation and understanding.
Thread Starter
jh
(@jethrohazelhurst)
Hi @shahzeenfarooq
Thanks – will we get an update when this is released?
Also can you please redact the URLs and links in my previous post. I can’t believe there is no option to edit posts on this forum.
Hi there!
You can keep an eye on the changelog everything is mentioned there when we add new features or fix bugs:
https://ww.wp.xz.cn/plugins/google-listings-and-ads/#developers
Also, we do not have an option to remove any links or URLs from the post.
Forum topics will only be edited or deleted if they represent a valid legal, security, or safety concern.
See https://ww.wp.xz.cn/support/forum-user-guide/faq/#will-you-delete-my-post-once-the-problem-is-solved and https://ww.wp.xz.cn/about/privacy/
Hi there!
This is a follow-up message to inform you that here is a workaround to add a custom field to Google attributes: https://woocommerce.com/document/google-for-woocommerce/attribute-mapping/use-cases/#mapping-custom-fields
Please follow these steps and let us know if this works for you
Thread Starter
jh
(@jethrohazelhurst)
Hi @shahzeenfarooq,
Thanks for the follow-up.
I understand the custom fields workaround, but I don’t think it solves this issue.
That guide shows how to add a custom field as a source field and then map it to an existing Google target attribute, such as GTIN.
The problem here is that unit_pricing_measure and unit_pricing_base_measure do not appear as available target attributes in the Google for WooCommerce attribute mapping dropdown.
So even if I add custom fields for the product values, there is nowhere to map them to.
Could you please confirm whether Google for WooCommerce currently supports sending unit_pricing_measure and unit_pricing_base_measure to Google Merchant Center?
If not, is there any current workaround via hook/filter, or is this still pending as a feature request?
Many thanks!
Hi @jethrohazelhurst ,
Thanks for your questions and I can confirm that the extension supports syncing any custom value supported by Google Merchant Center and in this case unit_pricing_measure and unit_pricing_base_measure are definitely supported. While there isn’t any native dropdown to set these as target attributes you can definietly configure these as custom variables to sync via the Google for WooCommerce extension.
If you review the documentation, a custom field such as ISBN is setup to be synced. ISBN isn’t natively supported by WooCommerce and hence the value is added via a custom field and you can use the custom snippet in the doc to add this field. Similarly, you can sync your unit_pricing_measure and unit_pricing_base_measure custom fields to Google Merchant Center via this custom attribute mapping workaround.
A code like this should help you surface this custom field. (Please tweak the code as necessary to map to the correct custom field)
add_filter(
‘woocommerce_gla_attribute_mapping_sources_custom_attributes’,
function( $values ) {
return array_merge( $values, [‘unit_pricing_measure’, ‘unit_pricing_base_measure’]);
}
);
I hope that helps. Please let us know if we can clarify anything further.
Thread Starter
jh
(@jethrohazelhurst)
Thank you for the fast response!
Thanks, that makes sense.
Just to confirm, if I use ACF instead of the native WordPress Custom Fields box, and create product fields with the exact field names:
unit_pricing_measure
unit_pricing_base_measure
Then add the snippet:
add_filter(
'woocommerce_gla_attribute_mapping_sources_custom_attributes',
function( $values ) {
return array_merge(
$values,
array(
'unit_pricing_measure',
'unit_pricing_base_measure',
)
);
}
);
Google for WooCommerce should then sync these values to Merchant Center, even though these attributes do not appear in the target attribute dropdown?
For example, on a 30ml product I would set:
unit_pricing_measure = 30 ml
unit_pricing_base_measure = 100 ml
And on a 70g product:
unit_pricing_measure = 70 g
unit_pricing_base_measure = 100 g
Please can you confirm this is the correct approach?
Thanks.
Hi @jethrohazelhurst,
Yes! Using ACF will work perfectly fine here. ACF stores field values in wp_postmeta using the field name as the meta key, so as long as the ACF field name (not the field label) is set to exactly unit_pricing_measure and unit_pricing_base_measure, the plugin will read them just like native WordPress custom fields. The snippet then surfaces those as available sources in the attribute mapping UI.
Your value format examples look right too. Just make sure to use Google’s accepted unit abbreviations: for volume that’s ml, cl, l, fl oz; for weight that’s mg, g, kg, oz, lb.
Once the snippet is in place and the ACF fields are populated on your products, after saving the attribute mapping configuration you should see unit_pricing_measure and unit_pricing_base_measure become available to map. Google for WooCommerce will then include these values in the feed sent to MC, which should resolve the warning across your products.
Give it a try and let us know how it goes!
