Hi @srenyer @secretlabel @helidirect, I wanted to follow up and let you know that I’ve submitted a feature request for this functionality to our team. Thank you for your feedback!

@helidirect yeah unfortunately you won’t be able to show comparative pricing within a product block, however, there is a potential workaround you could try since you seem to be manually selecting products (this won’t work for a feed pulling dynamically from catalog). 

You can remove the price entirely from the block, and then use columns to add text below the product images that align with your products. There you can type in the price and the sales price. This isn’t ideal if you plan to change your sales price frequently, but could be an option if this will be the sales price for some time. Then you can drag in buttons to the columns and link to the correct products you’ve selected.

Well it sucks if it’s a campaign element. If it’s part of a flow thats going out multiple times each day then you lose a ton of money not having it automated. Klaviyo needs to fix this, but Klaviyo will never gonna get around to adding this

I've been asking for this for a year. I was told multiple times they would put it on the roadmap. I now have a potential new client (ready to move forward, only this issue is holding them back). They have a business where they only do promotions, so for them it’s essential and it should work out of the box, without too much work. 

I can't believe that not more clients complain about this. Isn't this essential for an ecommerce business?

This is ridiculous.  Why would it bring in only one price field from Shopify to put into an email.  Why not bring in the MSRP and discount savings amount?  This was one of the main purposes for my signing up for Klavyio.  If I have to manually enter the product pricing, I can do that thru Mail Chimp.  Please tell me there is a way to show the savings amount in my email template.

We stumbled on this limitation as well. Is it really that hard to pull in the extra field from Shopify to get the Compare at price? For now doing the work around, but  could lead to outdated prices displayed. Seems like a rookie miss on getting this in the roadmap since it still is not in the product 8 months later.

Good morning,

I just wanted to share a new update! 

@walid.bendris recently published a Medium Article that provides more in-depth detail on building your own custom product block which I had previously mentioned as a solution to displaying both a regular and sales price. You can find his article here: Solution Recipe 4: Extending Klaviyo’s Product Block Functionality

In it, he details the steps needed to build the custom block in your Klaviyo template which would extend the default Product Block’s functionality. Keep in mind that this process is still fairly sophisticated and we do recommend working with a developer to implement this solution.

Thanks for sharing your product feedbacks and for being a part of the Klaviyo Community!

David

That is wonderful! It really is a deal breaker functionality. Thank you for addressing the issue so quickly.

Ive Just read through this whole thread really hoping that Klaviyo would have had the functionality added by the end of it. I honestly cant believe that they have such a detailed and complex application and yet dont have such a simple function. Get your act together Klaviyo …..people are loosing money and sales over this !! 

FANTASTIC!!!  It is just such an obvious thing missing, and will make a massive difference to us (and I think most ecommerce businesses).  Let's face it, most online selling is about offering some kind of discounted price on some products if not all. 

That is really good news.

Thanks

I completely agree, We are hesitating to fully move over to Klaviyo because of this limitation.  Is there any work around that can be used without manually having to add the RRP?  Or as previous poster suggests, show the savings?  Most ecommerce sellers require this surely??

Thanks for providing that screenshot @helidirect. What that image made me realize was I was referring to something different, so apologies on my end as I thought the ask was in reference to a dynamic product block. This is the block that is present in a flow like the Abandoned cart flow which shows the item that was abandoned. In a case like that, you can set up to strikethrough a price and reflect the sale price.

When it comes to achieving this same functionality from the product block where you are pulling products in from your catalog, unfortunately what you are trying to achieve is not a possibility at this time so it would be best to either omit the price or use the price indicated from the catalog source.

I've been asking for this function since the day I signed up to Klaviyo 3 years ago and they promised to send it to their team.

It's such a simple request that for whatever reason they keep ignoring. It's marketing 101 to have the regular price as the anchor followed by the sale price. 

I just dont understand why it's not a priority despite so many people requesting it

Yes I kind of got that far, but this seems to be an incredible basic element missing when Klaviyo is just so sophisticated in so many other respects.  

Sorry, forgot mention the screenshot. Here is the screenshot of the product block

https://cdn.shopify.com/s/files/1/0087/9050/7597/files/2020-12-01_22-21-31.jpg?v=1606879684

Save your money and ditch klaviyo. This upgrade isnt coming anytime soon

Hey @KuyaEddie,

If you were having any troubles following @walid.bendris’s Solution Recipe, I would strongly recommend reaching out and working with a developer or an email designer you are familiar. You can also reach out for additional assistance from our expanse network of Klaviyo Partners who can further offer you a hand. 

In addition, you may notice some differences in the email template you are using with the screenshots found in the Solution Recipe as you may be using our new email template builder which was recently released! This new template editor retains many of the classic editor’s capability with the inclusion of some other new ones. Building out a custom product block would still be possible in the new editor. If you wanted to follow along to the screenshots within the Recipe, you can still access the classic editor by selecting the classic editor option when creating a new template. 

In case you missed our KPE event, you can watch a recording of the event and all the exciting new features that were released from the following Community post:

David

Hi @DaveK, @Oyivalk, @Drewseph 

Thank you so much for sharing your feedback and honesty on your experience without the discounted price block. As @Julia.LiMarzi mentioned above, we have added this as a feature request, but I’ve also gone ahead and shared your additional comments and experiences with the appropriate teams. Although I do not have a specific timeline to reference, our team is exploring this functionality. I’ll be sure to update in this thread when there are more details to share. 

Again, thank you for sharing this with us and for being a part of the Community, 
-Cassy 

Hello @Shopado.com.au and @KuyaEddie,

Thank you both for showing such strong interest in having a comparative price feature within Klaviyo. 

We understand that the lack of this feature has been an inconvenience for many, and we highly appreciate your feedback and concerns. Our internal product teams have been made aware of the strong outpour of support for such a feature. In the interim, @walid.bendris has shared guidance on a workaround within their Solution Recipe 4: Extending Klaviyo’s Product Block Functionality article.

This solution is not a native feature of Klaviyo and is written mainly for developers and technically-advanced users. Due to its custom nature, we would not be able to provide specific guidance to its implementation or troubleshooting assistance. For this reason we do highly recommend working with a developer or working with a member of our Partner Agencies that are better geared towards assisting in this regard. 

We'll be closing this thread at this time as we do not have any updates to share. If there is an update to share we will be sure to reopen the topic for visibility. Again, we appreciate your patience as our teams actively works on exploring this feature.

Thanks for being members of our Klaviyo Community!

David

I’m into this now, using the XML Product Feed to feed products into the system. I’m looking to add an additional price point. (e.g. “Standard Price” + “Member Price”) that sort of thing. I can see it IS possible to add additional <price></price> to the xml field, - it displays as a list in the preview. but no way to utilise it. 

I’ve raised this in a support request but still no reply. 

Hey @KuyaEddie,

That’s an interesting point you make. One thing to keep in mind though is that although you can certainly include an additional price field in the XLM feed, you wouldn’t be able to map it to the standard price field if it has already been used. This would lead you to need to map this secondary price field to something else. Because Klaviyo’s default product block can only take advantage of the default price field for use to display the product price, we recommend building your own custom product block within Klaviyo as mentioned my previous comment to this thread. 

When building your own custom product block, you can then take advantage of these multiple price fields you have included within your XML feed. As a reminder, you can find further instructions on how to leverage this and build your own custom product block from the Solution Recipe 4: Extending Klaviyo’s Product Block Functionality published by the @walid.bendris.

David

Hi david. Thanks for that! 

Going to definitely need some assistance with that one I’m already stuck on Set the show/hide block feature logic for this Product Block to false.

What do I put in the logic text field? 

Actually the guides and their subsequent guides look to be dated? The editor doesn’t look like that now. Sorry I’m getting no where with this one. 

Hi David,

Thanks for that will review. You may want to specify or create a forenote in the guide that it uses the new editor. I am looking to DIY this so partners are out of the question for the moment. Is there a comprehensive guide for the new editor, particularly 1) with feature comparison or update comparison between old editor and 2) particular with retrieving the data-tags to reference collections? 

Hey @KuyaEddie,

The Solution Recipe was actually published on August 17, 2021 which proceeds when our new template editor was available. All screenshots shown in the guide is using Klaviyo’s classic editor. In addition, all functions highlighted in the Recipe can be implemented using both the classic and new editors as the core function stayed the same between the two. 

With the launch of Klaviyo’s new editor we also have a slew of newly published Help Center articles that go over the similar usages but referencing specifically to the new editor. You can find these article by searching “new editor” within the Klaviyo Help Center. I’ve also listed out a few below for your convenience:

• Guide to the Email Template Editor (new editor)
• Guide to Template Tags and Variable Syntax (new editor)
• How to Build Dynamic Blocks in a Flow Email (new editor)
• How to Access Klaviyo's New Email Template Editor

To retrieve the data-tags to reference your collections, I would suggest reading up on @walid.bendris’s point under the Preview Objects section which i’ve highlighted below. Here, he explains how to print a list of the available fields pertaining to the object which you can use to identify the field you want to reference the collections.

There are a few data objects being used in the examples below but we won’t go into detail about all of the existing data on each of these objects. Instead, you can preview the available data by just printing out that object on the template itself after it’s initialized. For example, if you want to see all of the available fields on the catalog_item initialized by a Catalog Lookup, you can print it out in a template by adding the tag:

{{ catalog_item }}

by itself within that Catalog Lookup scope (i.e. between the {% catalog %)and {% endcatalog %}tags). After adding this tag, save the block and preview it to see a full list of available fields for that object.

David