Can you create a trigger flow for multiple purchase at a POS location?

unfortunately not, still waiting … 

@alex.hong Any update on providing location with Placed Order? Thanks!

Hi there @Happy Camper,

Currently there is not a way to utilize this data to segment on. What I can do is submit this request to our team again. However, I wouldn't have insight on a timeline/guarantees on delivery or consideration. I do believe a strong case can be made here, as this is a top level datapoint in the Order payload and the benefits are numerous in unlocking this for you (and other customers).
A potential workaround here would be to see if you are able to set a unique 'Source Name' for each POS location that would pass with the (POS) Order Event. If possible, we would be able to segment on that data. 

In regards to this strategy, from what I've seen on our end, we actually would advise to reach out to Shopify to ask: 
 

• How can we add Location ID for Placed Orders via POS?
• Is it possible to add additional Source Names to correspond with your different store locations - and their POS instance?

I did also see a possible workaround utilizing Shopify Flow to Automate tagging your orders, though since this would be setup within Shopify, might also be a nice question to ask in addition to the above.

Typically customers Segmenting with POS specifically, are only segmenting on the Top Level data (was it POS or Web) vs drilling into specific Location. 

Apologies for the inconvenience, 

Alex

Thanks Alex. It sounds like the location info is not passed from Shopify to Klaviyo. Is that correct?

I can think of so many use cases for brick and mortar stores where we’ll want to segment based on where the customer purchased. 

In any case, thanks again for your insight!

Hi @Happy Camper,

If you're a Shopify POS customer, you may want to distinguish between your POS and web purchases.

Klaviyo syncs the source_name when a customer completes the checkout process and creates an order in your Shopify store. According to Shopify's documentation, "source_name" is defined as:
 

You can use the following to Segment orders (and purchasers) by source:



This information can be found in our help center: Guide to Differentiating Shopify POS and Shopify Web Data. Currently, the data coming in from Shopify is labeled as (POS) but not specific to what location. Hopefully this can be a native feature to the integration.

Hope that helped,

Alex

@alex.hong your post misses the point of the thread. It’s clear that the source_name can be used to differentiate between web and pos sales, however for multiple location stores all placed order events have the source_name=”pos” so we can’t filter based on multiple locations.

The location_id field stores the location but it isn’t a supported filter option. 

Please address this. Multiple people are asking and it’s clear other platforms support this

Edit: I see you originally did comment on this specific issue, not sure why your last post just mentions pos vs web in response to a question that was about multiple locations.

Also asking people here to pass the buck to Shopify to request they include differentiation of source_name is not helpful. This is clearly a limitation with klaviyo’s filtering since the placed order event (in klaviyo) shows the different location_ids. Fix that and the issue is resolved. Shopify is already uniquely identifying the locations so why would they change the source name. It doesn’t make klaviyo look better by pointing the blame towards another company whose webhook data from me looks extremely coherent.

Hello @ahurlburt,

If it is an absolute for you to want the capability to be segment by an order's POS location, I would imagine instead of using the default Shopify placed order you could custom code a custom Placed Order event that does track this sort of data. Or you could even pass a separate stand alone custom event that records the POS location of where the placed order occurred such event: POS Location with the metadata sharing this information. This would be a way to get this information into the respective systems and tracked as well.

Although it is a current feature request to have more information pulled in from Shopify, we do encourage customers to reach out to both sides as it puts more focus on these sorts of things being in high demand. As I do not work directly with the feature request/product team, I cannot offer an exact timeline but this is something we are working on.

Thanks,

Alex