Quantity on Google Merchant does not read correctly

  • Resolved WebePc Gianluca Molina

    (@webepc)


    11 months, 1 week ago

    Hi!

    I am having a problem.

    The plugin correctly generates the xml feed for google merchant

    The problem is that if I set the “quantity” field correctly in the settings however it doesn’t recognize it.

    In products the quantity field is correctly set but it is not “seen” in the feed

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support mansary

    (@mansary)

    11 months, 1 week ago

    Hi @webepc

    If you are not seeing a newly added attribute to the feed, the possible reason could be caching. Please clear your website and browser caching and then, regenerate the feed and open it on your browser and check again.

    To avoid further feed caching, make sure to exclude the feed directory from your caching tool. Here you can find the instructions on how to exclude the feed directory from a few popular caching tools – https://webappick.com/docs/ctx-feed/faqs/how-to-solve-feed-configuration-not-updating-issue/

    Best regards,

    Thread Starter WebePc Gianluca Molina

    (@webepc)

    11 months, 1 week ago

    Ok I added the URL in the exclusions of Litespeed

    This is the configuration:

    Thread Starter WebePc Gianluca Molina

    (@webepc)

    11 months, 1 week ago

    Despite having excluded the URL in Google Merchant, the error continues to appear
    Limited number

    It is as if it did not recognize the quantity of products

    Plugin Support mansary

    (@mansary)

    11 months, 1 week ago

    Hi,

    If you have cleared the cache but still not getting the attribute on the feed, make sure there are any object or server site caching. Because, it only can happen due to caching.

    You can try creating a new feed to check if the quantity field is getting added to the new feed to confirm your old feed is being cached.

    Thank you,

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Quantity on Google Merchant does not read correctly’ is closed to new replies.

Tags