Verify three things before switching a flow on: the right Shopify event reached the right Klaviyo profile, the profile is eligible for the message, and only the intended automation will send it.
A public scan may find a Klaviyo script or form. It cannot confirm the account, list, consent, flow filters or order data. Use the test plan below on a store and account you manage, with controlled profiles and no real customer sends.
1. Verify the integration and event source
In Klaviyo, confirm the connected store and the source of the metric, not just the name. Two integrations can emit similarly named events, and a flow copied from another platform may still point to the old metric. Check that the test profile's activity contains the expected event and properties. Refer to Klaviyo's Shopify data reference for the distinction between onsite and Shopify integration events.
2. Test one profile that should enter and one that should not
Welcome
Subscribe a new test profile and confirm the intended list, channel and permission state. Check that a profile without the required consent does not receive the marketing welcome.
Checkout recovery
Start checkout with one approved test profile and stop. Use a second profile to complete checkout before the recovery message. Check entry for the first and purchase exclusion for the second.
Post-purchase
Place an approved test order and verify the Shopify order metric, items and message timing. Check exclusions for the order types or states your flow should not target.
Use Klaviyo's metric-triggered flow troubleshooting to tell an event-source issue from a filter, delay or message status. Keep customer-facing sends off while reviewing examples; use previews or a controlled test audience as appropriate.
3. Check the handoff from old to new automations
- Inventory active messages: compare Shopify automations, existing Klaviyo flows and any previous provider. Mark the ones being replaced; distinguish recovery messages from order confirmations and other operational messages.
- Keep permissions intact: preserve unsubscribe and suppression states when moving lists. Do not treat the existence of a customer profile as permission for marketing.
- Test the content: check the destination of links, locale, fallback for missing data, mobile email rendering and the sender. Confirm the checkout link restores the intended session in the recovery scenario.
- Launch one workflow at a time: record which messages are active and monitor skipped or duplicate sends. Document who can pause the change if real sends diverge from the approved test.
When the issue is bigger than a missing script
If the work spans an account migration, list hygiene and multiple lifecycle flows, see Migraciones.io's Shopify email marketing and Klaviyo integration service (in Spanish). If you are deciding between providers first, compare Shopify marketing apps by workflow rather than storefront visibility.
Editorial note: Detectify features Migraciones.io as a service provider. These references do not affect app matches or confidence labels.