Skip to main content
Solved

Brick and Mortar Retailer / Integration in Klaviyo

  • March 5, 2026
  • 3 replies
  • 48 views

Forum|alt.badge.img

We are new to Klaviyo and are a brick and mortar retail chain with 100+ stores. We have been scouring the developer documentation trying to understand how we should properly map our many events and properties that are based around brick and mortar interactions. I have found info on mapping purchases and purchase item events for online orders but what about in-store (also store where the customer purchases more frequently, last purchase store, first purchase store, etc)? I want to ensure I can use as much native Klaviyo functionally as possible without doing custom events that I map to my business needs (I would much rather make my business needs fit to the Klaviyo formats). Any advice or recommendations from other brick and mortar folks would be greatly appreciated!

Best answer by whereisjad

@Vanessa Keefe have you looked at this article: 

https://developers.klaviyo.com/en/docs/guide_to_integrating_a_business_with_brick_and_mortar_locations

 

3 replies

whereisjad
Expert Problem Solver IV
Forum|alt.badge.img+17
  • Expert Problem Solver IV
  • Answer
  • March 5, 2026

Forum|alt.badge.img
  • Author
  • Contributor I
  • March 6, 2026

Yes I had passes this on to my Dev team and they came back asking for more detailed info to map our snowflake fields to. As we have a lot of other information we provide in a placed order (store number, store name, brand of store (we have several sister brands we run and you can be customers of both of them), whether an item is reg price or sale, if a promotion was use and the offer, if a coupon was used and the unique code, etc)


whereisjad
Expert Problem Solver IV
Forum|alt.badge.img+17
  • Expert Problem Solver IV
  • March 6, 2026

@Vanessa Keefe you are not going to find a guide specific to how things are structured in Snowflake but the Klaviyo properties model is very flexible, the example properties from the link shared don’t have to be followed verbatim.  You can define properties according to your business or what is available from Snowflake.  I hope this makes sense.