Klaviyo Abandoned Cart Flow Setup

Service Scope

Klaviyo Abandoned Cart Flow Setup is a fixed-scope automation service for one business, one Klaviyo account, one connected e-commerce store, and one abandoned cart flow containing up to three automated emails.

The service includes one supported cart-abandonment trigger, purchase-based exclusions, dynamic cart content, fixed time delays, limited conditional logic, testing, activation, and implementation handoff.

The connected store and Klaviyo integration must already be installed and transmitting the required customer, checkout, cart, and purchase data.

Review the E-commerce Integration

We review one existing connection between Klaviyo and a supported e-commerce store.

The review confirms whether the account visibly receives the events required for the approved flow, which may include:

• Started Checkout
• Added to Cart
• Placed Order
• Product information
• Cart or checkout details
• Customer profile information
• Checkout or cart URL

The review does not include installing the integration, reconnecting a broken store, repairing data synchronization, editing the checkout, rebuilding a product catalog, or developing custom tracking events.

Validate the Required Metrics

We confirm that Klaviyo has received recent examples of the selected abandonment event and the corresponding purchase event.

The flow requires:

• One supported entry event
• Sufficient cart or checkout data
• A functioning purchase event
• Identifiable customer profiles
• Usable product or cart information
• A working destination for returning to the cart or checkout

If the required data is missing, malformed, or not synchronized, flow production may pause until the integration is corrected.

Select One Abandonment Trigger

The service includes one supported flow trigger:

• Started Checkout, or
• Added to Cart

Started Checkout is commonly used because the shopper has progressed into checkout and supplied identifying information.

For eligible Shopify stores, Added to Cart may be available when the Klaviyo app embed and behavioral-event tracking are properly enabled. This trigger reaches shoppers earlier but depends on identifiable onsite activity.

Only one entry trigger is included. Separate Started Checkout and Added to Cart flows require separate services.

Configure the Purchase-Exclusion Filter

We configure the standard purchase-based exclusion needed to prevent later reminders from continuing after Klaviyo records a qualifying order.

The primary logic generally checks that the profile has placed zero orders since entering the flow.

This condition is reviewed before activation and before each included message where supported.

The effectiveness of the exclusion depends on the store sending accurate and timely order data to Klaviyo. Delayed, missing, duplicated, canceled, or custom order events may affect flow behavior.

Review Contact Eligibility and Consent

We review the approved email-eligibility rules for the abandoned cart flow.

Depending on account data, platform settings, and applicable law, an identifiable shopper may have one of several email-consent statuses.

The client must determine whether the flow should:

• Include only subscribed email profiles
• Include other eligible, non-suppressed profiles where legally permitted
• Apply additional consent filters
• Exclude specified geographic or customer groups

KizilCo does not determine whether implied consent or another legal basis applies to a specific profile, business, or jurisdiction.

Suppressed and unsubscribed profiles remain subject to Klaviyo’s sending restrictions.

Build the Flow Architecture

We build one abandoned cart flow containing up to 12 total components after the trigger.

The included components may consist of:

• Up to three email actions
• Up to three fixed time delays
• Up to two conditional splits
• Up to three supported profile or list update actions
• One additional approved standard component

The exact combination is determined by the approved flow plan and cannot exceed 12 post-trigger components.

Additional paths, messages, triggers, actions, and advanced logic require a separate service.

Configure Abandoned Cart Email One

The first email is configured after one approved delay following the selected abandonment event.

This message may:

• Remind the shopper about the incomplete cart
• Display the products left behind
• Provide a return-to-cart or checkout link
• Restate a key store benefit
• Present customer-support information
• Provide the primary recovery call to action

Klaviyo generally recommends allowing a short period after checkout begins before sending the first reminder. The final timing is approved by the client.

Configure Abandoned Cart Email Two

The second email is configured after the next approved fixed delay.

This message may:

• Reinforce the cart reminder
• Present additional product or service benefits
• Address common purchase concerns
• Highlight shipping or return information
• Include approved social proof
• Repeat the return-to-cart action

The client must provide the final content, policies, claims, prices, and offer information.

Configure Abandoned Cart Email Three

The optional third email is configured after the final approved delay.

This message may:

• Provide a final cart reminder
• Reinforce urgency supported by the client’s actual offer
• Include an approved static incentive
• Highlight customer assistance
• Present a final return-to-cart call to action

False urgency, inaccurate inventory claims, and unsupported expiration language are not added.

A fourth email or separate follow-up sequence is outside the included scope.

Configure Dynamic Cart Content

We configure supported dynamic content using the cart or checkout event data available in Klaviyo.

Depending on the connected platform and event payload, the email may display:

• Product image
• Product name
• Product price
• Quantity
• Variant information
• Product URL
• Cart or checkout URL

The dynamic section is previewed using available event data from the client’s account.

Custom event schemas, custom API data, malformed payload repair, and development of unsupported product variables are not included.

Configure the Return-to-Cart Action

We configure the primary button or link using the supported cart or checkout URL supplied through the event data.

The goal is to return the recipient to the appropriate cart, checkout, or store destination.

Functionality depends on:

• The connected e-commerce platform
• The event used to trigger the flow
• Available checkout or cart data
• Cookie and browser behavior
• Store-session duration
• Platform-specific cart restoration
• The shopper’s device

A permanently preserved cart or identical cart restoration on every device cannot be guaranteed.

Configure Fixed Time Delays

The service includes up to three fixed time delays.

These may include:

• A delay before the first email
• A delay between the first and second emails
• A delay between the second and third emails

Klaviyo currently recommends sending the first standard abandoned-checkout reminder approximately 2–4 hours after checkout begins and a second email approximately 20–48 hours later. Final timing is adjusted to the client’s approved strategy and store activity.

Behavior-based waiting, predictive send timing, extensive timezone branching, and multiple timing experiments are not included.

Configure Conditional Splits

We can configure up to two standard conditional splits using data already available in Klaviyo.

Approved split conditions may distinguish profiles by:

• Existing customer status
• Cart value
• Product or collection
• Email marketing consent
• Customer location
• Available profile property
• Another supported event-data condition

The required information must exist and be consistently available within the selected event or customer profile.

Nested logic systems, multiple parallel journeys, predictive splits, and custom-coded conditions are not included.

Configure Profile or List Actions

The service includes up to three supported profile-property or list actions when required by the approved flow plan.

Actions may include:

• Updating one approved profile property
• Adding an eligible profile to one approved list
• Removing a profile from one approved list
• Applying another standard Klaviyo-supported update

These actions are used only when appropriate and approved.

CRM synchronization, external API calls, webhook development, complex data transformation, and cross-platform automation are not included.

Assemble the Email Content

We place the client’s final approved content into one existing template or standard Klaviyo layout for each included email.

The service includes placement of up to 12 client-provided supporting images across the flow, in addition to product images generated through the dynamic cart block.

Email assembly may include:

• Headlines
• Body copy
• Dynamic product section
• Buttons
• Text links
• Supporting images
• Store benefits
• Social proof
• Contact information
• Footer elements

Copywriting, custom template design, photography, custom illustration, and advanced image editing are not included.

Configure Subject Lines and Preview Text

We configure one approved subject line and one preview-text version for each included email.

The service therefore includes up to:

• Three subject lines
• Three preview-text versions

Multiple alternatives, A/B testing, professional copywriting, and subject-line experimentation packages are not included.

Add Basic Personalization

We can configure basic profile or event personalization when the required data is available.

This may include:

• First name
• Product name
• Cart information
• Another approved standard property

Fallback content is used where practical.

Complex conditional personalization, individualized recommendations, dynamic cross-sells, and custom data transformation require a separate service.

Add a Client-Provided Incentive

An approved static discount code may be placed in one or more emails.

The client must provide:

• Final code
• Discount value
• Expiration information
• Eligible products
• Restrictions
• Destination URL
• Required disclaimer text

Creation of unique dynamic coupons, coupon synchronization, discount strategy, and troubleshooting store promotion rules are not included.

Configure Sender and Tracking Settings

We configure or review the approved:

• Sender name
• Sender email address
• Reply-to address
• Standard open tracking
• Standard click tracking
• UTM tracking
• Smart Sending setting
• Unsubscribe functionality

Sending-domain authentication, DNS changes, attribution consulting, Google Analytics configuration, and custom tracking development are not included.

Preview the Dynamic Emails

Each included email is previewed using available customer and event data from the connected store.

The review covers:

• Dynamic product information
• Product images
• Prices
• Cart or checkout link
• Subject line
• Preview text
• Sender information
• Personalization fallback
• Supporting images
• Buttons and links
• Footer content
• Desktop presentation
• Mobile presentation

Preview accuracy depends on the quality and completeness of the event data already stored in Klaviyo.

Complete a Controlled Store-Action Test

We complete one controlled abandoned-cart test using the client’s functioning store and up to three client-provided test inboxes or profiles.

The test may involve:

• Identifying a test shopper
• Starting an approved cart or checkout action
• Confirming that Klaviyo records the event
• Reviewing flow-trigger eligibility
• Previewing dynamic cart data
• Reviewing the purchase-exclusion logic
• Confirming the prepared email path

The test does not include placing a paid order unless the client independently authorizes and completes that purchase.

One standard correction attempt is included for an in-scope flow configuration issue. Integration or store-data failures require separate technical work.

Complete the Pre-Activation Review

Before activation, we review:

• Entry trigger
• Event source
• Purchase-exclusion filter
• Consent controls
• Flow components
• Time delays
• Conditional splits
• Profile or list actions
• Email content
• Dynamic product block
• Return-to-cart link
• Subject lines and preview text
• Sender information
• Tracking settings
• Test results

The completed flow remains in draft or manual status until written approval is received.

Activate After Written Approval

After the client provides written approval, the included messages and approved flow components are changed to the appropriate live status.

Activation applies only to the approved trigger, flow structure, content, and settings.

Existing profiles are not back-populated into the flow unless separately reviewed, authorized, and purchased as additional work.

Implementation Handoff

The client receives a concise implementation summary identifying:

• Store and integration reviewed
• Trigger selected
• Purchase exclusion configured
• Consent controls applied
• Emails created
• Delays and splits configured
• Dynamic content used
• Test completed
• Activation status
• Known data or platform limitations
• Practical maintenance recommendations

The Klaviyo account, store data, completed flow, supplied content, and associated business assets remain owned and controlled by the client.

Client Requirements

Before work begins, the client must provide:

• Klaviyo administrator access
• Appropriate e-commerce administrator access when needed for testing
• One functioning store integration
• Working cart or checkout events
• Working purchase events
• Recent testable event data
• Final approved copy for up to three emails
• One existing template or usable brand assets
• Up to 12 supporting images
• Destination URLs
• Approved sender information
• Approved consent instructions
• Approved delay and split logic
• Any static discount code and conditions
• Up to three test profiles or inboxes
• Timely consolidated feedback
• Written approval before activation

Work begins after all required access, data, materials, and instructions are received.

Delivery and Revisions

Standard delivery is 10–15 business days after all required access, content, data, and instructions are received.

Two consolidated revision rounds are included when submitted within seven days of the corresponding delivery and remain within the approved structure and original quantities.

Integration failures, missing metrics, incomplete event data, store changes, or delayed approvals may extend the completion time.

Important Scope Boundaries

The following are not included:

• Klaviyo subscription or sending fees
• E-commerce integration installation
• Multiple stores
• More than one abandoned cart flow
• More than one entry trigger
• More than three automated emails
• More than 12 post-trigger components
• More than three time delays
• More than two conditional splits
• More than three profile or list actions
• Custom event or API development
• Store, catalog, checkout, or data repair
• Separate Added to Cart and Started Checkout flows
• Browse-abandonment automation
• Multiple currencies or storefront-specific paths
• Dynamic or unique coupon development
• Advanced product recommendations
• SMS, push, or multichannel messages
• Custom email-template design
• Custom HTML development
• Email copywriting
• Historical-profile enrollment
• Sending-domain authentication
• A/B testing
• Google Analytics configuration
• Transactional email setup
• Ongoing monitoring or optimization
• Post-launch performance reporting
• Legal or regulatory compliance review
• Guaranteed recovery, conversion, delivery, or revenue results