Back in Stock Button @Homepage / "Featured Product"-Section [Shopify]
Hello!
We are running a shop with only one product.
Our customers can buy the product directly on the homepage ( luredrop.de )
We have implemented the “back in stock” feature + flow, which works fine on the product-page of or product. (example here).
Now my problem: we are not sending our users to the product page, but to the homepage. On the homepage the product is integrated as a “featured product”. At this location, the “out of stock”-button is not shown up, when the stock is at 0.
Is there any solution, to integrate the “back in stock”-feature at the homepage?
kindly regards!
Page 1 / 1
Hi @nougatfalte,
For this you will need a developer to work in the templates and make sure that whenever the out of stock button appears or if a specific event happens the Back in stock button is triggered and shown. I've not done this myself yet but I think having the default buttons and functionality that normally show on the productpages should be present. Don't forget to also check: https://help.klaviyo.com/hc/en-us/articles/360001895651 and https://help.klaviyo.com/hc/en-us/articles/360001894192
We help with e-commerce growth through CRO, Klaviyo and CVO
Hello @Omar, This is an excerpt of the site.js to be integrated by Klavio. This will also be included on the start page. I think the problem is that I am not triggering any of the "createXYZTrigger()" functions, as it is neither a product nor a collection.
I can't extend the code in site.js to allow the creation of a trigger on the home page, as far as I know, can I?
Unfortunately, my problem is not addressed in the URLs you sent.
"Are you sure that the BIS code is also loading on the homepage?" --> yes, I debugged it on the homepage via the browser. So I know that the code is definitely executed.
"Does the product on the homepage go out of stock or show a different message or button when it's out of stock?" --> yes
We help with e-commerce growth through CRO, Klaviyo and CVO
Hello!
Just in case someone else stumbled upon this, the simple solution for our theme was this answer from a previous post along with changing the the line `collection_urls: "/collections/"]` to `collection_urls: :"/"]` so that it applies to all pages rather than only the collection page.
