• Resolved tamrute

    (@tamrute)


    Hi, I’d like to set the base measure for Google Shopping so I’ll get the info e.g. 7,11 € / 100 ml. Apparently I need to add the following Google Shopping attributes: unit price base measure and unit pricing measure – is that correct?
    Not sure what to insert for Prefix, value and suffix. Can anybody tell what to do here? Thanks in advance!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi,

    Did you check out Google’s requirements for those fields?

    https://support.google.com/merchants/answer/6324490?hl=en
    https://support.google.com/merchants/answer/6324455?hl=en

    You can only add those fields, obviously, if you have the units saved in attributes at your products. If you have to use suffix or prefix also depends on how you have saved that data in your attributes. If you did not save it with prefixes and suffixes than you do indeed have to add those on the field mapping configuration page of the plugin.

    All the best,
    Eva

    Hi,

    Assuming the issue at hand has been resolved or our support is no longer required I will close this issue for housekeeping reasons now.

    Please don’t hesitate to reach out to us whenever you have a question again.

    All the best,
    Eva

    Thread Starter tamrute

    (@tamrute)

    Thanks for your answer! Unfortunately we still haven`t found a solution to our problem. Yes, Google states that we need to specify the unit price base measure and unit pricing measure. Based on that attributes Google s gonna calculate the unit pricing base measure.

    In field mappping I added the required attributes. But I am still not sure what value I have to choose. Eventually I decided to go for the following values.

    – Google Shopping attribute: g:unit_price_base_measure | Prefix: ml | Value: woosea unit pricing base measure (added custom attribute)

    – Google Shopping attribute: g:unit_pricing_measure | prefix: | Value: woosea unit pricing measure (added custom attribute)

    1st questions: is the field mapping ok? or do we need to choose different prefix & value?

    2nd question: Yout said “You can only add those fields, obviously, if you have the units saved in attributes at your products” – but where can I see that? and if I don`t have those units saved where and how do I do it? Could you please give me an example? Thanks in advance!
    Best

    Thread Starter tamrute

    (@tamrute)

    I forgot to mention that we chose to add a suffix for g:unit_price_base_measure
    suffix: 100

    Hi tamrute,

    Did you read Google’s help pages on the unit pricing (base) measure?
    https://support.google.com/merchants/answer/6324490?hl=en
    https://support.google.com/merchants/answer/6324455?hl=en

    An example of a g:unit_pricing_measure is given on the above page: 750ml, meaning you should add the ‘ml’ in the suffix field and not in the prefix like you did. Same goes for the g:unit_price_base_measure, you need to put the ml in the suffix field. When 100ml is your base measure for all products then make sure to fill in a static value ‘100’ in the unit_price_base_measure field mapping.

    The field mappings would then look like this:
    https://www.dropbox.com/s/wwvsyenw0gu2c8v/unit-pricing-measure.png?dl=0

    Bear in mind that the woosea unit pricing measure is an extra attribute which you can only enable on your product edit pages when you are using the Elite version of our plugin. Not sure if you do? When you enabled that field in the ‘Settings -> Extra fields’ page you need to fill in the values on your product edit pages for your products otherwise the unit pricing measure won’t show in your product feed.

    Hope this makes sense?

    All the best,
    Eva

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Base measure’ is closed to new replies.