Skip to main content
Contributor I
December 1, 2020
Solved

How to display product regular price and discounted price in the product block in Klaviyo?

  • December 1, 2020
  • 38 replies
  • 16803 views

Hello,

In my email content in Klaviyo, I added a product block into the email. Right now i can link the products either from the feed or from the catalog. It shows the products ok with only 1 product price. I would like it to show 2 product prices, one is for regular price with a strike across it and the second one is the discounted price . I can’t seem to figure this out or if Klaviyo even support it. Anyone here know how to do this or if you know this is even possible in Klaviyo?

 

Thanks

 

    This topic has been closed for replies.
    Best answer by David To

    Hello @Oyivalk@Drewseph and @LeightonS , 

    At present, Klaviyo’s product block does not support displaying more than one price, such as a product’s original price and its current sales price. As mentioned by @Julia.LiMarzi in this thread, the most common work around to this would be manually updating the price of the native product block to reflect the product’s sales price or adding a column block under the product block to manually display a secondary price. A YouTube video posted recently that highlighted how to put this strategy into action can be found here: https://www.youtube.com/watch?v=VMjrJ193iJ8&t=154s 

    If you are code-savvy, an additional solution available would be using a series of Django tags and Klaviyo’s Catalog Lookup function to custom code your own product block. Through using a Text block, you can custom code and simulate a native Klaviyo product block off your own design to reference any of your product’s properties including a regular and sales price field. Some resources I would suggest using to build this are the Django Documentation, Overview of the Catalog Lookup Tag, and Template Tags and Variable Syntax Help Center articles. You may also want to work with your template designer or finding one from one of our many partner agencies to further help you custom build this function.

    As another note, if you wanted to display a sales price in addition to a product’s regular price within a flow email which utilizes a dynamic table block; I would suggest reviewing if these two properties are being synced from the event used to trigger your flow. If both a sales price and the regular price are being shared, you can dynamically reference the variable tags for these properties to display within your emails. Here’s some refreshers on using and customizing dynamic table blocks: 

    This would further allow you to use the suggestion mentioned by @Paul S of using a strike through for your regular price tag <s> {{ whatever the price tag is }} <s> followed by including the tag to reference your sales price next to it or below it.

    Since this threads surrounds an interest in highlighting a price drop, in case you may have missed Klaviyo’s most recent KPE event, I’ve included a summary of the event below. I bring this up because one of the exciting new feature releases during this event was a Price Drop Flow Trigger!

    Thank you for being Klaviyo Community members!

    David

    38 replies

    Contributor I
    October 30, 2021

    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. 

    David To
    Klaviyo Employee
    Klaviyo Employee
    November 1, 2021

    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

    Contributor I
    November 2, 2021

    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? 

    David To
    Klaviyo Employee
    Klaviyo Employee
    November 2, 2021

    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:

     

    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

     

    Contributor I
    November 5, 2021

    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?

    Contributor I
    November 7, 2021

    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 !! 

    Contributor I
    November 9, 2021

    @david.to I’m still trying to use https://medium.com/solutions-klaviyo/solution-recipe-4-extending-klaviyos-product-block-functionality-7cea60ae9cda

    To get my head around the code and functions. I’ve pored over that article word by word and there’s just some assumed knowledge and jargon that is a road block. And “going to a partner” for this just isn’t an option. 

     

    My main goal is to be able to use that code to be able to manually retrieve data from my catalogue that I’ve fed to Klaviyo using an XML feed. Which I’ve been told is possible. 

     

    In that article above, I draw blanks at 

    Use a lookup on product_feed to get the ID of the first item, then use that ID to look up the same item in the Catalog using a Catalog Lookup and pull that item’s name into the HTML table. If you preview the template now, you should be able to see the name of the first item in the selected Product Feed.

     

    I’m sorry what? Lookup on product_feed? How do you mean lookup. Manually? Is there a process? Am I setting up the catalogue/product feeds wrong? I’ve even followed the links around to get an animated step by step to find the catalogue.item** info but it just gives me a broken link even if I follow exactly what’s shown. 

    It’s a struggle to begin with and I’m desperate to get through this but the articles don’t really help unless there’s some knowledge there. It should really link back and keep linking back till it gets to the basic steps then you can build forward there.

     

    I’ve asked support for assistance with this but still no reply. 

     

    {% with columns=3 product_feed=feeds.ExampleProductFeed|slice:":6" %}
    <table>
    <tbody>
    <tr>{% for item in product_feed %}
    <td>{% catalog item.item_id %}
    <table>
    <tbody>
    <tr>
    <th><a href="{{ catalog_item.url }}"><img alt="{{ catalog_item.title }}" src="{{ catalog_item.featured_image.thumbnail.src }}" /> </a></th>
    </tr>
    <tr>
    <th>{{ catalog_item.title }}</th>
    </tr>
    <tr>
    <td><p>{% currency_format catalog_item.metadata|lookup:"$price"|floatformat:2 %}</p></td>
    </tr>
    <tr>
    <td>
    <p><a href="{{ catalog_item.url }}">Buy Now</a></p>
    </td>
    </tr>
    </tbody>
    </table>
    {% endcatalog %}</td>
    {% if forloop.counter|divisibleby:columns %}</tr><tr>{% endif %}
    {% endfor %}</tr>
    </tbody>
    </table>
    {% endwith %}

     

    David To
    Klaviyo Employee
    Klaviyo Employee
    November 9, 2021

    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