RÜGAMER & STEINER · FLOW CHECKLIST
Freely usable template for Klaviyo flows · Last updated: 5 October 2026
https://www.ruegamer-steiner.de/en/insights/klaviyo-flows/

Copy this for each new flow. Record the test result, test time and evidence.
Work with your own authorised test data; do not include customer data in this file.

FLOW PROFILE
Name / version to be tested:
Customer situation and task:
Responsible / Date:
Shop system and integration:
Trigger / event name actually used in the account:
Trigger filter / profile filter:
Planned re-entry:
Messages, waiting times and branching:
Related flows and potential campaign overlaps:

DATA AND CONTENT
[ ] Triggering event present in the relevant test profile
[ ] Timing, order/product data and integration checked
[ ] sending authorisation checked in the specific setup
[ ] Each message has a distinct purpose
[ ] Personalisation and fallback texts are working
[ ] Product selection, prices, availability and return links checked
[ ] Actual test emails checked on desktop and smartphone
[ ] Contact details, unsubscription and all landing pages checked

CONTROLLED TEST CASES
For each case: document the permitted test profile, event times, expected behaviour,
actual result and appropriate evidence.

[ ] A standard entry leads to the intended path
[ ] A purchase before the next reminder prevents an inappropriate message
[ ] Lack of sending authorisation leads to the expected exclusion
[ ] Unsubscription before a subsequent email is taken into account
[ ] Missing personalisation data displays an appropriate fallback text
[ ] Re-entry follows the defined rules
[ ] Branches with appropriate and inappropriate conditions checked
[ ] Overlaps with other messages deliberately assessed
[ ] Manual/active states and planned changes checked

APPROVAL AND FOLLOW-UP CHECK
Outstanding errors and person responsible:
Reviewed flow version / approval:
Planned start date and first follow-up check:
Recipient activity, skipped messages and errors after launch:
Expected action / metric and its definition:
Measurement period and attribution rules used:
Result and next step:

A single successful test does not cover every recipient scenario. This list
aids documentation; the tests required depend on the specific
integration, flow logic and task.