Help! Merchant Product Feed; price and sale_price_effective_date

[William Davis]

Is there a sample of Miva Google Merchant Product Feed available? If so can some one please share it with me.

Having problem is with the following fields:

price: Displaying sales price versus regular price conditional not working.

sale_price_effective_date: No values, would like to display


Note: We use a conditional to conceal price for items no longer in stock.

price

<mvt:if expr="l.settings:product:inv_level EQ 'low'">&mvt:record:price; USD<mvt:elseif expr="l.settings:product:inv_level EQ 'out'"> <mvt:else>&mvt:record:price; USD</mvt:if>


sale_price_effective_date

​

[William Davis]

I thought this would have been a quick reply.

[Nick]

William Davis It looks like your conditional is checking for l.settings:product:inv_level when the feed array is l.settings:record so it would be l.settings:record:inv_level

As for the sale_price_effective_date you would need to use some template code to check the end date of the price group that is assigned to the product. This could be a bit tricky to solve seeing how a product can have multiple price groups as well as some that are only assigned to specific customers.

[thilsabeck]

Hello Bill,

That is because you're using &mvt:record:price; which will shows sale prices for products if they exist. Instead you want to use &mvt:record:original_price; to show prices without any discounts included.

Thank you,

[William Davis]

Thanks to you both. Tim helped me figure out the display of discounted price, now all I have to figure out the conditional to only display when in stock.

As to :

"As for the sale_price_effective_date you would need to use some template code to check the end date of the price group that is assigned to the product. This could be a bit tricky to solve seeing how a product can have multiple price groups as well as some that are only assigned to specific customers."

I don't think we need anything that complicated.

[Nick]

William Davis For the sale_price_effective_date you could have a custom product field then pull in that data. You would just need to manually populate and remove the data in the custom field.

[William Davis]

William Davis For the sale_price_effective_date you could have a custom product field then pull in that data. You would just need to manually populate and remove the data in the custom field.

Yikes! That's a shame having that data already on the database to have to create additional fields, populate is each time we have sales. We currently have thousands of products on sales, each category has different discount, this is not practical. But at least is a work around for now. Thank you.

Now I am trying to figure out why the use of "|[prefix] &mvt:record:name;|" would wrap quotations marks around the rendered value example:

prefix "Xwy"

What a mission.

[Nick]

William Davis Typically CSV files use double-quote marks to delimit field values that have spaces, so a value like Santa Claus gets saved as “Santa Claus” to preserve the space.