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?
Best answer by David ToView original
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.
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:
Customer: real time
Catalog: every 8 hours
Thanks for being a part of the Klaviyo Community!
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.
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
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.
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:
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?
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.
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?
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 !!
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
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.
@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!