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

    July 24, 2021

    Anybody else not buying it? My staff would never promise something with no timeline. 

    Contributor I
    July 26, 2021

    I just signed up with a paid plan only to find out that something so basic is missing.  I thought Klaviyo was a superior product but it seems like they don’t cater for something so simple.  

     

    Please get this feature in as soon as possible otherwise I’m better off saving my money and using Shopify Email.

    July 26, 2021

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

    David To
    Klaviyo Employee
    David ToAnswer
    Klaviyo Employee
    July 29, 2021

    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

    David To
    Klaviyo Employee
    Klaviyo Employee
    August 17, 2021

    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

    Contributor I
    August 27, 2021

    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.

    David To
    Klaviyo Employee
    Klaviyo Employee
    August 27, 2021

    Hey @stouchette,

    Appreciate you sharing your feedback pertaining to including an additional Compare at Price field within the Klaviyo Product Block! 

    To address your concern surrounding the possibility of @walid.bendris’s custom product block block solution mentioned in the Solution Recipe displaying an outdated price; because you are using a Shopify integration, the catalog would actually be updated in real time. This would result in the custom product block you have built referencing your Shopify catalog in real-time pulling in the most up to date pricing. Once built, this custom product block would act the same way as the native product block Klaviyo offers within its template builder. 

    You can find a chart pertaining to a number of Klaviyo integrations and how often they sync from the How Often Integrations Sync Help Center article. For your convenience, I’ve also included the chart pertaining specifically to ecommerce integrations and what comes through as part of the sync and how frequent the syncs occur below:

    Ecommerce Type What syncs How often it runs
    Shift4Shop (formerly 3dcart) Ecommerce Order, and catalog, and customer data every hour
    BigCommerce Ecommerce Order, and catalog, and customer data real time
    Magento 1 Ecommerce Order, and catalog, and customer data every 30 minutes
    Magento 2 Ecommerce Order, and catalog, and customer data every 30 minutes
    OpenCart Ecommerce Order and customer data every hour
    PrestaShop Ecommerce Order, and catalog, and customer data Transactional: every 30 minutes
    Customer: real time
    Salesforce Commerce Cloud Ecommerce Order, and catalog, and customer data Orders & customers: every hour
    Catalog: every 8 hours
    Shopify Ecommerce Order, and catalog, and customer data real time
    Spree Ecommerce Order, and catalog, and customer data every hour
    Woocommerce Ecommerce Order, and catalog, and customer data real time

     

    Thanks for being a part of the Klaviyo Community!

    David

    Contributor I
    October 28, 2021

    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. 

    David To
    Klaviyo Employee
    Klaviyo Employee
    October 28, 2021

    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

     

    Contributor I
    October 30, 2021

    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?