Contributor IV

Solved

Back In Stock Notification for only one Shopify Location

Forum|Forum|4 years ago
September 16, 2021
23 replies
2483 views

We have back in stock notifications set up with our Shopify store but we have multiple store locations where inventory is tracked.

We have an Online store (where online orders are fulfilled) and a retail store where inventory is separated for retail.

I noticed that when we marked a product in stock at our retail location (that we didn’t want to restock at our online location) a customer was alerted. (They went to the product page and it was still listed as sold out).

Is there a way I can only alert people when something is restocked at our online store location. I imagine this can be a dynamic event variable on the product detail in the code.

For example, similar to variant URL (below) there could be one for “Location”.

Thanks so much for your help! :)

Variant URL

{% catalog event.VariantId integration='shopify' %}{{ catalog_item.url }}?variant={{ catalog_item.variant.id }}{% endcatalog %}

Flows

Best answer by Dov

Hello @Nikki,

At this time, Klaviyo does not offer the ability to differentiate between locations when using Klaviyo's pre-built Back in Stock option for Shopify. The only way to achieve this would be to create two separate Klaviyo accounts (one for the physical store and one for retail store) and connect a unique Shopify URL (store) to each Klaviyo account and run each independently with their own respective Back in Stock flows.

That said, the ability for Klaviyo to distinguish between location-based inventory for Back in Stock is a previously requested feature and I have added your insight to our existing feature request.

We appreciate your patience and understanding with the current limitations. In the meantime, as another alternative, you can consider incorporating elements of the custom Back in Stock abilities outlined here: Shopify Back in Stock for Developers. If you’d like assistance with this, I recommend reaching out to one of our partners.

Thank you and have a great weekend.

Show previous replies

L

LRotherfield

Contributor I

Thanks for the response @stephen.trumble

Just so I understand correctly, how exactly does the “back in stock delay” trigger? I can see several options:

Does it poll the product and if the product has stock greater than the threshold then the delay triggers?
Does it trigger when the stock goes from below the threshold to above it, i.e if the stock is currently above the threshold then the delay will not trigger until it drops below and then comes back above the threshold?
Does it trigger whenever stock is added to the item and the total stock is greater than the threshold?

Or is there another way it calculates when to trigger?

Thanks again

Luke

stephen.trumble

Klaviyo Alum

Hey @LRotherfield,

Another great question!

The Back in Stock Delay is configurable on the account level. So it will depend on what you or someone else on your account has set up for how it will trigger. Here is a typical example, the delay is based on a minimum number of units that are restocked and how many subscribers are are “waiting” for the back in stock notification.

Check out the Help Center doc on back in stock notification settings Hope this helps!

-Stephen

L

LRotherfield

Contributor I

Thanks @stephen.trumble

Hopefully just one final question:

When the back in stock delay triggers, does it fetch all the product data at that point in time or does it use cached data for the product’s tags?

I ask because I want to implement your above solution so have written a Shopify flow that tags products as in/out of stock dependent on the website location stock location. This happens on inventory update, however there is a short delay while the flow runs, so if you use cached data or grab the data before the flow runs then the tag won’t exist.

Ultimately, If I put in a 5 minute delay after the back in stock delay and before the trigger split, will the trigger split refetch the product data?

I hope that makes sense

Kind Regards

Luke

L

LRotherfield

Contributor I

Depending on how often you restock your products, you can add a Time Delay for X number of days and then add another conditional split so the profiles in the flow will be reevaluated again if their product is back in stock. Adding the additional time delay and subsequent conditional splits will allow you to keep profiles in the flow longer until you have their product back in stock.

Do you mean something like this (ignore the value of the trigger split, that will be product tags that determine stock status)?:

N

NaokiKE

Contributor I

Hi @stephen.trumble do we have an update on above, it has been a year since @alex.hong confirmed that this issue was being looked at and that Klaviyo has had prior request to implement this? Thanks

stephen.trumble

Klaviyo Alum

Hey @LRotherfield

Thanks for the follow up! Klaviyo evaluates product inventory each step of the flow and should be updating in real time for the most updated information. Your solution looks great! It will recheck daily to see if the product has been restocked while allowing the profile to stay in the flow without exiting immediately.

@NaokiKE Our product team has not implemented any changes to this at this time. However, I will send a follow up feature request on your behalf. I know how important having the right tools can be to help drive business and will make sure to share your feedback with the product team.

Thank you both for helping make the community and Klaviyo better everyday!

-Stephen

A

AlexColorz

Contributor I

Hello, any update on this feature?

S

supportatnewtheory.is

Contributor I

@stephen.trumble ,

For my clarification. If there are multiple locations set up but only 1 location is set to “Fulfill online orders from this location”, the Back In Stock email will send when any location receives stock?

Thanks,
Thomas

A

anthonyfinix-joola

Contributor I

we saw this app which i think does the job https://apps.shopify.com/customer-back-in-stock-alert-user-notification-app

Is there any update on the feature implementation ? we have also met with the same roadblock and in search of a custom solution

N