How to Integrate Klaviyo With Shopify Using Zapier Settings

Connect Shopify to Klaviyo Before Building a Zap

Connect Shopify directly inside Klaviyo before adding any Zapier automation. The native connection should handle the store activity that Klaviyo uses for standard ecommerce flows and reporting.

Use this order:

1. In Klaviyo, open Integrations and select Shopify.
2. Complete the Shopify authorization and installation steps for the store.
3. Confirm that Shopify customer and order activity appears on Klaviyo profiles.
4. Review existing Klaviyo flows that use Shopify activity, including welcome, abandoned cart, and post-purchase flows.
5. Add a Zap only when the workflow requires data or a condition outside that native connection.

This setup prevents a common problem: sending the same purchase data through both Shopify and Zapier. Duplicate order events can trigger two post-purchase flows, inflate reporting, and make customer segments unreliable.

Klaviyo should own normal store behavior. Zapier should send a separate custom event or update a focused profile property for a defined business process.

For example, Zapier can send a Wholesale Application Approved event after a Shopify customer receives a wholesale tag. It should not create another version of Klaviyo’s purchase activity for every order.

Use the Right Connection for the Job

The native Shopify connection is for ongoing store synchronization. A Zap is for a narrow handoff with a clear trigger and outcome.

A Zap should describe one business event in plain language. For example:

When a paid Shopify order belongs to a wholesale customer, send Klaviyo a Wholesale Order Paid event with the order ID, order number, total, currency, and fulfillment status.

That is easier to build, test, and maintain than a large automation that tries to replace Shopify’s full connection to Klaviyo.

Build One Focused Shopify-to-Klaviyo Zap

Start with the simplest version of the workflow. Extra paths, formatters, searches, and updates can be added later only when they serve a real part of the process.

1. Choose the Shopify trigger that matches the event

The trigger should reflect the moment the workflow should begin.

Use a paid-order trigger when the Klaviyo event should happen only after payment is complete. Use an order-created trigger when the process begins at order creation, such as an internal review or a status process that happens before payment.

Those are not interchangeable.

A broad order trigger can include orders that are unpaid, canceled, or handled through manual payment methods. If the email or profile update is tied to a completed purchase, triggering it too early can start the wrong Klaviyo flow.

2. Add a filter before Klaviyo receives anything

Filters keep incomplete or irrelevant Shopify records out of Klaviyo.

Useful filter conditions include:

• The customer email is not blank.
• The order has the required payment status.
• The customer has a specific tag.
• The order has a specific fulfillment status.
• The event matches the internal condition that the automation is meant to handle.

For example, a wholesale workflow may need both a paid order and a wholesale customer tag. Without those filters, every order can enter an automation intended for a smaller group.

3. Send a custom Klaviyo event or update a profile field

Choose one outcome for the first version of the Zap:

• Send a custom event that starts a Klaviyo flow.
• Update a profile property used for segmentation or personalization.

Use a custom event when the workflow is tied to something that happened at a particular time, such as approval, payment, fulfillment, or a special order condition.

Use a profile property when Klaviyo needs to retain an ongoing customer attribute, such as an account type or internal status.

Keep custom event names specific. Wholesale Order Paid is much clearer than Order Update, especially when someone reviews the account months later.

Do not name a Zapier event Placed Order, Started Checkout, or another metric that the native Shopify integration already uses. Separate names keep reporting cleaner and make it easier to see why a flow fired.

4. Map stable Shopify identifiers

Map fields that help Klaviyo identify the customer and connect the event to the right order.

For customer and order workflows, use stable identifiers such as:

• Shopify customer ID
• Shopify order ID
• Order number
• Email address
• Currency
• Order total
• Payment status
• Fulfillment status
• Product IDs or SKUs when the automation is product-specific

The email address is especially important for Shopify customer workflows. Add a filter that stops the Zap when the email is blank.

Avoid building important conditions around product titles alone. Product titles can change, while IDs and SKUs are more stable references.

5. Test the record in Klaviyo, not just Zapier

A successful Zap run only shows that Zapier completed its steps. It does not prove that the Klaviyo flow received the right event or that the flow conditions match the data sent.

After testing, open the relevant Klaviyo profile and inspect:

• The event name
• Event timestamp
• Event properties
• Profile fields that were updated
• Shopify order ID and customer ID
• Related Klaviyo flow activity

The flow should fire once. If it fires twice, look for overlapping native Shopify events, duplicate Zap steps, or a flow trigger that is too broad.

Keep Zapier Task Use Under Control

Zapier adds another system to maintain, and every action step adds to task use. Plan for that before the workflow becomes busy.

A simple estimate is:

Monthly qualifying events × action steps = estimated task volume

For example, 2,000 qualifying orders per month with two action steps creates roughly 4,000 actions before extra branches or retries.

Filters help in two ways: they keep irrelevant contacts out of Klaviyo and reduce task use. A filter that stops non-wholesale orders, unpaid orders, or records without an email prevents the Zap from spending actions on activity that should not enter the workflow.

Keep the Zap small when volume is low:

• Under 100 qualifying events per month: Use a simple Zap and review it monthly.
• 100 to 1,000 qualifying events per month: Keep a written record of the trigger, filters, fields, and Klaviyo flow. Test edge cases after Shopify changes.
• Over 1,000 qualifying events per month: Keep standard ecommerce activity in the native integration and reserve Zapier for high-value exceptions.

More Zapier capacity suits a workflow that supports important account actions, such as approved wholesale accounts, subscription exceptions, or a service message tied to a specific order condition. It does not solve the problem of duplicated Shopify metrics.

Keep Consent Separate From Profile Updates

Creating or updating a Klaviyo profile is not the same as getting permission to send marketing messages.

A Zap can send customer details or operational events to Klaviyo without making that person subscribed to email or SMS. Marketing consent should stay tied to an approved consent process, such as Shopify’s marketing opt-in collection or a Klaviyo signup form with clear channel consent.

This matters most when a Zap uses a Shopify order or customer trigger. A customer may need an operational update associated with their order without having opted in to promotional messaging.

Keep subscription logic separate from profile creation. Do not use Zapier to add every Shopify customer to a Klaviyo marketing list.

Review Each Live Zap Every 90 Days

Zapier workflows can remain active even when the information they send has changed. A renamed Shopify tag, changed fulfillment process, blank email field, or altered order property can quietly send the wrong data into Klaviyo.

Review active Zaps every 90 days and after changes to Shopify apps, checkout processes, or fulfillment workflows.

Keep a short record for each Zap:

• Shopify trigger
• Filter conditions
• Klaviyo action
• Custom event name or profile property
• Required fields
• Shopify customer ID and order ID fields
• Klaviyo flow that uses the event
• Person responsible for reviewing errors and task use

Clear documentation makes it easier to spot overlap. If a flow starts from Wholesale Order Paid, anyone managing the account can see that it is a custom order event rather than a native Shopify purchase metric.

When Zapier Is the Wrong Tool

Skip Zapier when Klaviyo’s Shopify integration already covers the job or when the workflow needs complex, high-volume data handling.

Abandoned cart and browse abandonment belong in Klaviyo’s native Shopify setup. Those flows rely on ecommerce behavior, event timing, catalog data, and consent-aware messaging. A basic Zapier order trigger does not provide the same structure.

Use a direct API-based approach when the workflow requires precise event control, custom data models, or extensive two-way system logic. That route needs technical ownership and ongoing documentation, but it avoids forcing a complex process through a long chain of Zap steps.

Use another route when:

• You need to backfill a large amount of historical store activity.
• You need several data lookups and branching decisions for every order.
• You need a two-way sync between Shopify and Klaviyo.
• The Zap would recreate native Shopify metrics.
• The workflow handles sensitive customer data that should not pass through unnecessary systems.

Zapier is most useful as a connector for a bounded task. It is not a replacement ecommerce data layer.

Before You Turn the Zap On

Run through this list before publishing:

• Klaviyo’s direct Shopify integration is connected and receiving standard store activity.
• The Zap handles a workflow that the native integration does not cover.
• The Shopify trigger matches the actual business event.
• A filter stops blank emails and non-qualifying records.
• The Klaviyo event name is distinct from native Shopify metrics.
• Shopify order ID and customer ID are mapped where relevant.
• Marketing consent is handled separately from profile creation.
• The test record produced the expected Klaviyo profile data and event properties.
• The related Klaviyo flow fired once.
• Someone is responsible for reviewing Zap errors and task use.

Common Setup Mistakes

Recreating native order events

Using Zapier to send another purchase event creates duplicate data. This can trigger duplicate post-purchase sequences and make revenue reporting harder to interpret.

Keep native Shopify metrics in the direct Klaviyo integration. Give Zapier-created events their own names and purposes.

Using a trigger that is too broad

“New Order” and “New Paid Order” represent different points in the order process. Choose the one that matches the message or update you intend to send.

For purchase-related automation, sending an event before payment can create confusion for customers and staff.

Leaving out the filter

A Zap without filters can send every order, customer, or tag change into a workflow built for a specific condition. Filters should block blank email addresses, unsuitable payment statuses, and records that do not match the intended segment.

Treating a completed Zap run as a completed setup

The final check happens in Klaviyo. Inspect the profile, event properties, and flow activity after each test. A Zap can run successfully while sending an event name or field value that does not meet the flow’s trigger conditions.

FAQ

Does Zapier replace the Klaviyo Shopify integration?

No. Use Klaviyo’s direct Shopify integration for core store and ecommerce activity. Use Zapier for isolated custom workflows, such as acting on a special customer tag or sending a custom operational event.

Should I use Shopify New Order or New Paid Order in Zapier?

Use New Paid Order when the Klaviyo event should happen only after payment is complete. Use New Order when the workflow needs to begin when the order is created, such as an internal review or an order-status process before payment.

How do I prevent duplicate Klaviyo events?

Keep native Shopify metrics and Zapier-created events separate. Do not send a Zapier event named Placed Order when the Shopify integration already sends purchase activity. Use a specific custom event name and include the Shopify order ID in the event properties.

Does creating a Klaviyo profile through Zapier subscribe someone to marketing?

No. Profile creation and marketing consent are separate. Promotional email or SMS should be sent only when the customer has provided valid consent for that channel.

How much Zapier capacity does a Shopify-to-Klaviyo workflow need?

Estimate task use by multiplying qualifying monthly events by the number of action steps. A workflow with 500 qualifying orders and two actions requires roughly 1,000 actions per month before additional paths or retries.