Hey @wernstrom 

Did the support team get this solved for you? Just so we don't double our efforts, let me know if they got this figured out for you!

It’s in progress. The first issue it looks like it was just because the sync with the catalog is near real-time and the price value changed within a short window a few times.

The second issue is unresolved and the engineering team is looking into it.

Hey @wernstrom 

Im glad that the support team is on this issue and was able to help escalate your second challenge to our engineering team to help solve for you!

I can offer some insights into troubleshooting price drop notification issues. When dealing with price drop notifications in Klaviyo, it's important to review your setup and configurations. Start by confirming that your integration with BigCommerce is properly established, ensuring that the data sync between the platforms is functioning correctly. Next, check the conditions set in your Klaviyo flow for price drop notifications, ensuring that they accurately reflect the criteria for triggering notifications. Double-check the smart sending settings to ensure they align with your expectations. 

Regards and thanks

Hi!

It sounds like there may be a few factors at play here. For the first issue, where the price drop notification was triggered despite returning to the normal price, it could be due to a delay in how BigCommerce updates pricing data in the notification system. Sometimes, recent changes aren't immediately reflected in automated flows.

Regarding the second issue, with other price drop notifications not triggering, it’s possible that smart sending is affecting these sends in ways that aren’t recorded in the "skipped" data, or there could be a delay in syncing price updates. You might also check if any filters or conditions within the automation flow could be impacting these notifications.

Hope this helps!